When configuring a new VM in Hyper-V, take note that the OS will not see any disks if they are attached to a SCSI controller:
Hyper-V – Server 2008 VM: No drives were found
The drive that an OS will be installed into must be connected to one of the two available IDE Controllers. This is usually Controller 0.
Apparently, the primary reason for this is due to the way the driver is handled for the SCSI controller. It is loaded on OS boot, and cannot be inserted via the Integration Services disk into the setup portion of the OS.
Some further reading:
- Petri: Microsoft Hyper-V will not boot virtual SCSI devices.
- TechNet Forums: HyperV scsi syntheric drivers don"t run under Windows XP SP3 (sic).
- Microsoft Newsgroup: Hyper-V and Disk types in Virtual Server (Charlie Russel commenting).
Microsoft Small Business Specialists
*All Mac on SBS posts will not be written on a Mac until we replace our now missing iMac!