After running into this unresolved bug–domU hangs under heavy I/O (e.g disk) access–I’m done. Bye bye, Xen!
This kind of crap isn’t free like a puppy, that’s free like “I’ll kick you in the nuts for free!”. I’d rather have the puppy.
UPDATE 28-APR-2007:
Jesse Keating also mentioned today at Linuxfest Northwest that the Xen kernel modifications aren’t in the upstream kernel. KVM sounds promising, maybe I’ll check that out next. Heck, QEMU rocks and is probably fast enough for my needs.
At least in Fedora Core 6, if you rename the root filesystem volume group and/or logical volume names, there are a number of cleanup steps that must be performed.
(more…)
My data is important. Enough so that I’ve hemmed and hawed for quite a while over the best automated backup solution. I started out with tar, then moved on to rsync. Now I’m keen to rsnapshot. Here’s a Zod-focused guide to setting it up.
(more…)
I’m using a Fedora Core 6 host and have installed a Fedora Core 6 guest. I’d like to mount the guest’s main disk image, but I can’t get at the data since the guest uses file-backed virtual disks and LVM is used within those disks.
Xen is interesting. Xen is still pretty unstable, but is and continues to become more impressive.
Lesson learned: don’t use LVM in both host and guest. Especially when both are default Fedora Core 6 installs.
I keep seeing “LVM with Xen is a good idea” on mailing lists and even in the user manual. This is probably true where maximum flexibility and control are desired. But freedom has a price: simplicity (and perhaps a little performance). Plain old partitions are simple. I miss ‘em, and I’m going back!
For that matter, I’m sure SELinux is great and all, but there are some gotchas when using it with Xen. For instance, images must be installed into /var/lib/xen/images or something.