Custom Query (16363 matches)
Results (1222 - 1224 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #7516 | obsolete | Nvidia Graphics Driver 260.63 Breaks 3D Acceleration | ||
| Description |
Hi, So I am running http://www.nvidia.com/object/win7-winvista-64bit-260.63-beta-driver.html on Windows 7 x64. If I enable 3D Acceleration for a Windows Guest OS and try to boot it up I get the wonderfully famous "VirtualBox GUI has stopped working" error screen. Problem signature: Problem Event Name: APPCRASH Application Name: VirtualBox.exe Application Version: 3.2.8.0 Application Timestamp: 4c5aa88b Fault Module Name: nvoglv64.DLL Fault Module Version: 8.17.12.6063 Fault Module Timestamp: 4c8b035f Exception Code: c0000005 Exception Offset: 00000000007612d8 OS Version: 6.1.7600.2.0.0.256.1 Locale ID: 1033 Additional Information 1: 3f76 Additional Information 2: 3f76a2f97cb0d43752984c382605bc27 Additional Information 3: e1ac Additional Information 4: e1ac6728c9b4377ec1de68f89139c85d See Forum Thread @ http://forums.virtualbox.org/viewtopic.php?f=6&t=34764 Take Care, Will |
|||
| #7517 | obsolete | W2k3 guest time sync problems (VbglR3GetHostTime failed; rc2=VERR_IO_GEN_FAILURE) | ||
| Description |
Virtualbox 3.2.8 running on Windows Server 2003 (32Bit) Guest: Windows Server 2003 (32Bit) GuestAdditions: 3.2.8 The time of the guest isn't synchronized. Especially after a savestate and resume the guest clock is far far away from the host clock. In the Log files I found: 00:01:32.296 Guest Log: VBoxService.exe: Error: VbglR3GetHostTime failed; rc2=VERR_IO_GEN_FAILURE I've checked this with an earlier version of VIrtualbox (3.1.8, also GuestAdditions downgrades) but observe the same error. An test on Windows 7 host didn't show this behaviour, so I suggest it's an Server 2003 host issue. Even with "VboxService -vvv" I didn't get more information about the timesync problem. Attached the vbox.log The issue is rather critical, cause the clock is so fast out of time, that an workaround with a very shot poll interval of the windows w32time daemon is necessary. |
|||
| #7522 | obsolete | CPU Hotplug / Hot-unplug is unstable | ||
| Description |
Host: Windows XP, Core 2 Q6600, VBox 3.2.8. I did: VBoxManage modifyvm <vmname> --cpuhotplug on VBoxManage modifyvm <vmname> --cpus 2 after VM booted... Several time re-plugged CPU: VBoxManage controlvm <vmname> plugcpu 1 VBoxManage controlvm <vmname> unplugcpu 1 From inside guest: (openSUSE 11.3 64-bit) linux-0gkn:~ # dmesg | tail
[ 870.449212] microcode: CPU0 update to revision 0xb6 failed
[ 870.488455] microcode: CPU1 update to revision 0xb6 failed
[ 870.515200] microcode: CPU0 update to revision 0xb6 failed
[ 870.537351] microcode: CPU1 update to revision 0xb6 failed
[ 870.557087] microcode: CPU0 update to revision 0xb6 failed
[ 870.584368] microcode: CPU1 update to revision 0xb6 failed
[ 873.845725] CPU 1 is now offline
[ 873.845725] SMP alternatives: switching to UP code
[ 884.070333] VBoxService[1412]: segfault at 2800568e70
ip 0000000000409235 sp 00007f644d05cb80 error 4
in VBoxService[400000+69000]
[ 884.071618] ACPI: Device don't exist, dropping EJECT
Similar, but different problems were seen on many other guest OSes: RHEL6 (BETA1), Fedora12, openSUSE 11.0/11.1/11.2 (32+64bit), ... For now, only under Fedora 13 this feature magically worked. VBox log attached. -- -"Technologov", 28.9.2010 |
|||

