Custom Query (16363 matches)
Results (1204 - 1206 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #10991 | fixed | console.powerDown() hangs if console.powerButton() failed first | ||
| Description |
Assume a virtual machine which, for whatever reason, doesn't react well to ACPI shutdown requests (you can simulate this by changing /etc/acpi/powerbtn.sh to something like #!/bin/sh echo "Ignoring shutdown request" | wall exit 0 On your host, execute the following code (replace UbuntuServer with your vm name). vmname = 'UbuntuServer' from vboxapi import VirtualBoxManager vbox = VirtualBoxManager(None, None) virtualbox = vbox.getVirtualBox() machine = virtualbox.findMachine(vmname) mgr = vbox.mgr session = mgr.getSessionObject(vbox.getVirtualBox()) machine.lockMachine(session, 1) console = session.console console.powerButton() #this won't raise anything, but the VM won't shut down console.powerDown() The last call will leave your VM hanging in a shutting down state - kill -9 is needed to get out of it. Expected behaviour: console.powerDown() should be able to turn off the virtual machine regardless of its state. |
|||
| #1167 | fixed | VBoxGuest Support Driver for NT 4.0 wrong startup type => Fixed in 1.5.6 | ||
| Description |
The guest additions for Windows NT 4.0 do not work correctly as installed because the "VBoxGuest Support Driver" is installed with the wrong startup type. The startup type for the driver must be "Boot" but it is installed with a startup type of "System". The work around to get mouse integration working is to use the NT 4.0 Control Panel "Devices" function and change the startup type for the "VBoxGuest Support Driver" to "Boot". Then reboot Windows NT 4.0 and the mouse integration will work. |
|||
| #7609 | obsolete | Windows XP Guest - timeBeginPeriod( ) slows system clock | ||
| Description |
A system service running in a Windows XP SP3 Guest can use the Windows "timeBeginPeriod( )" function to change the system time tick resolution. That is common with multimedia or real-time applications. I have such a system service. After the service has changed the Windows XP Guest timer resolution a problem occurs when running on a Windows 7 Host. The system time in the Guest updates at a much slower rate than normal and the time in the Guest falls behind the correct time. Any time related events occur at a slower than normal rate. For example, desktop fade effects, animated mouse pointers, Task Manager refreshing, and multimedia applications all appear to be "slow" due to the system time updating at a slower rate. When the Windows time resolution is set back to the default by the system service then the time behaves normally again. If the Windows clock is reset to the correct time then it remains correct. The service changes the time using this code. TIMECAPS tc;
/* Get time capabilities of system */
if (timeGetDevCaps(&tc, sizeof(TIMECAPS)) != TIMERR_NOERROR)
{
Critical( );
}
/* Set the highest possible timer resolution (1 ms. if possible) */
gwTimerRes = min(max(tc.wPeriodMin, 1), tc.wPeriodMax);
if ( timeBeginPeriod(gwTimerRes) != TIMERR_NOERROR )
{
Critical( );
}
When the service is stopped it sets the time resolution back to normal. /* Set the timer resolution back to normal */
if ( timeEndPeriod(gwTimerRes) != TIMERR_NOERROR ) {}
Other than the system time and timers being "slow" there are no other apparent problems in the Guest OS. I did not see excessive CPU usage, I/O or Interrupt activity. Although many things appear "slow" due to the incorrect time updates the execution of CPU instructions in the Guest does not seem to be affected. I verified that the "timeBeginPeriod( )" Windows function causes the problem to occur and that the problem stops after calling "timeEndPeriod( )". This problem might explain some of the "Slow Windows Guest" complaints that are unresolved. The curious thing about the problem is that it does not appear to happen with Linux Host OS. I have also tested the system service on a number of real PCs in order to verify that the problem is not the system service. After only seeing the problem in a VirtualBox guest I decided to investigate the problem further. I removed code from the system service until I found the functions causing the problem. The problem also occurs with version 3.2.8 of VirtualBox under the same conditions. The problem occurs with or without the Guest Additions installed. |
|||

