[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1719282
Title:
Unable to
OK, so we're only talking about migrating a disk and not a whole VM, I
misunderstood. However... are you using qemu *2.7*? That's quite old!
Before digging into this further I need to insist that you try on a
supported release, either 4.0.1, 4.1.1, or 4.2.0.
** Changed in: qemu
Status: New
There is no source or destination machine. I used drive-mirror to
transfer VM Image to different physical disk on same machine ("mode":
"absolute-paths"). After block-job-complete and shutting down vm, I
start vm again with same command with different drive path pointing to
mirrored image. "-drive
It *looks* to me at a glance like the sequence should be safe, but I
don't have any hunches for what could be going wrong, or why.
Can you please post:
(1) The command-line used to launch QEMU on the source machine, and
(2) The command-line used to launch QEMU on the destination machine from the
In last try, vm shutdown before completing blockjob.
So i tried again and these are the exact qmp commands which i used:
Sequence of qmp commands:
socat UNIX-CONNECT:/var/run/qemu-server/48016.qmp STDIO
{"QMP": {"version": {"qemu": {"micro": 0, "minor": 7, "major": 2}, "package":
Do you have more information on the sequence of commands issued to QEMU?
I see the drive-mirror invocation, but then I don't see what causes the
shutdown or the BLOCK_JOB_COMPLETED event. Usually this is in response
to a user command. I'm wondering if the exact sequence issued is safe.
Do you
