Search results

Is there any way to change the boot order of a bhyve VM using the UEFI firmware before the VM is started? In a scenario where I have a guest OS already installed but want to reinstall it using a PXE booted network install, it seems that I first need to boot into the guest OS and use its own...

The device that FreeBSD is booting from is not a whole-disk pool. loader.efi is sitting in a simple EFI system partition on a GPT scheme disk. I've been running whole-disk pools on non-boot drives ever since ZFS was added to FreeBSD. I was pretty certain that's not the problem. Nevertheless...

The other disks contain whole-device ZFS pools. There's no partition scheme, ESP, or EFI binaries on them. The full gpart show output only shows some zvols from those pools that are used for virtual machine storage: [root@hyp0 ~]# gpart show => 40 488397088 nda0 GPT (233G)...

Nothing out of the ordinary, GPT scheme, first partition is an EFI system partition: [root@hyp0 ~]# gpart show nda0 => 40 488397088 nda0 GPT (233G) 40 2008 - free - (1.0M) 2048 262144 1 efi (128M) 264192 488132936 2 freebsd-zfs (233G)

tingo , your post indicates that your system is set to boot from efi/boot/BOOTx64.efi, not from efi/freebsd/loader.efi. Also, your loader.efi file is showing as 0 bytes long. What version of FreeBSD are you using, because on 14.0-RELEASE, neither loader.efi or boot1.efi are 393216 bytes long...

I spoke too soon. It seems that tap interfaces are only automatically added to the bridge if I explicitly create them with an ifconfig command or in the cloned_interfaces directive in rc.conf. If I let bhyve automatically create a tap interface when I start a VM, it isn't added to the bridge...

I have a system that fails to boot using loader.efi but works OK with boot1.efi when installed as BOOTX64.EFI. My UEFI boot variables are set as follows: Boot to FW : false BootCurrent: 0001 Timeout : 1 seconds BootOrder : 0001, 0000 +Boot0001* UEFI OS...

Tried again, it's working. I have no idea why it wasn't working yesterday.

Having had a read through /etc/rc.d/bridge, it seems that the autobridge directives only do something when the rc scripts run at boot. It doesn't continuously watch for interfaces to add to a bridge.

I recently noticed this in rc.conf: I thought I would make use of this to automatically add tap interfaces to a bridge when they are created by bhyve, so added the following to my /etc/rc.conf: ifconfig_igb0="DHCP" cloned_interfaces="bridge0" ifconfig_bridge0="addm igb0"...

Hi. I'm just after information for this one really. I've already fixed the problem. I've just updated my FreeBSD router system from 13.2-RELEASE to 14.0-RELEASE using freebsd-update. As per the instructions, the process was: freebsd-update -r 14.0-RELEASE upgrade freebsd-update install...

FreeBSD 13.2-RELEASE [root@router ~]# mount /boot/efi mount_msdosfs: /dev/gpt/esp: Invalid fstype: Invalid argument [root@router ~]# mount_msdosfs /dev/gpt/esp /boot/efi mount_msdosfs: /dev/gpt/esp: Invalid fstype: Invalid argument [root@router ~]# mount_msdosfs...

I should have said, I checked those already. They're both enabled: kern.geom.label.gptid.enable: 1 kern.geom.label.gpt.enable: 1

I've just noticed that GPT partition labels are not being exposed under /dev on my FreeBSD router system. When I built the system, I gave my ESP a GPT label of "esp" and the label was accessible as /dev/gpt/esp, and I added a line to /etc/fstab that use that label to mount the ESP...

Hi. Ever since FreeBSD first started supporting native UEFI boot, I always used to use /boot/boot1.efi as the first boot loader by copying it to [ESP]/EFI/BOOT/BOOTX64.EFI. This has always worked just fine. But I've just noticed the following in uefi: The UEFI boot process proceeds as...

Perfect, thank you!

My ISP provides native IPv6 /56 prefixes via DHCP and I've had it working on multiple home subnets, via my FreeBSD router, for a couple of years now. Here's an overview of my setup: I have the KAME dhcp6 package installed, configured as follows (/usr/local/etc/dhcp6c.conf): interface wan0 {...

I'm running a FreeBSD router system at home with six interfaces, igb0-5. I've renamed these lan0-lan4 and wan0. I've also configured a bridge and made lan0, lan1 and lan2 members of it. When I ping a certain host on my network, tcpdump shows the ICMP ping request and reply packets on the...

Thanks SirDice, that does the trick. It's strange that some network services are being started before the network though. Could this be a bug?

Hi. I've just upgraded a 12.2-RELEASE system to 13.0-RELEASE, and during one of the reboots, I noticed that ctld was failing to start. Scrolling back through the boot messages on the console, I noticed that it was only after ctld tried to start that the network interfaces were configured...