diff options
Diffstat (limited to 'mailinglist/output_launchpad/1593756')
| -rw-r--r-- | mailinglist/output_launchpad/1593756 | 24 |
1 files changed, 24 insertions, 0 deletions
diff --git a/mailinglist/output_launchpad/1593756 b/mailinglist/output_launchpad/1593756 new file mode 100644 index 00000000..2385cecf --- /dev/null +++ b/mailinglist/output_launchpad/1593756 @@ -0,0 +1,24 @@ +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). + |