Bugs item #2944508, was opened at 2010-02-02 03:46 Message generated for change (Comment added) made by iggy_cav You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2944508&group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: qemu Group: None Status: Pending Resolution: None Priority: 5 Private: No Submitted By: Marcel Kern (nsnkern) Assigned to: Nobody/Anonymous (nobody) Summary: QEMU (0.12.2) startup problem with kvm and flag -no-reboot Initial Comment: Problem description: --------------------------------------- QEMU (0.12.2) does not startup (not even one output message is displayed e.g. from BIOS boot etc.) if flag "-no-reboot" and kvm support is enabled. QEMU immediately quits if the following startup configuration is used. QEMU: qemu-0.12.2 (or qemu-kvm-0.12.2) (Note: qemu-kvm-0.11.1 is working fine) Not working anymore case: []$ qemu-system-x86_64 -kernel bzImage -initrd rootfs.cpio.gz -no-reboot -no-kvm-pit -enable-kvm []$ qemu-system-x86_64 -kernel bzImage -initrd rootfs.cpio.gz -no-reboot -no-kvm-pit -no-kvm-irqchip -enable-kvm []$ qemu-system-x86_64 -kernel bzImage -initrd rootfs.cpio.gz -no-reboot -no-kvm-irqchip -enable-kvm Working case: []$ qemu-system-x86_64 -kernel bzImage -initrd rootfs.cpio.gz -no-reboot -no-kvm-pit -no-kvm []$ qemu-system-x86_64 -kernel bzImage -initrd rootfs.cpio.gz -no-reboot -no-kvm-pit -no-kvm-irqchip -no-kvm []$ qemu-system-x86_64 -kernel bzImage -initrd rootfs.cpio.gz -no-reboot -no-kvm-irqchip -no-kvm Environment description: -------------------------------------------- cpuinfo: Intel(R) Xeon(R) CPU L5520 @ 2.27GHz OS Host: Red Hat Enterprise Linux Server release 5.4 (Tikanga) (x86_64) []$ uname -a Linux 2.6.18-164.el5 #1 SMP Tue Aug 18 15:51:48 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux RedHat KVM Kernel Module is used: []$ ll /lib/modules/2.6.18-164.el5/weak-updates/kmod-kvm/ ksm.ko -> /lib/modules/2.6.18-164.6.1.el5/extra/kmod-kvm/ksm.ko kvm-amd.ko -> /lib/modules/2.6.18-164.6.1.el5/extra/kmod-kvm/kvm-amd.ko kvm-intel.ko -> /lib/modules/2.6.18-164.6.1.el5/extra/kmod-kvm/kvm-intel.ko kvm.ko -> /lib/modules/2.6.18-164.6.1.el5/extra/kmod-kvm/kvm.ko OS Guest: Linux (Kernel 2.6.29 - 32-bit) ---------------------------------------------------------------------- >Comment By: Brian Jackson (iggy_cav) Date: 2010-02-10 11:11 Message: -enable-kvm doesn't do anything in qemu-kvm. Only in upstream qemu. If that's where you are seeing this issue, you need to file a bug with upstream. ---------------------------------------------------------------------- Comment By: Marcel Kern (nsnkern) Date: 2010-02-10 09:50 Message: Unfortunately still the same: Not working case: qemu-system-x86_64 -kernel bzImage -initrd rootfs -enable-kvm -no-reboot Working case: qemu-system-x86_64 -kernel bzImage -initrd rootfs -no-reboot and of course this works also: qemu-system-x86_64 -kernel bzImage -initrd rootfs -enable-kvm It seems the problem is the kvm module which is in use with the RedHat version mentioned above, because with kvm-88 (manually compiled) it works. Some debugging showed that there is occurs a timeout inside the qemu main loop, so the qemu exit is without an error but qemu does not startup at all. Any ideas? ---------------------------------------------------------------------- Comment By: Brian Jackson (iggy_cav) Date: 2010-02-08 14:13 Message: Have you tried without the -no-kvm-pit and -no-kvm-irqchip The following runs fine here with the latest qemu-kvm.git, so it's either fixed or it's one of those options kvm -no-reboot -kernel /boot/vmlinuz-2.6.32-trunk-amd64 -initrd /boot/initrd.img-2.6.32-trunk-amd64 -vnc :0 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2944508&group_id=180599 -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
