From owner-svn-src-projects@FreeBSD.ORG Wed Jan 14 16:38:26 2015 Return-Path: Delivered-To: svn-src-projects@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 75672FC7; Wed, 14 Jan 2015 16:38:26 +0000 (UTC) Received: from c.mail.sonic.net (c.mail.sonic.net [64.142.111.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5B9939F4; Wed, 14 Jan 2015 16:38:26 +0000 (UTC) Received: from comporellon.tachypleus.net (polaris.tachypleus.net [75.101.50.44]) (authenticated bits=0) by c.mail.sonic.net (8.14.9/8.14.9) with ESMTP id t0EGRiOA032293 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 14 Jan 2015 08:27:45 -0800 Message-ID: <54B69900.1050707@freebsd.org> Date: Wed, 14 Jan 2015 08:27:44 -0800 From: Nathan Whitehorn User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: Glen Barber , src-committers@freebsd.org, svn-src-projects@freebsd.org Subject: Re: svn commit: r277183 - projects/release-vmimage/release/tools References: <201501141523.t0EFNwF1046408@svn.freebsd.org> In-Reply-To: <201501141523.t0EFNwF1046408@svn.freebsd.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Sonic-CAuth: UmFuZG9tSVYWsJ/SaBKTDOlhhW/4+zO0xVOjmfsT9XIqlmGHAUPXx6w/Dks/cCrq/FCRnnhp2XBbNZ3eo8Zq/Hd5XelQiRR8W7VN+iX0bZY= X-Sonic-ID: C;gNbSRAqc5BGP1fCsS5uE/A== M;9oMiRQqc5BGP1fCsS5uE/A== X-Spam-Flag: No X-Sonic-Spam-Details: 0.0/5.0 by cerberusd X-BeenThere: svn-src-projects@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "SVN commit messages for the src " projects" tree" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Jan 2015 16:38:26 -0000 Is this a good idea? Do we know why there is a problem with VMs? If it is necessary, shouldn't this be some kind of default in the kernel rather than a hack in the release scripts? -Nathan On 01/14/15 07:23, Glen Barber wrote: > Author: gjb > Date: Wed Jan 14 15:23:58 2015 > New Revision: 277183 > URL: https://svnweb.freebsd.org/changeset/base/277183 > > Log: > Enable the textmode console by default for VM images, > since there is no way to tell if the environment will > be able to use the graphics-mode console. > > Sponsored by: The FreeBSD Foundation > > Modified: > projects/release-vmimage/release/tools/vmimage.subr > > Modified: projects/release-vmimage/release/tools/vmimage.subr > ============================================================================== > --- projects/release-vmimage/release/tools/vmimage.subr Wed Jan 14 14:50:31 2015 (r277182) > +++ projects/release-vmimage/release/tools/vmimage.subr Wed Jan 14 15:23:58 2015 (r277183) > @@ -84,6 +84,12 @@ vm_install_base() { > >> ${DESTDIR}/etc/fstab > fi > > + # Set hw.vga.textmode=1, with the assumption that the hypervisor > + # will not be capable of using the graphics console mode. > + echo '# Comment the next line to enable graphical console mode' \ > + >> ${DESTDIR}/boot/loader.conf > + echo 'hw.vga.textmode=1' >> ${DESTDIR}/boot/loader.conf > + > mkdir -p ${DESTDIR}/dev > mount -t devfs devfs ${DESTDIR}/dev > chroot ${DESTDIR} /usr/bin/newaliases >