qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Bharata B Rao <bharata@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Cc: david@gibson.dropbear.id.au, groug@kaod.org, mst@redhat.com
Subject: [Qemu-devel] QEMU terminates during reboot after memory unplug with vhost=on
Date: Thu, 14 Sep 2017 12:31:18 +0530	[thread overview]
Message-ID: <20170914070118.GA8181@in.ibm.com> (raw)

Hi,

QEMU hits the below assert

qemu-system-ppc64: used ring relocated for ring 2
qemu-system-ppc64: qemu/hw/virtio/vhost.c:649: vhost_commit: Assertion `r >= 0' failed.

in the following scenario:

1. Boot guest with vhost=on
  -netdev tap,id=mynet0,script=qemu-ifup,downscript=qemu-ifdown,vhost=on -device virtio-net-pci,netdev=mynet0
2. Hot add a DIMM device 
3. Reboot
   When the guest reboots, we can see
   vhost_virtqueue_start:vq->used_phys getting assigned an address that
   falls in the hotplugged memory range.
4. Remove the DIMM device
   Guest refuses the removal as the hotplugged memory is under use.
5. Reboot
   QEMU forces the removal of the DIMM device during reset and that's
   when we hit the above assert.

Any pointers on why we are hitting this assert ? Shouldn't vhost be
done with using the hotplugged memory when we hit reset ?

Regards,
Bharata.

             reply	other threads:[~2017-09-14  7:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-14  7:01 Bharata B Rao [this message]
2017-09-14  8:00 ` [Qemu-devel] QEMU terminates during reboot after memory unplug with vhost=on Igor Mammedov
2017-09-14  8:18   ` Bharata B Rao
2017-09-14  8:59     ` Igor Mammedov
2017-09-14 10:20       ` Bharata B Rao
2017-10-16 10:08       ` Bharata B Rao
  -- strict thread matches above, loose matches on Subject: below --
2017-11-16 12:23 Greg Kurz
2017-11-16 15:28 ` Michael S. Tsirkin
2017-11-16 15:34   ` Greg Kurz
2017-11-16 15:53   ` Alex Williamson
2017-11-16 15:59     ` Michael S. Tsirkin
2017-11-16 16:04       ` Alex Williamson
2017-11-16 16:17         ` Michael S. Tsirkin

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=20170914070118.GA8181@in.ibm.com \
    --to=bharata@linux.vnet.ibm.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=groug@kaod.org \
    --cc=mst@redhat.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).