Bug 1387863 - migrating a live virtual removes autostart
Summary: migrating a live virtual removes autostart
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Virtualization Tools
Classification: Community
Component: libvirt
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Libvirt Maintainers
QA Contact: Fangge Jin
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-22 17:38 UTC by William H. Haller
Modified: 2024-12-17 12:11 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-12-17 12:11:51 UTC
Embargoed:


Attachments (Terms of Use)

Description William H. Haller 2016-10-22 17:38:30 UTC
Description of problem: Using centos-qemu-vm tools, when a virtual is migrated from one host to another, the autostart is removed from the source host, but is not recreated on the destination host.


Version-Release number of selected component (if applicable):1.2.17-13.el7_2.5. May well need to be a different component in qemu or kvm.


How reproducible: always


Steps to Reproduce:
1.Move via libvirt
2.
3.

Actual results: autostart flag is not created on target host if present on source host


Expected results: autostart status flag is created on target host if present on source host


Additional info:I know this is the centos-qemu-vm (required for snapshots), but I suspect it might be an issue with cor RHEL as well. If you migrate a host, it should retain the autostart feature if it was selected on the old host. We had an ASR last night on a HP host, but due to moving some virtuals around that day to balance over a new host, the flags weren't propagated. When the host came back up, it didn't start its virtuals.

Comment 2 Jiri Denemark 2016-10-24 08:34:20 UTC
> Steps to Reproduce:
> 1.Move via libvirt

Could you provide a little bit more details here, such as virsh command line or libvirt API and its parameters?

Comment 3 William H. Haller 2016-10-24 14:25:08 UTC
Libvirt version is 1.3.2

qemu-guest-agent 10:2.3.0-4.el7

qemu-img-ev, qemu-kvm-common-ev, qemu-kvm-ev, qemu-kvm-tools-ev 10:2.3.0-31.el7.16.1

Using qemu+ssh for connection.

Migrate mode direct via standard 49152 port. unsafe not checked, temporary move not checked.

Those are the only options I see on the GUI - but I'll provide any other info you need that I can find.

Comment 4 William H. Haller 2016-10-24 14:26:50 UTC
Also checked for selinux messages in audit log, but no references to anything in the autostart directory. The migrate itself works fine - just the autostart is missing.

Comment 5 William H. Haller 2016-10-24 14:30:23 UTC
Using virtual machine manager GUI version 1.3.2. Sorry - I'm usually better at bug reports.

Comment 6 zhe peng 2016-10-25 02:38:53 UTC
I can reproduce this with latest libvirt build: libvirt-2.0.0-10.el7.x86_64
on source:
# virsh list --all --autostart
 Id    Name                           State
----------------------------------------------------
 13    rhel7.3                        running

run migration cmd:
# virsh migrate --live rhel7.3 qemu+ssh://$target_host/system --verbose --persistent
Migration: [100 %]

check on target host:
# virsh list --all
 Id    Name                           State
----------------------------------------------------
 7     rhel7.3                        running

[root@dell-per730-37 ~]# virsh list --all --autostart
 Id    Name                           State
----------------------------------------------------

Comment 7 Daniel Berrangé 2024-12-17 12:11:51 UTC
Thank you for reporting this issue to the libvirt project. Unfortunately we have been unable to resolve this issue due to insufficient maintainer capacity and it will now be closed. This is not a reflection on the possible validity of the issue, merely the lack of resources to investigate and address it, for which we apologise. If you none the less feel the issue is still important, you may choose to report it again at the new project issue tracker https://gitlab.com/libvirt/libvirt/-/issues The project also welcomes contribution from anyone who believes they can provide a solution.


Note You need to log in before you can comment on or make changes to this bug.