I've been trying to get my mind around this one for the last hour, if anyone has a pointer to who it's done I would appreciate it:
Background:
Our VMWare ESXi guests use scsi-based virtual disks all over. This lets us expand our virtual disks in real-time, a feature we use a LET, both on the OS drive (requires windows 2008 and later) and any data drives.
Now, evaluating Hyper-V I need to emulate this. The doc states that a hyper-v guest can only use IDE as boot device, and only SCSI-disk have the option to expand on the fly. So, I want to install Windows 2008R2 with two drives:
Disk 0: IDE: boot files only
Disk 1: SCSi: Windows (regular C drive)
If possible, I want to avoid giving the IDE-disk any drive letter at all, so that for a regular server admin it will look just like a regular (vmware) guest, with the windows folder on C: and all that.
Have anyone done this? Before I started researching it I thought this would be the way everyone did it, but I can't find much good info out there…
Best Answer
As user48838 alludes, you can't boot Hyper-V VMs from the "SCSI Adapter" (because it's not a SCSI adapter at all, they just used that name because people were familiar with it. Related, QEmu/KVM calls it's driver
virtioas most people understand virtualization much better than when MS picked the names of it's drivers).The "SCSI Adapter" is a complicated storage IO bus that Hyper-V's BIOS doesn't support; it's BIOS doesn't support the VMBUS at all. The Windows Boot Manager can only pull
winload.exefrom storage the BIOS can communicate with (IDE disk, IDE CD, Floppy, and PXE).In short, you can't do what you want to do. Though you can put the system drive on a dynamic disk and make it 2TB to begin with. This also allows you to shrink (recover unused space) the VHD occasionally.