[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH 20 of 20] n2 MSR handling and capability exposure
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
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |