Shawn Hyde, Blog

A little something about everything...

Step by Step install of CentOS 6.3 on Microsoft Hyper-V Server with Linux Integration Services Version 3.4

Create new VHD w/ Legacy Network Adapter for CentOS 6.3

Download CentOS 6.3-minimal.iso (insert disk & install)

Download LinuxICv34.iso (insert disk)

 mkdir -p /mnt/cdrom
 mount /dev/cdrom /mnt/cdrom
 cp -rp /mnt/cdrom /opt/linux_ic
 umount /mnt/cdrom
 cd /opt/linux_ic/RHEL63

Once the install is done, shutdown the VPS, note the mac address and then remove the legacy adapter.

Add a standard network adapter with static mac previously noted. apply and restart the VPS

Update your network settings via vi

 vi /etc/sysconfig/network-scripts/ifcfg-eth0

use "i" to insert text, (esc) to exit and ":wq" to write your changes.

It should look something like this:





 HWADDR=(MAC ADDRESS, This should match what is configured in Hyper-V)






If your system is still not online for static IP do this:

 ifconfig eth0 (IP) netmask (MASK) up

 service network restart

Comments (11) -

Just logged on to say thank you for the nice tutorial. Worked like a charm.

Turkey Recep YUKSEL

It's worked, no any problem.

Thank you very much Hyde..

Portugal Marco Faria

And does it still work after you do a yum update?
Whenever i do a yum update and get kernel updated to 2.6.32-279.19.1 and reboot the server it fails to start with kernel panic.
I have to boot to the old kernel to successfully load the kernel.

I did not seem to have any issues doing yum update. maybe you had a bad yum, try it again.

You can also check the repositories, verify you are not installing the wrong version (ie plus kernel)

The ICS kernel modules are compiled for the stock kernel that ships with CentOS 6.3 - 2.6.32-279 It may be possible to copy them over to the new kernel directory and do a depmod to use them with the new kernel.

The directory you'd need to copy is /lib/modules/2.6.32-279.el6.x86_64/extra/microsoft-hyper-v

Bit of a PITA but then that's MicroShaft for you...

Outstanding.  Thanks a bunch!

Maybe you underestimated the stupidity of a newbie like me, or maybe there was a way around this, but I had a lot of problems until I attached the iso file to the virtual DVD/CDROM drive.  I don't actually have a cdrom in my machine, so I just downloaded the LinuxICv34.iso file to my virtual machine and mounted it there.  It didn't work.  I tried extracting the iso file and downloading it as a directory tree.  No difference.  I tried writting the iso image to disk on a different machine, copying the folders from there and downloading them.  Still no love.  Finally, I figured out how to attach the virtual DVD/CDROM drive to an iso file in Hyper-V settings.  Everything worked!  So I don't know what the difference is (did I mention I'm a Linux newbie?) but I think it would be helpful to some people if you added that step in your instructions.  Otherwise, this was incredibly helpful.  Thank you!

United States Anonymous Coward

Thank you!

Thanks a lot!! Worked Great.

One question that I have is..
I have the outside ip configured correctly but I would also like to connect to other vm's internally. Do I create an internal switch in hyper-v and repeat the above process??


You should add an extra lan port both on the Hyper-V server and on the nix box, then vlan them or if you hyper-v has multiple physical nic cards you can have one go to a private switch and another go to public switch for best security.

Pingbacks and trackbacks (2)+