From: Stefan Hajnoczi <stefanha@redhat.com>
To: qemu-devel@nongnu.org
Cc: haozhong.zhang@intel.com, Xiao Guangrong <xiaoguangrong@tencent.com>
Subject: [Qemu-devel] NVDIMM live migration broken?
Date: Thu, 22 Jun 2017 15:08:27 +0100 [thread overview]
Message-ID: <20170622140827.GA29936@stefanha-x1.localdomain> (raw)
[-- Attachment #1: Type: text/plain, Size: 894 bytes --]
I tried live migrating a guest with NVDIMM on qemu.git/master (edf8bc984):
$ qemu -M accel=kvm,nvdimm=on -m 1G,slots=4,maxmem=8G -cpu host \
-object memory-backend-file,id=mem1,share=on,mem-path=nvdimm.dat,size=1G \
-device nvdimm,id=nvdimm1,memdev=mem1 \
-drive if=virtio,file=test.img,format=raw
$ qemu -M accel=kvm,nvdimm=on -m 1G,slots=4,maxmem=8G -cpu host \
-object memory-backend-file,id=mem1,share=on,mem-path=nvdimm.dat,size=1G \
-device nvdimm,id=nvdimm1,memdev=mem1 \
-drive if=virtio,file=test.img,format=raw \
-incoming tcp::1234
(qemu) migrate tcp:127.0.0.1:1234
The guest kernel panics or hangs every time on the destination. It
happens as long as the nvdimm device is present - I didn't even mount it
inside the guest.
Is migration expected to work?
If not we need a migration blocker so that users get a graceful error
message.
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
next reply other threads:[~2017-06-22 14:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-22 14:08 Stefan Hajnoczi [this message]
2017-06-23 0:13 ` [Qemu-devel] NVDIMM live migration broken? haozhong.zhang
2017-06-23 9:55 ` Stefan Hajnoczi
2017-06-26 2:05 ` Haozhong Zhang
2017-06-26 12:56 ` Stefan Hajnoczi
2017-06-27 14:30 ` Haozhong Zhang
2017-06-27 16:58 ` Juan Quintela
2017-06-27 18:12 ` Juan Quintela
2017-06-28 10:05 ` Stefan Hajnoczi
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=20170622140827.GA29936@stefanha-x1.localdomain \
--to=stefanha@redhat.com \
--cc=haozhong.zhang@intel.com \
--cc=qemu-devel@nongnu.org \
--cc=xiaoguangrong@tencent.com \
/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).