[Bug]: VirtualBox 7.2.10 in macOS Tahoe 26.5.1 failed to attach the network LUN

[crazeapple]

Version

7.2.10

Host OS Type

macOS

Host OS name + version

macOS Tahoe 26.5.1

Host Architecture

ARM

Guest OS Type

Linux

Guest Architecture

ARM

Guest OS name + version

Ubuntu 24.04 LTS

Component

API

What happened?

I have 2 MacBook Pro. With the MacBook Pro 2026 M5 Pro, namely Apple Silicon(ARM64), I turned off the SIP and installed VirtualBox 7.2.10, then I launched the guest OS Ubuntu 24.04 LTS, then it reported:

There was an error while executing VBoxManage, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["startvm", "a964933f-1aa8-4aed-93d8-2fd48a985b51", "--type", "headless"]

Stderr: VBoxManage: error: Error: vmnet_start_interface returned 1001 (VERR_INVALID_PARAMETER).
VBoxManage: error: Failed to attach the network LUN (VERR_INVALID_PARAMETER)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component ConsoleWrap, interface IConsole

I tried every way, it didn't work.

And, I have 2 virtual machines running for over a week in VirtualBox 7.2.4(x64) on another MacBook Pro 2019, x64 Intel-Chip. The guest OS is also Ubuntu 24.04 LTS. Then I updated the macOS to the latest Tahoe 26.5.1. After reboot, the 2 virtual machines was still running. Later I stopped one virtual machine, but when I started it, it reported the same error on my another MacBook. Even though, I added a new host-only network, switch to it, and the virtual machine still couldn't boot

How can we reproduce this?

Update macOS to the latest Tahoe 26.5.1

• x64 or arm64 VirtualBox 7.2.4+
• x64 or arm64 host OS
• x64 or arm64 Ubuntu 24.04 LTS

then lauch start the vm

Did you upload all of your necessary log files, screenshots, etc.?

• Yes, I've uploaded all pertinent files to this issue.

[alflr]

Can you please upload the full VBox.log?

[crazeapple]

Can you please upload the full VBox.log?

@alflr I hope it's not too late to reply to you.
I'd like to upload the logs of 2 VMs on the Intel-chip MacBook, with VirtualBox 7.2.4. But the VM on the MacBook Pro M5 Pro was deleted, and VirtualBox 7.2.10 was also uninstalled, because I temporarily turned to Multipass for VM.
Here is the first log, and this VM is still running after macOS upgraded to 26.5.1 and rebooting. You can see the VM was started on 2026-06-13T06:28:50, and at the tail of log, the VM state changed from SUSPENDED to RESUMING, then to RUNNING.
The second log recorded the starting process of the VM which I restarted, and reported above error. If I restart the first VM, I'm sure I'll get the same result as this one.
Hope this will help.

first.log

second.log