Hyper-V Limitations

Since my initial review on Hyper-V, many visitors ended up on this blog from google and other search engines searching for Hyper-V related information. While some of them were looking for a review of Hyper-V, most were actually looking for solutions to problems they are facing with Hyper-V. Now that several weeks have passedt and I have accumulated a good number of popular search phrases about Hyper-V leading to this Website, I can list what appears to be the most common problems or limitations of Hyper-V based on the frequency or repetition of these search phrases.

  1. Remote Access of Guest Machine Console
    Not being able to connect to to a Hyper-V guest console with VMRC like client seems to be the biggest problem. With the release of Hyper-V management control for Windows Vista SP1, this problem is reduced a little bit. But not too many people use Vista yet, none of the workstations that are in my control (about 15 of them) has Vista installed. Also, when connecting to a remote server via MMC, firewall configuration may be an issue.
  2. Guest Machine Console over Remote Desktop
    Although Microsoft is very straight froward in saying Hyper-V guest machine console is not supported over RDC, many of us seem to have no choice! The biggest problem seems to be mouse capture. Hyper-V release candidate don't even try to capture mouse when running within a Remote Desktop. Installing integration components does fix this issue, but not with Linux guest installations.
  3. Boot from SCSI
    I mentioned in my original review that Hyper-V final release better be able to boot from SCSI. As of RC0, it does not, and people are searching to see if it is possible. No one would want a server to run on IDE, specially when the underlying physical storage is SCSI. I don't like it, no matter how efficient the synthetic IDE driver is, there has to be some overhead in traslating IDE to underlying SCSI physical interface. So let me say this again: Hyper-V final release better be able to boot from SCSI!
  4. Various flavors of Linux distribution installation as guest OS
    Search terms seem to favor Ubuntu, SUSE and Fedora. But this is probably because I have made posts relating to these distributions. I think  all popular Linux distributions would be in demand.
  5. Slow connections over network
    I personally did not experience slow network performance, but people seem to be searching about it.
  6. Network access for Linux guest installations
    There are two solutions to this: install Linux integration components, or use a Legacy Network Adapter. You can add Legacy Network Card from Hyper-V machine's Settings - Add Hardware option.

Of course, quite a few people did search for a review on Hyper-V, and some were looking for comparisons between Hyper-V and Virtual Server 2005.

Posted on April 9, 2008 06:42 by Haider


September 8. 2008 12:57

billy bob

you'r complaints about hyper-v virtuals not 'booting from scsi' are, in a word, idiotic.  this is a virtual world.  whether driver are presented to the virtuals as ide or scsi (or fc, or mfm, or rll...) doesn't, by itself, make a rats ass bit of difference.  the IO requests are translated through to the appropriate VM HOST driver, which is doing all the communication on the IO 'wire'.  do some perf tests.  you'll see perf is actually excellent (granted, with the VM additions installed).  

billy bob