Opened 4 months ago
Last modified 3 months ago
#22279 new defect
startvm --type headless problem persists
| Reported by: | christaylor_la | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox-7.1.4 |
| Keywords: | Cc: | ||
| Guest type: | Linux | Host type: | Windows |
Description
Hi - I have Version 7.1.4 r165100 (Qt6.5.3) installed and the same extension pack, but I'm still running into this: https://www.virtualbox.org/ticket/22162
No logs are written to the 'Virtual VMs\<box>\Logs', I just get this message. Booting with the GUI works fine. Is there any workaround yet?
PS C:\Users\ctaylor\Downloads> & 'C:\Program Files\Oracle\VirtualBox\VBoxManage.exe' startvm f57c7f3a-7d49-4c7d-ad87-d30d918d2abb --type headless Waiting for VM "f57c7f3a-7d49-4c7d-ad87-d30d918d2abb" to power on... VBoxManage.exe: error: The virtual machine 'rocky9.4test1' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005) VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component MachineWrap, interface IMachine
Edition Windows 11 Pro Version 24H2 OS build 26100.2605 Experience Windows Feature Experience Pack 1000.26100.36.0
Another odd thing is I have another PC, same Windows build but it's 11 Home, and '--type headless' works no problem.
Change History (4)
comment:1 by , 4 months ago
comment:2 by , 4 months ago
It doesn't write any logs - is there a way to force it to write something out before it fails?
comment:3 by , 3 months ago
Does anyone have any suggestions for me to get some diagnostics? I've been using VBox for years on Windows and I've never hit something like this. It works fine on Windows 11 Home but I have to run on Pro for company support reasons. Nobody else is running into this?
comment:4 by , 3 months ago
I upgraded to Version 7.1.6 r167084 (Qt6.5.3) and I'm still having the problem.
Logs, please. Both hardening and VBox.log.