summary refs log tree commit diff stats
path: root/results/classifier/zero-shot/108/other/1659267
blob: 52810909445b02feecaf01df84b1d4faf97fce6c (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
other: 0.726
graphic: 0.709
network: 0.690
performance: 0.627
device: 0.618
semantic: 0.561
vnc: 0.490
socket: 0.394
permissions: 0.372
PID: 0.370
files: 0.320
debug: 0.288
boot: 0.268
KVM: 0.184

It's not possible to start a VM with a network cable unplugged

There should be a command line (sub)option to unplug a network cable.
While from the monitor interface I can issue:

set_link virtio-net-pci.0 off

There's no way to fire a VM from command line with that cable already unplugged.
As an example, virtualbox can do it.

this would be really useful for testing resilliance and auto fall-over systems in a vm, to be able to quickly virtually "unplug" a network connection.

Note that you can start QEMU with the "-S" flag which means CPUS are paused. This gives you ability to run the "set_link" monitor command above, and then run "cont" to actually start the VM. Less convenient that a CLI flag, but functionally it is eqivalent.

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.]