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.
Bug 1690685 - Fail to force clone an empty cdrom device
Summary: Fail to force clone an empty cdrom device
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: virt-manager
Version: 8.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: rc
: 8.0
Assignee: Pavel Hrdina
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On: 1564863
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-20 02:26 UTC by Xiaodai Wang
Modified: 2020-11-14 08:58 UTC (History)
6 users (show)

Fixed In Version: virt-manager-2.2.0-1.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1564863
Environment:
Last Closed: 2019-11-05 21:19:40 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2019:3464 0 None None None 2019-11-05 21:20:05 UTC

Comment 1 Pavel Hrdina 2019-03-27 13:09:18 UTC 
Upstream commit:

commit 57db41854c86704af331d283810db0d86786825a
Author: Pavel Hrdina <phrdina>
Date:   Thu Feb 28 17:53:58 2019 +0100

    virt-clone: fix force-copy of empty cdrom or floppy disk
Comment 3 zhoujunqin 2019-08-02 10:44:22 UTC 
Reproduce with:
virt-manager-2.0.0-5.el8.noarch
virt-install-2.0.0-5.el8.noarch

Verify with:
virt-install-2.2.1-1.el8.noarch
virt-manager-2.2.1-1.el8.noarch
libvirt-4.5.0-31.module+el8.1.0+3808+3325c1a3.x86_64
qemu-kvm-2.12.0-82.module+el8.1.0+3738+0d8c0249.x86_64

Steps:
Scenario-1
1. Prepare a guest which has a cdrom disk and no path is set to the cdrom.

    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <target dev='sda' bus='sata'/>
      <readonly/>
      <address type='drive' controller='0' bus='0' target='0' unit='0'/>
    </disk>


2.Force copy the cdrom device during virt-clone.
2.1 
# virt-clone -o rhel7.7-clone -n rhel7.7-clone-new --auto-clone --force-copy sda 
Allocating 'rhel7.7-clone-new.qcow2'                                                                                                                                  | 7.0 GB  00:00:02     

Clone 'rhel7.7-clone-new' created successfully.

2.2 
#virsh dumpxml rhel7.7-clone-new.qcow2 | grep disk
    <disk type='file' device='disk'>
      <driver name='qemu' type='qcow2'/>
      <source file='/var/lib/libvirt/images/rhel7.7-clone-new.qcow2'/>
      <target dev='vda' bus='virtio'/>
      <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/>
    </disk>
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <target dev='sda' bus='sata'/>
      <readonly/>
      <address type='drive' controller='0' bus='0' target='0' unit='0'/>
    </disk>


Results:Cloning finishes successfully with the empty cdrom device and new guest can start successfully.

Scenario-2
1.Prepare a guest which has a floppy disk and no path is set to the floppy disk.

    <disk type='file' device='floppy'>
      <driver name='qemu' type='raw'/>
      <target dev='fda' bus='fdc'/>
      <address type='drive' controller='0' bus='0' target='0' unit='0'/>
    </disk>


2.Force copy the floppy device during virt-clone.
2.1 
# virt-clone -o rhel7.7-clone -n rhel7.7-clone-fdc --auto-clone --force-copy fdc
Allocating 'rhel7.7-clone-fdc.qcow2'                                                                                                                                                        | 7.0 GB  00:00:02     

Clone 'rhel7.7-clone-fdc' created successfully.


2.2
# virsh dumpxml rhel7.7-clone-fdc | grep disk
    <disk type='file' device='disk'>
      <driver name='qemu' type='qcow2'/>
      <source file='/var/lib/libvirt/images/rhel7.7-clone-fdc.qcow2'/>
      <target dev='vda' bus='virtio'/>
      <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/>
    </disk>
    <disk type='file' device='floppy'>
      <driver name='qemu' type='raw'/>
      <target dev='fda' bus='fdc'/>
      <address type='drive' controller='0' bus='0' target='0' unit='0'/>
    </disk>


Result:Cloning finishes successfully with floppy disk attached and new guest can start successfully.

So I move this bug from ON_QA to VERIFIED.
Comment 5 errata-xmlrpc 2019-11-05 21:19:40 UTC 
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, 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/RHSA-2019:3464
Note You need to log in before you can comment on or make changes to this bug.