qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Michael Roth <mdroth@linux.vnet.ibm.com>
Cc: jasowang@redhat.com, Dietmar Maurer <dietmar@proxmox.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [Qemu-stable] [ANNOUNCE] QEMU 2.1.1 Stable released
Date: Thu, 11 Sep 2014 19:26:10 +0300	[thread overview]
Message-ID: <20140911162610.GA28605@redhat.com> (raw)
In-Reply-To: <20140911141140.32021.22872@loki>

On Thu, Sep 11, 2014 at 09:11:40AM -0500, Michael Roth wrote:
> Quoting Dietmar Maurer (2014-09-11 04:55:05)
> > Seems that we get a crash when we live-migrate a VMs using virtio-net-pci (vhost=on).
> > This worked in 2.1.0. Any ideas?
> 
> Is this what you're seeing on the source side?
> 
> qemu-system-x86_64: /home/mdroth/w/qemu3.git/hw/net/virtio-net.c:1348: virtio_net_save: Assertion `!n->vhost_started' failed. 
> 
> If so I can reproduce on both stable and current master. A bisect of master
> points to the following commit.
> 269bd822e7f5ab80048b05fb7076236ed66ffbce is the first bad commit
> commit 269bd822e7f5ab80048b05fb7076236ed66ffbce
> Author: Michael S. Tsirkin <mst@redhat.com>
> Date:   Thu Sep 4 13:32:54 2014 +0300
> 
>     virtio: don't call device on !vm_running
>     
>     On vm stop, virtio changes vm_running state
>     too soon, so callbacks can get envoked with
>     vm_running = false;
>     
>     Cc: qemu-stable@nongnu.org
>     Cc: Jason Wang <jasowang@redhat.com>
>     Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
>     Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
> 
> Any ideas Michael/Jason?

OK, I sent two patches to fix this. Will send upstream shortly, too.

> This is with:
> 
> qemu-system-x86_64 -enable-kvm -L build/build3-bios -M pc-i440fx-2.1 -m 512M -kernel boot/vmlinuz-x86_64 -initrd boot/test-initramfs-x86_64.img.gz -vga cirrus -append seed=1234 -drive file=disk1.img,if=virtio,cache=directsync -drive file=disk2.img,if=virtio -device virtio-net-pci,netdev=net0 -netdev tap,id=net0,vhost=on,script=/etc/qemu-ifup -incoming unix:/tmp/migrate.sock -monitor unix:/tmp/vm-hmp-incoming.sock,server,nowait -qmp unix:/tmp/vm-qmp-incoming.sock,server,nowait
> 
> Since this is such a common use-case of live migration I'll likely be putting out
> a minor 2.1.2 update once we identify the fix. I unfortunately didn't have vhost
> enabled in the migration tests, which was a pretty big oversight on my part.

Mee too :(

> > 
> > > I am pleased to announce that the QEMU v2.1.1 stable release is now available
> > > at:

      parent reply	other threads:[~2014-09-11 16:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-10 20:44 [Qemu-devel] [ANNOUNCE] QEMU 2.1.1 Stable released Michael Roth
2014-09-11  9:55 ` [Qemu-devel] [Qemu-stable] " Dietmar Maurer
2014-09-11 14:11   ` Michael Roth
2014-09-11 14:21     ` Michael S. Tsirkin
2014-09-11 16:26     ` Michael S. Tsirkin [this message]

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=20140911162610.GA28605@redhat.com \
    --to=mst@redhat.com \
    --cc=dietmar@proxmox.com \
    --cc=jasowang@redhat.com \
    --cc=mdroth@linux.vnet.ibm.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).