Date: Thu, 03 Oct 2013 22:38:53 -0700 From: Peter Grehan <grehan@freebsd.org> To: Craig Rodrigues <rodrigc@FreeBSD.org> Cc: "freebsd-virtualization@freebsd.org" <freebsd-virtualization@freebsd.org> Subject: Re: Problems with missing ttyv devices in BHyve? Message-ID: <524E546D.9000008@freebsd.org> In-Reply-To: <CAG=rPVcjg17OnjLmdDspsMp%2B70dBWaxnDrsqENfSeONKdP7ThA@mail.gmail.com> References: <CAG=rPVfLMvqfbPvdu2kOzOVyBNBF7GjGRk8oN3E3EnjadX_ZnQ@mail.gmail.com> <522B5010.1080105@freebsd.org> <CAG=rPVcjg17OnjLmdDspsMp%2B70dBWaxnDrsqENfSeONKdP7ThA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Craig, > A few questions for you. > > (1) I want to get the same FreeNAS image working inside Bhyve and on > real hardware. > In the source code for /sbin/init, when it parses /etc/ttys, > if the entry does not exist, it prints out an error message about > not being able to find > the tty entry to open it. > Do you know if there is a way to specify an entry for /dev/ttyu2, > only if it > exists, and not print out an error message otherwise? Not without modifying init :( This seems a very old Unix limitation. > (2) Is it possible to connect to the console of the BHyve VM via /dev/ttyu2 > or some other mechanism? I would like to be able to connect to > the BHyve VM > and use something like Expect or py-expect to execute console > commands in the VM, > for automated testing. Not currently - the only options you have are to run bhyve under expect, or set up a network port and log in and run expect on commands. I have what I think is a plan to fix this: maybe for 10.1. later, Peter.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?524E546D.9000008>