Re: qemu disk-mounting issue on openSUSE

[Colin Walters <walters verbum org>]

On Tue, 2013-01-08 at 04:59 -0500, Michael Hill wrote:
> Below is the qemu command line followed by the last screenful or two
> of output for four different attempts. I get similar results on F18,
> but can still boot today's qemu img with "/dev/vda" using the last
> host kernel I generated (2 Jan).
> 
> Mike
> 
> 
> /dev/vda with kernel vmlinuz-3.4.11-yocto-standard:

Let's forget this kernel existed, honestly =)

> /dev/vda with kernel vmlinuz-3.6.0-gnome-ostree:
> 
> # qemu-kvm -vga vmware -cpu core2duo -M pc-0.15 -kernel
> /boot/ostree/vmlinuz-3.6.0-gnome-ostree -initrd
> /boot/ostree/initramfs-3.6.0-gnome-ostree.img -drive
> file=/ostree/ostree-qemu.img,if=virtio -m 1024M -vga vmware -append
> 'rd.plymouth=0 root=/dev/vda ostree=gnome/current ' -monitor stdio
> 
> (some virtio_blk: Unknown symbol errors)

Hrm...the unknown symbol sounds like the root cause here.  One thing
that could cause this actually is a stale initramfs; at the moment
we're not automatically regenerating it when the kernel changes
unfortunately =/  I think I mentioned something like this on IRC, but
did you try:

$ rm /boot/ostree/initramfs-3.6.0-gnome-ostree.img
$ ostree admin update-kernel gnome-ostree /ostree/deploy/gnome-ostree/current

The latter should
regenerate /boot/ostree/initramfs-3.6.0-gnome-ostree.img .