blob: 6b70cee5e80bfadd04651c104a31371d0a4ea9c8 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
|
graphic: 0.843
device: 0.833
performance: 0.720
architecture: 0.667
mistranslation: 0.657
semantic: 0.635
socket: 0.612
register: 0.610
kernel: 0.598
PID: 0.570
permissions: 0.561
user-level: 0.538
risc-v: 0.528
network: 0.515
files: 0.481
boot: 0.473
ppc: 0.471
vnc: 0.467
i386: 0.456
peripherals: 0.445
KVM: 0.437
TCG: 0.435
VMM: 0.414
assembly: 0.385
x86: 0.384
debug: 0.369
hypervisor: 0.356
arm: 0.320
virtual: 0.190
Hard disk images are supporting ATAPI commands. They should fail.
When using a hard disk image (qcow, qcow2, vdi, vmdk, bochs), the emulated device can be a CD-ROM and support ATAPI commands.
These commands fails in real hard disks and these images are not prepared to handle optical disk formats, they should fail also.
Only images able to handle that formats (dmg, raw, host) should work with ATAPI commands and CD-ROM devices.
Looking through old bug tickets ... is this still an issue with the latest version of QEMU, or could we close this ticket nowadays?
[Expired for QEMU because there has been no activity for 60 days.]
|
