vbox Weird problem with vtnet adapter after update to VirtualBox 7.2.6

V

von_Gaden

I've noticed an unusual behaviour in FreeBSD guests with VirtIO network adapters. The setup is simple: Host is FreeBSD (currently 15.0-RELEASE), same as the guest (or at least 14.3-RELEASE). There is a
vtnet network adapter bridged to one of the host's - either physical or cloned VLAN.
After updating emulators/virtualbox-ose-72 from 7.2.4 to 7.2.6 (or 7.2.6_1) the guest hangs at the point of bringing vtnet interface up. Changing the guest network interface to some Intel (eg. Intel PRO/1000 Server) solves the problem and the system starts successfully with working network.
I've thought that this might be some setup-related issue but yesterday I hit the same problem with Debian guest. Using VirtIO adapter the system displays "performing startup task: bringing up the network" and repeats the message forever. Changing the adapter to Intel solves the problem.
The weirdest is, that there are some Windows guests (running on the same hosts) with VirtIO adapters (drivers provided by Fedora, different versions) and they work just fine. The *NIX systems seem to be only affected by the problem.
Unfortunately log files don't point to any clue.
I have about 10 problematic setups and I think this is a symptom.
Did someone hit the same problem? Perhaps I've missed some uptating note?

Thanks in advance!
 
I got home today and got welcomed by frozen boot screen. Right after the copyright banner and console video properties are listed.
I had to blacklist vboxdrv from loader prompt and then proceed into boot. Nothing else worked, and there were no additional info in verbose mode.

Last thing I done night before was upgrade latest pkg, I bet vbox was updated.

This is no VM, it is a physical machine, VirtualBox used as desktop hypervisor.
 
Thank you very much!
Adding
Code: 
hw.virtio.pci.transitional="1"
to /boot/loader.conf definitely helped. I'm curious what could cause this. Given the bug mentioned above it seems the reason is still unclear.
 
Zare said:
I got home today and got welcomed by frozen boot screen. Right after the copyright banner and console video properties are listed.
I had to blacklist vboxdrv from loader prompt and then proceed into boot. Nothing else worked, and there were no additional info in verbose mode.

Last thing I done night before was upgrade latest pkg, I bet vbox was updated.

This is no VM, it is a physical machine, VirtualBox used as desktop hypervisor.
Click to expand...
I'm not sure you are facing the same issue. All my setups with emulators/virtualbox-ose-72 use vboxdrv. Booting either UEFI or CSM with no problems. Each runs at least 1 VM in headless mode, but I think this happens later during the boot process.
 
You must log in or register to reply here.
Back
Top