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

RE: [Xen-devel] vmx status report against changeset 13826

  • To: "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Yu, Ping Y" <ping.y.yu@xxxxxxxxx>
  • Date: Fri, 9 Feb 2007 09:09:34 +0800
  • Delivery-date: Thu, 08 Feb 2007 17:09:27 -0800
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcdLUbF5zhYXkUEHTbudbOsozzXcWQADsSyAAAx/NfsAFQMKIA==
  • Thread-topic: [Xen-devel] vmx status report against changeset 13826


I have opened a bug http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=878 
track this issue, and we have some detail information for this bug there.

-- Ping

>-----Original Message-----
>From: Keir Fraser [mailto:Keir.Fraser@xxxxxxxxxxxx]
>Sent: 2007年2月8日 23:05
>To: Yu, Ping Y; xen-devel@xxxxxxxxxxxxxxxxxxx
>Subject: Re: [Xen-devel] vmx status report against changeset 13826
>On 8/2/07 09:07, "Yu, Ping Y" <ping.y.yu@xxxxxxxxx> wrote:
>> 2) Call trace are printed continually in serial port(p2)
>> A lot of call trace are printed in serial port, it exists in
>> both PAE and IA32e Xen0, and I am afraid it also exists on IA32.
>Do you have an example to show us? Are they softlockup warnings?
> -- Keir

Xen-devel mailing list



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