Date: Tue, 3 Dec 2013 00:28:12 -0800 From: Marc Fournier <scrappy@hub.org> To: Peter Grehan <grehan@freebsd.org> Cc: freebsd-virtualization@freebsd.org Subject: Re: Upcoming FreeBSD 10.x + bhyve ... Message-ID: <07A86855-DEE6-4B07-8D2E-47E97303B348@hub.org> In-Reply-To: <529D42C0.6020006@freebsd.org> References: <56DEE328-7C96-4AC9-BF87-2C41D4C7949F@hub.org> <529D210C.9020801@freebsd.org> <70B115D9-436C-45EC-8F2E-CEBB2A48A9A5@hub.org> <529D42C0.6020006@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] How about disk size? The Instructions for vmrun.sh state: ==== 6. Select default console type "vt100" or whatever is appropriate for you Install on disk device vtbd0 (appears as a 8GB disk device) At the end select "yes" when the "Manual Configuration" box appears. ==== I’m assuming that I can change that default, but, if let’s say I stick with 8G to start, but decide I want to make it bigger later … is there an ability to ‘growfs’ the file system? Or do I build a bigger system, rsync hte files from old to new and ditch the old? or … ? On Dec 2, 2013, at 18:32 , Peter Grehan <grehan@freebsd.org> wrote: > Hi Marc, > >>> It is. The easiest is using the recent change (r258668) which >>> allows bhyveload and bhyve to direct output to a tty instead of >>> just stdio. >> >> ‘k, that would work … so *if* I’m reading the docs right, the intiial >> build of the file system / install of guest OS, happens on an >> interactive remote ssh session, then I’d shutdown and restart it >> redirecting output … ? > > That will work, as will Michael Gmelin's tmux method mentioned in an earlier email. > > later, > > Peter. [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org iEYEARECAAYFAlKdlhwACgkQ4QvfyHIvDvOmUQCbBiZy9QsOBbviLQW0ppLcpWQO av8An0fTqVC56NdU+aeC5dWkD4wFaY27 =xUTp -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?07A86855-DEE6-4B07-8D2E-47E97303B348>