cockpit-machines
cockpit-machines copied to clipboard
cockpit-project
Launch viewer defaulting to VNC instead of spice after recent upgrade
After most recent upgrade, The launch viewer button downloads a "console.cc" file which appears to be set to use VNC settings and ports instead of the spice settings and ports. I had previously changed a config file somewhere to use my servername, instead of the default 172 local address. Making that change when first setting up allowed me to launch directly out of cockpit. I mention this just in case it plays a role, but i doubt it.
After upgrade the .cc file looks like this:
[virt-viewer] type=vnc host=servername.lan port=5900 delete-this-file=1 fullscreen=0
If i change it to spice connection it works:
[virt-viewer] type=spice host=servername.lan port=5901 delete-this-file=1 fullscreen=0
VM's can use both VNC and Spice. VNC inside the cockpit interface, and Spice for remote console access. I think if both vnc and spice where configured the .cc file would default to spice in it's config.
Adding some screenshots from virtmanager to show both vnc and spice config.
So I've been reading through the pull/merge requests, and it looks like maybe it was a design switch to VNC only? It also looks like they are adding the abilty to switch between spice and vnc as part of the next redesign? I'm hoping someone can maybe chime in and explain if this is by design or they are working on adding these options. I also read somewhere that redhat was dropping spice support, but i can't remember where i read that at.
References: https://github.com/cockpit-project/cockpit-machines/pull/2008 https://github.com/cockpit-project/cockpit-machines/issues/553
So I've been reading through the pull/merge requests, and it looks like maybe it was a design switch to VNC only?
Yes, that was by design but without a lot of reasons behind it.
It also looks like they are adding the abilty to switch between spice and vnc as part of the next redesign?
I was considering some way to configure the "Launch viewer" button so that it can do multiple things, depending on user preference:
- VNC via consolve.vv
- SPICE via console.vv
- VNC via a vnc://... link
- SPICE via a spice://... link
- virt-viewer qemu+ssh://... via console.vv
- ...
Thanks for bumping the priority of this! :-)
If i change it to spice connection it works:
Does VNC not work for you for some reason, or do you just prefer SPICE for the "Launch viewer" button?
If i change it to spice connection it works:
Does VNC not work for you for some reason, or do you just prefer SPICE for the "Launch viewer" button?
VNC works, i prefer spice. So having an option for both would be great. Sometimes VNC is fine, but othertimes i use the additional functionalist spice provides. Thanks for adding to your backlog.
When reading your backlog above, i didn't realize if only one viewer is configured it will default to that. I might have to test that. Something good to keep in mind.