From owner-freebsd-virtualization@FreeBSD.ORG Thu Jan 23 10:53:21 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 2B2DE709 for ; Thu, 23 Jan 2014 10:53:21 +0000 (UTC) Received: from mail-vb0-x236.google.com (mail-vb0-x236.google.com [IPv6:2607:f8b0:400c:c02::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D0F0F1F54 for ; Thu, 23 Jan 2014 10:53:20 +0000 (UTC) Received: by mail-vb0-f54.google.com with SMTP id w20so950996vbb.13 for ; Thu, 23 Jan 2014 02:53:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=ng5AZOKJSMl8GqIsLGOlm091Snuo1uv1+AEi4izIwws=; b=mSCKsiHBmwtJo/DLd/dnJAy+X4fSAUahSPukGPHITSLvqldQvNuw6/z2kzEeGzZHYb 5/IARZQjVgDMvLgJjhzQWor31BYzcCg9wD8t0v04VeV0bq4iBBJHi8Hlr3NKcP+2/4Mr M4va2EMaA9/J7kT/AoMjz3nBtFAw42mMflZFIw9+TS0AfTlIozbaCNAOecyAxgZsE1r6 9B+rUyXNPBWJOztQsc+HWTrAN9EBgxp8na2tsjuIeG4FjHvQumP8p4ZMXXmq+moZyi81 HTT37CbBGj1eNmstnUSqWjryDjAwODTO9O/ZncWLaQ9jqbB2/gktehU8B475veqLU0Qn HgjQ== MIME-Version: 1.0 X-Received: by 10.58.4.138 with SMTP id k10mr4172129vek.8.1390474399913; Thu, 23 Jan 2014 02:53:19 -0800 (PST) Received: by 10.220.0.137 with HTTP; Thu, 23 Jan 2014 02:53:19 -0800 (PST) In-Reply-To: References: <52E0C1D4.9000304@freebsd.org> <52E0D1BB.2050807@callfortesting.org> Date: Thu, 23 Jan 2014 11:53:19 +0100 Message-ID: Subject: Re: Linux on BHyVe in 10.0-RELEASE From: =?ISO-8859-1?Q?Jonas_B=FClow?= To: Aryeh Friedman Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.17 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: Thu, 23 Jan 2014 10:53:21 -0000 FWIW, I extracted the syslog for the failing ubuntu installation. The failing grub install shows up as: Jan 23 10:51:08 grub-installer: info: architecture: amd64/generic Jan 23 10:51:08 in-target: Reading package lists... Jan 23 10:51:08 in-target: Reading package lists... Jan 23 10:51:08 in-target: Jan 23 10:51:08 in-target: E: Write error - write (28: No space left on dev= ice) Jan 23 10:51:08 in-target: E: Can't mmap an empty file Jan 23 10:51:08 in-target: E: Failed to truncate file - ftruncate (9: Bad file descriptor) Jan 23 10:51:08 in-target: E: The package lists or status file could not be parsed or opened. Jan 23 10:51:08 grub-installer: info: Identified partition label for /dev/vda1: msdos Jan 23 10:51:08 main-menu[211]: (process:18530): chroot: can't execute 'grub-probe': No such file or directory Jan 23 10:51:08 main-menu[211]: (process:18530): sh: write error: No space left on device Jan 23 10:51:08 main-menu[211]: (process:18530): sh: write error: No space left on device Jan 23 10:51:08 main-menu[211]: (process:18530): sh: write error: No space left on device Jan 23 10:51:08 main-menu[211]: (process:18530): sh: write error: No space left on device Jan 23 10:51:08 main-menu[211]: (process:18530): sh: write error: No space left on device Jan 23 10:51:08 main-menu[211]: (process:18530): sh: write error: No space left on device Jan 23 10:51:08 main-menu[211]: (process:18530): sh: write error: No space left on device Jan 23 10:51:08 main-menu[211]: (process:18530): chroot: can't execute 'grub-probe': No such file or directory Jan 23 10:51:08 main-menu[211]: (process:18530): File descriptor 3 (pipe:[7196]) leaked on lvdisplay invocation. Jan 23 10:51:08 main-menu[211]: (process:18530): Parent PID 18735: /bin/sh Jan 23 10:51:08 main-menu[211]: (process:18530): File descriptor 4 (/dev/ttyS0) leaked on lvdisplay invocation. Jan 23 10:51:08 main-menu[211]: (process:18530): Parent PID 18735: /bin/sh Jan 23 10:51:08 main-menu[211]: (process:18530): File descriptor 5 (/dev/ttyS0) leaked on lvdisplay invocation. Jan 23 10:51:08 main-menu[211]: (process:18530): Parent PID 18735: /bin/sh Jan 23 10:51:08 main-menu[211]: (process:18530): File descriptor 6 (/dev/ttyS0) leaked on lvdisplay invocation. Jan 23 10:51:08 main-menu[211]: (process:18530): Parent PID 18735: /bin/sh Jan 23 10:51:08 main-menu[211]: (process:18530): Jan 23 10:51:08 main-menu[211]: (process:18530): Volume group "vda" not fou= nd Jan 23 10:51:08 main-menu[211]: (process:18530): Jan 23 10:51:08 main-menu[211]: (process:18530): Jan 23 10:51:08 main-menu[211]: (process:18530): Skipping volume group vda Jan 23 10:51:08 main-menu[211]: (process:18530): Jan 23 10:51:08 main-menu[211]: (process:18530): debconf: DbDriver "config": could not write /var/cache/debconf/config.dat-new: No space left on device Jan 23 10:51:08 main-menu[211]: WARNING **: Configuring 'grub-installer' failed with error code 1 Jan 23 10:51:08 main-menu[211]: WARNING **: Menu item 'grub-installer' fail= ed. Jan 23 10:51:09 main-menu[211]: INFO: Modifying debconf priority limit from 'medium' to 'low' Jan 23 10:51:09 debconf: Setting debconf/priority to low Jan 23 10:51:14 main-menu[211]: INFO: Menu item 'save-logs' selected On Thu, Jan 23, 2014 at 11:37 AM, Aryeh Friedman wrote: > > > > On Thu, Jan 23, 2014 at 5:05 AM, Jonas B=FClow wro= te: > >> I do use the precanned bhyve-script "vm0" (if that is what you mean). It >> explicitly mentions linux support. bhyveload can't be user for other ima= ges >> than FreeBSD so I don't know how to use your script for a linux OS >> > > Since I have not used bhyve-grub personally yet I can not recommend what > the correct loader command line but if bhyve-script is in anyway related = to > vmrun.sh I would be highly suspicious of any command lines you manage to > extract from it since they are often not the ones actual called. > > >> >> I assume the image is file backed as I have not assigned a dedicated >> partition to the vm (and I don't know how to do that). >> > > You can keep them anywhere no need for a special volume (mater of fact I > was just reusing the name of one of the diretoriess that PC creates durin= g > install even without it being a different vol [just assumes any FS > boundaries are the host OS's problem)... you can put the disk image any > where (your home directory would be fine for example) >