Posts mit dem Label Linux werden angezeigt. Alle Posts anzeigen
Posts mit dem Label Linux werden angezeigt. Alle Posts anzeigen

Mittwoch, 27. Juli 2011

Linux Integration Services 3.1 for Hyper-V


I had a mad busy day with meetings at customer sites today and that’s when this great news breaks out.  Microsoft has released version 3.1 of the Linux Integration Components (or Services) for Hyper-V.
The supported operating systems for 3.1 are:
  • “Red Hat Enterprise Linux (RHEL) 6.0 and 6.1 x86 and x64 (Up to 4 vCPU)
  • CentOS 6.0 x86 and x64 (Up to 4 vCPU)”
SLES 10 SP3 and 11, and RHEL 5.2 / 5.3 / 5.4 / 5.5 still have support using Integration Services 2.1 for Hyper-V.
Supported Host OS’s include:
  • “Windows Server 2008 Standard, Windows Server 2008 Enterprise, and Windows
  • Server 2008 Datacenter (64-bit versions only)
  • Microsoft Hyper-V Server 2008
  • Windows Server 2008 R2 Standard, Windows Server 2008 R2 Enterprise, and Windows
  • Server 2008 R2 Datacenter
  • Microsoft Hyper-V Server 2008 R2”
Service Packs 1 or 2 of those host OSs are supported too.
The features of V3.1 of the Linux Integration Services are:
  • “Driver support: Linux Integration Services supports the network controller and the IDE and
    SCSI storage controllers that were developed specifically for Hyper-V.
  • Fastpath Boot Support for Hyper-V: Boot devices now take advantage of the block
    Virtualization Service Client (VSC) to provide enhanced performance.
  • Timesync: The clock inside the virtual machine will remain synchronized with the clock on
    the virtualization server with the help of the pluggable time source device.
  • Integrated Shutdown: Virtual machines running Linux can be shut down from either Hyper-V
    Manager or System Center Virtual Machine Manager by using the “Shut Down” command.
  • Symmetric Multi-Processing (SMP) Support: Supported Linux distributions can use up to 4 virtual processors (VP) per virtual machine.  SMP support is not available for 32-bit Linux guest operating systems running on Windows Server 2008 Hyper-V or Microsoft Hyper-V Server 2008.
  • Heartbeat: Allows the virtualization server to detect whether the virtual machine is running
    and responsive.
  • KVP (Key Value Pair) Exchange: Information about the running Linux virtual machine can
    be obtained by using the Key Value Pair exchange functionality on the Windows Server 2008
    virtualization server”.
The really big news about the new Integration Components is that they now install using rpm, making the installation much easier (Windows admins thank you!).
You should really take a look at the KVP feature in the PDF (on the download page).  There’s some interesting information and links on how to use it to get information, such as the Linux IC version from the VMs on your hosts using PowerShell.

Dienstag, 31. Mai 2011

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.

Rename Onedrive Business root folder

Rename Onedrive Business root folder Here is what I remember: In the Office 365 web admin pages, change the organization name to a shorte...