Description of problem: Launching a Windows VM from the UP prompts the user to install virt-viewer every time it is launched. I get the prompt to install SpiceX_x64.cab every time I launch the VM from the UP or PUP. I tried to reproduce this on a Windows 7 client, and the client worked as expected. Version-Release number of selected component (if applicable): RHEV-M 3.2 (sf16.1) W2K8R2 client How reproducible: 100% Steps to Reproduce: 1. See above. 2. 3. Actual results: Launching a Windows VM from the UP prompts the user to install virt-viewer every time it is launched. Expected results: Launching a Windows VM from the UP prompts the user to install virt-viewer the first time it is launched, only. Additional info:
I have done further investigating and it seems this only happens after you connect to a previous UP, RHEV-M 3.1 was tested for upgrade in client, and then connect to a 3.2 UP. What I saw was the UP downloading the NEW client, but never updating the SpiceX - ActiveX control. Every time the UP was loaded, the old ActiveX was there with the new v-v. And the v-v install would happen every time the VM was launched.
Bill, if you uninstall the SpiceX first and than connect to 3.2, does it work as expected? If yes, I would say it should be moved to SPICE.
Tomas, I have moved this to activex-win since the browser is not getting updated with the 3.2 SpiceX and using the 3.1 version and failing.
Bill, is this a w2k8-only bug then? If yes, I think we should make that clear in the title and minor severity.
I have just installed sf17 and can't get this to fail. Not sure what was changed but will close for current release.