From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 82211] Cannot boot Xen under KVM with X2APIC enabled
Date: Fri, 20 Mar 2015 05:17:12 +0000 [thread overview]
Message-ID: <bug-82211-28872-yungIANZEQ@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-82211-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=82211
--- Comment #12 from Zhou, Chao <chao.zhou@intel.com> ---
(In reply to Radim Krčmář from comment #11)
> Should be fixed with "KVM: x86: call irq notifiers with directed EOI",
> (http://www.spinics.net/lists/kernel/msg1949367.html)
>
> can you check if it is?
>
> Thanks.
test this patch with kvm.git:4ff6f8e61eb7f96d3ca535c6d240f863ccd6fb7d
kernel version: 4.0.0-rc1+
qemu.git:cd232acfa0d70002fed89e9293f04afda577a513
test on Haswell_EP and Ivytown_EP
L1(xen on kvm) guest works fine when boot up L1 guest
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2015-03-20 5:17 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
2015-03-18 18:56 ` bugzilla-daemon
2015-03-20 5:17 ` bugzilla-daemon [this message]
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-yungIANZEQ@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox