Date: Wed, 04 Dec 2013 12:00:07 -0800 From: Peter Grehan <grehan@freebsd.org> To: Michael Dexter <editor@callfortesting.org> Cc: freebsd-virtualization@freebsd.org Subject: Re: Upcoming FreeBSD 10.x + bhyve ... Message-ID: <529F89C7.6070909@freebsd.org> In-Reply-To: <529F8656.7000408@callfortesting.org> References: <56DEE328-7C96-4AC9-BF87-2C41D4C7949F@hub.org> <529D210C.9020801@freebsd.org> <70B115D9-436C-45EC-8F2E-CEBB2A48A9A5@hub.org> <529F8656.7000408@callfortesting.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Michael, > In short: > > -S 31,uart,stdio > > Becomes: > > -S 31,uart,/dev/nmdm0A This will continue to work, though the preferred way of setting up a console port is to use the PCI-ISA (aka LPC) bridge -s N,lpc (N can be any slot number on bus 0, usually 1..31) There are 2 serial ports behind the LPC bridge, com1 and com2. These can have backends assigned to them in the same way as PCI devices, but use the "-l" option for configuration since they are 'lpc' devices e.g. -l com1,stdio -l com2,/dev/nmdm9B The advantage of using the LPC serial ports is that they will show up on the expected tty devices - com1 will be /dev/ttyu0 on FreeBSD as opposed to /dev/ttyu2 for the uart PCI device. So: "-S 31,uart/dev/nmdm0A" becomes "-s 31,lpc -l com1,nmdm0A" ... and change the guest's /etc/ttys file to set up a getty on ttyu0 later, Peter.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?529F89C7.6070909>