Linux on BHyVe in 10.0-RELEASE

[Jonas Bülow]

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 device)
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 found
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' failed.
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
<aryeh.friedman at gmail.com>wrote:

>
>
>
> On Thu, Jan 23, 2014 at 5:05 AM, Jonas Bülow <jonas.bulow at gmail.com>wrote:
>
>> 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 images
>> 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 during
> 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)
>