From: "SourceForge.net" <noreply@sourceforge.net>
To: noreply@sourceforge.net
Subject: [ kvm-Bugs-2944508 ] QEMU (0.12.2) startup problem with kvm and flag -no-reboot
Date: Tue, 02 Feb 2010 09:46:05 +0000 [thread overview]
Message-ID: <E1NcFKf-00036F-IF@cdv4jf1.ch3.sourceforge.com> (raw)
Bugs item #2944508, was opened at 2010-02-02 09:46
Message generated for change (Tracker Item Submitted) made by nsnkern
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: Open
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)
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2944508&group_id=180599
next reply other threads:[~2010-02-02 9:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-02 9:46 SourceForge.net [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-02-08 20:13 [ kvm-Bugs-2944508 ] QEMU (0.12.2) startup problem with kvm and flag -no-reboot SourceForge.net
2010-02-10 15:50 SourceForge.net
2010-02-10 17:11 SourceForge.net
2010-02-23 2:20 SourceForge.net
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1NcFKf-00036F-IF@cdv4jf1.ch3.sourceforge.com \
--to=noreply@sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox