IDE Controller Vs SATA Controller

[a cooperator]

Hellow everyone!

I really had the old verstion of VirtualBox ( V: 3.1. 4r57640.) and I have created a VM with fixed size virtual disk. However, I have found out that Virtual disk file was created under the IDE controller.



When I have updated inot the most recent version of VBox(VirtualBox-4.3.6-91406), then created a new VM with a dynamica size virtual disk. I have found out that Virtula disk ifle was created under 'SATA Cotroller'.



I really havn't been asked to choose which conroller I should use, IDE or SATA while creating a VM with either version of VBox. Thus, why was IDE conroller used on the first version of VBox, however, ASAT controller used in the second version of VBox?


Also, I found that the path of the old version of VBox is 'D:\Users\Mohammad\.VirtualBox'
However, the path of the new version of VBox is 'D:\Users\Mohammad\VirtualBox VMs'

[Martin]

Windows XP guests default to an IDE Controller, because it doesn't support SATA directly.
Windows 7 guests use SATA.

[a cooperator]

Windows XP guests default to an IDE Controller, because it doesn't support SATA directly.
Windows 7 guests use SATA.

Thanks a lot,

Yes, but on both VMs, I have installed a Windows 7. And I haven't installed a windows xp at all.

Also, I found that the path of the old version of VBox( V: 3.1. 4r57640.)) is 'D:\Users\Mohammad\.VirtualBox'
However, the path of the new version of VBox(VirtualBox-4.3.6-91406) is 'D:\Users\Mohammad\VirtualBox VMs'

[mpack]

I don't see the issue here. You do understand that different software versions do things differently, right? If they were the same then what would be the reason for changing the version number?

Did a Win7 template even exist in VBox v3?

[a cooperator]

I don't see the issue here. You do understand that different software versions do things differently, right? If they were the same then what would be the reason for changing the version number?

Did a Win7 template even exist in VBox v3?

Thanks a lot,

More details for this issue are as follows: As you know when creating a VM on any versions of VBox, you cannot go through a step asking you to choose which controller you would like to use, IDE or SATA, can you?.

However, I, myself, When I installed the very old version of VirtualBox ( V: 3.1. 4r57640.) and I have created a VM with fixed size virtual disk. However, I have found out that Virtual disk file was created under the IDE controller.



When I have updated inot the most recent version of VBox(VirtualBox-4.3.6-91406), then created a new VM with a dynamica size virtual disk. I have found out that Virtula disk file was created under 'SATA Cotroller'.




I really don't understand what is meant with Did a Win7 template even exist in VBox v3?

However, this is the screen shot for both VMs created, the first one was created on the very old version of VBox, and the second was created on the new version.

[Martin]

So the "old" VM is using IDE. Where is your problem?

[a cooperator]

So the "old" VM is using IDE. Where is your problem?

I don't have problem as you might see, I would like only to know if this is normal or not. Also, if there are some features good for SATA added only in new version of VBox.

Besides, VM created on old, and even when I installed the new version, it is still has VDI under IDE controller and not reversed into SATA.


Also, I found that the path of the old version of VBox( V: 3.1. 4r57640.)) is 'D:\Users\Mohammad\.VirtualBox'
However, the path of the new version of VBox(VirtualBox-4.3.6-91406) is 'D:\Users\Mohammad\VirtualBox VMs'

Thus, if I had removed all in the old path, then VM would have been corrupted.

[dlharper]

Some of the templates have been changed as VirtualBox has developed.

You state:

I really havn't been asked to choose which conroller I should use, IDE or SATA while creating a VM with either version of VBox. Thus, why was IDE conroller used on the first version of VBox, however, ASAT controller used in the second version of VBox?

VirtualBox could have been designed so that you did have to answer this and all other set-up questions before it allowed you to start. You would then have to tell it what chipset you required, what network card you wanted, etc, in order to set up any virtual machine. That would have been very tedious. Instead VirtualBox provides a set of "templates" based on what operating system you intend to install. Such a template is just a judgement about what is likely to work reasonably well with that OS. You do not have to stick to any of it. If you wish to change anything about it (such as whether you are using an IDE or SATA controller for the hard disk) then you can do so in the machine settings before you start to install anything on it.

[mpack]

Some of the templates have been changed as VirtualBox has developed.

...and been added to as new versions of Windows appear. VirtualBox v3.x will pre-date many current versions of Windows. Checking the dates: Windows 7 was still in beta when VBox 3.0 appeared. Vista was the then current Windows version. A VM created in VBox v3.x days probably wasn't created using a Win7 template. More likely it was created as an XP guest and then upgraded. Naturally a OS software upgrade does nothing to the hardware.

As to which is better between SATA and IDE. This is a bit like "if you need to ask the price, you can't afford it". If adding SATA support is so onerous that you need to ask about the benefits: then don't bother.

And yes: you can change everything about a VM if you edit the settings prior to launching it - but that doesn't mean that the guest OS can support whatever hardware you invent. For example, XP has no native support for SATA, which is why it isn't offered by default.