On 15/06/2018 15:02, Rodney W. Grimes wrote:
With the VM shutdown look in /dev/vmm for the same name as the VM,
if you see it there, make sure you do not have a running instnace
of it, then do:
bhyvectl --destroy --name=fbsd11-vm
You may have remanants of a prior/crashed VM hanging around
> On 14/06/2018 23:26, David P. Discher wrote:
> > Try in /boot/loader.conf of the VM :
> >
> > console=userboot
> >
> > or after beastie drop to loader OK promot ?and try :
> >
> > set console=userboot
> >
> > I think 11.x should fall back to userboot in?bhyve if vidconsole of
> > comconsole
On 14/06/2018 23:26, David P. Discher wrote:
Try in /boot/loader.conf of the VM :
console=userboot
or after beastie drop to loader OK promot and try :
set console=userboot
I think 11.x should fall back to userboot in bhyve if vidconsole of
comconsole were set.
(This is assuming non-EFI
Try in /boot/loader.conf of the VM :
console=userboot
or after beastie drop to loader OK promot and try :
set console=userboot
I think 11.x should fall back to userboot in bhyve if vidconsole of comconsole
were set.
(This is assuming non-EFI booting - using bhyveloader ).
--
David P.
Hello list,
context is freebsd-12 r317212 host and freebsd-11-stable r333924 guest
I run this freebsd instance in screen. I start it like this:
vmrun.sh -c 4 -m 8192M -t tap3 -d fbsd-guest.img fbsd-guest
It starts, I get the daemon screen, then this:
/boot/kernel/kernel text=0x70572d
