From: Paolo Bonzini <pbonzini@redhat.com>
To: "Ren, Yongjie" <yongjie.ren@intel.com>
Cc: Alex Palesandro <palexster@gmail.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: Xen as L1 support
Date: Wed, 15 May 2013 16:59:24 +0200 [thread overview]
Message-ID: <5193A2CC.9050304@redhat.com> (raw)
In-Reply-To: <1B4B44D9196EFF41AE41FDA404FC0A100112FE48@SHSMSX101.ccr.corp.intel.com>
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.
Paolo
>> I found some bug-traces [1] [2] but the hex value here is different from the
>> previously reported one, so maybe that is a different issue.
>>
>> Will Xen be supported as L1?
>>
> So far, I think it's NO. VMX doesn't work, but PV guest can work in L1 Xen.
> There's a bug tracking 'Xen on KVM' issue.
> https://bugzilla.kernel.org/show_bug.cgi?id=45931
>
> Best Regards,
> Yongjie (Jay)
>
>
>> Many Thanks.
>>
>> Alex
>>
>> [1] https://patchwork.kernel.org/patch/1318301/
>> [2} https://patchwork.kernel.org/patch/789632/
> N�����r��y���b�X��ǧv�^�){.n�+����h��\x17��ܨ}���Ơz�&j:+v���\a����zZ+��+zf���h���~����i���z�\x1e�w���?����&�)ߢ^[fl===
>
next prev parent reply other threads:[~2013-05-15 15:06 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 [this message]
2013-05-15 17:43 ` Jan Kiszka
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=5193A2CC.9050304@redhat.com \
--to=pbonzini@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=palexster@gmail.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