Skip to main content

Microsoft Hyper-V will not boot virtual SCSI devices



"Each IDE controller can have two devices. You can not boot from a SCSI controller. This means an IDE disk will be required. The boot disk will be IDE controller 0 Device 0. If you want a CDROM it will consume an IDE device slot." Source: MSDN Blog



The hypervisor that runs the virtual BIOS does not support booting from a SCSI controller, today, but it does support the following boot devices:
CD
IDE
Legacy Network Adapter
Floppy

The root reason is SCSI in a synthetic device and there is no VMBUS until after boot.

One might think that this shouldn't be a problem, after all, the virtual machines can still boot from regular IDE-based virtual disks. So where's the catch?

The main problem is related to the fact that in Virtual Server, virtual SCSI controllers have major performance benefits over virtual IDE controllers. In Virtual Server, it is recommended to attach the Virtual Disks to one or more SCSI controllers to improve disk input/output (I/O) performance. IDE is limited to one transaction at a time, regardless of whether the bus is physical or virtual. This means that a virtual machine with two virtual hard disks attached to the IDE adapter is limited to a single transaction for both disks. By contrast, a SCSI controllers allows for multiple simultaneous transactions, which provides better performance than disks attached to the IDE controllers.

This performance bottleneck of virtual IDE and technical limitations of virtual SCSI will oblige customers to have two virtual disks for each VM. A configuration hard to setup in P2V migration scenarios, and hard to manage on large scale deployments.

Note that since Hyper-V is still in Beta phase, all numbers are subject to change as are the behaviors. So there might be hope, after all…

Note: Under Virtual Server 2005, contrary to common sense, the performance of emulated SCSI controllers is slower than that of emulated IDE controllers. The reason for this is that the SCSI controller is a lot more complicated to emulate than the IDE controller. However, this changes once you have Virtual Machine Additions installed, because the Virtual Machine Additions install an accelerated SCSI driver. Once this driver is installed the performance of the emulated SCSI controllers is significantly faster than emulated IDE controllers.

Labels:

Popular posts from this blog

Fixing Tanzu Kubernetes Pod to External Services Connectivity Issues with NSX-T

Fixing Tanzu Kubernetes Pod to External Services Connectivity Issues with NSX-T Last month I got a call from a customer who was pulling their hair out over a networking issue. They had just deployed VMware Tanzu Kubernetes Grid on their vSphere with Tanzu environment, everything looked good in the dashboards, all pods were running, but their applications inside the pods could not reach external databases running on traditional VMs in the same datacenter. The frustrating part was that some pods could reach external services perfectly fine, while others would just timeout. There was no clear pattern. Let me tell you how we figured this out and fixed it. The Initial Problem Here is what the customer setup looked like: vSphere 8.0 with Tanzu enabled NSX-T 4.1.2 for networking Three Tanzu Kubernetes clusters running different microservices applications External PostgreSQL database running on traditional VMs (non-Kubernetes) External API services running on another se...
Read more

Troubleshooting vSAN Storage Policy Migration Failures in VMware Cloud Foundation 9.0

Recently I had a customer who migrated their VMware infrastructure from vSphere 7.0 to VMware Cloud Foundation 9.0. After the migration, they wanted to update their vSAN storage policies to take advantage of the new vSAN ESA (Express Storage Architecture) features. However, when they tried to change the storage policy for their production VMs, the operation kept failing with a cryptic error message. The error they were getting was: "Cannot complete operation due to insufficient resources to satisfy current storage policy." This was strange because they had plenty of disk space available. The vSAN cluster was only at 45% capacity, and all the hosts were healthy. Let me walk through how we troubleshooted and fixed this issue. Understanding the Problem First, let's understand what was happening in their environment: They had a 6-node vSAN cluster running VCF 9.0 vSAN was configured with the new ESA architecture They were trying to migrate VMs fro...
Read more

Unlocking VMware Cloud Foundation 9.0: A Strategic Blueprint for Enterprise Transformation

The evolution of VMware under Broadcom represents not disruption, but clarification—a focused vision toward unified private cloud excellence. As organizations navigate this transformation, the opportunity has never been greater to build truly modern, efficient, and powerful infrastructure with VMware Cloud Foundation. After architecting VMware solutions across diverse enterprise environments, I've observed a pattern: organizations that embrace VMware Cloud Foundation (VCF) strategically—rather than viewing the transition as a burden—emerge with significantly more capable, cost-effective, and future-ready infrastructure. This post shares a practical framework for successfully modernizing your VMware environment, maximizing your investment, and positioning your organization for the AI-driven, cloud-native future. Understanding the VMware Cloud Foundation Vision Let's start with clarity about what Broadcom and VMware are building: VMware Cloud Foundati...
Read more