From owner-freebsd-virtualization@FreeBSD.ORG Sun Mar 16 00:12:47 2014 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 678C4292 for ; Sun, 16 Mar 2014 00:12:47 +0000 (UTC) Received: from mail-lb0-x230.google.com (mail-lb0-x230.google.com [IPv6:2a00:1450:4010:c04::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id E55C0648 for ; Sun, 16 Mar 2014 00:12:46 +0000 (UTC) Received: by mail-lb0-f176.google.com with SMTP id 10so2708783lbg.21 for ; Sat, 15 Mar 2014 17:12:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=0ohbFSKXMPLIYAArT1UTtM9u5RJ3aI7ionEmnG4ommE=; b=UGVCNk2miC79cDdVqUeGQQhDIBDAtbfQY0TxQRg5imNI1qkJfhVp81Mrd6Dh/FwQN4 KBmdxBUUql6DWFJrMunb9UZuQH+cC68l6Q0G331y8hN//7+P5KSDdxjcl9Ob0Fv3MySA 3M/TRFnJFkIo2Au9JIJjN3RHY9GAi6/tyOSy8Yj4C7WNfTxxgto1L4yVl3jwhrWbKDCx y/63MowSW+SPlGPyTREq+7XledGA1/kegq0jT4cv9PpDfPWLWx8tPQd7kplEgCHae0Tx crE8NSrkEi2bU+4jIjn9IJCnzeKbtEa8DRZPzrEEz/9RurZQYYwLZcTbDcSH8huKNKId HIzw== MIME-Version: 1.0 X-Received: by 10.152.37.137 with SMTP id y9mr11100536laj.8.1394928765010; Sat, 15 Mar 2014 17:12:45 -0700 (PDT) Sender: crodr001@gmail.com Received: by 10.112.169.68 with HTTP; Sat, 15 Mar 2014 17:12:44 -0700 (PDT) In-Reply-To: <53174140.5040004@pix.net> References: <53174140.5040004@pix.net> Date: Sat, 15 Mar 2014 17:12:44 -0700 X-Google-Sender-Auth: _ThJzUnpEn8ofEO4a1ebWHvcuTw Message-ID: Subject: Re: Problem with ZFS userboot changes r262331 and VM with mixed partitions From: Craig Rodrigues To: Kurt Lidl Content-Type: text/plain; charset=ISO-8859-1 Cc: "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: Sun, 16 Mar 2014 00:12:47 -0000 On Wed, Mar 5, 2014 at 7:22 AM, Kurt Lidl wrote: > > > I ran into this same problem a couple of weeks ago when I first played > with the ZFS boot support in userboot.so. > > The following set of operations on the hypervisor can be used to add > bootable support to your zfs installation. > > (I don't know what the name of your zpool is on the emulated host. > If the name of that zpool is the same as the zpool on your hypervisor > host, you might have to go at this a different way.) I have taken > to naming the zpool for the any clients to be the same as the name > of the virtual machine, so I can easily mount it on the host running > the hypervisor and fiddle with it. > > For the purposes of this example, my virtual machine is called "vm0". > The zpool for that host lives in a zpool called "zdata" on my > hypervisor machine. In my case, my /boot was a symlink that > pointed to /bootdir/boot, so you might need to adjust the > following slightly. > > zfs import -f -R /mnt vm0 > > fsck_ufs /dev/zvol/zdata/vm0p2 > mount /dev/zvol/zdata/vm0p2 /mnt/bootdir > cd /mnt > chflags -h nosunlink boot > rm boot > cp -R bootdir/* . > umount /mnt/bootdir > cd / > zpool export vm0 > > Good luck. Hi, Thanks for breaking down the steps so nicely! I followed similar steps and got my VM to boot with the latest userboot. -- Craig