Opened 16 years ago
Closed 15 years ago
#5412 closed defect (wontfix)
VBoxHeadless allows non-headless VM to start
Reported by: | ToddAndMargo | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 3.0.10 |
Keywords: | Cc: | ||
Guest type: | Windows | Host type: | Linux |
Description ¶
Hi All,
Please do not allow
/usr/bin/VBoxHeadless --startvm $VM_Name
to start a VM if the VM's display is not configured for headless. You have to use "ps" to kill it and corruptions can occur in your VM.
Many thanks, -T
Change History (3)
follow-up: 2 comment:1 by , 16 years ago
comment:2 by , 16 years ago
Replying to frank:
What do you mean by "not configured for headless"?
Under /usr/bin/VirtualBox, "Settings", "Remote Display" tab, "Enable Server", do not run headless if this is not enabled. This because VRDP will not work with it.
You don't have to kill a VM but you can shut down it with VBoxManage controlvm VM_NAME powerdown.
I used "/usr/bin/VBoxManage controlvm $VM_Name acpipowerbutton". I don't remember it working, so I reverted to "ps" and "kill", since I could not VRDP into it.
-T
comment:3 by , 15 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
This VM setting is independent of the operation of VBoxHeadless and we don't intend to change this. As I wrote, the VM can be easily terminated with VBoxManage, and VBoxManage controlvm ... poweroff will work in any case. VBoxManage controlvm ... acpipowerbutton will not work if the guest does (currently) not handle ACPI events.
What do you mean by "not configured for headless"? You don't have to kill a VM but you can shut down it with VBoxManage controlvm VM_NAME powerdown.