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] most of qcow images cannot boot since c/s 16958.

To: "Li, Haicheng" <haicheng.li@xxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] most of qcow images cannot boot since c/s 16958.
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Sun, 03 Feb 2008 08:53:34 +0000
Delivery-date: Sun, 03 Feb 2008 00:53:29 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <FC1D1B23302A22499C60C967336B2AE00258F2F0@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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: AchmOTuLZUTRHr6QSuaoNS9OPb7wMwACQZhD
Thread-topic: [Xen-devel] most of qcow images cannot boot since c/s 16958.
User-agent: Microsoft-Entourage/11.3.6.070618
I'm not sure what causes that. Hanging 'xm destroy' is because qemu-dm is
now killed by SIGTERM rather than SIGKILL. I think that was a mistake to
change, so I'll probably revert that. But it doesn't explain why your
qemu-dm went bad in the first place. I think you will have to work out
exactly which changeset caused the problem.

 -- Keir

On 3/2/08 07:48, "Li, Haicheng" <haicheng.li@xxxxxxxxx> wrote:

> 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
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel



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