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 1332705 - libvirt is incompatible with qemu-rhev-2.6 with empty CDROM drive
Summary: libvirt is incompatible with qemu-rhev-2.6 with empty CDROM drive
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libvirt
Version: 7.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Libvirt Maintainers
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks: 1173757
TreeView+ depends on / blocked
 
Reported: 2016-05-03 20:53 UTC by Wei Huang (AMD)
Modified: 2016-11-03 18:44 UTC (History)
8 users (show)

Fixed In Version: libvirt-1.3.2-1.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-03 18:44:14 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2016:2577 0 normal SHIPPED_LIVE Moderate: libvirt security, bug fix, and enhancement update 2016-11-03 12:07:06 UTC

Comment 2 Jiri Denemark 2016-05-04 08:11:17 UTC 
Is there a reason for using ancient libvirt packages for aarch64 with a current development snapshot of qemu-kvm-rhev? The latest-RHELSA-VIRT-7 is about a year old. The current libvirt packages for aarch64 are 1.3.4-1.el7.aarch64.
Comment 3 Andrew Jones 2016-05-04 09:13:26 UTC 
(In reply to Jiri Denemark from comment #2)
> Is there a reason for using ancient libvirt packages for aarch64 with a
> current development snapshot of qemu-kvm-rhev? The latest-RHELSA-VIRT-7 is
> about a year old. The current libvirt packages for aarch64 are
> 1.3.4-1.el7.aarch64.

No reason. The batcave repo should be getting the latest build soon. Wei, can you retry after batcave gets the update?
Comment 4 Andrea Bolognani 2016-05-04 10:21:11 UTC 
This should have been fixed by

commit d7db33bfe978c89e1302609ac91e65be3d49379f
Author: Michal Privoznik <mprivozn>
Date:   Mon Dec 28 15:13:52 2015 +0100

    qemu: Specify format= iff disk source is not empty
    
    Just recently, qemu forbade specifying format for sourceless
    disks (qemu commit 39c4ae941ed992a3bb5). It kind of makes sense.
    If there's no file to open, why specify its format. Anyway, I
    have a domain like this:
    
        <disk type='file' device='cdrom'>
          <driver name='qemu' type='raw'/>
          <target dev='hda' bus='ide'/>
          <readonly/>
          <address type='drive' controller='0' bus='0' target='0' unit='0'/>
        </disk>
    
    and obviously I am unable to start it. Therefore, a fix on our
    side is needed too.
    
    Signed-off-by: Michal Privoznik <mprivozn>

so using the latest libvirt package should be enough.
Comment 5 Wei Huang (AMD) 2016-05-04 14:36:37 UTC 
There is no specific reasons to stick with older version. I can re-test when new compose is ready.
Comment 6 Peter Krempa 2016-05-05 06:27:54 UTC 
$ git describe d7db33bfe978c89e1302609ac91e65be3d49379f --match=v*
v1.3.0-166-gd7db33b
Comment 7 lijuan men 2016-05-06 06:51:56 UTC 
test the bug in x86 host:

result:
the problem is not reproduced.

version:
libvirt-1.3.4-1.el7.x86_64
qemu-kvm-rhev-2.5.0-4.el7.x86_64
kernel-3.10.0-390.el7.x86_64

step:
1.install a guest
[root@localhost ~]# virt-install -n r7 --cdrom ./RHEL-7.2-20151030.0-Server-x86_64-dvd1.iso  --boot uefi --vcpus=1 -r 2048 --disk size=6 --network default

After installation and reboot, the guest reboots successfully，and there is no error  showed above.
Comment 9 lijuan men 2016-09-06 02:55:58 UTC 
verify the bug on x86

version:
libvirt-2.0.0-6.el7.x86_64
qemu-kvm-rhev-2.6.0-22.el7.x86_64

steps:
1)prepare a guest with the following xml:
<disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <target dev='hda' bus='ide'/>
      <readonly/>
      <address type='drive' controller='0' bus='0' target='0' unit='0'/>
    </disk>
2)start the guest
[root@localhost ~]# virsh start bios
Domain bios started

[root@localhost ~]#ps -ef | grep drive
....-drive if=none,id=drive-ide0-0-0,readonly=on....

the result is expected.
Comment 11 errata-xmlrpc 2016-11-03 18:44:14 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://rhn.redhat.com/errata/RHSA-2016-2577.html
Note You need to log in before you can comment on or make changes to this bug.