VirtualBox

Ticket #20574 (new defect)

Opened 2 months ago

Last modified 8 weeks ago

VBoxManage 'start --type headless' cannot be correctly closed by 'controlvm acpipowerbutton'

Reported by: Q2K3 Owned by:
Component: VM control Version: VirtualBox 6.1.26
Keywords: VBoxManage Cc:
Guest type: Linux Host type: Windows

Description

After using:

VBoxManage startvm CentOS7-1 CentOS7-2 CentOS7-3 --type headless

CentOS7-1, 2, 3 are individual vms created by meself and started correctly.

After using:

VBoxManage controlvm CentOS7-3 acpipowerbutton

The vm named CentOS7-3 should have been closed correctly.

But after using:

VBoxManage startvm CentOS7-3 --type headless

It fails and outputs as below:

Waiting for VM "CentOS7-1" to power on...
VBoxManage.exe: error: The VM session was closed before any attempt to power it on
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component SessionMachine, interface ISession

you can find more detail infos in the topic I posted  https://forums.virtualbox.org/viewtopic.php?f=3&t=103980

What's more, through log file named VBoxHardening.log.I find log file which is closed incorrectly lack two lines outputs comparing to log file which is closed correctly:

3fd0.3fd4: supR3HardNtChildWaitFor[2]: Quitting: ExitCode=0x0 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 604653 ms, the end);
3f98.3f9c: supR3HardNtChildWaitFor[1]: Quitting: ExitCode=0x0 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 605077 ms, the end);

Hope this additional msg can help pro devs to solve this problems. Thx for devs attention and contributions!

Attachments

VB-logfiles.zip Download (105.0 KB) - added by Q2K3 2 months ago.
it contains log files which are closed correctly and incorrectly

Change History

Changed 2 months ago by Q2K3

it contains log files which are closed correctly and incorrectly

comment:1 follow-up: ↓ 3 Changed 2 months ago by Q2K3

  • Status changed from new to awaitsfeedback

comment:2 Changed 2 months ago by scottgus1

User 'lanza' also reports this problem  https://forums.virtualbox.org/viewtopic.php?f=6&t=103974

comment:3 in reply to: ↑ 1 Changed 2 months ago by fth0

Replying to Q2K3: I think the state awaitsfeedback means waiting for feedback from the reporter, so perhaps you want to change it back. ;)

comment:4 Changed 2 months ago by Q2K3

  • Status changed from awaitsfeedback to new

comment:5 Changed 2 months ago by fth0

In the corresponding forum thread, Q2K3 reported that the issue does not occur with VirtualBox 6.1.24, meaning that the issue was introduced between 6.1.24 and 6.1.26.

Additionally, Q2K3 reported that all 3 nested VBoxHeadless processes keep running. A third affected forum user reported that only 1 of the 3 processes is left running.

comment:6 Changed 8 weeks ago by fth0

This issue should be fixed in the VirtualBox test builds 6.1.27r147422 and newer.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use