[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] VMX status report for Xen-3.2.1-rc1. Xen: #16821 & Xen0: #488


  • To: "Li, Haicheng" <haicheng.li@xxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
  • Date: Thu, 27 Mar 2008 13:53:57 +0000
  • Delivery-date: Thu, 27 Mar 2008 06:55:19 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AciQDAjO7e3efW0tRDe4A8CkWKXq9gABfePK
  • Thread-topic: [Xen-devel] VMX status report for Xen-3.2.1-rc1. Xen: #16821 & Xen0: #488

On 27/3/08 13:11, "Li, Haicheng" <haicheng.li@xxxxxxxxx> wrote:

> Actually we conducted two rounds of nightly testing on this c/s; in 1st
> round we met dom0 crash on IA32E, but it cannot be reproduced in 2nd
> round of testing or manually retesting; the case " boot up 1 winXP VMX
> and 1 linux VMX" caused this crash, we captured serial log of this crash
> and attached it with this email, hopefully it could provide some hint of
> this failure. Other failed cases can get pass by manually retesting.

Somehow you ended up in ipv6 code in the dom0 kernel. Probably not something
you want, and not something that's particularly well tested.

 -- Keir



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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.