From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeroen Groenewegen van der Weyden Subject: Re: [PATCH 20 of 20] n2 MSR handling and capability exposure Date: Tue, 26 Jul 2011 17:25:11 +0200 Message-ID: <4E2EDC57.6060205@grosc.com> References: <1A42CE6F5F474C41B63392A5F80372B212DAC025EB@shsmsx501.ccr.corp.intel.com> <4E26E23D.4030000@grosc.com> <20110725140843.GC8970@whitby.uk.xensource.com> <20110725161657.GF8970@whitby.uk.xensource.com> <4E2E6992.9030407@grosc.com> <20110726100018.GH8970@whitby.uk.xensource.com> <20110726101140.GI8970@whitby.uk.xensource.com> <4E2E9B05.7030206@grosc.com> <20110726114233.GJ8970@whitby.uk.xensource.com> <4E2EC245.2030905@grosc.com> <20110726142141.GL8970@whitby.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20110726142141.GL8970@whitby.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Tim Deegan Cc: "Christoph.Egger@amd.com" , "xen-devel@lists.xensource.com" , "Dong, Eddie" List-Id: xen-devel@lists.xenproject.org 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. >