[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-devel] [Bug 1802150] Re: Guest undefined when destroyed on host af
From: |
Dr. David Alan Gilbert |
Subject: |
[Qemu-devel] [Bug 1802150] Re: Guest undefined when destroyed on host after migration |
Date: |
Wed, 14 Nov 2018 09:19:08 -0000 |
Dan:
Rereading your description I think this might be worth discussing on the
libvirt mailing list/bug trackers instead.
I *think* what you're saying is the migration works fine, the only problem is
that after you shutdown the VM it disappears.
My understanding (although I'm more qemu than libvirt) is that you need to
pass --persistent to the virsh migrate command to get it to stick on the
destination. However, I'd expected that without --persistent it would have
still existed on the source after shutdown.
Given that big long VM name, is it being managed by some higher level
thing rather than directly?
--
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