bhyve migrating KVM VM to Bhyve, stuck at bootloader

I've copied a raw VM image over from a Linux machine, created what I think is the appropriate template (cpu, memory, nic, pointed at img file) and when I do a "vm start <machine>" it starts, but "vm list" shows it at "Bootloader" under STATE, and no VNC listener opens up. How can I get into the VM to see what it's doing/why its not booting ?
 
Some Linux installations require specific settings for grub in the VM's config:


How can I get into the VM to see what it's doing/why its not booting ?
Look at the console; vm console <machine>.

and no VNC listener opens up
Only works if you UEFI boot the VM and enabled graphics

 
but why,why,a lot of users use vm-bhyve. It's not true that it helps to configure the bhyve vms. Without it is easier.
 
but why,why,a lot of users use vm-bhyve.
It makes me scared that we agree on something.

It seems many people don't recognize vm-bhyve as a crutch.
They think its normal use.
We can chuckle at them.
Just like users of CWM laugh at us for using xfce4 instead of compiling a WM.
 
The FreeBSD handbook Bhyve instructions for Linux guests work great.
Making a device.map is an important part.
 
I don't understand what you're saying, but asking why people choose specific tools doesn't help answer the question.

First of all vm-bhyve is not a tool,it's a wrapper. And to know why someone uses something help to understand a little better what are the user level of knowledge,or what like or dislikes. This help to direct a good answer.
 
Back
Top