Date: Tue, 26 Jan 2016 19:13:48 -0700 From: Sergey Manucharian <sm@ara-ler.com> To: dweimer <dweimer@dweimer.net> Cc: freebsd-virtualization@freebsd.org Subject: Re: bhyve with Linux guest, how to safely handle updates? Message-ID: <20160127021348.GE1799@dendrobates.araler.com> In-Reply-To: <9ee895854c862cccc0bcc84c16eee063@dweimer.net> References: <790acf0350e0f10e79b4120e564a553c@dweimer.net> <20160126230338.GM4109@debian.ara-ler.com> <9ee895854c862cccc0bcc84c16eee063@dweimer.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Excerpts from dweimer's message from Tue 26-Jan-16 19:07: > > Is there anything that normally needs to be done after a Linux kernel > update to refresh the grub2-bhyve setup? The kernel update should not have any effect since grub-bhyve uses the virtual disk mapping file, which should point to your linux drive. I'm using the following command: $ sudo grub-bhyve -m /path/to/device.map -r hd0,msdos1 -M 1024M debian where "device.map" contains the following: (hd0) /dev/zvol/zroot/linuxdisk1 (cd0) /stuff/vm/bhyve/debian/debian-testing-amd64-2015-11-30.iso "hd0" can be a real disk device, e.g. /dev/sda, or an image file (in my case it's a ZFS volume). How do you use that VM in VBox? If it's a .vdi file, bhyve will not be able to recognize it. You should use a raw HDD image file. To make it compatible with VBox you can create a .vmdk file pointing to that raw image. -- Sergey
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160127021348.GE1799>