In some situations it is desirable to run console through a file socket (which by default located in /var/lib/libvirt/qemu/domain-(...)/) as opposed to tcp sockets (i.e. 127.0.0.1:5900). An example of a situation is when using virgl acceleration which does not support sending data over a socket.
Right now trying to open a console of a vm that is configured to use file socket display will return http code 500 and write this in the logs - KCHVM0010E: Unable to connect to powered off virtual machine <vm-name>. (which is misleading, because the vm is clearly marked as running, and is in fact, running).
The socket however, works just fine when forwarded and connected through ssh -
In some situations it is desirable to run console through a file socket (which by default located in /var/lib/libvirt/qemu/domain-(...)/) as opposed to tcp sockets (i.e. 127.0.0.1:5900). An example of a situation is when using virgl acceleration which does not support sending data over a socket.
Right now trying to open a console of a vm that is configured to use file socket display will return http code 500 and write this in the logs -
KCHVM0010E: Unable to connect to powered off virtual machine <vm-name>.(which is misleading, because the vm is clearly marked as running, and is in fact, running).The socket however, works just fine when forwarded and connected through ssh -