blob: c041d24dd6ab36656be535ad8d330716436c20c9 (
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
|
other: 0.195
device: 0.176
semantic: 0.143
files: 0.115
graphic: 0.073
vnc: 0.048
PID: 0.036
network: 0.036
debug: 0.034
performance: 0.032
boot: 0.030
permissions: 0.029
socket: 0.027
KVM: 0.025
other: 0.181
debug: 0.138
files: 0.134
semantic: 0.131
device: 0.129
performance: 0.050
boot: 0.048
network: 0.043
PID: 0.043
permissions: 0.034
socket: 0.029
graphic: 0.017
vnc: 0.017
KVM: 0.007
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.]
|