VirtualBox 7.1.8 fails to start guests with long VM names or deep paths due to libslirp initialization failure (regression from 7.0.x)

[zxyliho]

Product: VirtualBox
Version: 7.1.8
Host OS: Windows 11, NTFS

After upgrading from VirtualBox 7.0.x to 7.1.8, some VMs fail to start with the following error in the VirtualBox log:
VMSetError: libslirp failed to create new instance - probably misconfiguration
VMSetError: Failed to attach the network LUN
VERR_INTERNAL_ERROR_4 (-228)

After isolating the issue, I discovered that:
The failure only occurs on guests with long VM names.
Shortening the VM name allows the guest to start normally.

This issue did not occur in VirtualBox 7.0.x — all guests with long names ran without error.

[alflr]

Please attach the VBox.log for further analysis.

[EvocativeOlash]

Yea hit the same error after finally doing the jump, had to uninstall 7.0 before reinstalling 7.1 or nothing would work.

Now its just the ones with too long names.

 VM Name: *too long name puppy linux bionix 8

Configuration error: libslirp failed to create new instance - probably misconfiguration (VERR_INTERNAL_ERROR_4).
Failed to attach the network LUN (VERR_INTERNAL_ERROR_4).
Result Code:
E_FAIL (0x80004005)
Component:
ConsoleWrap
Interface:
IConsole {6ac83d89-6ee7-4e33-8ae6-b257b2e81be8}

[alflr]

This will be fixed in the next upcoming maintenance release (> 7.1.10).