WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

RE: [Xen-devel] [PATCH 20 of 20] n2 MSR handling and capability exposure

To: Jeroen Groenewegen van der Weyden <groen692@xxxxxxxxx>
Subject: RE: [Xen-devel] [PATCH 20 of 20] n2 MSR handling and capability exposure
From: "Dong, Eddie" <eddie.dong@xxxxxxxxx>
Date: Wed, 20 Jul 2011 21:44:01 +0800
Accept-language: en-US
Acceptlanguage: en-US
Cc: Tim, "Christoph.Egger@xxxxxxx" <Christoph.Egger@xxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Dong, Eddie" <eddie.dong@xxxxxxxxx>, Deegan <Tim.Deegan@xxxxxxxxxx>
Delivery-date: Wed, 20 Jul 2011 06:44:46 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4E258DC4.4050106@xxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <patchbomb.1307607905@xxxxxxxxxxxxxxxxxxxx> <480cfcea095bddb2e7c4.1307607925@xxxxxxxxxxxxxxxxxxxx> <20110613082700.GA17634@xxxxxxxxxxxxxxxxxxxxxxx> <1A42CE6F5F474C41B63392A5F80372B2562BF1EC@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20110615124527.GG17634@xxxxxxxxxxxxxxxxxxxxxxx> <4DFEE946.9070603@xxxxxxxxx> <4E0C84C8.1030804@xxxxxxxxx> <20110701090145.GS9784@xxxxxxxxxxxxxxxxxxxxxxx> <4E0D9948.5000508@xxxxxxx> <4E0D9D48.20308@xxxxxxxxx> <20110704085810.GZ17634@xxxxxxxxxxxxxxxxxxxxxxx> <4E16ADD9.4060304@xxxxxxxxx> <1A42CE6F5F474C41B63392A5F80372B212DAB9DD82@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <4E258DC4.4050106@xxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcxGHD4Kb4Gc2cIPTBGgdyVGNGWinQAxSbxQ
Thread-topic: [Xen-devel] [PATCH 20 of 20] n2 MSR handling and capability exposure
Hi Jeroen:
        What L1 guest do u use? Xen or KVM? 
Thx, Eddie

> -----Original Message-----
> From: Jeroen Groenewegen van der Weyden [mailto:groen692@xxxxxxxxx]
> Sent: Tuesday, July 19, 2011 10:00 PM
> To: Dong, Eddie
> Cc: xen-devel@xxxxxxxxxxxxxxxxxxx; Tim Deegan;
> Christoph.Egger@xxxxxxx
> Subject: Re: [Xen-devel] [PATCH 20 of 20] n2 MSR handling and capability
> exposure
> 
> Hi eddie, I use the same settings. however my setup becomes in-response
> after start of the second nested kvm quest. were does that leave us?
> Should I make some trace and sent it to you. I can give you access to my
> system as well if you want. just give me your thoughts on how to move
> forward.
> 
> mfg,
> Jeroen.
> 
> Op 18-7-2011 17:41, Dong, Eddie schreef:
> > Jeroen:
> >     Sorry for later response.
> >     I did a double check locally, I was able to create 2 layer 2 guests. My
> environment is L1 guest: 64 bits Linux 2.6.25 + KVM-76. One L2 guest is 32
> bits Linux, another one is 64 bits guest.
> >     For layer 1 guest, I am setting:
> >
> > hap=1
> > nestedhvm = 1
> >
> > Thx, Eddie
> >
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@xxxxxxxxxxxxxxxxxxx
> > http://lists.xensource.com/xen-devel
> >


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>