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.

Description of problem:
ability to run 2 guest with the same name on one host (qemu process will not contain vm name just uuid)
Version-Release number of selected component (if applicable):
libvirt-4.5.0-10.el7_6.3.x86_64

How reproducible:
everytime

Steps to Reproduce:

1. create with name vmA on hostA
2. rename vmA while vm is running to vmA-1
3. create vm with name vmA on hostB
4. try to migrate vmA from hostB to hostA

Actual results:
migration fail with error:
libvirtError: operation failed: domain 'vmA' already exists with uuid b1486f27-ece8-49f2-9ed7-fc89cc147b30

Expected results:
vms will not contain the vm name just uuid of the vm thus migration will succeed

Additional info:

When running QEMU has a number of files on disk whose filename is based on the VM name. You can't have two QEMUs using the same filename concurrently, eg for QEMU monitor socket, so we must forbid having two guests with same the name. In addition from an mgmt application POV, the name has long been considered to be a unique identifier scoped to a host. If libvirt allowed 2 Vms with the same name it would break mgmt apps using name as unique identifier.