host_cdrom support is compiled out of qemu, for good reasons, as mentioned here:

https://bugzilla.redhat.com/show_bug.cgi?id=760885

Though the implementation means that any attempt to use /dev/sr0 through libvirt will fail. /dev/sr0 is detected as host_cdrom, qemu reports host_cdrom isn't available, and fails.

This breaks some prominent bits of virt-manager and boxes UI that expect to be able to attach a host cdrom device to a guest. There are bugs for that:

https://bugzilla.redhat.com/show_bug.cgi?id=1072611
https://bugzilla.redhat.com/show_bug.cgi?id=1072610

However it seems like less work and friendly for our users to just have qemu fall back to treating /dev/sr0 like it would any other block device, and not use the special host_cdrom integration.

This patch works for me, but may not be suitable as is:

diff --git a/block/raw-posix.c b/block/raw-posix.c
index 1688e16..7802724 100644
--- a/block/raw-posix.c
+++ b/block/raw-posix.c
@@ -2028,28 +2028,7 @@ static int cdrom_open(BlockDriverState *bs, QDict *option
 
 static int cdrom_probe_device(const char *filename)
 {
-    int fd, ret;
-    int prio = 0;
-    struct stat st;
-
-    fd = qemu_open(filename, O_RDONLY | O_NONBLOCK);
-    if (fd < 0) {
-        goto out;
-    }
-    ret = fstat(fd, &st);
-    if (ret == -1 || !S_ISBLK(st.st_mode)) {
-        goto outc;
-    }
-
-    /* Attempt to detect via a CDROM specific ioctl */
-    ret = ioctl(fd, CDROM_DRIVE_STATUS, CDSL_CURRENT);
-    if (ret >= 0)
-        prio = 100;
-
-outc:
-    qemu_close(fd);
-out:
-    return prio;
+    return 0;
 }


This may not solve the libvirt + /dev/sr0 + udev + selinux relabelling issues as linked in the host_cdrom bug report, I'm not sure (but they may have been due to a side effect of host_cdrom behavior, so perhaps they will be avoided). There may well be other reasons, but I think something along the above idea should be considered.