blob: a1d9fb1c8c3433a1e6de36517c2fbf8b437d38ce (
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
|
graphic: 0.984
architecture: 0.850
network: 0.778
arm: 0.767
performance: 0.730
device: 0.717
socket: 0.698
risc-v: 0.590
mistranslation: 0.571
semantic: 0.539
VMM: 0.537
files: 0.505
ppc: 0.492
PID: 0.486
permissions: 0.466
register: 0.455
debug: 0.422
assembly: 0.391
boot: 0.366
vnc: 0.346
peripherals: 0.273
TCG: 0.271
i386: 0.235
kernel: 0.213
virtual: 0.182
user-level: 0.163
hypervisor: 0.041
KVM: 0.019
x86: 0.008
vdagent is not working properly after live migration
Additional information:
when validating on windows server 2016 Datacenter Evaluation, i found that if vdagent process or vdservice is restarted, copy/paste from host to guest or reverse will work again. i am wondering if we should send something(eg, a event?) to guest to let it reopen the port after live migration?
|