From: "Halsey Pian" <halsey.pian@gmail.com>
To: 'Stefan Hajnoczi' <stefanha@gmail.com>,
'Bug 1434779' <1434779@bugs.launchpad.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Bug 1434779] [NEW] qemu hangs on live-migration with storage(virtual machine: windows Server 2008 with only one disk )
Date: Tue, 31 Mar 2015 19:03:28 +0800 [thread overview]
Message-ID: <010e01d06ba2$542550b0$fc6ff210$@gmail.com> (raw)
In-Reply-To: <20150323133221.GH9268@stefanha-thinkpad.redhat.com>
> -----Original Message-----
> From: qemu-devel-bounces+halsey.pian=gmail.com@nongnu.org [mailto:qemu-devel-bounces+halsey.pian=gmail.com@nongnu.org]
> On Behalf Of Stefan Hajnoczi
> Sent: 2015年3月23日 21:32
> To: Bug 1434779
> Cc: qemu-devel@nongnu.org
> Subject: Re: [Qemu-devel] [Bug 1434779] [NEW] qemu hangs on live-migration with storage(virtual machine: windows Server 2008
> with only one disk )
>
> On Sat, Mar 21, 2015 at 07:44:37AM -0000, youyunyehe wrote:
> > We are using “Windows Server 2008” with qemu-kvm-2.0.1 (linux kernel:3.10.0) as a host of a VM.
>
> Please give the exact qemu-kvm package version and Linux distro name.
> The code in qemu.git/master is slightly different so maybe the issue no longer happens, but it would be worth looking at the exact
> source code your qemu-kvm is built from.
[Halsey] I also recreated this issue today, qemu hangs at bdrv_rw-co() -> bdrv_prwv_co() -> aio_poll(0 -> qemu_poll_ns() -> ppoll(). I'm just call bdrv_write to write data to qcow2 file. My qemu version is qemu-2.2.0.
> I have CCed Jeff Cody, who maintains drive-mirror.
>
> > Using drive_mirror to do live-migration on the same host for
> > different disks Local disk: /sf/data/local/
> > Shared disk(iscsi): /sf/other/local/ --- the disk is busy, the IO rate is about 30MB/s
> > qemu-system-x86_64 -k en-us -m 2048 -smp 2 -vnc :3100 -usbdevice
> > tablet -boot c -enable-kvm -drive
> > file=/sf/data/local/vm-disk-1.qcow2,if=none,id=drive-ide0,cache=none,a
> > io=native -device
> > ide-hd,bus=ide.0,unit=0,drive=drive-ide0,id=ide0,bootindex=100
> >
> > Step 1:
> > Start migration: Drive_mirror -f drive-ide0
> > /sf/other/local/test.qcow2
> >
> > Step 2:
> > When detect the migration has completed, then send cmd:
> > block_job_complete -f drive-ide0
> >
> > Step 3:
> > send cmd: info status
> > What surprised me is that the qemu monitor reports can’t be connected.
> >
> > Then find bellows:
> > The qemu process hangs on the
> > mirror_run->bdrv_drain_all->aio_poll->qemu_poll_ns->ppoll (), None
> > events were received and poll forever. I don’t know why the aio can’t be responsed. This case is hardly to be generated but it really
> happens sometimes . I’m looking forward to getting help from you .
> > The stack capture snapshot:
next prev parent reply other threads:[~2015-03-31 11:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-21 7:44 [Qemu-devel] [Bug 1434779] [NEW] qemu hangs on live-migration with storage(virtual machine: windows Server 2008 with only one disk ) youyunyehe
2015-03-21 7:45 ` [Qemu-devel] [Bug 1434779] " youyunyehe
2015-03-23 13:32 ` [Qemu-devel] [Bug 1434779] [NEW] " Stefan Hajnoczi
2015-03-31 11:03 ` Halsey Pian [this message]
2018-05-22 13:26 ` [Qemu-devel] [Bug 1434779] " Thomas Huth
2018-07-22 4:17 ` Launchpad Bug Tracker
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='010e01d06ba2$542550b0$fc6ff210$@gmail.com' \
--to=halsey.pian@gmail.com \
--cc=1434779@bugs.launchpad.net \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
/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).