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.
Just to make clear how is libvirt acting on migration with non-shared storage (just 'migration' hereafter). On migration request, the source checks for 'nbd-server-start' command (*) and advertises this fact to the destination libvirt. If the destination libvirt sees that the source knows NBD migration, it checks for the very same command, and adds all non-shared disks to the migration queue (via 'nbd-server-add'). If the command is not present, the old way of migration is assumed. The presence and successfulness of all nbd-server-* commands is then advertised back to the destination, which then just start 'drive-mirror' to all non-shared disks. Then, the source libvirt waits for storage migration to settle down after which the actual migration of RAM & internal state is started.
In case any of source or destination doesn't support 'nbd-server-start' the old way of migration is used.
So what we need here is:
1) disable 'blk' and 'inc' flags to 'migrate' command
2) hide/disable 'nbd-server-start' command
Doing just 1) (what is done here IIUC) is not enough for the reason mention above - if libvirt detects 'nbd-server-start' on both source and destination it won't even get to the 'blk' or 'inc' in migrate where an error would be thrown.
---
* - in fact, the command presence is checked on qemu startup and it's remembered. Moreover, if the command is presented all other nbd-server-* commands are assumed too. But their presence is not checked, though.
This request was resolved in Red Hat Enterprise Linux 7.0.
Contact your manager or support representative in case you have further questions about the request.