From: Jan Kiszka <jan.kiszka@web.de>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Ren, Yongjie" <yongjie.ren@intel.com>,
Alex Palesandro <palexster@gmail.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: Xen as L1 support
Date: Wed, 15 May 2013 19:43:25 +0200 [thread overview]
Message-ID: <5193C93D.5020707@web.de> (raw)
In-Reply-To: <5193A2CC.9050304@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1065 bytes --]
On 2013-05-15 16:59, Paolo Bonzini wrote:
> Il 15/05/2013 03:24, Ren, Yongjie ha scritto:
>>> -----Original Message-----
>>> From: kvm-owner@vger.kernel.org [mailto:kvm-owner@vger.kernel.org]
>>> On Behalf Of Alex Palesandro
>>> Sent: Tuesday, May 14, 2013 10:51 PM
>>> To: kvm@vger.kernel.org
>>> Subject: Fwd: Xen as L1 support
>>>
>>> Hi,
>>> I'm new to KVM. I'm doing some test on nested Virtualization with Xen
>>> and KVM. I tried to test the Xen hypervisor as L1 over KVM ( Linux
>>> 3.9.0) and I found this in
>>> "xm dmesg" log ( for the complete log, see the attached file).
>>> --------------------------------------------
>>> (XEN) VMX: CPU0 has insufficent VMExit Control (00036fff but requires
>>> min 00008200)
>>> (XEN) VMX: failed to initialise.
>>> --------------------------------------------
>
> This is the "Acknowledge interrupt on exit" control. It shouldn't be
> hard to implement it.
Isn't this a pretty recent feature Xen should be able to live without -
if it finds itself on a (virtually) older CPU?
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
next prev parent reply other threads:[~2013-05-15 17:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAAj9-pm5rxgez=_HbMsDDBX3J9umzL1qYw47c2x4i9zRvaEoaQ@mail.gmail.com>
2013-05-14 14:50 ` Fwd: Xen as L1 support Alex Palesandro
2013-05-15 1:24 ` Ren, Yongjie
2013-05-15 14:59 ` Paolo Bonzini
2013-05-15 17:43 ` Jan Kiszka [this message]
2013-05-15 17:45 ` Gleb Natapov
2013-05-15 17:49 ` Jan Kiszka
2013-05-15 17:44 ` Gleb Natapov
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=5193C93D.5020707@web.de \
--to=jan.kiszka@web.de \
--cc=kvm@vger.kernel.org \
--cc=palexster@gmail.com \
--cc=pbonzini@redhat.com \
--cc=yongjie.ren@intel.com \
/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