Re: [ovirt-users] some ISO images not recognized

2016-03-03 Thread Simon Lévesuqe

Did you use ovirt-iso-uploader?

Sometimes iso files with uppercase ".ISO" doesn't show up in the list. 
Try re-upload them with lowercase filename.


I know that ISOs downloaded from MS habitually are all uppercase names.

Simon

Le 03/03/2016 03:45 AM, Stefano Cislaghi a écrit :


Hello everyone,
I configured a test environment with 2 hosts (centos), hosted engine 
and NFS storage for data domain and iso domain.
I noticed that windows 2012 ISOs are marked as "unknown" in iso domain 
and therefore I can't attach them to virtual machines.
Maybe something is wrong with my iso? I tried to do a fresh download 
with same result. Centos, Fedora and Windows 10 iso are working, so I 
think the iso domain is ok.

Did someone else noticed such behaviour? Any solution?
Thanks
Stefano


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] Know the console client IP from guest

2016-03-01 Thread Simon Lévesuqe
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?


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.


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.


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.


Thanks!

Simon L
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users