WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] VMX status report 9532:5baf152d63ef

To: "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] VMX status report 9532:5baf152d63ef
From: "Ahamed K, Rafiq (HP)" <rafiq.ahamed@xxxxxx>
Date: Wed, 19 Apr 2006 16:47:45 -0400
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 19 Apr 2006 13:48:15 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcZjyB67KyREkGbmSquM438dyk1yHwAKUobQ
Thread-topic: [Xen-devel] VMX status report 9532:5baf152d63ef
Kier , Is the fix available for this problem in xen unstable version? I
am also facing the same problem while trying to load the windows 2003 on
XEON servers with VT-x enabled and FC5 running xen unstable version.

The terminal shows the initial boot sequence and then hangs with this
log?

Any help is appreciated!

Booting from Hard Disk...
unsupported PCI BIOS function 0x0E
*** int 15h function AX=5300, BX=0000 not yet supported!
int13_harddisk: function 15, unmapped device for ELDL=81

Thanks Rafiq


from [Keir Fraser] [Permanent Link][Original] 

To:  "Shi, Alex" <alex.shi@xxxxxxxxx> 
Subject:  Re: [Xen-devel] VMX status report 9532:5baf152d63ef 
From:  Keir Fraser <Keir.Fraser@xxxxxxxxxxxx> 
Date:  Wed, 5 Apr 2006 13:53:06 +0100 
Cc:  xen-devel@xxxxxxxxxxxxxxxxxxx 
Delivery-date:  Wed, 05 Apr 2006 05:52:52 -0700 
Envelope-to:  www-data@xxxxxxxxxxxxxxxxxx 
In-reply-to:  <97482BF90993634BAE7D886C5B89B5ED887685@pdsmsx403> 
List-help:  <mailto:xen-devel-request@xxxxxxxxxxxxxxxxxxx?subject=help> 
List-id:  Xen developer discussion <xen-devel.lists.xensource.com> 
List-post:  <mailto:xen-devel@xxxxxxxxxxxxxxxxxxx> 
List-subscribe:
<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
<mailto:xen-devel-request@xxxxxxxxxxxxxxxxxxx?subject=subscribe> 
List-unsubscribe:
<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
<mailto:xen-devel-request@xxxxxxxxxxxxxxxxxxx?subject=unsubscribe> 
References:  <97482BF90993634BAE7D886C5B89B5ED887685@pdsmsx403> 
Sender:  xen-devel-bounces@xxxxxxxxxxxxxxxxxxx 


On 5 Apr 2006, at 13:42, Shi, Alex wrote:


We have tested the latest xen on VT platform with Intel 915/E8500
chipset.Here is the test summary.



Yes, we've reproduced that same bug in Cambridge. It's due to changeset
9530. We're currently testing a fix for xen-unstable. The offending
changeset is not in our 3.0.2 release candidate. 

 -- Keir

 

Attachment: qemu-dm.5858.log
Description: qemu-dm.5858.log

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