VBox 3.1.2 broke my Win2000 guest
Posted: 20. Dec 2009, 16:31
Host system is 64-bit CentOS 5.4, Q9400 processor and 8 gig RAM.
Yesterday I upgraded from VirtualBox 3.0.12 to 3.1.2. The upgrade was accomplished by uninstalling the existing VirtualBox, then installing 3.1.2. When I ran "rpm -Uvh ..." it told me that every file in the update conflicted with an existing package, so I had to go the uninstall/reinstall route.
My Windows 2000 guest is now blue-screening during boot. All my other guest machines are working including one on Windows XP.
When launched from a cold start, the system goes through the char-mode boot screen, hits the graphical boot screen and gets about 2/3 of the way across with the marching dots. Then it issues a BSOD.
If I "reset" (as opposed to "power off"), it will not issue the BSOD, but will also never get past the graphical boot screen.
The BSOD message is:
The Win2000 machines has Guest Additions 3.0.10 installed. It is SP4 with all the post-SP4 rollups, IE6.01, etc. I had to do the delay setting (documented in the appendix of the VBox user manual) in order for the original setup to run, but since then it has worked perfectly.
Networking is set up for bridged mode using the PCNet FAST-III adapter. There are no shared folders and no mounted ISO images. RAM is set for 512 meg and video ram is 16 meg. 2D and 3D accelerations are not enabled.
Can anyone help?
Yesterday I upgraded from VirtualBox 3.0.12 to 3.1.2. The upgrade was accomplished by uninstalling the existing VirtualBox, then installing 3.1.2. When I ran "rpm -Uvh ..." it told me that every file in the update conflicted with an existing package, so I had to go the uninstall/reinstall route.
My Windows 2000 guest is now blue-screening during boot. All my other guest machines are working including one on Windows XP.
When launched from a cold start, the system goes through the char-mode boot screen, hits the graphical boot screen and gets about 2/3 of the way across with the marching dots. Then it issues a BSOD.
If I "reset" (as opposed to "power off"), it will not issue the BSOD, but will also never get past the graphical boot screen.
The BSOD message is:
Code: Select all
*** STOP: 0x00000050 (0xF22DF000, 0X00000000, 0X804F5586, 0X00000000)
PAGE_FAULT_IN_NONPAGED_AREA
*** Address 804f5586 base at 80400000 DateStamp 4a781s9a - ntoskrnl.exeNetworking is set up for bridged mode using the PCNet FAST-III adapter. There are no shared folders and no mounted ISO images. RAM is set for 512 meg and video ram is 16 meg. 2D and 3D accelerations are not enabled.
Can anyone help?