TLDR; It looks like it was removed? IMO it's a moot point and you shouldn't use it anyway?
Hmmm. Typically I turn off/remove the displays devices after getting SSH or RDP setup because VNC is not particularly secure so I hadn't checked this after I upgraded. Been using SCALE as my hypervisor since the beginning...so this is interesting to me. Thanks for posting.
As an aside, I wouldn't recommend you use the "DISPLAY" feature in TrueNAS for anything other than debugging or initial setup purposes... SPICE or VNC are by their nature a security risk, you are literally exposing (unnecessary) console-level access to your systems over the network. In your case you are at least using a good VNC client, but unfortunately any bad
This VM has been off a while (since before I upgraded.)
It has an existing display device, and it does sees to have been converted to SPICE.
For giggle and laughs, I can confirm that I no longer see the VNC/SPICE option menu (when adding a new Display Device after the VM creation Wizard), IIRC that was present before. But for sure, it always defaulted to VNC.
I dug a bit deeper, and unless it was named something other than "novnc" it just seems be gone. I'd assume they chose to support SPICE over VNC and dropped one of them to have to maintain less packages. FWIW I had all sorts of problems with VNC throughout different versions of SCALE that made it unusable for me in the WebUI anyway.
It was a weird and highly inconsistent (but repeatable for those systems affected) problem that I saw crop up here from some other folks as well. I don't think anyone ever figured out exactly why some of the issues happened but they did improve the implementation over time. At one point I couldn't use it at all, and now it works most of the time...and when it doesn't a reboot fixes it. FWIW this only ever affected the WebUI button, using an external client like you are always worked.
My problem recap here is really only to express that I personally never really used an external NoVNC client for anything...other than testing because of my problem. I also prefer to use more secure methods of working on my VMs anyway. I'd bet alot of other folks here would agree with this as being a better workflow.
Obviously I haven't looked back at it since I upgraded last week...so I'm curious if SPICE solved my problem anyway. I never tried it before now. So thank you for the journey down this rabbit hole lol
Code:
root@prod[/]# find / -path /mnt -prune -o -name novnc -print
find: ‘/proc/2164464’: No such file or directory
find: ‘/proc/2164605’: No such file or directory
find: ‘/proc/2164610’: No such file or directory
find: ‘/proc/2164612’: No such file or directory
find: ‘/proc/2164613’: No such file or directory
find: ‘/proc/2164616’: No such file or directory
find: ‘/proc/2164617’: No such file or directory
find: ‘/proc/2164676’: No such file or directory
root@prod[/]#
Sidenote: What's interesting is the tooltip reports as being the bind port for VNC, which may just be a UI artifact that wasn't caught in pre-BETA testing.