![]() |
![]() | ![]() | ![]() | ![]() | ![]() | ![]() | ![]() |
| Welcome to Windows Vista Forums. Our forum is dedicated to helping you find solutions with any problems, errors or issues you are experiencing with Windows Vista. The Vista forum also covers news and updates and has an extensive Windows Vista tutorial section that covers a wide range of tips and tricks. |
| |||||||
![]() |
| |
| | #1 (permalink) |
| | Hyper-V and Disk types Basically, I am curious how the performance works out on Hyper-V. If for example, I had a SAS drive setup to host my VM's hard drive, if I configured the VM for IDE I would take a performance hit correct? And if this is the case, what is the reason to have any VM's use IDE as it is possible that later on they could be placed on a faster BUS. The only reason I can think is compatability, for example if you cannot use SCSI devices in your OS or something. Please enlighten me. Thanks! |
My System Specs![]() |
| | #2 (permalink) |
| | Re: Hyper-V and Disk types You're incorrect. The actual choice of IDE v. SCSI has nothing whatsoever to do with the underlying physical hardware. It is purely a question of which drivers are available at that point in the process. Thus you always have to choose IDE for a system boot drive, because of how the synthetic SCSI driver works. But there is no performance hit at all. I tend to use IDE for the system drive, and add a SCSI bus and drives VMs that need more than 2 drives/VHDs. You can not choose SCSI for any OS that doesn't have available Integration Components, since the drivers won't be available. -- Charlie. http://msmvps.com/blogs/xperts64 http://mvp.support.microsoft.com/profile/charlie.russel "news.microsoft.com" <None@xxxxxx> wrote in message news:%23T8HMh$fJHA.5244@xxxxxx Quote: > Basically, I am curious how the performance works out on Hyper-V. If for > example, I had a SAS drive setup to host my VM's hard drive, if I > configured the VM for IDE I would take a performance hit correct? And if > this is the case, what is the reason to have any VM's use IDE as it is > possible that later on they could be placed on a faster BUS. The only > reason I can think is compatability, for example if you cannot use SCSI > devices in your OS or something. Please enlighten me. > > Thanks! > |
My System Specs![]() |
| | #3 (permalink) |
| | Re: Hyper-V and Disk types Got it! Thank you!!! "Charlie Russel - MVP" <charlie@xxxxxx> wrote in message news:%23VGyFSAgJHA.824@xxxxxx Quote: > You're incorrect. The actual choice of IDE v. SCSI has nothing whatsoever > to do with the underlying physical hardware. It is purely a question of > which drivers are available at that point in the process. Thus you always > have to choose IDE for a system boot drive, because of how the synthetic > SCSI driver works. But there is no performance hit at all. > > I tend to use IDE for the system drive, and add a SCSI bus and drives VMs > that need more than 2 drives/VHDs. > > You can not choose SCSI for any OS that doesn't have available Integration > Components, since the drivers won't be available. > > -- > Charlie. > http://msmvps.com/blogs/xperts64 > http://mvp.support.microsoft.com/profile/charlie.russel > > "news.microsoft.com" <None@xxxxxx> wrote in message > news:%23T8HMh$fJHA.5244@xxxxxx Quote: >> Basically, I am curious how the performance works out on Hyper-V. If for >> example, I had a SAS drive setup to host my VM's hard drive, if I >> configured the VM for IDE I would take a performance hit correct? And if >> this is the case, what is the reason to have any VM's use IDE as it is >> possible that later on they could be placed on a faster BUS. The only >> reason I can think is compatability, for example if you cannot use SCSI >> devices in your OS or something. Please enlighten me. >> >> Thanks! >> |
My System Specs![]() |
![]() |
| Thread Tools | |
| |
Similar Threads | ||||
| Thread | Forum | |||
| Hyper-V standalone vs Hyper-V windows 2008 Core | Virtual Server | |||
| dynamic disk always in offline state when VM restarts in Hyper-v | Virtual Server | |||
| Disk controler with hyper-v | Virtual Server | |||
| Cannot manage an Hyper-V on Core from a full installed W2K8 with Hyper-V... | Virtual Server | |||