I tried Chrome and it worked fine right out of the box. All I had to do
was download the file first (because Chrome is stupid about that - way
to go Google) and then right click on the file in the bottom download
bar and select Always open files of this type and it found and used
remote-viewer. If I delete the vv file and open another vm console it
works fine. Chrome is also more responsive and faster. Bye Firefox -
this was the last application that needed you.
On 01/18/2017 08:46 AM, Alexander Wels wrote:
On Tuesday, January 17, 2017 6:10:43 PM EST Brett Holcomb wrote:
> On my Windows machine I can run the web portal without issues but I
> would like to use the console from the portal on the VMs. I installed
> the virt-manager but it if I do
>
> spice://myengine.my.domain:5900 it tells me I can't connect.
>
> I've found a lot of contradictory advice (big surprise! <G>). Some say I
> need to install spice.cab (link does not work and a working link lead to
> a site with malware which got blocked).
>
> So what do I need to use a console in the portal in Windows 7?
>
> Also, when will the portal work with Chrome?
>
Download the virt VIEWER from
https://virt-manager.org/download/sources/virt-viewer/virt-viewer-x64-5.0... assuming you
have a 64 bit windows. If you
don't there are links to 32 bit on
https://virt-manager.org/download/ again
make sure to download the VIEWER not the manager.
Then in your browser associate .vv files with the virt viewer and clicking the
console button should be all you need to make it work.
The portal has worked in Chrome since at least oVirt 3.1 maybe even earlier.
Anything in particular that doesn't work for you?
> Thanks.
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
>
http://lists.ovirt.org/mailman/listinfo/users