Opened 4 years ago
Closed 4 years ago
#19706 closed defect (fixed)
MacOS hosts no longer able to run VBoxHeadless as of 6.0.18 and 6.1.4 => fixed in svn/6.1.x x>12
Reported by: | myshell | Owned by: | paulson |
---|---|---|---|
Component: | guest control | Version: | VirtualBox 6.1.4 |
Keywords: | Cc: | ||
Guest type: | all | Host type: | Mac OS X |
Description (last modified by )
It is impossible to launch a VM in headless mode because of a problem of setugid which is not allowed.
It works fine with VirtualBox 6.1.2 but not with the following versions.
The error message seen is:
$ /Applications/VirtualBox.app/Contents/MacOS/VBoxHeadless -s solaris Oracle VM VirtualBox Headless Interface 6.1.4 (C) 2008-2020 Oracle Corporation All rights reserved.
2020-07-24 09:40:25.798 VBoxHeadless[2026:18559] The application with bundle ID org.virtualbox.app.VirtualBox is running setugid(), which is not allowed.
Attachments (1)
Change History (6)
comment:1 by , 4 years ago
Status: | new → awaitsfeedback |
---|
comment:2 by , 4 years ago
I tried the 3 ways, they all failed
$ VBoxHeadless -s Buster Oracle VM VirtualBox Headless Interface 6.1.10 (C) 2008-2020 Oracle Corporation All rights reserved.
2020-07-09 09:54:39.267 VBoxHeadless[28189:26305689] The application with bundle ID org.virtualbox.app.VirtualBox is running setugid(), which is not allowed.
comment:3 by , 4 years ago
Description: | modified (diff) |
---|---|
Owner: | set to |
Status: | awaitsfeedback → accepted |
Summary: | MacOS Mojave and VboxHeadless → MacOS hosts no longer able to run VBoxHeadless as of 6.0.18 and 6.1.4 |
Version: | VirtualBox 6.1.10 → VirtualBox 6.1.4 |
This is related to the VirtualBox hardened runtime which I didn't run into since this Mac system has System Integrity Protection (SIP) disabled. Once I re-enabled SIP I was able to reproduce the problem and have a fix in progress. This issue was introduced in VirtualBox 6.0.18 and 6.1.4.
comment:4 by , 4 years ago
Summary: | MacOS hosts no longer able to run VBoxHeadless as of 6.0.18 and 6.1.4 → MacOS hosts no longer able to run VBoxHeadless as of 6.0.18 and 6.1.4 => fixed in svn/6.1.x x>12 |
---|
This has been addressed in revision r139544 of the development branch of VirtualBox and is available now in the development snapshot Testbuilds. The fix has also been backported to the 6.1 branch of VirtualBox as of revision r139010 and is available now in the 6.1.x Testbuilds. The fix will also be part of the next maintenance release of VirtualBox 6.1.x.
comment:5 by , 4 years ago
Resolution: | → fixed |
---|---|
Status: | accepted → closed |
Can you provide further details about the issue you are seeing? Which method are you using to start your headless VM? The manual (https://www.virtualbox.org/manual/ch07.html) explains there are several ways to start a headless VM:
I am able to launch a headless VM using VirtualBox 6.1.10 on Mojave using all of the above methods so there must be something different about your setup.
Can you try the 'VBoxHeadless' command above and include any error messages seen? Can you also attach a VBox.log from a failed instance to start the VM in headless mode?