Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

+++ This bug was initially created as a clone of Bug #881092 +++

Description of problem:

Unable to migrate VM which is not running.

Virt-manager UI disables migration (Migrate...) option when machine is  Shutoff. When the machine is running Migrate... option is enabled.

It seems to me pointless to run machine to be able to select 'Migrate... -> Migrate offline'.

Version-Release number of selected component (if applicable):
libvirt-0.9.11.7-1.fc17.x86_64
libvirt-client-0.9.11.7-1.fc17.x86_64
libvirt-daemon-0.9.11.7-1.fc17.x86_64
libvirt-daemon-config-network-0.9.11.7-1.fc17.x86_64
libvirt-daemon-config-nwfilter-0.9.11.7-1.fc17.x86_64
libvirt-python-0.9.11.7-1.fc17.x86_64
python-virtinst-0.600.3-2.fc17.noarch
qemu-kvm-1.0.1-2.fc17.x86_64
redland-virtuoso-1.0.15-1.fc17.x86_64
virt-manager-0.9.4-2.fc17.noarch
virt-manager-common-0.9.4-2.fc17.noarch
virt-viewer-0.5.3-1.fc17.x86_64
virtuoso-opensource-6.1.6-1.fc17.x86_64


How reproducible:
100%

Steps to Reproduce:
1. at least one machine created
2. start 'virt-manager'
3. right-click -> Migrate... (unable to select)
  
Actual results:
Migration of shutoff machine is disabled.

Expected results:
Migration of shutoff machine should be enabled.

Additional info:

The same problem occurs in current RHEL6.3 virt-manager as well.
  fence-virt-0.2.3-9.el6.x86_64
  libvirt-0.9.10-21.el6_3.6.x86_64
  libvirt-client-0.9.10-21.el6_3.6.x86_64
  libvirt-python-0.9.10-21.el6_3.6.x86_64
  python-virtinst-0.600.0-8.el6.noarch
  qemu-kvm-0.12.1.2-2.295.el6_3.2.x86_64
  virt-manager-0.9.0-14.el6.x86_64
  virt-what-1.11-1.1.el6.x86_64
  virt-who-0.6-6.el6.noarch
  virtio-win-1.5.3-1.el6_3.noarch

This is not always wanted behaviour, because when the machine gets "offline-migrated" with current APIs (dumpxml -> define), there is no QEMU ran on target host as well as no migration hook performed for that domain XML.  New API might get this fixed (or improved, I'd say), so before this gets done in virt-manager, this will (most probably) be cloned for libvirt.

In comment #2, I forgot to mention the (obvious) workaround for this at least with virsh:

 # virsh -c <connection_uri> dumpxml <machine_name> >machine.xml
 # virsh -c <migration_uri> define machine.xml &&
       virsh -c <connection_uri> undefine <machine_name>

But as I said, this doesn't go through migration hooks, there is no check for supported features etc.