Custom Query (16363 matches)
Results (2212 - 2214 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #10693 | obsolete | OpenGL broken with guest additions | ||
| Description |
Host: Redhat 6.3 Guest: Ubuntu 12.04 VBox: 4.1.18 (Matching guest additions and extension pack installed.) When 3D acceleration is enabled via the VirtualBox settings, OpenGL programs do not display properly in the Guest OS. The program being run in the guest (IQmol) gives the following terminal info: OpenGL Warning: No pincher, please call crStateSetCurrentPointers() in your SPU X Error: BadDrawable (invalid Pixmap or Window parameter) 9 Major opcode: 14 (X_GetGeometry) Resource id: 0x3e0000c Turning off the 3D acceleration removes the error but also disables 3D capability. The VBox.log (attached) has many instances of OpenGL Warning: Trying to switch contexts when the attribute stacks weren't empty. Currently, this is not supported.'' I originally thought that this issue was the same one, but my BIOS tell me that the Intel switching feature is disabled. For additional discussion and previous troubleshooting, see here. If it helps at all, I've also encountered 3D issues in my Win7 guest on the same host. |
|||
| #10694 | obsolete | VirtualBox claims I do not have VT-x support. | ||
| Description |
I am receiving this error when trying to launch a Windows 8 64-bit VM for the first time: VT-x/AMD-V hardware acceleration has been enabled, but is not operational. Your 64-bit guest will fail to detect a 64-bit CPU and will not be able to boot. Please ensure that you have enabled VT-x/AMD-V properly in the BIOS of your host computer. It is claiming I do not have VT-x enabled, which I know for a fact that I do and that my hardware supports it. Proof that my CPU supports it: http://ark.intel.com/products/65520/Intel-Core-i5-3570K-Processor-%286M-Cache-up-to-3_80-GHz%29 Proof that my BIOS settings are correct: http://i.imgur.com/m7jd7.jpg I've updated my BIOS to the most recent version and am using the most recent version of VirtualBox. I've searched for similar problems to mine and have only found a solution of disabling a "trusted execution" setting, but my processor does not even have that feature. |
|||
| #10695 | obsolete | [PATCH] OSS Audio driver uses wrong volume for recording, making recording in guest practically impossible if it is used | ||
| Description |
When recording in guest while OSS audio driver is used, nothing is recieved. This affects the FreeBSD and Solaris hosts, and also Linux hosts under certain configurations. src/VBox/Devices/Audio/ossaudio.c includes the following: #ifndef VBOX
#else
#endif VBox is usually defined when compiling, so pcm_in_volume is used. But pcm_in_volume is almost never set (it's set by the AUD_set_volume() method which is almost never called - only the SB16 driver calls it [The ICH driver also has it, but under an #ifdef which is not usually defined]). So pcm_in_volume is zero, and programs on the guest recieve nothing at all... The suggested fix is to do like most other audio drivers (ALSA and Pulse's drivers come to mind) and use nominal_volume exclusively. The patch below has been tested and fixes the problem on my end and for another user. Note that some other drivers use pcm_in_volume (solaudio.c and dsoundaudio.c) and may require this change as well. --- ossaudio.c.old 2012-06-22 23:29:17.854555530 +0300
+++ ossaudio.c 2012-06-22 23:38:53.797799295 +0300
@@ -795,13 +795,8 @@
hw->info.align + 1);
}
read_samples += nread >> hwshift;
-#ifndef VBOX
hw->conv (hw->conv_buf + bufs[i].add, p, nread >> hwshift,
&nominal_volume);
-#else
- hw->conv (hw->conv_buf + bufs[i].add, p, nread >> hwshift,
- &pcm_in_volume);
-#endif
}
if (bufs[i].len - nread) {
|
|||

