From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 82211] Cannot boot Xen under KVM with X2APIC enabled
Date: Tue, 17 Mar 2015 17:01:58 +0000 [thread overview]
Message-ID: <bug-82211-28872-x0uzznn1wJ@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-82211-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=82211
Radim Krčmář <rkrcmar@redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rkrcmar@redhat.com
--- Comment #10 from Radim Krčmář <rkrcmar@redhat.com> ---
I can reproduce with kernel-4.0.0-0.rc3.git2.1.fc23.x86_64 and attached Xen.
qemu-kvm -kernel ./xen -initrd /boot/vmlinuz-[...] -cpu kvm64,+x2apic
Xen doesn't use x2APIC (which is good), but x2APIC enables directed EOI for
xAPIC, which doesn't work. All is good if we manually avoid it
qemu-kvm [...] -append ioapic_ack=new
KVM IOAPIC never gets EOI.
I'll take a look where the problem is.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2015-03-17 17:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-12 7:35 [Bug 82211] New: [Nested xen on kvm] L1 guest panic and reboot when L1 guest boot up bugzilla-daemon
2014-08-12 7:36 ` [Bug 82211] " bugzilla-daemon
2014-08-12 7:40 ` bugzilla-daemon
2014-08-21 17:56 ` [Bug 82211] [BISECTED][Nested " bugzilla-daemon
2014-09-01 12:46 ` bugzilla-daemon
2014-09-01 13:09 ` [Bug 82211] Cannot boot Xen under KVM with X2APIC enabled bugzilla-daemon
2014-09-01 13:19 ` bugzilla-daemon
2014-09-02 4:50 ` bugzilla-daemon
2014-09-02 6:31 ` bugzilla-daemon
2014-09-03 1:50 ` bugzilla-daemon
2014-09-03 1:58 ` bugzilla-daemon
2014-09-03 11:25 ` bugzilla-daemon
2015-03-17 3:53 ` bugzilla-daemon
2015-03-17 17:01 ` bugzilla-daemon [this message]
2015-03-18 18:56 ` bugzilla-daemon
2015-03-20 5:17 ` bugzilla-daemon
2015-04-08 8:36 ` 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-82211-28872-x0uzznn1wJ@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.