On Wed, May 15, 2013 at 07:43:25PM +0200, Jan Kiszka wrote: > On 2013-05-15 16:59, Paolo Bonzini wrote: > > Il 15/05/2013 03:24, Ren, Yongjie ha scritto: > >>> -----Original Message----- > >>> From: kvm-owner@xxxxxxxxxxxxxxx [mailto:kvm-owner@xxxxxxxxxxxxxxx] > >>> On Behalf Of Alex Palesandro > >>> Sent: Tuesday, May 14, 2013 10:51 PM > >>> To: kvm@xxxxxxxxxxxxxxx > >>> 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? > IIRC the feature was always there. KVM started to use it only from 3.10 since posted interrupt requires it. -- Gleb. -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
