Custom Query (16363 matches)
Results (517 - 519 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #9551 | obsolete | Keyboard letter keys not working inside VM over ssh | ||
| Description |
I am opening up a Windows 7 guest from an ssh session to an openSUSE 11.4 machine (using the -X flag). I am running ssh on an aluminum Macbook in terminal. The letter keys on the keyboard are not functioning within the VM. Function keys, caps lock, delete, space, etc. all work. Any help would appreciated and I would be glad to give any additional information required, thank you! |
|||
| #9199 | fixed | Memory Leak when Audio=WindowsDirectSound+ICH AC97 | ||
| Description |
VirtualBox 4.0.10 r72479 running on Windows7 Professional 64 host, guest is Debian squeeze, kernel 2.6.32-5-686. When audio is enabled using WindowsDirectSound and ICH AC97, memory leaks at alarming rate - the commit charge for the VirtualBox guest process, as shown by the Windows Resource Monitor, grows at a rate of about 7 MiB/minute! It grows without bound, eventually consuming several GiB until the system becomes very sluggish. Disabling audio stops the leak. Changing to any of NullAudioDriver or Intel HD Audio or Soundblaster 16 stops the leak. The leakage occurs whether the guest OS is sitting at a login prompt or whether a user is logged in doing nothing at a shell prompt. A Vbox.log from the leaking configuration is attached. |
|||
| #10291 | obsolete | VirtualBox 4.1.8 kills NTFS junctions? | ||
| Description |
I run a laptop with an SSD + HDD configuration, where my Windows user profile is symlinked from the SSD to the HDD via an NTFS junction point. I just installed 4.1.8 to test out the Windows 8 Beta, and when creating the first VM I received a "Path not found" error. From that point on, almost everything in my session is hosed (no links work, services are all asking me to sign in). I did a system restore, but my profile was still broken (Windows logged me in with a "new" profile). I noticed that my junction point was gone (the SSD now had a real folder with only the VirtualBox files). When I deleted that profile on the SSD and recreated the junction, my machine is back to normal. Is it expected that VBox should blow away junctions like this? |
|||

