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/
Home Products Support Community News


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: Tim Deegan <Tim.Deegan@xxxxxxxxxx>
Date: Tue, 26 Jul 2011 11:11:40 +0100
Cc: "Christoph.Egger@xxxxxxx" <Christoph.Egger@xxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Dong, Eddie" <eddie.dong@xxxxxxxxx>
Delivery-date: Tue, 26 Jul 2011 03:12:36 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20110726100018.GH8970@xxxxxxxxxxxxxxxxxxxxxxx>
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: <20110704085810.GZ17634@xxxxxxxxxxxxxxxxxxxxxxx> <4E16ADD9.4060304@xxxxxxxxx> <1A42CE6F5F474C41B63392A5F80372B212DAB9DD82@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <4E258DC4.4050106@xxxxxxxxx> <1A42CE6F5F474C41B63392A5F80372B212DAC025EB@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <4E26E23D.4030000@xxxxxxxxx> <20110725140843.GC8970@xxxxxxxxxxxxxxxxxxxxxxx> <20110725161657.GF8970@xxxxxxxxxxxxxxxxxxxxxxx> <4E2E6992.9030407@xxxxxxxxx> <20110726100018.GH8970@xxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.21 (2010-09-15)
At 11:00 +0100 on 26 Jul (1311678018), Tim Deegan wrote:
> If you want to double-check that you've done the patch right,
> edit xen/arch/x86/hvm/vmx/vvmx.c, and at line 1185, just under the line
> ` /* Even if this VMCS isn't the current one, we must clear it. */ '
> add a line ` printk("boo!\n"); '.  Then when you recompile and test you
> should see "boo!" printed just after each "vvmx.c:1182:d3" line on the
> console.

Oh, and when the domU is hung, can you run the command 
/usr/lib/xen/bin/xenctx -aCS 1 
(replacing '1' with the domid of your domU) three or four times 
and post the output here?  On a 64-bit dom0 I think the correct path
will be /usr/lib64/xen/bin/xenctx.



Tim Deegan <Tim.Deegan@xxxxxxxxxx>
Principal Software Engineer, Xen Platform Team
Citrix Systems UK Ltd.  (Company #02937203, SL9 0BG)

Xen-devel mailing list

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