Closed mkunz7 closed 4 years ago
That's strange:
ERROR kvm.go:565: unable to dial vm vnc: dial unix /tmp/minimega/45/vnc: connect: no such file or directory
Did QEMU fail to create the domain socket for VNC?
@mkunz7: have you seen this since we rolled back novnc?
Possibly related: https://lists.gnu.org/archive/html/qemu-devel/2017-04/msg05455.html
What's the status on this? @mkunz7 @jcrussell
Reliably happens with osx High Sierra >2.9 qemu. I’ve noticed elsewhere but much rarer.
So what's the plan here then? This looks like an existing bug in qemu that we can't work around - looks like maybe it was fixed in 2.9.0 but @mkunz7 says otherwise...
@mkunz7 can you debug trace or verbose log something something with qemu and see if qemu is closing the socket?
@mkunz7 this is the only holdout for cutting 2.6. Can you comment? We could push this to 2.7 or just invalidate it as it seems like maybe it's a qemu thing. Thoughts?
Checking this now. Give me a second to update the kernel and qemu and look closer at this.
OSX issue is fixed on ubuntu 18.04, 5.28 kernel, qemu 4.1.0. I can't recreate it reliably. Close it for now.
Thanks for investigating!
I've noticed a number of times now where novnc works on a vm for a while, then is no longer able to connect to a vm. Showing a black screen saying
Connecting...
Other virtual machines still work.I can still screenshot it with
vm screenshot
and control it with vncviewer, but novnc won't reconnect. This shows up in miniwebs output38049 is not a vnc port
developer console shows:
When this happens novnc won't work until I kill and start the VM again.
vnc inject win1 PointerEvent,0,0,0
is unable to dial the connection too