Red Hat Bugzilla – Bug 649333
Unable to boot Fedora 13 guest
Last modified: 2013-01-09 06:42:12 EST
Description of problem:
After upgrade of Fedora 13 host to Fedora 14, I can't boot old Fedora 13 qcow2 guests. I use i686 kvm guest. Same problem with f12 guest.
Version-Release number of selected component (if applicable):
Fully updated minimal F13 stable guest.
always, also after reinstall of guest
Steps to Reproduce:
1.install Fedora 13 guest
2.remove "rhgb quiet" from kernel parameters to see more messages
Probing EDD (edd=off to disable)... ok
System stops here. CPU is used by qemu process, but boot does not continue.
Also no more messages with "earlyprintk=vga" kernel parameter. Does not matter, if I remove "rhgb quiet" from kernel parameters. How can I debug grub booting?
"edd=off" kernel parameter does not help too.
Same problem running from command line:
qemu-kvm -drive file=fedora-13.img,cache=none,format=qcow2,if=virtio,boot=on -m 1024
But works with qemu (non kvm version), just it's slow.
I have the same problem,
after update host from fedora 13 to fedora 14, my guest (fedora 13, fedora 12) stop working (Probing EDD (edd=off to disable)... ok .)
edd=off dont help :).
i move guest to fedora 13 host for now :(.
no my laptop (with Core i5-430M, fedora 13 guest working on fedora 14 hosts).
but on server (Intel(R) Xeon(R) CPU E5440) not.
maybe some special CPU features?
Created attachment 459049 [details]
qemu info commands registers and x/30i
Looks like this is a complement of bug #650215. Suggested qemu commands are attached. Curious, that when if fails, these commands returns same always and every time same content (same register content and same output, at least for first look).
Can somebody help me to more debug this bug?
I've had the same issues, but using kernel-188.8.131.52-59.fc14.i686.rpm form koji solved them for me.
Can you please test with the latest koji f14 kernel and see if that works for you, there is a major issue impacting i686 hosts resolved there.
fedora 14 koji kernel solve problem.
*** This bug has been marked as a duplicate of bug 650215 ***
*** Bug 663087 has been marked as a duplicate of this bug. ***