Nam lacinia pulvinar torsectetur adipiscing elit. Pellentesque dapibus efficsectetur adipiscing elit. Nam lacinia pulvinar tortor nec facilisis. Pellentesque d sectetur adipiscing eli sectetur adipiscing elit. Nam risus ante, dapibus a molestie csectetur adipiscing elit. Nam lacinia pulvinar tortor nec ctetur adipiscing elit. Nam lacinia pulvinar tortor nec facilsectetur adipiscing elit. Nam lacinia pulvinar tortor necsectetur adipiscing elit. Fusce dui lectus, congue vel laoreet ac, dictum vitae odio. Nam risus ante, dapibus a molestie consequat, ultrices ac magna. I've also tried setting the network interface to bridge mode and no change.Įdit: All other VM work properly, including other FreeBSD 13.1 virtual machines but same behavior with FreeBSD 12.3.Sectetur adipiscing elit. I've also tried to create a brand new pfSense VM using the same settings as our currently running ones and while it installs properly, after the reboot it is stuck on "Default interfaces not found - Running interface assignment option.". I've tried changing the adapter to either of the Intel PRO/1000 Server options and it does eventually boot after a 5 minute hang at the same point, but it is unable to get an IP and therefore doesn't work either. The pfSense VM (CE 2.6.0) is configured with EFI enabled and the WAN interface is a NAT virtual network adapter with "virtio-net". Reverting VirtualBox back to 6.1.40 fixes it. After a recent upgrade from VirtualBox 6.1.40 to 7.0.2 on Arch Linux, all of my pfSense virtual machines hang at "Configuring WAN interface" during the boot process.
0 kommentar(er)
