diff options
Diffstat (limited to 'results/classifier/118/none/588691')
| -rw-r--r-- | results/classifier/118/none/588691 | 52 |
1 files changed, 52 insertions, 0 deletions
diff --git a/results/classifier/118/none/588691 b/results/classifier/118/none/588691 new file mode 100644 index 000000000..5d77e77bf --- /dev/null +++ b/results/classifier/118/none/588691 @@ -0,0 +1,52 @@ +kernel: 0.734 +performance: 0.725 +device: 0.690 +architecture: 0.585 +network: 0.545 +semantic: 0.539 +graphic: 0.529 +PID: 0.528 +mistranslation: 0.527 +permissions: 0.413 +boot: 0.399 +peripherals: 0.374 +register: 0.365 +risc-v: 0.334 +vnc: 0.332 +ppc: 0.331 +debug: 0.329 +files: 0.315 +socket: 0.280 +user-level: 0.271 +hypervisor: 0.264 +arm: 0.241 +i386: 0.192 +x86: 0.172 +VMM: 0.160 +TCG: 0.159 +assembly: 0.130 +KVM: 0.123 +virtual: 0.085 + +QEMU is not correctly detecting host CDs + +QEMU's block layer contains code for detecting and using ioctls when real CD-ROM host devices are attached. + +This detection is not working in some host OSes while bad implemented on anothers. + +E.g., in Linux host qemu -cdrom /dev/sr0 is not detecting it as a CD-ROM +E.g., in Mac OS X host qemu asks the kernel to enumerate optical devices and the compares it to the constant string "/dev/cdrom". This is useless, that enumeration is just enough, and "/dev/cdrom" will NEVER exist in Mac OS X unless manually created by the user. + +The linux /dev/sr0 issue should be fixed upstream: + +http://git.savannah.gnu.org/cgit/qemu.git/commit/?id=3baf720e6b920d583ce2834d05e5a4e9603a1d56 + +Maybe it's worth a backport to stable + +Looking through old bug tickets... can you still reproduce this issue with the latest version of QEMU? Or could we close this ticket nowadays? + + +I use real CD-ROM disc in Mac OS and Windows guests on my Mac OS 10.12 host. I have to run QEMU in root mode using the sudo command in order to access the CD-ROM drive. So I know QEMU's support for using real optical media on Mac OS hosts does work. + +OK, thanks for the confirmation, John, so seems like this bug has been fixed in the past and we can close it now. + |