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.

(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?

This should have been fixed by

commit d7db33bfe978c89e1302609ac91e65be3d49379f
Author: Michal Privoznik <mprivozn@redhat.com>
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@redhat.com>

so using the latest libvirt package should be enough.

There is no specific reasons to stick with older version. I can re-test when new compose is ready.

$ git describe d7db33bfe978c89e1302609ac91e65be3d49379f --match=v*
v1.3.0-166-gd7db33b

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.

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.

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