• Currently using VMware at work? We want to hear from you.

    Thinking of making a switch from VMware? We'd love to hear your thoughts and feedback about which hypervisor you have been researching or already using. Click here to vote and share your thoughts! You can vote HERE!

VM boot

Status
Not open for further replies.

Plotkin

Cadet
Joined
Apr 5, 2017
Messages
9
Pretty sure I'm doing something wrong here.

I'm having some trouble installing a VM and would appreciate some pointers.

Installed ubuntu server 17 on a VM with 2GIB (MEM) and 15GIB (VDD) and 2 virtual cores.

Installation goes without a hitch but when I try to boot into it via VNC I get what you see in the picture.
fRa7v6


https://ibb.co/fRa7v6 (that is the image)

I tried going into behyve "bios" but boot order seems fine.

Appreciate any help.
 

Plotkin

Cadet
Joined
Apr 5, 2017
Messages
9
UPDATE: installed server 16 in same method and it works fine.

humph.

UPDATE #2: Spoke too soon, after stopping the VM and starting it (also with snapshot revert) still goes to that bios screen.

Any clues?
 
Last edited:

KrisBee

Wizard
Joined
Mar 20, 2017
Messages
1,288

icsy7867

Contributor
Joined
Dec 31, 2015
Messages
167
I had a similar issue and did what that thread said which worked fine.

I actually followed a post in this post:
https://forums.freenas.org/index.php?threads/freenas-11-bhyve-and-zentyal-4-2.54290/

  1. Install Ubuntu Server 16.04.2 into a VM (which will install ok)
  2. It will then drop you out to the UEFI shell on first boot, as the required EFI file location won't be there (thanks to Krisbee's guide here to explain the reason https://forums.freenas.org/index.ph...-boot-linux-vms-using-uefi.54039/#post-375824)
  3. Type exit in UEFI shell and go to Boot Maintenance Manager and select Boot From File
  4. Step through the only option and select grubx64.efi
  5. Your VM will now boot up
  6. Run sudo su - and cd to /boot/efi/EFI
  7. Run mkdir BOOT
  8. Run cp /boot/efi/EFI/ubuntu/grubx64.efi /boot/efi/EFI/BOOT/bootx64.efi
  9. Shutdown your VM and start again. It should boot normally now
 

Plotkin

Cadet
Joined
Apr 5, 2017
Messages
9
Cheers man, I managed to get the hang of it due to your link on my ubuntu server.

Much appreciated!

It's basically a compatibility issue of a missing expected file:

On a different CentOS 7 installation:

1. bhyve looks for: "/EFI/BOOT/bootx64.efi"

2. Was found under: "/boot/efi/EFI/BOOT"

Copying the file over and creating the directories worked fine.

The workaround works well also, to manually guide bhyve bios to the absolute path of bootx64.efi on the installed guest destribution.

Again, thank you.
 
Last edited:
Status
Not open for further replies.
Top