Linux on BHyVe in 10.0-RELEASE

Lars Engels lars.engels at 0x20.net
Thu Jan 23 11:38:13 UTC 2014


Am 2014-01-23 11:53, schrieb 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
> 
> 
> 

Normally you can switch to another virtual console with Alt+F1 to F4 
(IIRC), I don't know if
that's also possible in bhyve.
If it works, please open a shell and see with "df" which filesystem is 
full.


More information about the freebsd-virtualization mailing list