Direkt zum Hauptbereich

Step By Step Guide To Install CentOS Linux Virtual Machine in Windows Hyper-V Server

Question:

Please follow this step by step guide to load CentOS 5.x or other Linux Operating System in Windows Hyper-V server.

Solution:

1) Creating a Hyper-V server

First, create a virtual machine within Hyper-V manager. If yo don't know, please refer to Step by Step Guide to Create Windows Hyper-V Virtual Machine.

2) Adding Legacy Network Adapter

CentOS5 doesn't support synthetic deivces. We created an emulated network adapter to access Interate in order to make installation convenient. Select the new VM -> In Actions pane, select Settings... -> In the new VM's setings window, on the left pane under Hardware, click Add Hardware. -> On the right pane under Add Hardware selec Legacy Network Adapterand click Add.

Figure 1


The right pane's content will change to Legacy Network Adapther . Drop down Network: list and select External Virtual Network. Click Apply. Now you have an emulated network adapter to be used to access Internet before enable synthetic network adapter.

Firgure2



3) Install CentOS 5

On left pane under Hardware, select IDE Control 1 -> DVD Drive. On right pane under Media select proper installation media. We used CentOS DVD image to install, so select Image file : and Browse to the image file and open.
Click OK



Firgure3

Double click the VM in Hyper-V manger. There would pop up the Virutal Machine Connection Window. On the new VM window, select menu Action -> Start. Now CentOS installation start.

Figure4


The intall process is much the same like to install on a physical server. The emulated network adapter should be recognized and should show up as Figure 5.. We would configure it to make installation more convenient.

Figure 5



4) Install Linux Service Integration Component

Now we'll go through the most exciting part of the installation, Linux IC installation. Donwload Linux Integration Components for Windows Server 2008 Hyper-V to your host server. The URL for the time this article is writen is here

Figure6


After extract the ISO file, mount it to the new VM's DVD drive (shows in Figure3). To install the drivers we need the development tools. The easiest way to install those is via Yum.

    sudo yum groupinstall "Development Tools"      

Next we will copy the contents of the cdrom to the server

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

Then let's install it.

Please note that if you want to shift to root user before execute this command by running 'su', it may not work. You need to run 'su -'. It will load root user's context completely(Thank you José! for providing your experience.).
    cd /opt/linux_ic     sudo ./setup.pl drivers      
But you may fail and get the following information:
    Checking if required components are installed...     No kernel-devel or kernel-source package installed.      You must install this package before installing the drivers.      
It requires "kernel-devel". So let's install via Yum
    sudo yum install kernel-devel     
Let's try again.But you may fail again and get the following:
    Checking if required components are installed...done.     Installing Linux integration components (vmbus, enlightened ide, enlightened scsi      and network drivers) for Hyper-V...     Building vmbus driver...An error has occured during the setup!      Please view the drvinstall.err for more details. 
And detailed info shows in drvinstall.err as
    [root@localhost linux_ic]# cat drvinstall.err     make: *** /lib/modules/2.6.18-128.el5/build: No such file or directory.  Stop.     make[1]: *** [default] Error 2     make: *** [public] Error 2 
We need to update whole system by running
    sudo yum update     
Then reboot the VM.
    reboot     
After reboot let's try again:
    [root@localhost linux_ic]#./setup.pl drivers     Checking if required components are installed...done.     Installing Linux integration components (vmbus, enlightened ide, enlightened scsi      and network drivers) for Hyper-V...     Building vmbus driver...done.     Building blkvsc driver...done.     Building storvsc driver...done.     Building netvsc driver...done.     Installing vmbus driver...done.     Installing blkvsc driver...done.     Installing storvsc driver...done.     Installing netvsc driver...done.     Updating module dependencies. This may take a while...done.     Installing various udev rules and scripts...done.     Updating initrd image...             Backing up /boot/initrd-2.6.18-164.el5.img to /boot/initrd-2.6.18-164.el5.img.backup0             Done. Updated /boot/initrd-2.6.18-164.el5.img     Updating grub conf file...             Done.     Installing vmbus startup script...     *** The drivers have been installed successfully.***       [  OK  ]     
You can verify it by running "lsmod | grep vsc". If you get the following, you succeeded. Congratulations!
    [root@localhost linux_ic]# lsmod | grep vsc     storvsc                67208  0     netvsc                 74088  0     vmbus                  86504  2 storvsc,netvsc     scsi_mod              196697  4 storvsc,scsi_dh,libata,sd_mod     [root@localhost linux_ic]#   


5) Post install configuration

When reboot VM you may get error like "kernel panic". It's becuase another kernel was install during update. You can check it out by clicking any key at the very beginning of startup.

Figure7


You can select one of them manually each time reboot. But it's annoying.. To solve it, you could modify Grub configuration file,/boot/grub/grub.conf, changing the default to the proper one.
    default=0  
Now everghings are OK. You can reboot the server now. During reboot there would be a new network interface named seth0. It's the new recognized synthetic network adapter. You can configure it and remove the emulated one.

Kommentare

Beliebte Posts aus diesem Blog

Microsoft Office 2013 aktivieren via Kommandozeile

Wie man das neue Microsoft Office 2013 aktiviert via Kommandozeile, das werde ich euch in dem folgenden Beitrag Schritt für Schritt erklären. Gerade in grösseren Systemumgebungen in welchen die Clients und Standard Software automatisiert installiert werden, kann das sehr hilfreich sein und erspart einem viel Arbeit nach der Installation des Clients. Das Ziel sollte sein, möglichst viel zu automatisieren und soweit möglich, wenig noch händisch zu konfigurieren. Da kommt dieser Beitrag sicherlich nicht ungelegen. Die folgenden Befehle könnte man beispielsweise ganz einfach in eine MDT (Microsoft Development Toolkit) Umgebung mit einbeziehen oder auch mit anderer Software benutzen. Wichtig zu wissen ist, dass dies nur dann funktioniert, wenn Microsoft Office 2013 über das Internet aktiviert wird. Hat man einen eigenständigen Aktivierungsserver (KMS), funktioniert dies nicht. Zudem müssen die Befehle alle mit Administrator Rechte ausgeführt werden. Normale Benutzerberechtigungen genügen …

Windows Domain Controller: Es sind momentan keine Anmeldeserver zum Verarbeiten der Anmeldeanforderung verfügbar

Zurzeit häuft sich (warum auch immer) das Problem dass nach einem Neustart eines Windows Domain Controllers bei der Anmeldung die Fehlermeldung „Es sind momentan keine Anmeldeserver zum Verarbeiten der Anmeldeanforderung verfügbar“ kommt und eine Anmeldung so nicht möglich ist Das Problem ist hierbei das der Domain Controller im Active Directory Reperatur Modus (Abgesicherter Modus) startet. Am einfachsten lässt sich dieses Problem folgendermaßen beheben: 1) Anmeldung mit dem DSRM (Directory Services Restore Mode) / Verzeichnisdienstwiederherstellungskennwort Falls die Anmeldung nicht funktioniert kann man einen Workaround wie hier beschrieben durchführen. 2) Systemkonfiguration mittels msconfig.exe aufrufen

WSUS won’t uninstall or re-install

Hat heute ein Problem mit WSUS unter Windows Server 2008 R2 bei einem Kunden. Das Problem - die Clients konnten keinen Verbindung zum WSUS Server herstellen. Die Deinstallation wurde unerwartet beenden mit folgender Fehlermeldung: Attempt to un-install Windows Server Update Services failed with error code 0x80070643. Fatal error during installation  Die Lösung: I don’t like Windows Server Update Services (WSUS), but it’s the free alternative many companies select over the higher cost alternatives like Intune or Systems Center. So, today I had to repair a damaged WSUS installation. Turns out someone uninstalled SQL Server 2005 Express not realizing WSUS was using it. Now firing up the WSUS console just yielded an error complaining about the missing SQL database. So like any good troubleshootin IT guy the first thing I tried was to uninstall WSUS…sadly, however the product would not uninstall or re-install. Here’s how I finally got rid of it: [the problem] WSUS 3.0 SP2 is missing SQL serv…