This is troubling me for quite a while and it isnt vm-bhyve specific, but just for quick example:
ssh to server
vm create -t windows win10
vm install win10 windows10.iso
vm console win10
sockstat -4l | grep bhyve
So far so good. Now the fun begins. I try to connect to 5900 from client (ubuntu), and i get disconnected where all consequent retrys to connect fail, while there are some code (persumably bios) being thrown into ssh terminal but completely unreadable, bunch of escape codes etc. I would expect a screen within a vnc and if redirected to ssh, at least something readable? Probably something should be set on terminal level (i guess) but I wasnt able to find what.
From what I have seen i should get a "bios" screen with option to boot from dvd but it doesnt work =/
ssh to server
vm create -t windows win10
vm install win10 windows10.iso
vm console win10
Code:
Starting win10
* found guest in /vm/win10
* booting...
sockstat -4l | grep bhyve
Code:
root bhyve 19627 7 tcp4 *:5900 *:*
So far so good. Now the fun begins. I try to connect to 5900 from client (ubuntu), and i get disconnected where all consequent retrys to connect fail, while there are some code (persumably bios) being thrown into ssh terminal but completely unreadable, bunch of escape codes etc. I would expect a screen within a vnc and if redirected to ssh, at least something readable? Probably something should be set on terminal level (i guess) but I wasnt able to find what.
From what I have seen i should get a "bios" screen with option to boot from dvd but it doesnt work =/