From owner-freebsd-virtualization@FreeBSD.ORG Tue Jan 7 13:24:39 2014 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AE43863E; Tue, 7 Jan 2014 13:24:39 +0000 (UTC) Received: from mail.ijs.si (mail.ijs.si [IPv6:2001:1470:ff80::25]) by mx1.freebsd.org (Postfix) with ESMTP id 394441773; Tue, 7 Jan 2014 13:24:39 +0000 (UTC) Received: from amavis-proxy-ori.ijs.si (localhost [IPv6:::1]) by mail.ijs.si (Postfix) with ESMTP id 3dzDpF5m0BzGMnD; Tue, 7 Jan 2014 14:24:37 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ijs.si; h= user-agent:message-id:references:in-reply-to:organization :subject:subject:from:from:date:date:content-transfer-encoding :content-type:content-type:mime-version:received:received :received:received; s=jakla2; t=1389101072; x=1391693073; bh=NpN yhc32++ITh99bAm0vjXkAsYyBZToVmTkT3Ro9IeM=; b=LA50GyXOhQQXFvCNHRE i4hjo852hu6GYtyDfQafpXjUIIsXyDx2oqnxxc/UeyYb0eC/pIKHA7S/v3Z6VZEt EcmTtF17OvwNApLTHH5uL6QJ8CUhAvbLOAICSG6wIEO2DPstzgv2LVAWuVzK094t XdBhUD3RhbKia8owjaHh8lM4= X-Virus-Scanned: amavisd-new at ijs.si Received: from mail.ijs.si ([IPv6:::1]) by amavis-proxy-ori.ijs.si (mail.ijs.si [IPv6:::1]) (amavisd-new, port 10012) with ESMTP id tXy9jHBNp34N; Tue, 7 Jan 2014 14:24:32 +0100 (CET) Received: from mildred.ijs.si (mailbox.ijs.si [IPv6:2001:1470:ff80::143:1]) by mail.ijs.si (Postfix) with ESMTP; Tue, 7 Jan 2014 14:24:32 +0100 (CET) Received: from neli.ijs.si (neli.ijs.si [193.2.4.95]) by mildred.ijs.si (Postfix) with ESMTP id DE0D5989; Tue, 7 Jan 2014 14:24:31 +0100 (CET) Received: from sleepy.ijs.si ([2001:1470:ff80:e001::1:1]) by neli.ijs.si with HTTP (HTTP/1.1 POST); Tue, 07 Jan 2014 14:24:31 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Date: Tue, 07 Jan 2014 14:24:31 +0100 From: Mark Martinec To: Craig Rodrigues Subject: Re: Installer fails with "out of swap space" when installing ZFS-on-root with less then 4 GB mem (10.0-RC4) Organization: J. Stefan Institute In-Reply-To: References: <7a61b7a1f156dcf67b3ba44bca7dd906@mailbox.ijs.si> Message-ID: X-Sender: Mark.Martinec+freebsd@ijs.si User-Agent: Roundcube Webmail/0.9.5 Cc: crodr001@gmail.com, freebsd-stable@freebsd.org, freebsd-virtualization@freebsd.org X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Jan 2014 13:24:39 -0000 > On Sun, Jan 5, 2014 at 5:27 PM, Mark Martinec wrote: >> I was playing with bhyve on 10.0-RC4, trying to install another >> 10.0-RC4 >> into a 16 GB ZFS volume using the network installation DVD. Mostly >> kept >> defaults, except that I chose a ZFS-on-root installation. The amd64 >> [guest] >> was given 1 GB of RAM on the first attempt, but failed. It fails on 2 >> GB RAM >> too, but succeeds when given 4 GB of RAM. 2014-01-06 22:13, Craig Rodrigues wrote: > How far did you get with this? If you use BHyve to boot FreeBSD, > the loader which is used is in /usr/src/sys/boot/userboot, and > this loader does not support a complete ZFS-only install. > I recently tried to do this, and the install worked (with 4G of RAM), > but when I tried to reboot the BHyve VM, the VM did not boot. You are right, I wasn't able to boot such newly-installed disk under bhyve. But I was able to verify that the installation was successful: copied the created zfs volume to another host (running 9.2), pointed a VirtualBox .vmdk disk description file to that zfs volume, and VirtualBox was able to successfully boot and run from such disk. So the installer running under bhyve did its job, successfully installed a root-on-zfs 10-RC4. > If you look at: https://admbugs.freebsd.org/show_bug.cgi?id=428#c7 > > you will see I had to use a variation of these steps: > https://wiki.freebsd.org/RootOnZFS/UFSBoot > > where the /boot directory which contained the kernel and loader was on > a > UFS partition, but everything else was on ZFS. That's the only way I > could get the BHyve VM to boot, with userboot. Thanks, useful link. I wish the bhyve would be able to boot off the freebsd-boot partition containing a gptzfsboot bootcode. Devin writes: >> - let the installer mount the available swap partitions before jumping >> into heavy installation work; > That sounds reasonable enough. Thanks for considering! >> - avoid covering an underlying failure with a quickly-redrawn >> installer >> menu; at least some delay after a failure but before erasing the >> screen >> would be useful, avoiding the user to go to great lengths to be able >> to >> capture the failure reason. > > While the error reporting could be improved in that area of bsdinstall > that > you fingered, the perception that the errors are quickly being erased > is > incorrect. What's actually going on is the errors are being shunted > over to > vty1 (Alt+F2) Under bhyve there is only a serial console currently, afict. > as well as /tmp/bsdinstall_log Didn't know that. Thanks for the useful information. > But granted... the error messages that are displayed on vty0 could > certainly > be improved (which will take time). Mark