[Bug]: Virtualbox can't open bridge network on macos 27.2

Open
#941 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 6 days

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
c, macos

Research direction

Start by reading the VMNet startup errors in the issue logs, especially the timeout and vmnet_start_interface return value; the report does not name a source file or test. Compare behavior on macOS 27.2 with the prior OS version where the VM worked, then identify a reproducible cause and verify bridge networking starts successfully.

Written by the indexing model from the issue text.

Description

bug
Version

trunk/main

Host OS Type

macOS

Host OS name + version

macOS 27.2

Host Architecture

ARM

Guest OS Type

Linux

Guest Architecture

ARM

Guest OS name + version

No response

Component

Unspecified

What happened?

vm never starts. this error shows in the logs:

00:00:01.307800 SCSI#1: Enabled UNMAP support
00:00:01.308012 E1000#0: Chip=82540EM LinkUpDelay=5000ms EthernetCRC=on GSO=enabled Itr=disabled ItrRx=enabled TID=disabled R0=disabled RC=disabled
00:00:01.308176 VMNet: Bridge to en0
00:01:01.310091 VMNet: Failed to start VMNET interface due to time out!
00:01:01.310177 VMSetError: /Users/vbox/tinderbox/7.2-mac-rel/src/VBox/Devices/Network/DrvVMNet.m(650) int drvVMNetConstruct(PPDMDRVINS, PCFGMNODE, uint32_t); rc=VERR_INVALID_PARAMETER
00:01:01.310180 VMSetError: Error: vmnet_start_interface returned 1001

selectorwindow.log
VBoxSVC.log

How can we reproduce this?

running a linux VM ion OS 27. this did not occur with this VM prior to upgrade

Did you upload all of your necessary log files, screenshots, etc.?
  • Yes, I've uploaded all pertinent files to this issue.
Dominant language
C
Stars
1.4k
Forks
219
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from VirtualBox/virtualbox

All issues in VirtualBox/virtualbox

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.