blob: 8f5399bd3eaa58e07959b90522470503c8a81ca0 (
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
|
architecture: 0.783
kernel: 0.741
virtual: 0.702
device: 0.647
hypervisor: 0.633
mistranslation: 0.628
semantic: 0.541
performance: 0.507
graphic: 0.453
user-level: 0.435
socket: 0.369
peripherals: 0.344
network: 0.332
PID: 0.325
permissions: 0.316
arm: 0.312
register: 0.303
debug: 0.301
assembly: 0.292
ppc: 0.284
VMM: 0.265
vnc: 0.255
x86: 0.247
boot: 0.235
risc-v: 0.195
i386: 0.169
TCG: 0.157
files: 0.128
KVM: 0.116
qemu-ga won't start on Windows 8.1 guest
System: Arch Linux, kernel 4.6.2
VM created with virt-manager 1.3.2
qemu version 2.6.0
Windows guest: 8.1, with latest updates (as of now)
Drivers installed from virtio-win iso image (arch package version 0.1.118.2-1)
in particular: vioserial driver version 62.73.104.11800
I can start the Guest Agent VSS Provider manually, but the Guest Agent itself doesn't come up. When launched from Console, I get the following:
<timestamp>: critical: error opening path
<timestamp>: critical: error opening channel
<timestamp>: critical: failed to create guest agent channel
<timestamp>: critical: failed to initialize guest agent channel
(As possible side effects I have experienced that suspend / resume of the VM only works when I resume, suspend again and resume again. After first resume the VM's screen is frozen and doesn't accept any input. After second resume, all seems to be well.)
Oh, qemu-ga worked before (not sure whether before upgrade to kernel 4.6.x or before upgrade to qemu 2.6.0 though). Re-installed a clean windows into a new VM to verify issue.
It turned out that this is not a bug but instead I overlooked to add a channel for qemu-ga via virt-manager. Don't know how it got lost on the working machine, but nvm, it works now.
Anyone feel free to close this (didn't find an option to do so).
|