Date: Tue, 20 Jan 2015 17:37:08 +0100 From: Willem Jan Withagen <wjw@digiware.nl> To: Peter Grehan <grehan@freebsd.org> Cc: Conrad Rad <cse.cem@gmail.com>, "freebsd-virtualization@freebsd.org" <freebsd-virtualization@freebsd.org> Subject: How to connect ssh and /dev/nmdm devices Was:( Re: Native Linux guest in Bhyve (no grub2-bhyve) status? ) Message-ID: <54BE8434.3070901@digiware.nl> In-Reply-To: <54AA4E32.1080303@digiware.nl> References: <CAG6CVpVt2gjZvHiLfruMXh-u0pBeF3Lc-_SGA%2BEY7E1fVmgKzg@mail.gmail.com> <5448305F.8010307@freebsd.org> <CAG6CVpUa4b5zFwN%2BBcD7OCYV9Xz8z9j9iRs721YYqFhvoJbOLA@mail.gmail.com> <54483712.8050007@freebsd.org> <54A9CAFB.1090902@digiware.nl> <54A9CC90.2020103@freebsd.org> <54AA4E32.1080303@digiware.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2015-01-05 9:41, Willem Jan Withagen wrote: > On 2015-01-05 0:28, Peter Grehan wrote: >> Hi Willem, >> >>> Would it it be possible in the meantime to enhance grub2-bhyve with the >>> same possibility as bhyve itself has for the console? >>> >>> So I can redirect grub screen access to /dev/nmdm12041, and one can even >>> use this channel to see the grubscreen during rebooting. >>> >>> Or if it is not that hard, give some pointers to write it myself. >> >> Conrad contributed this to grub-bhyve with >> https://github.com/grehan-freebsd/grub2-bhyve/pull/2 >> >> It's available in v0.30 which has been in ports for a while now: >> >> https://github.com/grehan-freebsd/grub2-bhyve/releases/tag/v0.30 > > Right, > > Did miss that, I guess. > I'll upgrade my bhyve-grub. Yup, works really nice. Now in a continuance from this... What is the easiest way to "propagate" the full-duplex tty stream from a SSH-login to a /dev/nmdmXXXXA. This will give easy access to the console screens. one would type: ssh -p XXXX user@management-ip and end up at the console on /dev/nmdmxxxxA Currently I'm using tip for this, but that also requires hacking new VMs into /etc/remote. So a very basic TIP, without the serial/ACU/speed stuff, would really be useful. Preferably all signals are sent thru as well. And if this might not be 100% secure, it would require an ssh-jailed setup. A bit like sftp. hints and or suggestion welcome. --WjW --WjW
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?54BE8434.3070901>