I have a few systems that noVNC seems to behave differently between them.
If I open a noVNC to a non-running VM of course I get a "Failed to connect to server" but if I use the noVNC commands from the GUI to start it, it will sit and wait for a connection and present me with the logo and firmware screen.
On another system the same thing happens but I only get like one second of trying then the "Failed to connect to server" then I need to "Reload" to get a connection.
Does not matter if I user OVMF or SeaBIOS.
Could I be missing something on a config to make it work like the first scenario?
Thx,
-Waz
If I open a noVNC to a non-running VM of course I get a "Failed to connect to server" but if I use the noVNC commands from the GUI to start it, it will sit and wait for a connection and present me with the logo and firmware screen.
On another system the same thing happens but I only get like one second of trying then the "Failed to connect to server" then I need to "Reload" to get a connection.
Does not matter if I user OVMF or SeaBIOS.
Could I be missing something on a config to make it work like the first scenario?
Thx,
-Waz