From: Peter Lieven <pl@kamp.de>
To: John Snow <jsnow@redhat.com>, qemu-block@nongnu.org
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [Qemu-block] Migration sometimes fails with IDE and Qemu 2.2.1
Date: Mon, 06 Apr 2015 21:10:25 +0200 [thread overview]
Message-ID: <5522DA21.1010702@kamp.de> (raw)
In-Reply-To: <5522D85D.20907@kamp.de>
Am 06.04.2015 um 21:02 schrieb Peter Lieven:
> Am 06.04.2015 um 20:50 schrieb John Snow:
>>
>> On 04/06/2015 02:47 PM, Peter Lieven wrote:
>>> Hi all,
>>>
>>> is there a known issue in Qemu 2.2.1 where IDE stalls sometimes after a migration with Qemu 2.2.1?
>>> The migration succeeds, but it seems that the complete I/O is hanging. This happens only sometimes
>>> and only with extreme old Linux Guests (SLES 10 with Kernel 2.6.16) thus the IDE controller as
>>> storage controller for the system disk.
>>>
>>> Maybe this sounds familiar to someone.
>>>
>>> Thank you,
>>> Peter
>>>
>> It's news to me.
> Okay, I was hoping that I just missed a patch or someone forgot to CC qemu-stable... :-)
>
>> Is this a regression?
> I can't say we see those vServers hang sometime after migration since we changed the hypervisor from qemu-kvm-1.2.0 to qemu-2.2.0.
>
>
>> Any particular workload or reproducer?
> Workload is almost zero. I try to figure out if there is a way to trigger it.
>
> Maybe playing a role: Machine type is -M pc1.2 and we set -kvmclock as
> CPU flag since kvmclock seemed to be quite buggy in 2.6.16...
>
> Exact cmdline is:
> /usr/bin/qemu-2.2.1 -enable-kvm -M pc-1.2 -nodefaults -netdev type=tap,id=guest2,script=no,downscript=no,ifname=tap2 -device e1000,netdev=guest2,mac=52:54:00:ff:00:65 -drive format=raw,file=iscsi://172.21.200.53/iqn.2001-05.com.equallogic:4-52aed6-88a7e99a4-d9e00040fdc509a3-XXX-hd0/0,if=ide,cache=writeback,aio=native -serial null -parallel null -m 1024 -smp 2,sockets=1,cores=2,threads=1 -monitor tcp:0:4003,server,nowait -vnc :3 -qmp tcp:0:3003,server,nowait -name 'XXX' -boot order=c,once=dc,menu=off -drive index=2,media=cdrom,if=ide,cache=unsafe,aio=native,readonly=on -k de -incoming tcp:0:5003 -pidfile /var/run/qemu/vm-146.pid -mem-path /hugepages -mem-prealloc -rtc base=utc -usb -usbdevice tablet -no-hpet -vga cirrus -cpu qemu64,-kvmclock
>
> Exact kernel is:
> 2.6.16.46-0.12-smp (i think this is SLES10 or sth.)
>
> The machine does not hang. It seems just I/O is hanging. So you can type at the console or ping the system, but no longer login.
>
> Thank you,
> Peter
Interesting observation: Migrating the vServer again seems to fix to problem (at least in one case I could test just now).
2.6.8-24-smp is also affected.
Thanks,
Peter
next prev parent reply other threads:[~2015-04-06 19:10 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-06 18:47 [Qemu-devel] Migration sometimes fails with IDE and Qemu 2.2.1 Peter Lieven
2015-04-06 18:50 ` [Qemu-devel] [Qemu-block] " John Snow
2015-04-06 19:02 ` Peter Lieven
2015-04-06 19:10 ` Peter Lieven [this message]
2015-04-07 8:43 ` Dr. David Alan Gilbert
2015-04-07 15:11 ` Peter Lieven
2015-04-07 15:14 ` Paolo Bonzini
2015-04-07 18:54 ` Peter Lieven
2015-04-07 15:29 ` Dr. David Alan Gilbert
2015-04-07 18:44 ` Peter Lieven
2015-04-07 18:56 ` John Snow
2015-04-07 19:02 ` Peter Lieven
2015-04-07 19:13 ` John Snow
2015-04-09 6:34 ` Peter Lieven
2015-04-09 12:46 ` Peter Lieven
2015-04-09 12:50 ` Paolo Bonzini
2015-04-07 19:01 ` Dr. David Alan Gilbert
2015-04-07 19:04 ` Peter Lieven
2015-04-09 12:49 ` Peter Lieven
2015-04-09 13:32 ` Peter Lieven
2015-04-09 13:43 ` Dr. David Alan Gilbert
2015-04-09 14:54 ` Peter Lieven
2015-04-09 15:17 ` Paolo Bonzini
2015-04-11 13:11 ` Peter Lieven
2015-04-11 15:00 ` Peter Lieven
2015-04-13 7:20 ` Peter Lieven
2015-04-07 20:05 ` Paolo Bonzini
2015-04-09 6:43 ` Peter Lieven
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=5522DA21.1010702@kamp.de \
--to=pl@kamp.de \
--cc=jsnow@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.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).