Custom Query (16363 matches)
Results (601 - 603 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #6010 | fixed | ACPI conflict with with Serial com port in debug windows guest | ||
| Description |
can't use windbg to do remote kernel debugging on a windows guest. adding the debug flag in boot.ini and using COM1 with a pipe. starting windows normally doesn't give problems, com port haven't got any conflict. starting windows with kernel debug make COM port conflict with ACPI, that makes debugging impossible. i've also found a way to make windows guest lock, it's something like that: adding a COM2 port connected to a pipe to vm and not adding it to devices in windows, then modify COM1 properties in windows guest to use COM2 configuration (base configuration 0002), then start the virtual machine and attach windbg which will say "waiting to reconnect" reboot windows guest in debug mode and windbg will succesfully attach but locks the guest. in debug mode COM port used to debug conflicts with some ACPI device. two logs are attached, one with guest in normal mode and COM port without conflict, the other one in debug mode with conflict. sorry for my bad english. regards ocean |
|||
| #12859 | wontfix | ACPI keystrokes not sent to guest | ||
| Description |
I'm talking about the ACPI Power, ACPI Sleep and ACPI Wake keys on some keyboards. The guest doesn't receive them. My keyboard also has a "mystery" key (not labeled; I tried to look up the scancode and it might be "Help") which doesn't reach the guest. I'd say the rule should be, if you don't recognize the scancode, give it the benefit of the doubt and pass it to the guest. Host: XP SP3 32-bit. Guest: same. (I also tried Android, though I'm not sure what effect ACPI keys should have there and I don't have a key test program for Android) Tip for testing your ACPI keys on a Windows host: set them to do nothing in the Power Options control panel applet. (they still generate keystrokes though) |
|||
| #7880 | invalid | ACPI power button pauses the VM | ||
| Description |
After sending the ACPI power off command from either the virtualbox GUI interface or VBoxManage, the VM is paused. It does not seem to receive the shutdown signal at all. After sending the shutdown signal, first the CPU usage by the VM goes up to (nearly) 100%, after a few seconds the VM is paused. When I unpause the VM, the Windows Vista guest indicates that the desktop has been locked to the login screen. |
|||

