Since I bought Yamato I have been trying my best to make use of the AMD-V support in the Opterons, this included continuing the fight with VirtualBox to get it to work properly, with Solaris and Fedora, then trying RedHat’s virt-manager and now, after the failure the other day QEmu 0.10 (under Luca’s insistence).
The summary of my current opinions is something like the following:
- VirtualBox is a nice concept but the limitation in the “Open Source Edition” are quite nasty, plus it has huge problems (at least, in the OSE version) with networking under Solaris (which is mind boggling for me since both products are developed by Sun), making it unusable for almost anything in my book; replacing the previously used Linux tun/tap code with its own network modules wasn’t very nice because it reminded me of VMware, and it didn’t solve much in my case;
- RedHat’s virt-manager is a nice idea but it has limitations that are (quite understandably from one point of view) tied with the hardcoding of RedHat style systems; I say quite understandably because I’m not even dreaming to ask RedHat to support other operating systems before they feel their code is absolutely prime-time ready; on the other hand it would be nice if there was better support for Gentoo, maybe with an active branch for it;
- I still don’t like the kqemu approach, so I’m hoping for the support to Linux’s own KVM interface in the next kernel release (2.6.29), but it should be feasible; on the other hand, setting up QEmu (or kvm manually) is quite a task the first time.
So while I’m using VirtualBox to virtualise a Windows XP install (which, alas, I have to use for some work tasks and to offer Windows support to my “customers”) I decided to try QEmu for a FreeBSD (vanilla) virtual system; I needed a vanilla FreeBSD to try a couple of things out, so that was a good choice to start. I was actually impressed by the sheer speed of FreeBSD install in the virtual system even without kqemu or KVM, it indeed took less than on my old test systems. I don’t know if the I/O difference between QEmu and VirtualBox was because VirtualBox uses more complex virtual disk images (with recovery data I expect), or because I set QEmu to work straight on a block device (lvm logical volume); I had, though, to curse a bit to get networking working.
A side on networking; since what I wanted was to be able to interface the virtual machines with the rest of my network transparently, I decided to give a try to
net-misc/vde; unfortunately getting the thing working with that has been more troublesome than expected. For once, if you don’t set up the TAP device explicitly with OpenRC, vde will try to do so for you, but on my system, it put udev in a state that continuously took up and down the interface, quite unusable. Secondly, I had some problem with
dhcpd: even if I set the
DHCPD_IFACE variable in
/etc/conf.d/dhcpd, the init script does not produce proper service dependencies, I have to explicitly set
RC_NEED. In both those case the answer would be “dynamic” dependencies of the scripts, calculating the needed network services based on the settings in the
conf.d files. I guess I should open bugs for those.
Once I finally had the networking support working properly, I set up SSH, connected and started the usual task of basic customisation. The first step for me is always to get
zsh as shell. Not bash because I don’t like bash as a project, I find zsh more useful too. But once it started building
m4, and in particular to test for
strstr() time linearity, the virtual machine was frozen solid; qemu strted taking 100% CPU constantly, and even after half an hour it never moved from there. I aborted the VM and tried again, hoping it was just a glitch, but it’s perfectly reproducible. I don’t know what the problem is with that.
So I decided to give a try to installing Solaris, I created a new logical volume, started up again qemu and .. it is frozen solid during boot from the 2008.11 DVD.
In truth, I’m disappointed because the FreeBSD install really looked promising: fast, nice, not overloading more than a single core (I have eight, I can spare one or two for constantly-running VMs), it also worked fine when running as unprivileged user (my user) after giving it access to the kqemu device and the block device with the virtual disk; it didn’t work as nice with the tun/tap support in qemu itself in this setup since it required root to access the tap device, but at least with vde it reduced the amount of code running unprivileged.
On the other hand, since the KVM and QEmu configuration is basically identical (beside the fact that they emulate different network cards), I just tried again kvm, using the manual configuration I used for QEmu and vde for networking (networking configuration was what made me hope to use virt-manager last time, but now I know I don’t need it); it does seem faster, and it also passed the
strstr() test before. So I guess the winner this round is KVM, and I’ll wait for the next Linux release to test the QEmu+Linux KVM support.
Post Scriptum: even KVM is unable to start the OpenSolaris LiveDVD though, so I wonder if it’s a problem with Solaris itself; I’d like to try the free as in soda version of Solaris 10, but the “Sun Download Manager” does not seem to work with IcedTea6 and downloading that 4GB image with Firefox is masochistic.
During my attempts to install the piece of Sun kvm crashed randomly. Yep, -kernel-qemu doesn’t allow to type jack but works after.
Recently we went through the pain of testin several virtualization implementations to finally stick with kvm. Running kvm vms can be a bit hacky but we managed to make it work on systems that refused anything else.OpenSolaris can be a problem. I’d suggest to try using either an older kvm version or just the newest one. It may also help to try to play with the virtual hw – at one occasion I had a networking problem that was ‘solved’ by not using the ‘qemu networking card’ but rtl8139.
When i tried Solaris in vmware, i couldn’t install it until i set number of cpu’s to one.
What about XEN? It has proven stable for us, once you setup it correctly.So you _could_ try it, if you’re out of options.
I know this is a bit of a late comment, but I hear of people struggling with tun/tap all over where I just use the user mode network stack in qemu with little problem. If you don’t need the guest to listen for anything it’s zero-hassle as far as I can see. Listening is another matter, requiring each port or range of ports to be specified, but it doesn’t seem too bad to me.On the flip side I’m still using qemu 0.9.1 that I installed from source.The strstr time detection bug I can’t speak for, except to say that I’ve heard that a few OSs may actually run faster without kqemu. Perhaps it’s actually a bug in autotools, assuming it will run on physical hardware. 😉