Hi,
I am new virtual box user.I have encountered by a problem:
guest machine: windows Xp
host machine: win 7
I have made a vmdk using VMware-converter-4.0.1-161434 of my guest machine. I have created new profile in virtual box(VirtualBox-3.2.8-64453-Win) with this vmdk assigning sufficient memory. But when it is going to boot its giving following (green death )error:
A problem has been detected and windows has been shut down to prevent damage to your computer
if this is first time you have seen this stop error screen, restart your computer...
check for virus on your computer . remove any newly installed hard drive and hard drive controller. check your hard drive to make sure it is properly configured and terminated. run chkdsk /f to check your hard drive corruption....
technical information...
Anyone can help please??
my current virtual box setting:
General
Name:finbd2virtual
OS Type:Windows XP
System
Base Memory:1024 MB
Processor(s):1
Boot Order:Hard Disk
VT-x/AMD-V:Enabled
Nested Paging:Enabled
Display
Video Memory:16 MB
3D Acceleration:Disabled
2D Video Acceleration:Disabled
Remote Display Server:Disabled
Storage
IDE Controller
IDE Primary Master:finbd2.vmdk (Normal, 48.87 GB)
Audio
Host Driver:Windows DirectSound
Controller:ICH AC97
Network
Adapter 1:PCnet-FAST III (NAT)
Serial Ports
Disabled
USB
Device Filters:0 (0 active)
Shared Folders
None
Virtual box with VMDK green death problem
-
nalmir
- Posts: 15
- Joined: 3. Aug 2010, 16:27
- Primary OS: MS Windows Vista
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: win 2003 server 32bit and 64 bit
Re: Virtual box with VMDK green death problem
what kind of disk controller was on the source machine?.. most likely it was SATA
so try SATA first, then SCSI. and boot in safe mode
so try SATA first, then SCSI. and boot in safe mode
-
draxbear
- Posts: 1
- Joined: 31. Oct 2010, 03:27
- Primary OS: Ubuntu other
- VBox Version: OSE Debian
- Guest OSses: Windows XP
Re: Virtual box with VMDK green death problem
In my case I'd upgraded Virtual box to a more recent version with the Guest OS complaining in a similar manner to the above.
It looks like the main difference between the old and new VXbox from the guest OS point of view was the jump from a "PIIX3" to "PIIX4" IDE Controller default type.
Location: Settings -> Storage -> Type -> PIIX4 to PIIX3
Once I dropped back to PIIX3 windows was much happier. I went safe for the first startup and then stopped and restarted in normal. Looks ok now.
It looks like the main difference between the old and new VXbox from the guest OS point of view was the jump from a "PIIX3" to "PIIX4" IDE Controller default type.
Location: Settings -> Storage -> Type -> PIIX4 to PIIX3
Once I dropped back to PIIX3 windows was much happier. I went safe for the first startup and then stopped and restarted in normal. Looks ok now.