From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 42779] New: KVM domain hangs after loading initrd with Xenomai kernel
Date: Thu, 16 Feb 2012 05:45:29 GMT [thread overview]
Message-ID: <bug-42779-28872@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=42779
Summary: KVM domain hangs after loading initrd with Xenomai
kernel
Product: Virtualization
Version: unspecified
Kernel Version: 3.0.0-15
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: kvm
AssignedTo: virtualization_kvm@kernel-bugs.osdl.org
ReportedBy: madengineer10@gmail.com
Regression: No
Attempting to boot a 32 bit Debian guest with a Xenomai kernel inside KVM
causes it to hang and spin (using 1 full CPU core) after loading the initrd, as
determined by serial console output. The only error message is "KVM internal
error. Suberror: 1"/"emulation failure". Booting a regular Debian kernel
succeeds, as does running the Xenomai kernel with software emulation (-no-kvm).
Info:
CPU: Intel Core i7-2670QM
Emulator: qemu-kvm 0.14.1
Host kernel: 3.0.0-15 (Ubuntu build), x86_64
Guest OS: Debian Squeeze, kernel.org 2.6.37 kernel with Xenomai 2.6.0 (config
attached)
Qemu command: kvm -M pc-0.14 -enable-kvm -m 1024 -drive
file=/var/lib/libvirt/images/eve.img,if=none,id=drive-ide0-0-0,format=raw
-device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -netdev
tap,fd=21,id=hostnet0 -device
e1000,netdev=hostnet0,id=net0,mac=52:54:00:b5:f4:00,bus=pci.0,addr=0x3 -chardev
stdio,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -usb
-device usb-tablet,id=input0 -vga cirrus
Effects of flags: Adding one or both of --no-kvm-irqchip or --no-kvm-pit has no
apparent effect. Adding --no-kvm appears to correct the problem, at the cost of
performance due to using the software emulator.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next reply other threads:[~2012-02-16 5:45 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-16 5:45 bugzilla-daemon [this message]
2012-02-16 5:46 ` [Bug 42779] KVM domain hangs after loading initrd with Xenomai kernel bugzilla-daemon
2012-02-16 5:47 ` bugzilla-daemon
2012-02-16 5:47 ` bugzilla-daemon
2012-02-16 5:48 ` bugzilla-daemon
2012-02-16 5:57 ` bugzilla-daemon
2012-02-16 6:32 ` bugzilla-daemon
2012-02-16 7:15 ` bugzilla-daemon
2012-02-16 7:22 ` bugzilla-daemon
2012-02-16 7:43 ` bugzilla-daemon
2012-02-16 7:56 ` bugzilla-daemon
2012-02-16 7:57 ` bugzilla-daemon
2012-02-16 8:04 ` bugzilla-daemon
2012-02-16 8:31 ` bugzilla-daemon
2012-02-16 8:40 ` bugzilla-daemon
2012-02-16 11:40 ` bugzilla-daemon
2012-02-16 11:51 ` bugzilla-daemon
2012-02-16 16:48 ` bugzilla-daemon
2012-02-16 16:51 ` bugzilla-daemon
2012-02-16 17:24 ` bugzilla-daemon
2012-02-16 17:30 ` bugzilla-daemon
2012-02-16 22:01 ` bugzilla-daemon
2012-03-21 18:21 ` bugzilla-daemon
2012-03-31 20:10 ` bugzilla-daemon
2012-04-01 14:15 ` bugzilla-daemon
2012-04-01 23:38 ` bugzilla-daemon
2012-04-01 23:39 ` bugzilla-daemon
2012-04-01 23:40 ` bugzilla-daemon
2012-04-02 9:12 ` bugzilla-daemon
2012-07-01 9:42 ` bugzilla-daemon
2012-08-15 21:57 ` bugzilla-daemon
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=bug-42779-28872@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=kvm@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.