Bug 2038040
| Summary: | Clone a guest with sysinfo uuid failed | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | Lili Zhu <lizhu> |
| Component: | virt-manager | Assignee: | Jonathon Jongsma <jjongsma> |
| virt-manager sub component: | Common | QA Contact: | Hongzhou Liu <hongzliu> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | low | ||
| Priority: | low | CC: | crobinso, hongzliu, jsuchane, juzhou, meili, tyan, tzheng, virt-maint, xuzhang |
| Version: | 9.0 | Keywords: | Triaged |
| Target Milestone: | rc | Flags: | pm-rhel:
mirror+
|
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | virt-manager-4.1.0-1.el9 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-05-09 07:39:17 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 2135791 | ||
| Bug Blocks: | |||
virt-clone would need to adjust the uuid element of sysinfo too. Thanks for the report. This is fixed upstream now:
commit b0d0516736320315a70f74aff3759fb35dd35d9d (HEAD -> main)
Author: Cole Robinson <crobinso>
Date: Sun Aug 21 16:21:10 2022 -0400
cloner: Sync <uuid> and <sysinfo> system uuid
Jonathon - for when you do the next virt-manager rebase. Pre-verify this bug with:
libvirt-8.9.0-2.el9.x86_64
virt-install-4.1.0-1.el9.noarch
Step 1:
1.define a guest with the following xml snippet
# virsh dumpxml rhel9
<domain type='kvm'>
<name>rhel9</name>
<uuid>be2137b2-e265-4102-897f-0320a829a55a</uuid>
...
<sysinfo type='smbios'>
<system>
<entry name='uuid'>be2137b2-e265-4102-897f-0320a829a55a</entry>
</system>
</sysinfo>
...
2. clone the guest
# virt-clone -o rhel9 -n rhel9-clone --auto-clone
Allocating 'rhel9-5-clone-1.qcow2' | 1.6 GB 00:00:12 ...
Clone 'rhel9-clone' created successfully.
Test result, guest can be cloned successfully
Based on this, I add verified:tested flag, Thanks
Verify this bug on latest RHEL9.2
packages:
virt-install-4.1.0-2.el9.noarch
libvirt-8.10.0-2.el9.x86_64
qemu-kvm-7.2.0-3.el9.x86_64
Step 1:
1.define a guest with the following xml snippet
# virsh dumpxml rhel9u2
<domain type='kvm'>
<name>rhel9u2</name>
<uuid>14bddeec-7977-4796-abb3-3fcdc761951e</uuid>
...
<sysinfo type='smbios'>
<system>
<entry name='uuid'>14bddeec-7977-4796-abb3-3fcdc761951e</entry>
</system>
</sysinfo>
...
2. clone the guest
# virt-clone -o rhel9u2 -n rhel9-clone --auto-clone
Allocating 'rhel9-clone.qcow2' | 1.7 GB 00:00:17 ...
Clone 'rhel9-clone' created successfully.
3: check the xml for rhel9-clone:
<domain type='kvm'>
<name>rhel9u2</name>
<uuid>14bddeec-7977-4796-abb3-3fcdc761951e</uuid>
...
<sysinfo type='smbios'>
<system>
<entry name='uuid'>14bddeec-7977-4796-abb3-3fcdc761951e</entry>
</system>
</sysinfo>
...
Test result, guest can be cloned successfully and the uuid for clone guest is the same with origin guest.
Based on this, I change the status to VERIFIED, Thanks
Correct my verify steps,
1.define a guest with the following xml snippet
# virsh dumpxml rhel9u2
<domain type='kvm'>
<name>rhel9u2</name>
<uuid>14bddeec-7977-4796-abb3-3fcdc761951e</uuid>
...
<sysinfo type='smbios'>
<system>
<entry name='uuid'>14bddeec-7977-4796-abb3-3fcdc761951e</entry>
</system>
</sysinfo>
...
2. clone the guest
# virt-clone -o rhel9u2 -n rhel9-clone --auto-clone
Allocating 'rhel9-clone.qcow2' | 1.7 GB 00:00:17 ...
Clone 'rhel9-clone' created successfully.
3: check the xml for rhel9-clone:
<domain type='kvm'>
<name>rhel9-clone</name>
<uuid>dba4bc4e-1b19-4024-99ac-3b9664ab66c0</uuid>
...
<sysinfo type='smbios'>
<system>
<entry name='uuid'>dba4bc4e-1b19-4024-99ac-3b9664ab66c0</entry>
</system>
</sysinfo>
...
Test result, guest can be cloned successfully.(virt-clone will generate a new uuid for clone guest)
Based on this, I change the status to VERIFIED, Thanks
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (virt-manager bug fix and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2023:2255 |
Description of problem: Clone a guest with sysinfo uuid failed Version-Release number of selected component (if applicable): virt-install-3.2.0-11.el9.noarch libvirt-7.10.0-1.el9.x86_64 How reproducible: 100% Steps to Reproduce: 1.define a guest with the following xml snippet # virsh dumpxml avocado-vt-vm1 <domain type='kvm'> <name>avocado-vt-vm1</name> <uuid>80d5908b-4402-4a91-8465-6e3f16541215</uuid> ... <sysinfo type='smbios'> <system> <entry name='uuid'>80d5908b-4402-4a91-8465-6e3f16541215</entry> </system> </sysinfo> ... 2. clone the guest # virt-clone -o avocado-vt-vm1 -n clone --auto-clone ERROR UUID mismatch between <uuid> and <sysinfo> Actual results: Cloning failed Expected results: Cloning succeed Additional info: If I define a guest whose UUID mismatch between <uuid> and <sysinfo>, then it will report the same error # virsh define avocado-vt-vm1.xml error: Failed to define domain from avocado-vt-vm1.xml error: UUID mismatch between <uuid> and <sysinfo> I guess when clone the guest, it will generate a new uuid for the new guest, but this new uuid will not be applied to the sysinfo uuid. sysinfo uuid in new guest remains the same with the one in orginal guest. Then libvirt will report the above error. Please help to check.