blob: e5110301a14106e6dd3166713b029ae1d8be1e5e (
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
|
device: 0.767
graphic: 0.661
architecture: 0.525
network: 0.522
mistranslation: 0.494
files: 0.487
semantic: 0.463
vnc: 0.438
register: 0.436
performance: 0.412
i386: 0.390
permissions: 0.368
ppc: 0.347
PID: 0.341
hypervisor: 0.340
debug: 0.335
x86: 0.334
peripherals: 0.321
socket: 0.316
risc-v: 0.296
assembly: 0.283
kernel: 0.269
boot: 0.261
VMM: 0.260
user-level: 0.246
TCG: 0.218
KVM: 0.199
virtual: 0.195
arm: 0.184
add next free device option to qemu-img
I'd like to propose an option to be added to qemu-img which returns the next free NBD (the device file) very similar to losetup -f. It would make life a lot easier.
Followers of this enhancement request might be interested in the following workaround: http://stackoverflow.com/questions/22535222/next-free-device-option-for-qemu-nbd/
The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to "Incomplete" now.
If you still think this bug report here is valid, then please switch the state back to "New" within the next 60 days, otherwise this report will be marked as "Expired". Or mark it as "Fix Released" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience.
[Expired for QEMU because there has been no activity for 60 days.]
|