<div dir="ltr">The IP of the VM should be reported to the management via the guest agent. Is this what you are looking for?</div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><pre cols="72"><span style="font-family:arial,helvetica,sans-serif">Yaniv Dary
Technical Product Manager
Red Hat Israel Ltd.
34 Jerusalem Road
Building A, 4th floor
Ra'anana, Israel 4350109
Tel : +972 (9) 7692306
8272306
Email: <a href="mailto:ydary@redhat.com" target="_blank">ydary@redhat.com</a>
IRC : ydary</span></pre>
</div></div></div></div></div>
<br><div class="gmail_quote">On Wed, Mar 2, 2016 at 6:18 AM, Simon Lévesuqe <span dir="ltr"><<a href="mailto:moi@simminfo.com" target="_blank">moi@simminfo.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">From a windows guest (can be useful for linux guest as well), is it possible to get the IP of the spice client connected to console?<br>
<br>
I setup oVirt for a VDI. The users use thin clients that PXE boot using LTSP. I need the client IP to offer remote support via VNC. Now, I use epoptes as remote support tool, its an excellent peace of software but I need technicians from other branch of the company to be able to offer remote support to my users and they are all Windows guy ans don't want to connect to the LTSP server to start epoptes... They already use VNC to support Wyse type clients so I installed x11vnc on my clients chroot and setup it to start at boot. I know this is a security issue but this is the boss decision.<br>
<br>
Some client log to terminal servers using xfreerdp (LTSP clients boot directly to xfreerdp). In that case, everything is ok, we setup bginfo to print the client name and ip as they are windows environment variables.<br>
<br>
The problem is that many other clients boot to the oVirt user portal and users log to Windows 7 vm using Virt-Viewer and Spice. In bginfo, the only thing i can get is the IP of the Windows guest. It's ok, for most cases we can take control of the guest ant it do the trick but sometimes it's useful to vnc the thin itself.<br>
<br>
Thanks!<br>
<br>
Simon L<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman/listinfo/users</a><br>
</blockquote></div><br></div>