[XEN BUG] XEN + Qemu upstream + Qcow2 + coroutine = BOOM

[XEN BUG] XEN + Qemu upstream + Qcow2 + coroutine = BOOM

[herbert cland]

[-- Attachment #1.1: Type: text/plain, Size: 442 bytes --]

Dear ALL!

qcow2 format disk works well with xen for most cases;
BUT if using coroutine function such as block-stream, the qemu process crashed!
And we can found following msg from cmd dmesg

qemu-system-i38[20514]: segfault at 60 ip 00007f2b60dc879a sp 00007ffffcc2f000 error 4 in qemu-system-i386[7f2b60cdf000+529000] 

Any suggestion?

----------------
XEN version： xen 4.4.0-rc3
guest os : centos 6.4





herbert cland

[-- Attachment #1.2: Type: text/html, Size: 1622 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: [XEN BUG] XEN + Qemu upstream + Qcow2 + coroutine = BOOM

[Ian Campbell]

On Mon, 2014-02-10 at 17:47 +0800, herbert cland wrote:
> Dear ALL!
>  
> qcow2 format disk works well with xen for most cases;
> BUT if using coroutine function such as block-stream, the qemu process
> crashed!
> And we can found following msg from cmd dmesg
>  
> qemu-system-i38[20514]: segfault at 60 ip 00007f2b60dc879a sp
> 00007ffffcc2f000 error 4 in qemu-system-i386[7f2b60cdf000+529000] 
>  
> Any suggestion?

Please can you try installing the necessary debug symbols package (I
don't know how to do this on centos) and try and capture a core dump
(which might require adjusting rlimits) or running qemu under gdb
somehow, in either case getting a backtrace out of this crash will help
us make progress.

Please also take a look at
http://wiki.xen.org/wiki/Reporting_Bugs_against_Xen and see what other
info might be useful, like guest config file, which toolstack you are
using, other useful logs etc.

Since this is a qemu issue you might also want to include the qemu list
in your report.

Ian.

Re: [XEN BUG] XEN + Qemu upstream + Qcow2 + coroutine = BOOM

[herbert cland]

[-- Attachment #1.1: Type: text/plain, Size: 1413 bytes --]

Thx， Ian

I am trying to analyze the crash reason.
This BUG is only happended when using IDE disk (hd* name for vdisk).
If using SCSI disk (sd* name) in vm config file, Qemu works well.




herbert cland

From: Ian Campbell
Date: 2014-02-10 22:19
To: herbert cland
CC: xen-devel
Subject: Re: [Xen-devel] [XEN BUG] XEN + Qemu upstream + Qcow2 + coroutine = BOOM
On Mon, 2014-02-10 at 17:47 +0800, herbert cland wrote:
> Dear ALL!
>  
> qcow2 format disk works well with xen for most cases;
> BUT if using coroutine function such as block-stream, the qemu process
> crashed!
> And we can found following msg from cmd dmesg
>  
> qemu-system-i38[20514]: segfault at 60 ip 00007f2b60dc879a sp
> 00007ffffcc2f000 error 4 in qemu-system-i386[7f2b60cdf000+529000] 
>  
> Any suggestion?

Please can you try installing the necessary debug symbols package (I
don't know how to do this on centos) and try and capture a core dump
(which might require adjusting rlimits) or running qemu under gdb
somehow, in either case getting a backtrace out of this crash will help
us make progress.

Please also take a look at
http://wiki.xen.org/wiki/Reporting_Bugs_against_Xen and see what other
info might be useful, like guest config file, which toolstack you are
using, other useful logs etc.

Since this is a qemu issue you might also want to include the qemu list
in your report.

Ian.

[-- Attachment #1.2: Type: text/html, Size: 3293 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel