VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (403 - 405 of 16363)

Ticket Resolution Summary Owner Reporter
#9110 obsolete Process Explorer, Remote Desktop causing blue screens on 64-bit Windows Server 2008 R2 guest Matt
Description

I have a newly-created guest that I installed from a 64-bit Windows Server 2008 R2 with Service Pack 1 installation disc. It has no additional applications or Windows components installed beyond the defaults, and the only configuration changes I've made are setting the computer name, static network configuration, and a few changes in local Group Policy. I have been experiencing reproducible blue screens when performing either of the following actions:

  • Running (or, usually, exiting) Process Explorer 14.12
  • Logging out of a Remote Desktop session (connected to Windows' RDP server, not VirtualBox's)

These blue screens do not occur every single time I perform one of the above actions, but usually every third or fourth. Most often the stop code is 0x0000001A MEMORY_MANAGEMENT, but occasionally I'll see 0x0000000A IRQL_NOT_LESS_OR_EQUAL. I've experimented with versions 4.0.8, 4.0.0, and 3.2.12 of VirtualBox Guest Additions, as well as no Guest Additions installed at all, and I'm still seeing this problem.

The host is running 64-bit Ubuntu Server 11.04 "Natty Narwhal" and I use VBoxHeadless to run virtual machines. I used to have a 64-bit Windows Server 2008 guest that worked fine with VirtualBox 3.2 but began experiencing similar blue screens after upgrading to 4.0, which is why I'm trying to isolate this problem now. Today I upgraded to version 4.0.10 of VirtualBox and VirtualBox Extension Pack from 4.0.8 and this issue is still present.

To produce this Process Explorer blue screen for which I added attachments, I performed the following steps:

  1. Restored a snapshot taken immediately after installing Windows and making the configuration changes noted above
  2. Powered on
  3. Logged in to Windows
  4. Copied Process Explorer from an SMB share to the local Desktop
  5. Double-clicked to launch procexp.exe and Windows blue-screened soon thereafter (within seconds)

I will upload logs and dumps for the MEMORY_MANAGEMENT blue screen and Remote Desktop blue screens as I am able to produce them.

#6842 fixed Guests clocks not kept synchronized after upgrade to VirtualBox 3.2.0, Ubuntu Server 10.04 Matt
Description

I have a computer with an AMD Athlon64 X2 3600+, 6 GB RAM, and Cool 'n Quiet currently disabled in an attempt to solve this problem. It runs 64-bit Ubuntu Server and hosts two 64-bit Ubuntu Server and one 64-bit Windows Server 2003 guests. Back when I was using VirtualBox 3.1.x and the host and two Linux guests were running Ubuntu Server 9.10, I had a problem where the clocks on the two Ubuntu guests were kept in sync but the entire Windows guest (including its clock) would run slow after any significant load was placed on that system. (More information can be found in this forum post. I will not detail that problem in this bug unless asked to do so.)

I recently upgraded the host and two Linux guests to Ubuntu Server 10.04 and also upgraded to VirtualBox 3.2.0 using Aptitude. Since then, none of the guests' clocks are kept in sync. Sometimes the Ubuntu guests' clocks are more in sync than the Windows guest, sometime it's the other way around, and sometimes they're off by different amounts. Currently, the Windows guest is 607 seconds behind, one Ubuntu guest is 1,127 seconds behind, and the other is 183 seconds behind. They seem to speed up and slow down with no rhyme or reason. All guests have the latest version of VirtualBox Guest Additions installed. The two Ubuntu guests are using the linux-virtual kernel package from Aptitude, and the host uses the linux-server kernel; all are currently version 2.6.32-22-server. None of the guests see very heavy usage; they're idle most of the time and mainly just file servers that provide a few other services.

With VirtualBox 3.1.x/Ubuntu Server 9.04 I noticed long repetitions of "TM: Giving up catch-up attempt at a..." and "TM: u64DeltaPrev=... u64PrevNanoTS=... u64NanoTS=..." entries in the Windows guest's log; now those entries appear in the logs of all three guests.

#13205 obsolete windows NT 4.0 video driver not working (4.3.10) BANGEXPLOSIVE
Description

On my windows 8.1 64-bit machine I have a Windows NT 4 sp6a VM. The Virtualbox Guest additions video driver does not work. It installs, but when I boot it it says:

The currently selected graphics display driver cannot be used. It is either missing or not properly configures. The system has been started with the default VGA graphics mode.

I have tried reinstalling GA and re-activating the driver, nothing seems to work. The GA and virtualbox are at the same version (4.3.10).

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy