Ubuntu 8.10 on Hyper-V

Reporting successful installation of Ubuntu 8.10 Server Edition (With LAMP) on Hyper-V. No patch was necessary like it was for Ubuntu 7.10. Over a Remote Desktop connection to the Hyper-V host, installation screens appear very slow. But the installation was otherwise smooth.

Remember to use a 'Legacy Network Adapter' for the virtual machine if you would like networking to work out of the box. Installing Linux Integration Components should enable standard Network Adapter and improve network performance.

I have yet to try Linux Integration Components on an Ubuntu Installation.

If you know a tutorial for installing the Integration Components, please post a link.

Ubuntu Patch for Hyper-V

My original post about installing Ubuntu 7.10 on Hyper-V had a link to a patch that you needed to apply before installing Ubuntu 7.10 on Hyper-V. The original link to the patch seems no longer pointing to the right thread on the Citrix Forum. I received some requests for an update on this patch, and since I had a copy, I am leaving it here for download.

If you have any Ubuntu 7.10 ISO in the same folder where this patch is being run, it will fix those ISO and you should be able to install Ubuntu on Hyper-V without any issue. How stable is Ubuntu on Hyper-V? Well we do have Ubuntu Servers on Hyper-V running production Web Sites and so far they are working great. No linux Integration Components installed yet.

I take no credit for this patch, and I wish I knew who originally posted it on the citrix forum.

Download the patch (491KB)

Hyper-V SCSI vs IDE Boot

Looking at the number of searches relating to this issue, it appears to be the biggest concern about Hyper-V so far.

While it is not acceptable that a Virtual Machine must boot from an IDE drive interface when the underlying storage is SCSI, it is possible that the IDE performance in Hyper-V could be better than pre-existing virtual SCSI storages (Virtual Server, for example). The virtualization team on Microsoft explains it better, but the new synthetic drivers on Hyper-V utilizes a much better way of providing virtualization, resulting in better performance. It is possible that the IDE driver in Hyper-V can perform better than SCSI driver in Virtual Server 2005.

We have yet to run a performance comparison between Hyper-V IDE and Virtual Server 2005 SCSI. However, once the integration services (synthetic drivers) installed on a Windows 2003 guest machine, it appears pretty fast.

Also, a SCSI hard drive can be added to a Virtual Machine and used as the data storage. We often seperate boot and data drives on servers anyways. Having a seperate data drive makes it easy to backup virtual machine data.

These of course, are just work arounds until Microsoft figures a way to boot Hyper-V machines from SCSI.

They must be working hard on it. 

Hopefully soon we will be able to run some performance comparison between Hyper-V and Virtual Server guest machines.

Networking issue with Hyper-V External Virtual Network

Pretty much like Virtual Server 2005, Hyper-V has options to create virtual network cards for guest machines that directly maps with a physical network adapter on the host machine. There is  an important issue that may surprise you, however, especially if you are working on a remote server.

When you create a virtual network and map it to a physical Network Adapter (External Virtual Network), Hyper-V automatically removes all protocols from the physical Network Adapter on the host machine and enables Virtual Network Switch Protocol. This means TCP/IP protocol is also removed! The host server will appear disconnected/offline from the outsite world. If you were working over remote desktop, you will be kicked out, and won't be able to connect anymore.

All you have to do is re-enable TCP/IP on the physical Network Adapter in order to bring the server back online. Which of course you can't do unless you are logging in locally.

It is not a big deal if you have a second network card that is also connected to the Internet. In fact thats how I was saved, twice.

Why does Hyper-V remove all protocols from the physical network adapter except virtual networking? Is there some stability issues? Security issues? poor performance? I have yet to check the documentation on this.

But if you are reading this before it is too late, at least you can be prepared.

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.