Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 26 Jan 2016 19:07:58 -0600
From:      dweimer <dweimer@dweimer.net>
To:        Sergey Manucharian <sm@ara-ler.com>
Cc:        freebsd-virtualization@freebsd.org
Subject:   Re: bhyve with Linux guest, how to safely handle updates?
Message-ID:  <9ee895854c862cccc0bcc84c16eee063@dweimer.net>
In-Reply-To: <20160126230338.GM4109@debian.ara-ler.com>
References:  <790acf0350e0f10e79b4120e564a553c@dweimer.net> <20160126230338.GM4109@debian.ara-ler.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On 2016-01-26 5:03 pm, Sergey Manucharian wrote:
> Hi Dean,
> 
> Excerpts from dweimer's message from Tue 26-Jan-16 08:26:
>> I installed some updates using Aptitude within the
>> Debian guest which promptly broke the VM.
> 
> Additional info is needed to help:
> - bhyve command line you use to start the VM
> - what error messages do you see stating that it's broken?
> 
> Sergey

It was a while back I was running it, so I am not quite sure which 
method I had finally stuck with I worked through multiple different 
management scripts at the time before settling on the one I liked best. 
I tried at the time to manually run the VM without using the management 
script to no avail. It would start with no bhyve error on FreeBSD side, 
but when connecting to the console the grub boot loader couldn't find 
the kernel. It appeared to be a disconnect between the kernel upgrade 
within Linux updating grub configuration and the grub2-bhyve setup. 
Maybe it was just a one off issue and something went wrong during the 
Linux update and nothing to do with byhve. However at the time, I didn't 
have time to play with it and new I could get it working with 
VirtualBox.

Is there anything that normally needs to be done after a Linux kernel 
update to refresh the grub2-bhyve setup?
Its winter now, so I have some time to play with it again.
Unfortunately the old external hard drive I wrote a backup of the data 
to save until I had time to work on it again was too old, and doesn't 
want to spin up now, or I could provide the exact error information.

-- 
Thanks,
    Dean E. Weimer
    http://www.dweimer.net/



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9ee895854c862cccc0bcc84c16eee063>