This was done with virsh on the cli - not through virt-manager. Virt manager was only used to see the visual residence of the vm. The exact command is below:
virsh migrate 79fdd9dd-068b-41cc-b97b-d0f9d8e9df84 --desturi qemu+ssh://kvmadmin@192.168.0.84/system after migrating, shutting down the guest vm results in destruction of vm (undefined) Thanks, Dan On 11/07/2018 02:33 PM, Thomas Huth wrote: > This is the QEMU bug tracker here ... Can you also reproduce such an > issue with plain QEMU? If not, could you please report this to the virt- > manager project first? See https://virt-manager.org/bugs/#report for > details. > > ** Changed in: qemu > Status: New => Incomplete > -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1802150 Title: Guest undefined when destroyed on host after migration Status in QEMU: Incomplete Bug description: After a live migration, guest VMs are being undefined from the host they were migrated to after shutdown. I have experienced this at two (2) separate locations on more than one hardware configuration. This happens when utilizing virt-manager to view current allocations on hosts, and virsh on the CLI to migrate guests. When the guest is migrated from one host to another, no errors are thrown, and only lose 1 packet from infinite ping. Shutting guest down *from* the guest OS results in the Guest VM being undefined on the residing host, and XML config lost. If needed, I can provide a recorded session of this happening. Thanks, Dan To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1802150/+subscriptions