From: "herbert cland" <herbert.cland@gmail.com>
To: xen-devel <xen-devel@lists.xen.org>
Subject: [XEN BUG] XEN + Qemu upstream + Qcow2 + coroutine = BOOM
Date: Mon, 10 Feb 2014 17:47:33 +0800 [thread overview]
Message-ID: <2014021017472829063425@gmail.com> (raw)
[-- 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
next reply other threads:[~2014-02-10 9:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-10 9:47 herbert cland [this message]
2014-02-10 14:19 ` [XEN BUG] XEN + Qemu upstream + Qcow2 + coroutine = BOOM Ian Campbell
2014-02-12 4:15 ` herbert cland
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2014021017472829063425@gmail.com \
--to=herbert.cland@gmail.com \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).