Hi Sven,

Why I had to compile the agent was in order to get the dll OVirtCredProv.dll, as I just checked with the iso you linked me, it does not install.

With that dll, I can single sign on from my application directly to the VDI.

Anyway, I've just installed a clean windows 7 desktop, and installed ovirt-guest-tools, and configuring the serial-device on the VM, it gave me the same results. 100% CPU with one processor and 50% if I put two.

This is my configuration, if anybody sees something wrong, please advice.

args: -chardev socket,id=ovirtagent,path=/tmp/112.com.redhat.vdsm,server,nowait -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x7 -device virtserialport,chardev=ovirtagent,name=com.redhat.rhevm.vdsm,bus=virtio-serial0.0,id=port1

Thank you in advance,


El 08/07/14 09:25, Sven Kieske escribió:
Well I'm really not familiar with the guest agent on windows
but you shouldn't need to compile it yourself.
You don't mention which version of windows you use, which complicates
things a little bit.

In general, this should be the iso to use:
http://resources.ovirt.org/pub/ovirt-master-snapshot-static/iso/ovirt-guest-tools/ovirt-guest-tools-3.5-2.iso

I know this maybe won't work for windows server 2012 R2 yet, but it
should run on other versions.

HTH

Am 07.07.2014 15:50, schrieb Angel Docampo:
Hello everybody,

This is my very first email here. I've just compiled both 32 and 64 bits
oVirtGuestAgent in order to make SSO from my application to a Windows VM.

32 bits works flawlessly, I can login, logout and lock screen at the moment, but
the 64 bits version cannot login (but can lock screen and logout) and the worse
of all, puts the VM CPU at 99%, making it useless.

Anyone has experieced this? Or give me some guidance to investigate?

--


        
*Angel Docampo
*
*Datalab Tecnologia, s.a.*
Castillejos, 352 - 08025 Barcelona
Tel. 93 476 69 14 - Ext: 706
Mob. 670.299.381

_______________________________________________
Users mailing list
[email protected]
http://lists.ovirt.org/mailman/listinfo/users

Reply via email to