3 ms·
Have you ever seen a crashed ESX Server with no community support, tons of home-brew utilities with wired command line arguments which throw a bizarre error mes
by c00p3r 16y ago
Have you ever seen a crashed ESX Server with no community support, tons of home-brew utilities with wired command line arguments which throw a bizarre error messages to you that even google know nothing about? I did. ^_^
The idea is about reducing complexity and reusing community-tested solutions, not creating a new layer of complexity with a coded in a rush, badly tested poorly documented closed-source layer.
btw, if I use native lvm I can get a lot of flexibility.
edit: some BS removed.
btw, there is still no x86_64 xen-host for a modern kernels.
- cdavid 16y agoI feel sorry for your experience, it just does not match mine. Note that we are not talking about the same products - I mainly use vmware workstation/player/fusion (I deal a lot with cross platform issues in some medium-size open source projects). Concerning things coded in a rush, I cannot say about vmware, but libvirt and the associated tools certainly are far from mature in my experience, at least for an end user.
- c00p3r 16y agoI had once a system which runs 64-bit FreeBSD, RHEL and Solaris on one Core-Quad box with Fedora 13. It used for testing mostly while FreeBSD instance was used as a Windows VPN server (mpd5) and OpenVPN. Btw, there is an issues with last updates of qemu-kvm in Fedora 13. beware.
- allertonm 16y agoIt was Citrix, not VMWare, that bought XenSource.
- c00p3r 16y agoOh. Thank you. Need more sleep. ^_^
- munchhausen 16y agoESX Server does not have community support, but it has commercial support. If you are tenacious and patient enough to make it past the first tier of support, you will get your crashed server fixed, possibly faster than it would take to wait for an answer on a mailing list.