João Dalvi
Junior Member
- Joined
- Jan 17, 2014
- Messages
- 15
Isn't it possible to symlink bootx64.efi to grubx64.efi?
Will this issue ever be corrected?
Will this issue ever be corrected?
Yes - to the EFI partition.rEFInd goes on the guest OS, right?
If would be interesting to know just what development work is taking place on bhyve. The mailing list https://lists.freebsd.org/pipermail/freebsd-virtualization points to current and recent problems and http://bhyvecon.org/ provies gives a few hints. The latter lists one piece of work by Marcelo Araujo for FreeNAS/FreeBSD for 2018..Finally, is FreeBSD developers actively improving bhyve, so that threads like this sound less troublesome?
Might be. But when you try to boot your VM what messages to do you see in the logs re: bhyve?@soko: same issue here, started separate thread https://forums.freenas.org/index.ph...d-disk-not-visible-in-efi-boot-manager.69640/
tail -f /var/log/middlewared.log
[2018/09/03 03:12:27] (DEBUG) VMService.run():155 - ====> NIC_ATTACH: re0 [2018/09/03 03:12:27] (DEBUG) VMService.run():231 - Starting bhyve: bhyve -H -w -c 1 -m 4096 -s 0:0,hostbridge -s 31,lpc -l com1,/dev/nmdm1A -l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd -s 3,e1000,tap0,mac=00:a0:98:7b:b4:ad -s 29,fbuf,vncserver,tcp=0.0.0.0:5901,w=1024,h=768,, -s 30,xhci,tablet -s 4,virtio-blk,/dev/zvol/ssd480enc/ubuntu/ubuntu -s 5,ahci-cd,/mnt/vol/Install_Files/ubuntu/ubuntu-16.04.5-desktop-amd64.iso 1_ubuntu [2018/09/03 03:12:27] (DEBUG) VMService.run():250 - ubuntu: 02/09/2018 20:12:27 Listening for VNC connections on TCP port 5901 [2018/09/03 03:12:27] (DEBUG) VMService.run():250 - ubuntu: 02/09/2018 20:12:27 Listening for VNC connections on TCP6 port 5901
[2018/09/04 18:15:40] (DEBUG) VMService.run():155 - ====> NIC_ATTACH: igb0 [2018/09/04 18:15:40] (DEBUG) VMService.run():231 - Starting bhyve: bhyve -H -w -c 4 -m 4096 -s 0:0,hostbridge -s 31,lpc -l com1,/dev/nmdm2A -l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd -s 3,e1000,tap0,mac=00:a0:98:7c:b0:ec -s 29,fbuf,vncserver,tcp=192.168.31.12:5902,w=1920,h=1200,, -s 30,xhci,tablet -s 4,ahci-hd,/dev/zvol/volume0/vm-epiphyt-sda,sectorsize=4096 2_epiphyt [2018/09/04 18:15:40] (DEBUG) VMService.run():244 - ==> Start WEBVNC at port 5802 with pid number 33869 [2018/09/04 18:15:40] (DEBUG) VMService.run():250 - epiphyt: 04/09/2018 20:15:40 Listening for VNC connections on TCP port 5902 [2018/09/04 18:15:40] (DEBUG) VMService.run():250 - epiphyt: 04/09/2018 20:15:40 Listening for VNC connections on TCP6 port 5902
Correct, this problem surface some time ago in FreeNAS 11.2 betas. Since I habitually use virtio for NIC and HDD devices I clean forgot the obvious when looking at your posts.I spotted the differenceL soko uses virtio driver instead of ahci. Turning to virtio makes the virtual disk visible in the "boot from file" menu of the Boot Maintenance Manager. The vm properly boots after manually choosing the grubx64.efi. So the issue is related to the ahci setting.
# Work around buggy UEFI implementations that do not support boot entries # correctly: # https://wiki.debian.org/UEFI#Force_grub-efi_installation_to_the_removable_media_path d-i grub-installer/force-efi-extra-removable boolean true
d-i preseed? Not for the casual user then. But just use expert install, surely that's easier than mounting then copying an ios , changing the preseed file and then generating a new iso.I had to do a little searching to find this since it doesn't show up in Debian's example preseed, but you can also do this if you use preseeds:
Code:# Work around buggy UEFI implementations that do not support boot entries # correctly: # https://wiki.debian.org/UEFI#Force_grub-efi_installation_to_the_removable_media_path d-i grub-installer/force-efi-extra-removable boolean true
Unfortunately this is still necessary with 11.2-BETA3.