Hi, thank you for looking at this.
So you're using initramfs-tools 0.109 with kernel 3.2.0-4-amd64?
Which linux-image-amd64 version exactly?
And which combination of initramfs-tools and linux-image works for
you? Because AFAIK we haven't had any changes in initramfs-tools that
could be responsible for a breakage here.
I investigated some more. After some tests, I found out what happens:
* xen-create-image (from the package "xen-tools") just takes the dom0
kernel and initram and puts them in the domU config file.
* the domU isn't booting as the initram on the dom0 doesn't contain the
necessary xen block device modules. "modules=most" should include, by
description, all the ide/ata/scsi block device drivers, but actually it
doesn't include the xen ones.
* if creating the domU with xen-create-image and specifying "--pygrub",
the domU will self-create an initramfs image and it will contain the
specific modules. And it will perfectly boot.
In the past (Squeeze and before), we needed to install a specific xen
kernel (for dom0 and domU) and the initramfs contained the modules even
on the dom0. After kernel 3.0, it's not needed anymore as xen support is
in the mainline.
Maybe xen-create-image should, by default, create pygrub domUs or
initramfs should include the xen block devices modules when configured,
as default, in "modules=most".
Thank you for your attention,
Stefano
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
