To update Intel SATA driver

[Winxp-on-Macos]

Hi,
It is about Windows XP virtual machine which was created not by from-scratch installation but by p2v conversion.
Yet for conversion the drivers for Intel ICH8M controller was injected.
Currently the version 7.6.0.1011 is installed and I believe it is the same version as that one used for injection for conversion.

There is a seek to make the device driver update. However using 10....1008 did not succeed: BSOD even if according to
other thread viewtopic.php?p=192460#p192460 it should work.

Any chance to apply newer driver that the 7.6.0.1011?
What can be the reasons of BSOD in case of installing 10.1.0.1008?

[scottgus1]

There's a tutorial on migrating a physical XP PC to virtual here: https://www.virtualbox.org/wiki/Migrate_Windows

and two posts on how to run XP on SATA drivers here: viewforum.php?f=28

Some of the above steps have to be done to the original PC before you migrate it.

Note: Although SATA is supposed to be better than IDE, I doubt you'll see much difference. XP runs on IDE by default. You can tell the XP guest its drives are IDE (by "plugging" them into the guest's virtual IDE ports) even though the physical drives in your host PC are SATA or something else.

[Winxp-on-Macos]

Yes, I am aware of the p2v porting article and have used it for conversion of this Win XP.
Please note the conversion/migration completed successfully and converted XP works fine. I have used lot of how-to articles from web.
So I believe the question of p2v migration is closed as such. All these articles can help if they address the SATA driver question.
However I did a search for SATA drivers problem discussions and all porting focused articles should be covered by this search.

Amongst all found articles few especially helpful make different statements than my experience, e.g. the 10....1008 driver leads to BSOD
but this was mentioned in my initial post. It is not the way I did no search nor research. Rather my research did not provide helpful points, before migration and after. Therefore this thread.
It seems no evident information be available. I understand this situation and close this thread.
It was open due to my hope the opposite is true.

The original PC was running on SATA. According to VirtualBox manual the emulated SATA controller shows better performance.
Furthermore the migrated PC should be as its original as far as possible. Sure due to hardware related dependences it is not possible 100 per cent.
Means only those adaptations which were necessary this Win XP installation run as virtual machine. Updating the SATA driver is simple maintenance,
switching to IDE more than maintenance.

[mpack]

Furthermore the migrated PC should be as its original as far as possible.

XP has no native support for SATA, so in fact most physical XPs rely on IDE emulation in the BIOS. The OS never actually sees a SATA API. When P2V-ing such a system the correct disk controller to choose in the VM is IDE.

Even if the original PC did use native SATA, the chances that the VM will use the same SATA chipset are slim. Therefore it simply isn't possible to keep the VM "original" in this regard.

The XP guest should be P2V'd and got working initially using IDE, then if you wish you can follow the HOWTO to install the correct SATA drivers (i.e. the ones that work on VirtualBox hardware).

[michaln]

What can be the reasons of BSOD in case of installing 10.1.0.1008?

The possible causes of BSODs are listed here: https://msdn.microsoft.com/en-us/librar ... 85%29.aspx

[Winxp-on-Macos]

I agree with most your arguments.
However in case of this Win XP installation, it ran for many years on physical machine and system partition on disk on SATA controller.
Of course, no Windows-own SATA/RAID device driver cause such simply not available. Instead driver provided by chipset vendor.
It worked pretty well. Also the p2v conversion completed with success. However a set of problem areas had to be considered prior the conversion - a kind of preparation to conversion.
Like removal of proprietary device drivers as far as possible. Removal of AGP driver, graphic drivers, IDE proprietary driver, a.s.o. Of course for SATA/RAID controller it was not possible.
There is also the aspect of HAL version which need to be considered. Injection of SATA driver for SATA controller emulated in VirtualBox , Intel ICH8M, I guess 82801.
All these measures of preparation helped to have a smooth p2v conversion. The machine runs now as virtual pretty well.
The aim was just to update the driver.

> Therefore it simply isn't possible to keep the VM "original" in this regard.
I confirmed that in previous post.

I can see post here guys have also problems if to convert to virtual in IDE mode then switch to SATA.
So IDE does not seem to be guarantee for success.

Thanks for link regarding the upgrade to 10...1008 driver version. Will have a look at that.

[jorgensen]

I have been through the hole process of adding SATA support to a XP guest, and it is not worth it.
Regards performance it doesn't matter if you use a virtual IDE or SATA controller at the guest.
What matters is what you use on the host site, and for best disk performance it is essential to keep the vdi file as less fragmented as possible. If you have a huge harddisk, you can put the vdi files on a separated partition to improve the seeking times.
If you insist on a SATA drive, the easiest way to add a dummy SATA controller, where XP then will ask for the driver to access this drive.