blob: cd9f67f2b6a1a33a23c52c6b0fb27881a2a0f19b (
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
55
56
57
|
device: 0.152
other: 0.115
semantic: 0.114
PID: 0.095
graphic: 0.082
performance: 0.068
debug: 0.066
files: 0.060
vnc: 0.054
network: 0.050
socket: 0.045
permissions: 0.041
boot: 0.035
KVM: 0.022
debug: 0.527
device: 0.163
network: 0.058
files: 0.054
KVM: 0.036
PID: 0.035
socket: 0.030
other: 0.024
semantic: 0.017
performance: 0.015
permissions: 0.012
vnc: 0.011
boot: 0.009
graphic: 0.009
[Qemu-devel] [BUG] vhost-user: hot-unplug vhost-user nic for windows guest OS will fail with 100% reproduce rate
Hi, guys
I met a problem when hot-unplug vhost-user nic for Windows 2008 rc2 sp1 64
(Guest OS)
The xml of nic is as followed:
<interface type='vhostuser'>
<mac address='52:54:00:3b:83:aa'/>
<source type='unix' path='/var/run/vhost-user/port1' mode='client'/>
<target dev='port1'/>
<model type='virtio'/>
<driver queues='4'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/>
</interface>
Firstly, I use virsh attach-device win2008 vif.xml to hot-plug a nic for Guest
OS. This operation returns success.
After guest OS discover nic successfully, I use virsh detach-device win2008
vif.xml to hot-unplug it. This operation will fail with 100% reproduce rate.
However, if I hot-plug and hot-unplug virtio-net nic , it will not fail.
I have analysis the process of qmp_device_del , I found that qemu have inject
interrupt to acpi to let it notice guest OS to remove nic.
I guess there is something wrong in Windows when handle the interrupt.
|