Custom Query (16363 matches)
Results (1138 - 1140 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #7200 | obsolete | No Sound on Windows 7 host after host sleep | ||
| Description |
Version info: Host: Windows 7 64-bit VM: Windows XP SP3 32-bit VirtualBox: 3.2.6 Guest Additions: 3.2.6 I have two soundcards in this VM - the virtual AC'97 card, and a physical USB sound card. Sound works coming through the USB card, but not the AC'97 card. None of the volume controls are muted, all turned up to full. Sound works normally on the host. Sounds has previously worked on this VM running on a different Win7 PC. I found that VBox.log is full of these messages (full log attached): 00:22:50.180 DSound: Reason: The buffer memory has been lost and must be restored I have tried:
There doesn't appear to be any conflicts between the two sound cards. Discussion here: http://forums.virtualbox.org/viewtopic.php?f=6&t=32982 |
|||
| #7201 | obsolete | [Apple keyboard & PC] Numlock problem | ||
| Description |
Hi, Host: Windows 7 x64 Pro Guest : Debian GNU/Linux Lenny 5.0.4 x86 VirtualBox : 3.2.6 I've got a minor problem with the numlock by using an Apple keyboard on PC and Virtualbox. Host numlock OFF and I start my VM, guest numlock is ON. Switch the state it's applied to both OS. Host numlock ON and I start my VM, guest numlock is OFF. Switch the state just it's applied to host but guest numlock is always OFF. In this case, I must switch numlock to OFF and Ctrl Alt Backspace (X.Org forced restart). Note: VBoxGuestAdditions is installed and in Microsoft Virtual PC numlock works normally. |
|||
| #7212 | obsolete | Fedora 13 guest fails, error looks like keyboard failure | ||
| Description |
This bug report is described on the forums at http://forums.virtualbox.org/viewtopic.php?f=6&t=33034 Since that report was made I've done further testing. The failure occurs whether the host is Windows 7 or Linux. Also it appeared that keyboard input was simply not being accepted after 20 minutes or so. Further testing showed that the keyboard input was accepted it is just that the display wasn't being updated to show the characters being entered and the results of entering such characters. It is as if X believes that a large opaque window covers the whole screen. Thus X appears to not be sending redraw events to the windows on the screen. Certain operations can force the windows to redraw themselves even without a repaint event and in that case you see the keystrokes you've been making beforehand. This failure seems to occur more quickly if network activity is happening. I took a totally vanilla Fedora 13 install and added the Forecast Fox extension to Firefox. This caused periodic network activity to check the weather. Within 20 minutes the guest had gotten into the state described above where windows are not redrawn so it appears that the keyboard isn't working. The bottom line is that there is something in Fedora 13 that is not compatible with Virtual Box 3.2.6. |
|||

