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: Tim Deegan <Tim.Deegan@xxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH 20 of 20] n2 MSR handling and capability exposure
From: Jeroen Groenewegen van der Weyden <groen692@xxxxxxxxx>
Date: Tue, 26 Jul 2011 17:25:11 +0200
Cc: "Christoph.Egger@xxxxxxx" <Christoph.Egger@xxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Dong, Eddie" <eddie.dong@xxxxxxxxx>
Delivery-date: Tue, 26 Jul 2011 08:26:16 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20110726142141.GL8970@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: <1A42CE6F5F474C41B63392A5F80372B212DAC025EB@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <4E26E23D.4030000@xxxxxxxxx> <20110725140843.GC8970@xxxxxxxxxxxxxxxxxxxxxxx> <20110725161657.GF8970@xxxxxxxxxxxxxxxxxxxxxxx> <4E2E6992.9030407@xxxxxxxxx> <20110726100018.GH8970@xxxxxxxxxxxxxxxxxxxxxxx> <20110726101140.GI8970@xxxxxxxxxxxxxxxxxxxxxxx> <4E2E9B05.7030206@xxxxxxxxx> <20110726114233.GJ8970@xxxxxxxxxxxxxxxxxxxxxxx> <4E2EC245.2030905@xxxxxxxxx> <20110726142141.GL8970@xxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0
Tim! everyhting seems to work now. domu is working ok, all 4 nested kvm guests are running.

only dmesg seems te complain about something
(XEN) vvmx.c:1205:d2 vmclear gpa 1920de000 != 000000018c829000
(XEN) vvmx.c:1205:d2 vmclear gpa 1920de000 != 000000018c829000
(XEN) vvmx.c:1205:d2 vmclear gpa 1920de000 != 00000001f9372000
(XEN) vvmx.c:1205:d2 vmclear gpa 1ec8f7000 != 00000001f9372000
(XEN) vvmx.c:1205:d2 vmclear gpa 1920de000 != 00000001ec8f7000
(XEN) vvmx.c:1205:d2 vmclear gpa 18c829000 != 00000001ec8f7000
(XEN) vvmx.c:1205:d2 vmclear gpa 1920de000 != 00000001ec8f7000


mfg,
Jeroen

Op 26-7-2011 16:21, Tim Deegan schreef:
At 15:33 +0200 on 26 Jul (1311694437), Jeroen Groenewegen van der Weyden wrote:
Tim, This improved a lot. the domu does not become in-responsive
anymore. However, all four l2 guest are started. but 2 out of 4 are
hanging/in-responsive after 30 to 60 seconds.

L1 domu (sles11sp1)
  ->  seems to be ok

L2-1 propetary OS, seems to be ok
L2-2 propetary OS, seems to be ok
l2-3 sles10sp3, hanging/in-responsive
l2-4 sles10sp3, hanging/in-responsive

no degug/error messages in dmesg.
Anything in the l1 dmesg?

I'm trying to repro with actual linux guests but I've found that
PXELINUX is hanging for me. :(  I'll have a look at that later if I can.

In the meantime I realised I didn't quite get the logic right in the
first patch; there's one case missing.  Can you please try this one?

Tim.



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

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