Description of problem: With one VM launched from the Power User Portal, you can launch the same VM from the User Portal. Version-Release number of selected component (if applicable): On RHEV-M 3.1: spice-vdagent-0.8.1-3.el6.x86_64 rhevm-userportal-3.1.0-32.el6ev.noarch rhevm-webadmin-portal-3.1.0-32.el6ev.noarch rhevm-tools-common-3.1.0-32.el6ev.noarch rhevm-spice-client-x64-cab-3.1-8.el6.noarch rhev-guest-tools-iso-3.1-9.noarch rhevm-spice-client-x86-cab-3.1-8.el6.noarch On RHEL 5.9: spice-client-0.8.1-6.el5_8.2 spice-xpi-2.4-4.el5 How reproducible: Steps to Reproduce: 1. Launch VM from Power User Portal (Extended Tab). 2. From User Portal, launch same VM (Basic Tab) 3. Actual results: You can launch the identical VM from the User Portal that you did from Power User Portal. Expected results: The User Portal shouldn't launch a VM that is already open with a SPICE client. Additional info:
trouble is with MIME launched spice we'd have no way how to figure out if spice is still/already opened or not. So in 3.3 we would anyway have to give up on this behavior at least for non-plugin launched consoles Another option is to connect this with SSO and logged in user reporting. A bit more complicated solution How much of an issue is it?
You could possibly disable USB access, disable sending CTRL-ALT-DEL to VM and open up in full-screen when you want windowed mode or just the opposite. If you have a VM open, the values in the console that you re-open with the User Portal could be all opposite. Why, when I open a VM from the User Portal, can't I open the same way from the Power User Portal? Why is this now an issue, when in 3.1, it seemed to work? You shouldn't be asking me how much of an issue it is. That is for PM to decide.
Handling this properly (eg. two different client machines) will require work from spice as well. Pushing out to scope further
*** Bug 919171 has been marked as a duplicate of this bug. ***
per scrub mtg push to 3.4
still planned for 3.4?
I would think that we are not going to pursue the exclusive lock on console anymore with the .vv execution this is complicated and I doubt there is any benefit. Unless PM plans the SPICE changes for this...
From what I have seen with 3.3, you can download the .vv file, you can launch the .vv file (If you have vv or a similar program to launch), or use the browser plugin. I think this bug is now not relevant due to the choices to open the VM.