No network devices detected after installation of SLES10SP2 guest in Hyper-V environment
This document (7001863) is provided subject to the disclaimer at the end of this document.
Microsoft Windows Server 2008
- Make sure Hyper-V is on current patch level
- Download the Linux Integration Components for Microsoft Hyper-V from
A Live ID account is needed in order to access this website. Once the account exists, apply the Linux Integration Components for Microsoft Hyper-V
to the dashboard in order to be able to have access to the download.
- Extract the Microsoft Windows Server 2008 Hyper-V Linux Integration Components.exe file to a convenient location and read the Linux ICs for Hyper-V.rtf file that was extracted.
- Please note:
Support is limited to SUSE Linux Enterprise Server 10 SP2 (32/64bit)
- According to the documentation the following software pattersn are necessary:
- Xen Virtual Machine Host Server
C/C++ Compiler and Tools
HINT: Please just install the kernel-xen* as the remaining parts of the XEN environment is not necessary. Furthermore do not
install all packages from C/C++ Compiler and Tools. It is sufficient to just install the packages kernel-source
and gcc plus dependencies in order to build the modules and save disk space.
Search for kernel-xenpae (for 32bit installations) and kernel-xen (for 64bit installations) as this package does not
get added automatically when the pattern Xen Virtual Machine Host Server is chosen.
According to the documentation that ships with version 1.0 of Linux Integration Components for Microsoft Hyper-V the following steps are necessary in order to configure the system after all required packages got installed:
- Attach the LinuxIC.iso image to the virtual machine
- Mount the ISO using
mount /dev/cdrom /mnt
- Create a directory in /opt in the following way:
- Copy all content from the iso to this directory:
cp -R /mnt/* /opt/linux_ic
- Run the command:
/opt/linux_ic/setup.pl x2v /boot/grub/menu.lst
This step adjusts the default= setting in the global section of GRUB
to point to the Xen section and switches the boot entry for the Xen
hypervisor kernel fromkernel /boot/xen.gztokernel /boot/x2v-32.gzfor a 32-bit installation orkernel /boot/x2v-64.gzfor a 64-bit installation.
In case /boot is on a separate partition, make sure it gets mounted prior before
running this command. If everything worked as expected, the command output
will prompt to reboot the system.
- Once the system rebooted, run the command
/opt/linux_ic/setup.pl driversto start the compilation of the drivers.
If compilation finish successful, the service /etc/init.d/vmbus will get
activated automatically and added to runlevel 3 and 5. Even though YaST2 is able
to configure the network card without a reboot, please follow the advise to
reboot the server.
- After the reboot run
yast2 lanas root to start the configuration of the network interface. The network interface is active as soon as YaST2 finished.
Updating the guest system using YOU / ZMD
Please note that updating the kernel will result in a system not being able to boot. The reason is the default= entry in grub's global section pointing to the previous entry before the system was updated. As YaST2 only maintains one kernel at the same time, the old image was removed and only the backup initrd is left. If a kernel update took place during an online update, the following steps are necessary.
Hint: Re-running '/opt/linux_ic/setup.pl x1v /boot/grub/menu.lst'will not help as it does not update the recently added entry for the latest kernel.
- Open /boot/grub/menu.lst with a familiar editor.
- Search for recently added boot entry, e.g.
###Don't change this comment - YaST2 identifier: Original name: xen### title Xen -- SUSE Linux Enterprise Server 10 SP2 - 220.127.116.11-0.31 root (hd0,1) kernel /boot/xen.gz module /boot/vmlinuz-18.104.22.168-0.31-xen root=/dev/hda2 vga=0x0317 resume=/dev/hda1 splash=silent showopts module /boot/initrd-22.214.171.124-0.31-xenand change the linekernel /boot/xen/gztokernel /boot/x2v-32.gzfor a 32-bit kernel or tokernel /boot/x2v-64.gzfor a 64-bit kernel.
- Make sure 'default=' points to this section.
Hint: Counting the entries start at 0 (zero). If the section above is the third entry in the file. default= needs to be set to 2.
- Save the changes and reboot.
- Once the system rebooted, network setup will fail. Login as root and run the command
/opt/linux_ic/setup.pl driversto rebuild the drivers for the current kernel.
- When the compilation finished, run
rcnetwork restartto activate the network settings.
In order to verify the system boots properly, please reboot it and monitor its console output.
This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
- Document ID:7001863
- Creation Date: 13-Nov-2008
- Modified Date:14-Dec-2021
- SUSE Linux Enterprise Server
For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com