From: Paolo Bonzini <pbonzini@redhat.com>
To: Chris Friesen <chris.friesen@windriver.com>,
Amit Shah <amit.shah@redhat.com>
Cc: qemu-devel@nongnu.org, armbru@redhat.com
Subject: Re: [Qemu-devel] virtio-serial-pci very expensive during live migration
Date: Fri, 09 May 2014 10:19:09 +0200 [thread overview]
Message-ID: <536C8F7D.2050302@redhat.com> (raw)
In-Reply-To: <536C2712.3030803@windriver.com>
Il 09/05/2014 02:53, Chris Friesen ha scritto:
>
>
> Turns out I spoke too soon. With the patch applied, it boots, but if I
> try to do a live migration both the source and destination crash. This
> happens for both the master branch as well as the stable-1.4 branch.
The destination doesn't crash, it simply stops because it got an
incomplete migration stream. Thanks for the report, the patch seems
correct so it's worthwhile looking at it more closely.
> If I back out the patch, it works fine. If I leave the patch in and
> disable kvm acceleration it works fine.
Indeed, non-KVM doesn't use ioeventfd at all.
Paolo
next prev parent reply other threads:[~2014-05-09 8:19 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-06 20:01 [Qemu-devel] virtio-serial-pci very expensive during live migration Chris Friesen
2014-05-07 5:58 ` Markus Armbruster
2014-05-07 6:39 ` Paolo Bonzini
2014-05-07 22:25 ` Chris Friesen
2014-05-08 13:02 ` Amit Shah
2014-05-08 13:14 ` Paolo Bonzini
2014-05-08 13:30 ` Amit Shah
2014-05-08 13:36 ` Paolo Bonzini
2014-05-08 13:47 ` Amit Shah
2014-05-08 15:40 ` Chris Friesen
2014-05-09 0:53 ` Chris Friesen
2014-05-09 8:19 ` Paolo Bonzini [this message]
2014-06-19 15:19 ` Chris Friesen
2014-06-19 15:31 ` Paolo Bonzini
2014-05-08 14:31 ` Chris Friesen
2014-05-08 14:34 ` Paolo Bonzini
2014-05-08 15:57 ` Chris Friesen
2014-05-08 16:02 ` Paolo Bonzini
2014-05-08 20:57 ` Chris Friesen
2014-05-09 1:44 ` ChenLiang
2014-05-09 3:31 ` Chris Friesen
2014-05-08 2:54 ` Gonglei (Arei)
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=536C8F7D.2050302@redhat.com \
--to=pbonzini@redhat.com \
--cc=amit.shah@redhat.com \
--cc=armbru@redhat.com \
--cc=chris.friesen@windriver.com \
--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).