From owner-freebsd-questions@FreeBSD.ORG Sun Jan 6 19:03:10 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 385B2647 for ; Sun, 6 Jan 2013 19:03:10 +0000 (UTC) (envelope-from freebsd-questions@m.gmane.org) Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) by mx1.freebsd.org (Postfix) with ESMTP id E53011456 for ; Sun, 6 Jan 2013 19:03:09 +0000 (UTC) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1TrvVA-0002Uu-7d for freebsd-questions@freebsd.org; Sun, 06 Jan 2013 20:03:20 +0100 Received: from 79-139-19-75.prenet.pl ([79.139.19.75]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 06 Jan 2013 20:03:20 +0100 Received: from jb.1234abcd by 79-139-19-75.prenet.pl with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 06 Jan 2013 20:03:20 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-questions@freebsd.org From: jb Subject: Re: FB 9.1 boot loader problem in VirtualBox Date: Sun, 6 Jan 2013 19:02:43 +0000 (UTC) Lines: 65 Message-ID: References: <50E96648.6090303@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: sea.gmane.org User-Agent: Loom/3.14 (http://gmane.org/) X-Loom-IP: 79.139.19.75 (Mozilla/5.0 (X11; Linux i686; rv:10.0.11) Gecko/20121121 Firefox/10.0.11) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Jan 2013 19:03:10 -0000 Matthew Seaman FreeBSD.org> writes: > > On 06/01/2013 11:19, jb wrote: > > Next problem: > > when I am logged out from FB, and I do (I tested it repeatedly) > > > > Machine-Close-Power off the machine > > to cloce VM with FB, then on subsequent VM Start and FB reboot I get error > > msgs: > > ... > > Trying to mount root from ufs:/dev/ada0s1a [rw]... > > WARNING: / was not properly dismounted > > ... > > Starting file system checks: > > ** SU+J Recovering /dev/ada0s1a > > ... > > > > but when I do > > Machine-Close-Send the shutdown signal > > there are no errors, just normal msgs: > > ... > > Trying to mount root from ufs:/dev/ada0s1a [rw]... > > ... > > Starting file system checks: > > /dev/ada0s1a: FILE SYSTEM CLEAN; SKIPPING CHECKS > > ... > > > > Ummm... what did you expect to happen? 'Machine-Close-Power off' is > essentially the same as ripping the power cord out of a physical > machine. It's designed to stop the guest system no matter what: even if > the guest is trapped in so tight a loop it can't respond to anything else. > > 'Machine-Close-Send shutdown' is more like pressing the power button on > the front of most modern machines, in that what it does is signal the > guest OS to shut itself off and power down the system after that. You > can achieve the same effect from within the guest OS by typing: > > shutdown -p now > > 'Machine-Close-Send shutdown' is what you want to use routinely. > > Cheers, > > Matthew > Right, but the wordings are unfortunate and counterintuitive/misleading: 'Machine-Close-Send shutdown' means to 'shutdown -p now' (equivalent to 'poweroff') of Guest, followed by unforced "Close" of VM. 'Machine-Close-Power off' means "Kill VM' without regard of the Guest - but the "Power off" in its name may make user believe that there is "Poweroff" (orderly shutdown, poweroff) involved as part of the process. It would be better, in my opinion, if these options were called "Machine-Close-Shutdown-Guest" "Machine-Close-Kill-Guest" No margin for error/misunderstanding. jb