Sorry, I'm out of ideas without getting behind your screen...
> -----Oorspronkelijk bericht----- > Van: Frank Sfalanga Jr. [mailto:fr...@csiglobalvcard.com] > Verzonden: dinsdag 2 augustus 2016 16:44 > Aan: Dominique Ramaekers > CC: qemu-discuss@nongnu.org > Onderwerp: Re: [Qemu-discuss] [problem] QEMU-GA & Windows 10 > > Hi Dominique, > > Thank you again for all of your help. > > I was not able to find an '/etc/libvirt.qemu.conf' file specifically on my > system. > My distro is likely different than yours. I was able to find > '/etc/libvirt/qemu.conf > however, and have added the value there: > > -------------------------------- > frank@Linux-Precision-T1500:/etc$ sudo grep -r security_driver * > libvirt/lxc.conf:#security_driver = "selinux" > libvirt/qemu.conf:# security_driver = [ "selinux", "apparmor" ] > libvirt/qemu.conf:# value of security_driver cannot contain "dac". The value > "none" is libvirt/qemu.conf:# a special value; security_driver can be set to > that > value in libvirt/qemu.conf:security_driver = "none" > > -------------------------------- > > I also uncommented '/etc/libvirt/lxc.conf:#security_driver = "selinux"' > above and modified it to be "none". > > (I'm not using LXC but sure, why not?) > > I've restarted my workstation and logged into the Windows 10 VM. Sadly, I > have to report the same issue. > > -------------------------------- > > 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. > > -------------------------------- > > Any additional idea(s)? > > As always, thank you in advance. > > Kind regards, > > -Frank > > > -----Original Message----- > From: Dominique Ramaekers <dominique.ramaek...@cometal.be> > To: Frank Sfalanga Jr. <fr...@csiglobalvcard.com> > Cc: qemu-discuss@nongnu.org <qemu-discuss@nongnu.org> > Subject: RE: [Qemu-discuss] [problem] QEMU-GA & Windows 10 > Date: Sat, 30 Jul 2016 13:32:35 +0000 > > > > -----Oorspronkelijk bericht----- > > Van: Frank Sfalanga Jr. [mailto:fr...@csiglobalvcard.com] > > Verzonden: dinsdag 26 juli 2016 19:51 > > Aan: Dominique Ramaekers > > CC: qemu-discuss@nongnu.org > > Onderwerp: Re: [Qemu-discuss] [problem] QEMU-GA & Windows 10 > > > > Hi Dominique, > > > > Perhaps I'm missing something, I could not find an apparmor profile > > for qemu (specifically) at all on my system. I did do this: > > > > ---------------------------------------------- > > frank@Linux-Precision-T1500:~$ sudo aa-complain /usr/sbin/libvirtd > > [sudo] password for frank: > > Setting /usr/sbin/libvirtd to complain mode. > > frank@Linux-Precision-T1500:~$ sudo > > aa-complain /usr/lib/libvirt/virt-aa-helper Setting > > /usr/lib/libvirt/virt-aa- helper to complain mode. > > ----------------------------------------------- > > > > After restarting even, I get the same error when I try to start QEMU-GA. > > > > Anything more specific I should try? > > Put security_driver = "none" in /etc/libvirt.qemu.conf > + > Restart libvirt > > > > > Thanks in advance. > > > > -Frank > > > > -----Original Message----- > > From: Dominique Ramaekers <dominique.ramaek...@cometal.be> > > To: Frank Sfalanga Jr. <fr...@csiglobalvcard.com> > > Cc: qemu-discuss@nongnu.org <qemu-discuss@nongnu.org> > > Subject: RE: [Qemu-discuss] [problem] QEMU-GA & Windows 10 > > Date: Tue, 26 Jul 2016 12:01:18 +0000 > > > > Maybe something to try, I disabled apparmour in the qemu hypervisor > > conf file.... > > > > > > > -----Oorspronkelijk bericht----- > > > Van: Frank Sfalanga Jr. [mailto:fr...@csiglobalvcard.com] > > > Verzonden: maandag 25 juli 2016 23:54 > > > Aan: Dominique Ramaekers > > > CC: qemu-discuss@nongnu.org > > > Onderwerp: Re: [Qemu-discuss] [problem] QEMU-GA & Windows 10 > > > > > > 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 > > > >
