[Cross-posting to Fedora cloud development list]
On Tue, Mar 18, 2014 at 04:05:42PM -0400, Eric V. Smith wrote:
> I want to use the stock Fedora cloud image,
> Fedora-x86_64-20-20131211.1-sda.raw. Dom0 is also Fedora 20, running the
> Xen kernel. I've yum update'd everything.
> ...
> [ 1.270965] xenbus_probe_frontend: Device with no driver: device/vbd/2048
> [ 1.271019] xenbus_probe_frontend: Device with no driver: device/vbd/2064
> [ 1.271100] xenbus_probe_frontend: Device with no driver: device/vif/0
> [ 1.271178] Magic number: 1:252:3141
> [ 1.271222] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
> [ 1.271323] md: Waiting for all devices to be available before autodetect
> [ 1.271373] md: If you don't use raid, use raid=noautodetect
> [ 1.271504] md: Autodetecting RAID arrays.
> [ 1.271536] md: Scanned 0 and added 0 devices.
> [ 1.271576] md: autorun ...
> [ 1.271604] md: ... autorun DONE.
> [ 1.271671] VFS: Cannot open root device
> "UUID=e78f2b16-8836-4e6a-9e5e-fdc6c9d3cfc3" or unknown-block(0,0): error -6
It isn't obvious from the logs but pygrub isn't parsing the extlinux block
label Fedora-x86_64-20-20131211.1 (3.11.10-301.fc20.x86_64)
kernel /boot/vmlinuz-3.11.10-301.fc20.x86_64
append ro root=UUID=e78f2b16-8836-4e6a-9e5e-fdc6c9d3cfc3 console=tty1
console=ttyS0,115200n8
initrd /boot/initramfs-3.11.10-301.fc20.x86_64.img
as desired as it doesn't seem to understand the initrd line, hence xen tries to
boot the image without the initramfs file and not surprisingly it fails.
Michael Young
_______________________________________________
virt mailing list
virt@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/virt
