Now the channel is there and the VM is booting but the QEMU-GA still will not start. It is failing with the same (original) error:
------------------------------------------------------ Windows could not start the QEMU Guest Agent service on local computer. Error 1053: the service did not respond to the start or control request in a timely fashion. ------------------------------------------------------- Following Dominique's directions, I was able to get past the "Failed to bind socket: Permission denied errors" below using information I found here: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1407434 "WORKAROUND for those who want to go on with MV creation while this bug is valid : 0. do not quit virt-manager vm creation 1. locate apparmor profile for your VM with ls-ltr /etc/apparmor.d/libvirt/libvirt-* (the long string with numbers is your vm UUID - look inside to find your vm name) 2. set this apparmor profil in complain mode # aa-complain /etc/apparmor.d/libvirt/libvirt-73aa79f1-0023-4e37-8001-5be78e884348 (for example) 3. go on with vm creation - it will succeed" Now the Windows 10 VM is booting up and working fine. Also, the channel appears to be created too: root@Linux-Precision-T1500:/var/lib/libvirt/qemu/channel/target# ls -l total 0 srwxr-xr-x 1 libvirt-qemu kvm 0 Jul 25 17:16 Windows10.org.qemu.quest_agent.0 -------------------------------------------------- As I said above, I'm still not able to get the QEMU-GA to start, although the VSS starts fine. -Frank
