I've used the occasion of http://wiki.xen.org/wiki/Hackathon/May2014
learn how Xen is managed, and to start scoping how it can be done within
I've laid out my impressions on http://www.ovirt.org/Xen
; some of it
may false. For example, up until few minutes ago, it stated that Xen is
missing spice support. Feel free to fix it, it's a wiki.
The bottom line is that, with a bit of help, and with limited feature
set, oVirt can manage Xen-based hypervisors. I've posted a couple of
Vdsm tweaks to support that
The nicest patch there is a brute script that munches an oVirt-generated
libvirt domxml and strips it from anything that it finds offensive to
libvirt's xl driver.
The most painful of the things dropped is qcow2 images - I did not find
a way to specify them for Xen domains (admittedly, I did not search too
Another hurdle was my failure to boot the guest from its cdrom. To have
something running in the guest, I copied
onto the VM disk volume.
Plenty of other caveats are listed in
. But hey, it's working!(ish)
I'd like to thank the all nice and helpful people at the Xen hackathon
(too many to mention by name!), who invited me there and helped me debug
numerous failures and misconfigurations.