> Hello
>
> after setting up my first w2K3r2sp2 vm on hyper-v, i was surprised to see
> that i was unable to choose an scsi disk. Only IDE controler is available
> and seen is hyper-v despite the fact that my server his a dell R200 with 2
> SAS 3Gb/s hard drives 15 Ktmins on a perc6/iR controller
>
> any idea ?
>
> In advance Thks
> fafa

> so it's not intersting to load a scsi driver to have better performance
>
> thks
> fafa
> Charlie Russel - MVP a écrit :
>> This is "normal" in Hyper-V. The IDE and SCSI designations for disks have
>> _nothing_ to do with the underlying physical hardware. They are simply
>> the way that Hyper-V presents the synthetic disk controller to the child
>> operating systems. Because the synthetic SCSI would require a driver to
>> be loaded before the disk could be seen by the OS, the boot disk must
>> always be "IDE". In order to use the synthetic SCSI disks, the
>> integration components must be loaded. But the IDE type is available to
>> all OSs without additional drivers, so use that for your boot disk.
>>
>> An important note: unlike Virtual Server, the effective speed of the IDE
>> and SCSI disk types are the same, so there's no penalty for choosing IDE.
>>

> This is "normal" in Hyper-V. The IDE and SCSI designations for disks
> have _nothing_ to do with the underlying physical hardware. They are
> simply the way that Hyper-V presents the synthetic disk controller to
> the child operating systems. Because the synthetic SCSI would require a
> driver to be loaded before the disk could be seen by the OS, the boot
> disk must always be "IDE". In order to use the synthetic SCSI disks, the
> integration components must be loaded. But the IDE type is available to
> all OSs without additional drivers, so use that for your boot disk.
>
> An important note: unlike Virtual Server, the effective speed of the IDE
> and SCSI disk types are the same, so there's no penalty for choosing IDE.
>