From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: marcandre.lureau@redhat.com, maxime.coquelin@redhat.com
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Hotplug ram and vhost-user
Date: Tue, 5 Dec 2017 17:41:00 +0000 [thread overview]
Message-ID: <20171205174100.GD2405@work-vm> (raw)
Hi,
Since I'm reworking the memory map update code I've been
trying to test it with hot adding RAM; but even on upstream
I'm finding that hot adding RAM causes the guest to stop passing
packets with vhost-user-bridge; have either of you seen the same
thing?
I'm doing:
./tests/vhost-user-bridge -u /tmp/vubrsrc.sock
$QEMU -enable-kvm -m 1G,maxmem=2G,slots=4 -smp 2 -object memory-backend-file,id=mem,size=1G,mem-path=/dev/shm,share=on -numa node,memdev=mem -mem-prealloc -trace events=vhost-trace-file -chardev socket,id=char0,path=/tmp/vubrsrc.sock -netdev type=vhost-user,id=mynet1,chardev=char0,vhostforce -device virtio-net-pci,netdev=mynet1 $IMAGE -net none
(with a f27 guest) and then doing:
(qemu) object_add memory-backend-file,id=mem1,size=256M,mem-path=/dev/shm
(qemu) device_add pc-dimm,id=dimm1,memdev=mem1
but then not getting any responses inside the guest.
I can see the code sending another set-mem-table with the
extra chunk of RAM and fd, and I think I can see the bridge
mapping it.
Dave
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next reply other threads:[~2017-12-05 17:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-05 17:41 Dr. David Alan Gilbert [this message]
2017-12-07 15:52 ` [Qemu-devel] Hotplug ram and vhost-user Maxime Coquelin
2017-12-07 15:56 ` Michael S. Tsirkin
2017-12-07 16:35 ` Maxime Coquelin
2017-12-07 16:55 ` Michael S. Tsirkin
2017-12-07 16:56 ` Michael S. Tsirkin
2017-12-07 16:25 ` Dr. David Alan Gilbert
2017-12-07 16:42 ` Maxime Coquelin
2017-12-07 18:23 ` Dr. David Alan Gilbert
2017-12-07 18:33 ` Maxime Coquelin
2017-12-07 18:57 ` Dr. David Alan Gilbert
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=20171205174100.GD2405@work-vm \
--to=dgilbert@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=maxime.coquelin@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.