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/
Home Products Support Community News


[Xen-devel] most of qcow images cannot boot since c/s 16958.

To: "xen-devel" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] most of qcow images cannot boot since c/s 16958.
From: "Li, Haicheng" <haicheng.li@xxxxxxxxx>
Date: Sun, 3 Feb 2008 15:48:58 +0800
Delivery-date: Sat, 02 Feb 2008 23:50:08 -0800
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: AchmOTuLZUTRHr6QSuaoNS9OPb7wMw==
Thread-topic: most of qcow images cannot boot since c/s 16958.
Hi all,

We found since c/s 16958, most of our qcow images will hang on boot; xm
dmesg shows:
(XEN) HVM3: int13_harddisk: function 41, unmapped device for ELDL=81
(XEN) HVM3: int13_harddisk: function 08, unmapped device for ELDL=81
(XEN) HVM3: *** int 15h function AX=00C0, BX=0000 not yet supported!

When this hang happens, "xm destroy" command cannot destroy that domain
any more; and xend will lose response after running "xm destroy" until
this qemu process is killed by "kill -9".

This issue blocks our testing. And c/s 16945 has no such issue. 

Detailed xm dmesg log is attached.

-- haicheng

Attachment: qcow
Description: qcow

Xen-devel mailing list