Discuss the VirtualBox 7.2.4 release here

[Boxy]

I hope, after replacing the INTEL PRO/1000 DESKTOP virtual ether by virtio, the guest crashes will not happen again, and the (maybe) related 100% CPU of Virtualbox Manager disappears as a consequence.

Revised: network adapter wasn't the problem. Changed RHEL 9.6 from xterm to wayland and VM with 3D acceleration + 128M graphics memory: boot problem disappeared.

[ftolead]

I ran into this issue after upgrading from 7.2.2 to 7.2.4.

Windows 11 host, Rocky Linux and Linux Mint guests both failed to start.

This was fixed after a reboot of the host.

[hwertz]

I also see the 100% CPU usage. Hitting "H" in top tells me it's the NAT thread using 100%. I'm just sticking with it for now since I assume 7.2.5 or something will fix it; but I read on an Arch Linux thread that some are working around this by switching to bridged networking. This does make your VM a 'full participant' on your LAN (it gets a DHCP address from it and stuff on the LAN can then connect in to the VM) so keep that in mind.

[FREAKINGUSER]

Bring along the python you need to dont give me stuff to do manually.

'Also it doesn't work. USED THIS FOR YEARS and it's broken. Not sure if it's because of the python popup or not, but it fails to load my VMs that have worked for years. I rolled back to the previous one I was using.

Please fix this nonsense. And bring along what your code needs to give me a confusing alert about it needing something else.

sigh...

[Rezyder]

With NAT, I had a problem with 100% CPU load on the host. After switching to BRIDGE, the problem disappeared, but another problem arose. The bandwidth on the guest decreased three times compared to the host. I reverted to version 7.1.14, set it to NAT, and everything works better.