blob: f125d35e52a7578e51766052f1d8509cf672aa0b (
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
43
44
45
46
47
48
49
50
51
52
53
54
|
x86: 0.881
device: 0.742
i386: 0.630
user-level: 0.589
graphic: 0.589
performance: 0.562
architecture: 0.524
semantic: 0.507
VMM: 0.491
mistranslation: 0.476
kernel: 0.460
network: 0.453
virtual: 0.444
socket: 0.444
vnc: 0.432
risc-v: 0.388
hypervisor: 0.371
permissions: 0.369
register: 0.354
ppc: 0.341
peripherals: 0.326
PID: 0.326
boot: 0.315
arm: 0.260
assembly: 0.232
files: 0.187
debug: 0.182
TCG: 0.144
KVM: 0.111
Cannot create cdrom device with open tray and cache option
When trying to create cdrom device with open tray and either of "cache" or "discard" options specified, I get the following error:
qemu-system-x86_64: -drive if=none,id=drive-ide0-0-0,readonly=on,cache=writeback,discard=unmap,throttling.iops-total=900: Must specify either driver or file
This bug essentially forbids live migration of VMs with open cdrom trays.
I was able to find the same bug at RedHat:
https://bugzilla.redhat.com/show_bug.cgi?id=1338638
The bug was encountered in versions 2.5 and 2.11.
Hi, versions 2.5 and 2.11 are quite old (though version 2.10 fixed the bug mentioned in the Red Hat BZ, so I think this might be a different bug.)
It's not clear at what step this is failing or where you are seeing the error message, so:
1. What is your full command line for QEMU?
2. Do you see this error message when migrating? If so, what does the destination QEMU command line look like?
3. Does the problem reproduce on a currently-supported upstream QEMU? (4.1.1, 4.2.0)
[Expired for QEMU because there has been no activity for 60 days.]
|