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

RE: [Xen-devel] VMX status report 12733:0bea8e773508

  • To: "Ewan Mellor" <ewan@xxxxxxxxxxxxx>
  • From: "Yu, Ping Y" <ping.y.yu@xxxxxxxxx>
  • Date: Thu, 7 Dec 2006 14:05:58 +0800
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Wed, 06 Dec 2006 22:06:22 -0800
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AccZHi25NPfmB7kWQn2pf7BniHW18QAp3D1A
  • Thread-topic: [Xen-devel] VMX status report 12733:0bea8e773508


Xinmei has sent out a patch for this bug. Thanks


>-----Original Message-----
>From: Ewan Mellor [mailto:ewan@xxxxxxxxxxxxx]
>Sent: 2006年12月6日 18:06
>To: Yu, Ping Y
>Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
>Subject: Re: [Xen-devel] VMX status report 12733:0bea8e773508
>On Wed, Dec 06, 2006 at 04:02:05PM +0800, Yu, Ping Y wrote:
>> We have tested the latest xen on VT platform with Intel 965/5000P
>> chipset.
>> Here is the test summary:
>> Issues:
>> ==========================
>> 1). Both Linux and Windows VMX domain fail to reboot with "cdrom" is
>> configured in all platforms, such as IA32,IA32pae, and x86_64.
>>     http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=832
>This one looks easy to fix.  Could you please use xen-bugtool to attach your
>logs to this bug?  Thanks.

Xen-devel mailing list



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