Custom Query (16363 matches)
Results (598 - 600 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #18762 | duplicate | ACPI Shutdown lead to "Failed to open session" | ||
| Description |
I have 9 virtual machines joined in a group, configured as headless. When I use 'ACPI Shutdown' on the group, sometimes (not always) I get error: Failed to open a session for the virtual machine Witness4Tuchanka.
Failed to get a console object from the direct session (NS_ERROR_ABORT).
Result Code: VBOX_E_VM_ERROR (0x80BB0003)
Component: MachineWrap
Interface: IMachine {5047460a-265d-4538-b23e-ddba5fb84976}
Also I created few script, which simply start/stop all VMs in a loop: $ less is_vm_running.bash
# $1 VM name to test
. "${script_dir}/is_function_absent.bash"
if is_function_absent 'is_vm_running'
then
function is_vm_running {
test 0 -ne $(VBoxManage list runningvms | { grep --count --fixed-strings "\"$1\"" || [ $? -eq 1 ]; })
}
readonly -f is_vm_running
fi
$ less start_vms.bash
. "${script_dir}/is_function_absent.bash"
. "${script_dir}/is_vm_running.bash"
. "${script_dir}/vm_ssh.bash"
if is_function_absent 'start_vms'
then
function start_vms {
local i
for i in "${!vm_name[@]}"
do
if ! is_vm_running "${vm_name[$i]}"
then
echo "Start ${vm_name[$i]}"
VBoxManage startvm "${vm_name[$i]}"
fi
done
for i in "${!vm_name[@]}"
do
echo "Waiting for system on ${vm_name[$i]}"
until vm_ssh "${vm_hostname[$i]}" 'systemctl is-system-running' 2>/dev/null
do
sleep 1
done
done
sleep 5
}
readonly -f start_vms
fi
$ less soft_off.bash
. "${script_dir}/is_function_absent.bash"
. "${script_dir}/is_vm_running.bash"
. "${script_dir}/vm_ssh.bash"
if is_function_absent 'soft_off'
then
function soft_off {
local i
for i in "${!vm_name[@]}"
do
if is_vm_running "${vm_name[$i]}"
then
VBoxManage controlvm "${vm_name[$i]}" acpipowerbutton
fi
done
for i in "${!vm_name[@]}"
do
echo "Waiting Off of ${vm_name[$i]}"
while is_vm_running "${vm_name[$i]}"
do
sleep 1
done
done
sleep 5
}
readonly -f soft_off
fi
$ less power_loop #!/bin/bash
# safe bash
set -o errexit -o noclobber -o nounset -o pipefail
readonly script_dir="$(dirname "${BASH_SOURCE[0]}")"
. "${script_dir}/load_config.bash"
. "${script_dir}/start_vms.bash"
. "${script_dir}/soft_off.bash"
i=0
echo "i=$i $(date +'%FT%T')" |tee 'test.log'
while true
do
start_vms
soft_off
let i=$i+1
echo "i=$i $(date +'%FT%T')" |tee -a 'test.log'
done
And also I get the same error, less often. Just GUI window with message about error (I has opened GUI), but all other keep working. |
|||
| #12707 | worksforme | ACPI Shutdown shortcut conflicts with Hide global shortcut. | ||
| Description |
To execute ACPI via a keyboard shortcut you're to use HOST-h. In the Mac OS X case HOST is cmd and cmd-h is the Hide VirutalBox menu item from the application (VirutalBox) menu.
Reproduce:
Expected: |
|||
| #11950 | obsolete | ACPI battery state of host hardware stuck after installation of VBox | ||
| Description |
After installating Virtualbox on Windows 8 (both 64 bit) the battery charge value (acpi charge level as reported by the machine's bios) gets stuck in one direction and stops updating into the corresponding direction (can be charge or discharge). Before installing Virtualbox the charge level behaved normally (tested over multiple cycles). The "one way only/stuck" ACPI charge value persists over reboots - even changing the operating system (multibooting) to Linux (Ubuntu 13.10) does not help! Therefore this bug-report is most probably machine-specific for my Asus Ultrabook UX51VZ (Zenbook) with bios 203 or bios 204 - nontheless it indicates problems with the ACPI-forwarding portion of Virtualbox. To resolve the problem I had to uninstall Virtualbox, re-flash the Bios (winflash with /nodate parameter), re-configure my bios-settings and then perform a cycle with the notebook's battery in order to get the battery back to a working state! Suggestion: please review the acpi-forwaring-code for possible causes of the lockup (writing calls/race conditions?) - maybe add functions to disable the corresponding blocks at driver level (workaround). Thanks! PS: The problem has been reported to Asus as well as their bios is the component that's getting permanently stuck. PPS: Tool used for better battery-metering in windows: CPUID's HWMonitor - normally shows charge updates every 1-2 seconds - the problem first occurred without it beeing installed, so it can be ruled out. |
|||

