You can just rebuild the current RHEV spice-xpi source RPM and drop the resulting files into you ovirt install. - Found here: http://ftp.redhat.com/pub/redhat/linux/enterprise/6Server/en/RHEV/SRPMS/rhev... - rpmbuild --rebuild rhevm-spice-client-3.0-21.el6.src.rpm (install dependent packages via yum if build fails due to deps, not that many needed) - unpack the resulting spice-xpi client isntallers and cabs from the rpms using: rpm2cpio - rpm2cpio <nameofrpm> | cpio -ivd - place the files into their corresponding locations on your ovirt install. - you can find the paths where things go via rpm -qlp <packagename> replace "rhevm" with "engine" pathing wise - Pathing on ovirt should be something like: --> /usr/share/ovirt-engine/engine.ear/engineanger.ear/ --> /usr/share/ovirt-engine/enginer.ear/userportal.ear/ovirt.org... -restart jboss and you will be good to go - Chris -----Original Message----- From: users-bounces@ovirt.org [mailto:users-bounces@ovirt.org] On Behalf Of Itamar Heim Sent: Monday, January 30, 2012 2:01 PM To: André Felício Cc: spice-devel@lists.freedesktop.org; users@ovirt.org; David Blechter Subject: Re: [Users] oVirt console plans On 01/30/2012 09:58 PM, André Felício wrote:
There are many SO (windows) that access by SPICE is a little tricky.
What's tricky with Spice? If there's anything we can do to help make Spice easier to use, let us know.
I tried compiling spice-xpi for windows it several times and it still fails. Anyone have the spice-client and spice-xpi compiled for windows?
cc'ing spice-devel to provide input on status/availability of spice-xpi for windows and/or spice-activex.
OVirt appears VNC console in the option but does not have a way to access it over webadmin.
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users