From mboxrd@z Thu Jan 1 00:00:00 1970 From: "herbert cland" Subject: [XEN BUG] XEN + Qemu upstream + Qcow2 + coroutine = BOOM Date: Mon, 10 Feb 2014 17:47:33 +0800 Message-ID: <2014021017472829063425@gmail.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4738104836848553965==" Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: xen-devel List-Id: xen-devel@lists.xenproject.org This is a multi-part message in MIME format. --===============4738104836848553965== Content-Type: multipart/alternative; boundary="----=_001_NextPart213635228552_=----" This is a multi-part message in MIME format. ------=_001_NextPart213635228552_=---- Content-Type: text/plain; charset="GB2312" Content-Transfer-Encoding: base64 RGVhciBBTEwhDQoNCnFjb3cyIGZvcm1hdCBkaXNrIHdvcmtzIHdlbGwgd2l0aCB4ZW4gZm9yIG1v c3QgY2FzZXM7DQpCVVQgaWYgdXNpbmcgY29yb3V0aW5lIGZ1bmN0aW9uIHN1Y2ggYXMgYmxvY2st c3RyZWFtLCB0aGUgcWVtdSBwcm9jZXNzIGNyYXNoZWQhDQpBbmQgd2UgY2FuIGZvdW5kIGZvbGxv d2luZyBtc2cgZnJvbSBjbWQgZG1lc2cNCg0KcWVtdS1zeXN0ZW0taTM4WzIwNTE0XTogc2VnZmF1 bHQgYXQgNjAgaXAgMDAwMDdmMmI2MGRjODc5YSBzcCAwMDAwN2ZmZmZjYzJmMDAwIGVycm9yIDQg aW4gcWVtdS1zeXN0ZW0taTM4Nls3ZjJiNjBjZGYwMDArNTI5MDAwXSANCg0KQW55IHN1Z2dlc3Rp b24/DQoNCi0tLS0tLS0tLS0tLS0tLS0NClhFTiB2ZXJzaW9uo7ogeGVuIDQuNC4wLXJjMw0KZ3Vl c3Qgb3MgOiBjZW50b3MgNi40DQoNCg0KDQoNCg0KaGVyYmVydCBjbGFuZA== ------=_001_NextPart213635228552_=---- Content-Type: text/html; charset="GB2312" Content-Transfer-Encoding: quoted-printable
Dear ALL!
 
qcow2 format disk works well with xen for = most=20 cases;
BUT if using coroutine function such as=20 block-stream, the qemu process crashed!
And we can found following msg from cmd=20 dmesg
 
qemu-system-i38[20514]: segfault at 60 ip=20 00007f2b60dc879a sp 00007ffffcc2f000 error 4 in=20 qemu-system-i386[7f2b60cdf000+529000]
 
Any suggestion?
 
----------------
XEN version=A3=BA xen 4.4.0-rc3
guest os : centos 6.4
 
 
herbert cland
------=_001_NextPart213635228552_=------ --===============4738104836848553965== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel --===============4738104836848553965==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: [XEN BUG] XEN + Qemu upstream + Qcow2 + coroutine = BOOM Date: Mon, 10 Feb 2014 14:19:52 +0000 Message-ID: <1392041992.26657.6.camel@kazak.uk.xensource.com> References: <2014021017472829063425@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <2014021017472829063425@gmail.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: herbert cland Cc: xen-devel List-Id: xen-devel@lists.xenproject.org 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. From mboxrd@z Thu Jan 1 00:00:00 1970 From: "herbert cland" Subject: Re: [XEN BUG] XEN + Qemu upstream + Qcow2 + coroutine = BOOM Date: Wed, 12 Feb 2014 12:15:14 +0800 Message-ID: <2014021212150776651942@gmail.com> References: <2014021017472829063425@gmail.com>, <1392041992.26657.6.camel@kazak.uk.xensource.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2228157291637945671==" Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Campbell Cc: xen-devel List-Id: xen-devel@lists.xenproject.org This is a multi-part message in MIME format. --===============2228157291637945671== Content-Type: multipart/alternative; boundary="----=_001_NextPart328835548817_=----" This is a multi-part message in MIME format. ------=_001_NextPart328835548817_=---- Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: base64 VGh477yMIElhbg0KDQpJIGFtIHRyeWluZyB0byBhbmFseXplIHRoZSBjcmFzaCByZWFzb24uDQpU aGlzIEJVRyBpcyBvbmx5IGhhcHBlbmRlZCB3aGVuIHVzaW5nIElERSBkaXNrIChoZCogbmFtZSBm b3IgdmRpc2spLg0KSWYgdXNpbmcgU0NTSSBkaXNrIChzZCogbmFtZSkgaW4gdm0gY29uZmlnIGZp bGUsIFFlbXUgd29ya3Mgd2VsbC4NCg0KDQoNCg0KaGVyYmVydCBjbGFuZA0KDQpGcm9tOiBJYW4g Q2FtcGJlbGwNCkRhdGU6IDIwMTQtMDItMTAgMjI6MTkNClRvOiBoZXJiZXJ0IGNsYW5kDQpDQzog eGVuLWRldmVsDQpTdWJqZWN0OiBSZTogW1hlbi1kZXZlbF0gW1hFTiBCVUddIFhFTiArIFFlbXUg dXBzdHJlYW0gKyBRY293MiArIGNvcm91dGluZSA9IEJPT00NCk9uIE1vbiwgMjAxNC0wMi0xMCBh dCAxNzo0NyArMDgwMCwgaGVyYmVydCBjbGFuZCB3cm90ZToNCj4gRGVhciBBTEwhDQo+ICANCj4g cWNvdzIgZm9ybWF0IGRpc2sgd29ya3Mgd2VsbCB3aXRoIHhlbiBmb3IgbW9zdCBjYXNlczsNCj4g QlVUIGlmIHVzaW5nIGNvcm91dGluZSBmdW5jdGlvbiBzdWNoIGFzIGJsb2NrLXN0cmVhbSwgdGhl IHFlbXUgcHJvY2Vzcw0KPiBjcmFzaGVkIQ0KPiBBbmQgd2UgY2FuIGZvdW5kIGZvbGxvd2luZyBt c2cgZnJvbSBjbWQgZG1lc2cNCj4gIA0KPiBxZW11LXN5c3RlbS1pMzhbMjA1MTRdOiBzZWdmYXVs dCBhdCA2MCBpcCAwMDAwN2YyYjYwZGM4NzlhIHNwDQo+IDAwMDA3ZmZmZmNjMmYwMDAgZXJyb3Ig NCBpbiBxZW11LXN5c3RlbS1pMzg2WzdmMmI2MGNkZjAwMCs1MjkwMDBdIA0KPiAgDQo+IEFueSBz dWdnZXN0aW9uPw0KDQpQbGVhc2UgY2FuIHlvdSB0cnkgaW5zdGFsbGluZyB0aGUgbmVjZXNzYXJ5 IGRlYnVnIHN5bWJvbHMgcGFja2FnZSAoSQ0KZG9uJ3Qga25vdyBob3cgdG8gZG8gdGhpcyBvbiBj ZW50b3MpIGFuZCB0cnkgYW5kIGNhcHR1cmUgYSBjb3JlIGR1bXANCih3aGljaCBtaWdodCByZXF1 aXJlIGFkanVzdGluZyBybGltaXRzKSBvciBydW5uaW5nIHFlbXUgdW5kZXIgZ2RiDQpzb21laG93 LCBpbiBlaXRoZXIgY2FzZSBnZXR0aW5nIGEgYmFja3RyYWNlIG91dCBvZiB0aGlzIGNyYXNoIHdp bGwgaGVscA0KdXMgbWFrZSBwcm9ncmVzcy4NCg0KUGxlYXNlIGFsc28gdGFrZSBhIGxvb2sgYXQN Cmh0dHA6Ly93aWtpLnhlbi5vcmcvd2lraS9SZXBvcnRpbmdfQnVnc19hZ2FpbnN0X1hlbiBhbmQg c2VlIHdoYXQgb3RoZXINCmluZm8gbWlnaHQgYmUgdXNlZnVsLCBsaWtlIGd1ZXN0IGNvbmZpZyBm aWxlLCB3aGljaCB0b29sc3RhY2sgeW91IGFyZQ0KdXNpbmcsIG90aGVyIHVzZWZ1bCBsb2dzIGV0 Yy4NCg0KU2luY2UgdGhpcyBpcyBhIHFlbXUgaXNzdWUgeW91IG1pZ2h0IGFsc28gd2FudCB0byBp bmNsdWRlIHRoZSBxZW11IGxpc3QNCmluIHlvdXIgcmVwb3J0Lg0KDQpJYW4u ------=_001_NextPart328835548817_=---- Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable =EF=BB=BF
Thx=EF=BC=8C Ian
 
I am trying to analyze the crash reason.
This BUG is only happended when using IDE disk (hd* name for vdisk).<= /DIV>
If using SCSI disk (sd* name) in vm config file, Qemu works well.
 
herbert cland
 
Date: 2014-02-10 22:19
CC: xen-devel
Subject: Re: [Xen-devel] [XEN BUG] XEN + Qemu upstream + = Qcow2=20 + coroutine =3D 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=20 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= ]=20
> 
> Any suggestion?
 
Please can you try installing the necessary debug symbols package (I<= /DIV>
don't know how to do this on centos) and try and capture a core dump<= /DIV>
(which might require adjusting rlimits) or running qemu under gdb
somehow, in either case getting a backtrace out of this crash will=20 help
us make progress.
 
Please also take a look at
http://wiki.xen.org/wiki/Reporting_Bugs_against_Xen and see what=20 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=20 list
in your report.
 
Ian.
 
 
 
------=_001_NextPart328835548817_=------ --===============2228157291637945671== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel --===============2228157291637945671==--