On Thu, Apr 20, 2006 at 03:54:59PM -0700, Daniel Hiltgen wrote: Yes, that's a known problem when using a whole drive image, the boot arguments are extracted by a python script, and removed once the domain is launched though xm create. Adding the discovery part of pygrub to libvirt itself would be rather nasty, it sounds saner to add it on the domain launching side. yeah, this dynamic extraction of kernel and initrd on the Dom0 is a serious pain. The Xen creation requires kernel and initrd paths interpreted in Dom0 filesystem, while the actual kernel and initrd resources are ultimately available only in the DomU filesystem. You could save the paths statically for example in xenguest-install.py but this could break very easilly. Basically requiring the kernel and initrd files to be present in Dom0 for domain creation is a limitation of Xen paravirt current tools. It's a known mismatch when using xvda images. Fixing it purely in libvirt would force to add some rather hard to maintain code for boot sector and filesystem extraction. Ideally at least from my POV it should be fixed by the creation code when it sees a xvda image. Alternatively libvirt could upon detection of a bootloader argument in the description, try to use that bootloader to get the informations, but this may fail for example by lack of permissions. I don't know yet how to best attack the problem, Daniel -- Daniel Veillard | Red Hat http://redhat.com/ veillard(a)redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/