[fedora-virt] KVM Rawhide machine trouble

Jerry James loganjerry at gmail.com
Wed Sep 23 16:43:40 UTC 2009

I've got a KVM virtual machine running Rawhide inside an F-11 host.
After updating packages on Tuesday, Sept. 22, the machine failed to
reboot.  The initialization sequence reported that mount failed
because it was unable to locate libc.  I was able to boot up in rescue
mode off of a Rawhide install CD image, and a subsequent chroot to
/mnt/sysimage was successful.  There was nothing wrong with the
installed glibc or the installed mount, which made me wonder if this
was a dracut problem.  So I built a new dracut initramfs image and
rebooted.  The boot got farther this time, but still failed.  The
colored bars creep all the way to the right, but at the point where X
should start, the system just hangs.

I found this in the boot messages and wonder if it is significant.
Can anybody interpret this for me and tell if if might have something
to do with my boot trouble?

------------[ cut here ]------------
WARNING: at kernel/trace/ftrace.c:1003 ftrace_bug+0x198/0x27e() (Not tainted)
Hardware name:
Modules linked in: virtio(+)
Pid: 167, comm: modprobe Not tainted 2.6.31-33.fc12.x86_64 #1
Call Trace:
 [<ffffffff810642ec>] warn_slowpath_common+0x95/0xc3
 [<ffffffffa0000660>] ? register_virtio_driver+0x8/0x50 [virtio]
 [<ffffffff81064341>] warn_slowpath_null+0x27/0x3d
 [<ffffffff810d4ace>] ftrace_bug+0x198/0x27e
 [<ffffffffa0000660>] ? register_virtio_driver+0x8/0x50 [virtio]
 [<ffffffff810d5d26>] ftrace_convert_nops+0x201/0x2b9
 [<ffffffffa0000660>] ? register_virtio_driver+0x8/0x50 [virtio]
 [<ffffffff810d5e2a>] ftrace_module_notify+0x4c/0x7f
 [<ffffffff81509c65>] notifier_call_chain+0x72/0xba
 [<ffffffff81086e71>] ? __blocking_notifier_call_chain+0x4c/0x8e
 [<ffffffff81086e88>] __blocking_notifier_call_chain+0x63/0x8e
dracut: Scanning devices vda2  for LVM volume groups
dracut: Reading all physical volumes. This may take a while...
dracut: Found volume group "vg_bluesbrothers" using metadata type lvm2

... and that's it.  It's been sitting there for 10 minutes now, so I
don't think it's going any further.  After using rescue mode to get a
root shell inside the affected machine, I did a "yum upgrade" to get
today's updates.  The identical boot problems remain.

Jerry James

More information about the Fedora-virt mailing list