Windows 2003 P2V Blue Screen (?SATA)

This is for discussing general topics about how to use VirtualBox.
Post Reply
Rastus
Posts: 37
Joined: 13. Jan 2010, 04:19
Primary OS: Ubuntu other
VBox Version: OSE Debian
Guest OSses: Windows

Windows 2003 P2V Blue Screen (?SATA)

Post by Rastus »

OK,
I have several older Dell servers with SCSI RAID that I have migrated to Virtualbox with no problems.

Unfortunately, I also have a newer Dell server with Dual Quad core processors and a SATA RAID array. I made the low level copy and convertfromraw and attach it to the windows virtual machine just like I did for the SCSI machines and I get a blue screen error when the guest boots. Since the Processor and the SATA Drive are the only different variables, I am concerned that I have missed something.

Image

Even though the older servers had SCSI RAID I used the IDE controller in Virtualbox guest and it worked. This does not work with the image from the newer server. The guest will boot to the windows splash screen and then go to blue screen as above. If I boot using the windows install disk, it can find the C: drive in Recovery mode but the recovery mode tests seem to check out fine so I don't know why it would not work.

I also tried using the SATA controller on the guest and that did not work either. Whe I attache the vdi to the SATA controller, If I try to run windows Recovery manager from the boot CD it can't even find the drives (see error below)

Image

I noticed the notes in the Manual (yes, I looked before I asked) that say that Windows 2003 does not have SATA drivers and they need to be installed when installing the system but this is an image from a windows 2003 server that is working fine with a SATA drive so I would not think that I needed to install the drivers??

The machine that I am trying to use as a host has only an Intel core 2 Duo processor. Is it likely that is the problem? if so how would I find out?

I would welcome any suggestions.
"Putting the FUN back in Dysfunctional"
Rastus
Posts: 37
Joined: 13. Jan 2010, 04:19
Primary OS: Ubuntu other
VBox Version: OSE Debian
Guest OSses: Windows

Re: Windows 2003 P2V Blue Screen (?SATA)

Post by Rastus »

Update

If this is helpful to anyone. Changing the IDE controller from PIIX4 to ICH6 seems to have solved the problem.

??
I will update further as I find out if it is stable.
"Putting the FUN back in Dysfunctional"
mpack
Site Moderator
Posts: 39134
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Mostly XP

Re: Windows 2003 P2V Blue Screen (?SATA)

Post by mpack »

Rastus wrote:I noticed the notes in the Manual (yes, I looked before I asked) that say that Windows 2003 does not have SATA drivers and they need to be installed when installing the system but this is an image from a windows 2003 server that is working fine with a SATA drive so I would not think that I needed to install the drivers??
I have no experience of Windows 2003 so I don't know that the initial proposition (no support for SATA) is true, but no, your logic is wrong. Real PCs often have IDE emulation in the BIOS every though they use SATA drives. The SATA-ignorant OS sees an ordinary IDE interface. If you P2V that image to a pure SATA VM then it will crash. If you P2V it to an IDE VM then it should work provided you followed the P2V migration advice given on this site, i.e. that you ran MergeIDE to make it more tolerant of IDE controller changes.
Rastus
Posts: 37
Joined: 13. Jan 2010, 04:19
Primary OS: Ubuntu other
VBox Version: OSE Debian
Guest OSses: Windows

Re: Windows 2003 P2V Blue Screen (?SATA)

Post by Rastus »

Thanks,
That was helpful
"Putting the FUN back in Dysfunctional"
Post Reply