Description of problem: Version-Release number of selected component (if applicable): L0 host: 3.6.10-2.fc17.x86_64 #1 SMP Tue Dec 11 18:07:34 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux qemu-* versions: qemu-kvm-tools-1.0.1-2.fc17.x86_64 qemu-img-1.0.1-2.fc17.x86_64 qemu-common-1.0.1-2.fc17.x86_64 qemu-system-x86-1.0.1-2.fc17.x86_64 qemu-kvm-1.0.1-2.fc17.x86_64 How reproducible: Steps to Reproduce: 1.install f17 L0 host with vdsm-nested-hook 2.create L1 nested hypervisor running rhel63 on it 3.add L1 nested host to an ovirt/rhevm setup as host. Actual results: qemu crash on l0 host, and nested l1 host is in bootloop/pause mode Expected results: nested l1 host is running and booting OK. Additional info:
Created attachment 669563 [details] proc cpuinfo on the host
Tried switching the host to fedora18. experiencing a kernel panic upon boot after turning on nested kvm in the kernel.
F17 + F18 have the 3.8 kernel nowdays, can someone retest and see if the issue persists?
I don't see a qemu crash anymore. but I do encounter a different problem https://bugzilla.redhat.com/show_bug.cgi?id=923840
Thanks Ohad, closing this as CURRENTRELEASE then, we can track the kernel issue in your other bug.