Set default console in oVirt 3.6 (NoVNC VS. Native)
Hi, with oVirt 3.5 (and prior) it was possible to set the default console like this: # engine-config -s ClientModeVncDefault=NoVnc Unfortunately, starting with oVirt 3.6 this doesn't seem to work anymore. The root cause seems to be that I am no longer allowed to use the previous Video Type for my VMs ("Other OS"), oVirt forces me to choose "QXL" for several VMs now. And hence I am presented with both SPICE and VNC as console options (although I don't want to use SPICE at all). What's the new way to set NoVNC as default console in that case? Is there still a way to set VNC as default for "QXL"? A related question: How to set the default console for SPICE to "SPICE HTML5"? Regards - Frank
On 02 Feb 2016, at 12:48, Frank Wall <fw@moov.de> wrote:
Hi,
with oVirt 3.5 (and prior) it was possible to set the default console like this:
# engine-config -s ClientModeVncDefault=NoVnc
Unfortunately, starting with oVirt 3.6 this doesn't seem to work anymore.
The root cause seems to be that I am no longer allowed to use the previous Video Type for my VMs ("Other OS"), oVirt forces me to choose "QXL" for several VMs now. And hence I am presented with both SPICE and VNC as console options (although I don't want to use SPICE at all).
what do you mean “forces”? you should be able to switch to cirrus (which forces vnc) or even use just the vnc on qxl
What's the new way to set NoVNC as default console in that case?
It should work the same. Just for SPICE+VNC mode you need to pick which one you want to use (then the invocation is taken from teh parameter) We don’t have a concept of “preferred” console, though…if you want to use only one then don’t use SPICE+VNC in the first place
Is there still a way to set VNC as default for "QXL"?
A related question: How to set the default console for SPICE to "SPICE HTML5”?
hm…doesn’t seem to be supported:/ worth a bug or contribute a fix:) Thanks, michal
Regards - Frank _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Hi Michal, On Tue, Feb 09, 2016 at 12:04:44PM +0100, Michal Skrivanek wrote:
what do you mean ???forces???? you should be able to switch to cirrus (which forces vnc) or even use just the vnc on qxl
on the affected VMs the following error occurs when trying to start them: Error while executing action: Cannot run VM. Selected display type is not supported by the operating system. This is the case on VMs with Operating System set to "Other OS" and Video Type set to "CIRRUS". PLEASE NOTE that this only occurs on my "old" VMs (that have been available *before* upgrading from oVirt 3.5.x to 3.6.x). When creating new VMs this actually does work as expected. So I assume this is an upgrade issue in oVirt 3.6.x. Regards - Frank
On 10 Feb 2016, at 13:26, Frank Wall <fw@moov.de> wrote:
Hi Michal,
On Tue, Feb 09, 2016 at 12:04:44PM +0100, Michal Skrivanek wrote:
what do you mean ???forces???? you should be able to switch to cirrus (which forces vnc) or even use just the vnc on qxl
on the affected VMs the following error occurs when trying to start them:
Error while executing action: Cannot run VM. Selected display type is not supported by the operating system.
This is the case on VMs with Operating System set to "Other OS" and Video Type set to "CIRRUS”.
PLEASE NOTE that this only occurs on my "old" VMs (that have been available *before* upgrading from oVirt 3.5.x to 3.6.x). When creating new VMs this actually does work as expected. So I assume this is an upgrade issue in oVirt 3.6.x.
that makes sense...there was a UI bug fixed in 3.6.3 - the code was setting something different than what you’ve selected…3.6.3 was just released, give it a try after an upgrade Thanks, michal
Regards - Frank
participants (2)
-
Frank Wall -
Michal Skrivanek