(Optional) Installing Native KVM Drivers on a Xen ECS

Before using a Xen ECS to create a Linux private image, you need to install native Xen and KVM drivers on the ECS.

This section describes how to install native KVM drivers.

• The virtualization type of the ECS is Xen.

  lscpu

  • If the value of Hypervisor vendor is KVM, install drivers as instructed in (Optional) Installing Native KVM Drivers on a KVM ECS.

  Figure 1 Checking the virtualization type of a Linux ECS

  
  

• The ECS kernel version must be later than 2.6.24.
• Disable your antivirus and intrusion detection software. You can enable them after the driver installation is complete.
• Operations in Changing Disk Identifiers in the GRUB File to UUID and Changing Disk Identifiers in the fstab File to UUID have been completed.

To ensure that you can successfully install native Xen and KVM drivers, you must uninstall PV drivers from the ECS first.

1. Log in to the ECS as root using VNC.
2. Check whether PV drivers are installed in the OS.

    ps -ef | grep uvp-monitor 
   
   

   • If the following information is displayed, PV drivers are installed.
   • Otherwise, PV drivers are not installed. No further actions are required.

   root     4561        1    0   Jun29 ?           00:00:00    /usr/bin/uvp-monitor 
   root     4567     4561    0   Jun29 ?           00:00:00    /usr/bin/uvp-monitor 
   root     6185     6085    0   03:04  pts/2      00:00:00   grep uvp-monitor
   
   

3. In the VNC login window, open the CLI. (For how to open the CLI, see the OS manual.)
4. Uninstall PV drivers.

    /etc/.uvp-monitor/uninstall 
   
   

   • If the following information is displayed, PV drivers are uninstalled successfully:

     The PV driver is uninstalled successfully. Reboot the system for the uninstallation to take effect.
     
     

   • If the command output indicates that .uvp-monitor is not found, go to 5.

     -bash: /etc/.uvp-monitor/uninstall: No such file or directory
     
     

5. To prevent log overflow, perform the following operations to delete uvp-monitor that failed to be applied in KVM:
   1. Check whether UVP user-mode programs are installed in the OS.

       rpm -qa | grep uvp 
      
      

      Information similar to the following is displayed:

      libxenstore_uvp3_0-3.00-36.1.x86_64
      uvp-monitor-2.2.0.315-3.1.x86_64
      kmod-uvpmod-2.2.0.315-3.1.x86_64
      
      

   2. Delete the installation packages.

       rpm -e kmod-uvpmod 
       rpm -e uvp-monitor 
       rpm -e libxenstore_uv  p 
      
      

Modify the configuration file based on the Linux distribution.

1. Run the following command to open the /etc/dracut.conf file:

    vi   /etc/dracut.conf 
   
   

2. Press i to enter insert mode and add Xen PV and VirtIO drivers to add_drivers (the format varies depending on the OS).

   [root@CTU10000xxxxx ~]# vi /etc/dracut.conf 
   # additional kernel modules to the default 
    add_drivers+="xen-blkfront   xen-netfront   virtio_blk   virtio_scsi   virtio_net   virtio_pci   virtio_ring virtio"  
   ......
   
   

3. Press Esc, enter :wq, and press Enter. The system saves the change and exits the /etc/dracut.conf file.
4. Run the following command to regenerate initrd:

    dracut   -f   /boot/initramfs-2.6.32-573.8.1.el6.x86_64.img 
   
   

   If the virtual file system is not the default initramfs, run dracut -f <actual-initramfs-or-initrd-filename>. You can obtain the actual initramfs or initrd file name from the grub.cfg file, which can be /boot/grub/grub.cfg, /boot/grub2/grub.cfg, or /boot/grub/grub.conf depending on the OS.

5. Check whether native Xen and KVM drivers have been installed. If the virtual file system is initramfs, run the following commands:

    lsinitrd   /boot/initramfs-`uname   -r`.img   |   grep   xen 
    lsinitrd   /boot/initramfs-`uname   -r`.img   |   grep   virtio 
   
   

   If the virtual file system is initrd, run the following commands:

    lsinitrd   /boot/initrd-`uname   -r`   |   grep   xen 
    lsinitrd   /boot/initrd-`uname   -r`   |   grep   virtio 
   
   

   Assume that the virtual file system is initramfs. The command output will be:

   [root@CTU10000xxxxx home]# lsinitrd /boot/initramfs-`uname -r`.img | grep xen 
   -rwxr--r--   1 root     root        54888 Jul 16 17:53 lib/modules/2.6.32-573.8.1.el6.x86_64/kernel/drivers/block/ xen-blkfront.ko  
   -rwxr--r--   1 root     root        45664 Jul 16 17:53 lib/modules/2.6.32-573.8.1.el6.x86_64/kernel/drivers/net/ xen-netfront.ko  
    
   [root@CTU10000xxxxx home]# lsinitrd /boot/initramfs-`uname -r`.img | grep virtio 
   -rwxr--r--   1 root     root        23448 Jul 16 17:53 lib/modules/2.6.32-573.8.1.el6.x86_64/kernel/drivers/block/ virtio_blk.ko  
   -rwxr--r--   1 root     root        50704 Jul 16 17:53 lib/modules/2.6.32-573.8.1.el6.x86_64/kernel/drivers/net/ virtio_net.ko  
   -rwxr--r--   1 root     root        28424 Jul 16 17:53 lib/modules/2.6.32-573.8.1.el6.x86_64/kernel/drivers/scsi/ virtio_scsi.ko  
   drwxr-xr-x   2 root     root            0 Jul 16 17:53 lib/modules/2.6.32-573.8.1.el6.x86_64/kernel/drivers/ virtio  
   -rwxr--r--   1 root     root        14544 Jul 16 17:53 lib/modules/2.6.32-573.8.1.el6.x86_64/kernel/drivers/virtio/ virtio.ko  
   -rwxr--r--   1 root     root        21040 Jul 16 17:53 lib/modules/2.6.32-573.8.1.el6.x86_64/kernel/drivers/virtio/ virtio_pci.ko  
   -rwxr--r--   1 root     root        18016 Jul 16 17:53 lib/modules/2.6.32-573.8.1.el6.x86_64/kernel/drivers/virtio/ virtio_ring.ko 
   
   

   Note

   If you add built-in drivers to the initrd or initramfs file, the ECS will not be affected but such drivers cannot be shown by running the lsinitrd command. You can run the following commands to check whether there are built-in drivers in the kernel:

    cat   /boot/config-`uname -r`   |   grep   CONFIG_VIRTIO   |   grep   y 
    cat   /boot/config-`uname -r`   |   grep   CONFIG_XEN   |   grep   y 
   
   

1. Run the following command to open the modules file:

    vi   /etc/initramfs-tools/modules 
   
   

2. Press i to enter editing mode and add Xen PV and VirtIO drivers to the /etc/initramfs-tools/modules file (the format varies depending on the OS).

   [root@CTU10000xxxxx ~]#vi /etc/initramfs-tools/modules 
   ......
   # Examples: 
   # 
   # raid1 
   # sd_mOd 
    xen-blkfront 
    xen-netfront 
    virtio_blk 
    virtio_scsi 
    virtio_net 
    virtio_pci 
    virtio_ring 
    virtio 
   
   

3. Press Esc, enter :wq, and press Enter. The system saves the change and exits the /etc/initramfs-tools/modules file.
4. Run the following command to regenerate initrd:

    update-initramfs   -u 
   
   

5. Run the following commands to check whether native Xen and KVM drivers have been installed:

    lsinitramfs   /boot/initrd.img-`uname   -r`   |grep   xen 
    lsinitramfs   /boot/initrd.img-`uname   -r`   |grep   virtio 
   
   

   [root@ CTU10000xxxxx home]# lsinitramfs /boot/initrd.img-`uname -r` |grep xen 
   lib/modules/3.5.0-23-generic/kernel/drivers/net/ethernet/qlogic/ netxen  
   lib/modules/3.5.0-23-generic/kernel/drivers/net/ethernet/qlogic/netxen/ netxen_nic.ko  
   lib/modules/3.5.0-23-generic/kernel/drivers/net/ xen-netback  
   lib/modules/3.5.0-23-generic/kernel/drivers/net/xen-netback/ xen-netback.ko  
   lib/modules/3.5.0-23-generic/kernel/drivers/block/ xen-blkback  
   lib/modules/3.5.0-23-generic/kernel/drivers/block/xen-blkback/ xen-blkback.ko  
    
   [root@ CTU10000xxxxx home]# lsinitramfs /boot/initrd.img-`uname -r` |grep virtio 
   lib/modules/3.5.0-23-generic/kernel/drivers/scsi/ virtio_scsi.ko 
   
   

   Note

   If you add built-in drivers to the initrd or initramfs file by mistake, the ECS will not be affected. The drivers cannot be found by running the lsinitrd command. You can run the following commands to check whether there are built-in drivers in the kernel:

   [root@ CTU10000xxxxx home] #   cat   /boot/config-`uname   -r`   |   grep   CONFIG_VIRTIO   |   grep   y 
   CONFIG_VIRTIO_BLK=y
   CONFIG_VIRTIO_NET=y
   CONFIG_VIRTIO=y
   CONFIG_VIRTIO_RING=y
   CONFIG_VIRTIO_PCI=y
   CONFIG_VIRTIO_MMIO_CMDLINE_DEVICES=y
   [root@ CTU10000xxxxx home] #   cat   /boot/config-`uname   -r`   |   grep   CONFIG_XEN   |   grep   y 
   CONFIG_XEN_BLKDEV_FRONTEND=y
   CONFIG_XEN_NETDEV_FRONTEND=y
   
   

If the OS version is earlier than SUSE 12 SP1 or openSUSE 13, modify the /etc/sysconfig/kernel file.

 rpm   -qa   |grep   xen-kmp 

xen-kmp-default-4.2.2_04_3.0.76_0.11-0.7.5

1. Run the following command to open the /etc/sysconfig/kernel file:

    vi /etc/sysconfig/kernel 
   
   

2. Add Xen PV and VirtIO drivers to INITRD_MODULES="" (the format varies depending on the OS).

   SIA10000xxxxx:~ # vi /etc/sysconfig/kernel 
   # (like drivers for scsi-controllers, for lvm or reiserfs)
   #
    INITRD_MODULES="ata_piix   ata_generic   xen_vnif   xen_vbd   xen_platform_pci   virtio_blk   virtio_scsi   virtio_net   virtio_pci   virtio_ring   virtio" 
   
   

3. Run the mkinitrd command to regenerate initrd.
   Note

   If the virtual file system is not the default initramfs or initrd, run dracut -f <actual-initramfs-or-initrd-filename>. The actual initramfs or initrd file name can be obtained from the menu.lst or grub.cfg file (/boot/grub/menu.lst, /boot/grub/grub.cfg, or /boot/grub2/grub.cfg).

   The following is an example initrd file of SUSE 11 SP4:

   default 0
   timeout 10
   gfxmenu (hd0,0)/boot/message
   title sles11sp4_001_[_VMX_]
   root (hd0,0)
   kernel /boot/linux.vmx vga=0x314 splash=silent console=ttyS0,115200n8 console=tty0 net.ifnames=0 NON_PERSISTENT_DEVICE_NAMES=1 showopts
   initrd  /boot/initrd.vmx 
   title Failsafe_sles11sp4_001_[_VMX_]
   root (hd0,0)
   kernel /boot/linux.vmx vga=0x314 splash=silent ide=nodma apm=off noresume edd=off powersaved=off nohz=off highres=off processor.max+cstate=1 nomodeset x11failsafe console=ttyS0,115200n8 console=tty0 net.ifnames=0 NON_PERSISTENT_DEVICE_NAMES=1 showopts
   initrd /boot/initrd.vmx
   
   

   /boot/initrd.vmx in the initrd line is the initrd file actually used. So, the command used to regenerate initrd is dracut -f /boot/initrd.vmx. If /boot is missing from the initrd file path, you need to add it when you run the dracut -f command. For example, if the file path is /initramfs-xxx, the command should be dracut -f /boot/initramfs-xxx.

4. Run the following commands to check whether Xen PVOPS and KVM VirtIO drivers have been installed:

   lsinitrd /boot/initrd-`uname -r` | grep xen

   lsinitrd /boot/initrd-`uname -r` | grep virtio

   SIA10000xxxxx:~ # lsinitrd /boot/initrd-`uname -r` | grep xen
   -rwxr--r-- 1 root root 42400 Jun 22 2012 lib/modules/2.6.32-279.el6.x86_64/kernel/drivers/block/ xen-blkfront.ko 
   -rwxr--r-- 1 root root 44200 Jun 22 2012 lib/modules/2.6.32-279.el6.x86_64/kernel/drivers/net/ xen-netfront.ko 
   
   SIA10000xxxxx:~ # lsinitrd /boot/initrd-`uname -r` | grep virtio
   -rwxr--r-- 1 root root 19248 Jun 22 2012 lib/modules/2.6.32-279.el6.x86_64/kernel/drivers/scsi/ virtio_scsi.ko 
   -rwxr--r-- 1 root root 23856 Jun 22 2012 lib/modules/2.6.32-279.el6.x86_64/kernel/drivers/block/ virtio_blk.ko 
   drwxr-xr-x 2 root root 0 Jul 12 14:53 lib/modules/2.6.32-279.el6.x86_64/kernel/drivers/ virtio 
   -rwxr--r-- 1 root root 15848 Jun 22 2012 lib/modules/2.6.32-279.el6.x86_64/kernel/drivers/virtio/ virtio_ring.ko 
   -rwxr--r-- 1 root root 20008 Jun 22 2012 lib/modules/2.6.32-279.el6.x86_64/kernel/drivers/virtio/ virtio_pci.ko 
   -rwxr--r-- 1 root root 12272 Jun 22 2012 lib/modules/2.6.32-279.el6.x86_64/kernel/drivers/virtio/ virtio.ko 
   -rwxr--r-- 1 root root 38208 Jun 22 2012 lib/modules/2.6.32-279.el6.x86_64/kernel/drivers/net/ virtio_net.ko 
   
   

5. Restart the ECS.
6. Modify the /boot/grub/menu.lst file to add xen_platform_pci.dev_unplug=all and change the root settings.

   Before the modification:

   ###Don't change this comment -YaST2 identifier: Original name: linux###
   title SUSE Linux Enterprise Server 11SP4 - 3.0.76-0.11 (default) 
   root (hd0,0) 
   kernel /boot/vmlinuz-3.0.76-0.11-default  root=UUID=4eb40294-4c6f-4384-bbb6-b8795bbb1130  splash=silentcrashkernel=256M-:128M showopts vga=0x314
   initrd /boot/initrd-3.0.76-0.11-default
   
   

   After the modification:

   ###Don't change this comment -YaST2 identifier: Original name: linux###
   title SUSE Linux Enterprise Server 11SP4 - 3.0.76-0.11 (default) 
   root (hd0,0) 
   kernel /boot/vmlinuz-3.0.76-0.11-default  root=UUID=4eb40294-4c6f-4384-bbb6-b8795bbb1130  splash=silentcrashkernel=256M-:128M showopts vga=0x314  xen_platform_pci.dev_unplug=all  
   initrd /boot/initrd-3.0.76-0.11-default
   
   

   Note

   • Ensure that the root partition is in UUID format.
   • xen_platform_pci.dev_unplug=all is used to shield QEMU devices.
   • For SUSE 11 SP1 64bit to SUSE 11 SP4 64bit, add xen_platform_pci.dev_unplug=all to the menu.lst file. For SUSE 12 or later, QEMU device shield is enabled by default, and you do not need to configure it.
7. Run the following commands to check whether Xen drivers exist in initrd:

   lsinitrd /boot/initrd-`uname -r` | grep xen

   lsinitrd /boot/initrd-`uname -r` | grep virtio

   SIA10000xxxxx:~ # lsinitrd /boot/initrd-`uname -r` | grep xen
   -rwxr--r-- 1 root root 42400 Jun 22 2012 lib/modules/2.6.32-279.el6.x86_64/kernel/drivers/block/ xen-blkfront.ko 
   -rwxr--r-- 1 root root 44200 Jun 22 2012 lib/modules/2.6.32-279.el6.x86_64/kernel/drivers/net/ xen-netfront.ko 
   
   SIA10000xxxxx:~ # lsinitrd /boot/initrd-`uname -r` | grep virtio
   -rwxr--r-- 1 root root 19248 Jun 22 2012 lib/modules/2.6.32-279.el6.x86_64/kernel/drivers/scsi/ virtio_scsi.ko 
   -rwxr--r-- 1 root root 23856 Jun 22 2012 lib/modules/2.6.32-279.el6.x86_64/kernel/drivers/block/ virtio_blk.ko 
   drwxr-xr-x 2 root root 0 Jul 12 14:53 lib/modules/2.6.32-279.el6.x86_64/kernel/drivers/ virtio 
   -rwxr--r-- 1 root root 15848 Jun 22 2012 lib/modules/2.6.32-279.el6.x86_64/kernel/drivers/virtio/ virtio_ring.ko 
   -rwxr--r-- 1 root root 20008 Jun 22 2012 lib/modules/2.6.32-279.el6.x86_64/kernel/drivers/virtio/ virtio_pci.ko 
   -rwxr--r-- 1 root root 12272 Jun 22 2012 lib/modules/2.6.32-279.el6.x86_64/kernel/drivers/virtio/ virtio.ko 
   -rwxr--r-- 1 root root 38208 Jun 22 2012 lib/modules/2.6.32-279.el6.x86_64/kernel/drivers/net/ virtio_net.ko 
   
   

   Note

   If you add built-in drivers to the initrd or initramfs file by mistake, the ECS will not be affected. The drivers cannot be found by running the lsinitrd command. You can run the following commands to check whether there are built-in drivers in the kernel:

    cat   /boot/config-`uname   -r`   |   grep   CONFIG_VIRTIO   |   grep   y 
    cat   /boot/config-`uname   -r`   |   grep   CONFIG_XEN   |   grep   y 
   
   

If the OS version is SUSE 12 SP1, modify the /etc/dracut.conf file and add Xen PV and VirtIO drivers.

1. Run the following command to open the /etc/dracut.conf file:

    vi   /etc/dracut.conf 
   
   

2. Press i to enter insert mode and add Xen PV and VirtIO drivers to add-drivers (the format varies depending on the OS).

   [root@CTU10000xxxxx ~]# vi /etc/dracut.conf 
   # additional kernel modules to the default
   add_drivers+= "ata_piix   ata_generic   xen_vnif   xen_vbd   xen_platform_pci   virtio_blk   virtio_scsi   virtio_net   virtio_pci   virtio_ring   virtio" 
   
   

3. Press Esc, enter :wq, and press Enter. The system saves the change and exits the /etc/dracut.conf file.
4. Run the following command to regenerate initrd:

    dracut -f /boot/initramfs- filename
   
   

   If the virtual file system is not the default initramfs, run the dracut -f <actual-initramfs-or-initrd-filename> command. The actual initramfs or initrd file name can be obtained from the grub.cfg file, which can be /boot/grub/grub.cfg, /boot/grub2/grub.cfg, or /boot/grub/grub.conf depending on the OS.

5. Check whether native Xen and KVM drivers have been installed. If the virtual file system is initramfs, run the following commands:

    lsinitrd   /boot/initramfs-`uname   -r`.img   |   grep   xen 
    lsinitrd   /boot/initramfs-`uname   -r`.img   |   grep   virtio 
   
   

   If the virtual file system is initrd, run the following commands:

    lsinitrd   /boot/initrd-`uname   -r`   |   grep   xen 
    lsinitrd   /boot/initrd-`uname   -r`   |   grep   virtio 
   
   

If the OS version is later than SUSE 12 SP1 or openSUSE 13, modify the /etc/dracut.conf file and add Xen PV and VirtIO drivers.

The following uses SUSE Linux Enterprise Server 12 SP2 (x86_64) as an example:

1. Run the following command to open the /etc/dracut.conf file:

    vi   /etc/dracut.conf 
   
   

2. Press i to enter insert mode and add Xen PV and VirtIO drivers to add_drivers (the format varies depending on the OS).

   [root@CTU10000xxxxx ~]# vi /etc/dracut.conf 
   # additional kernel modules to the default
    add_drivers+="  ata_piix   ata_generic   xen-blkfront   xen-netfront   virtio_blk   virtio_scsi   virtio_net   virtio_pci   virtio_ring   virtio" 
   
   

3. Press Esc, enter :wq, and press Enter. The system saves the change and exits the /etc/dracut.conf file.
4. Run the following command to regenerate initrd:

    dracut -f /boot/initramfs- filename
   
   

   If the virtual file system is not the default initramfs, run the dracut -f <actual-initramfs-or-initrd-filename> command. The actual initramfs or initrd file name can be obtained from the grub.cfg file, which can be /boot/grub/grub.cfg, /boot/grub2/grub.cfg, or /boot/grub/grub.conf depending on the OS.

5. Check whether native Xen and KVM drivers have been installed. If the virtual file system is initramfs, run the following commands:

    lsinitrd   /boot/initramfs-`uname   -r`.img   |   grep   xen 
    lsinitrd   /boot/initramfs-`uname   -r`.img   |   grep   virtio 
   
   

   If the virtual file system is initrd, run the following commands:

    lsinitrd   /boot/initrd-`uname   -r`   |   grep   xen 
    lsinitrd   /boot/initrd-`uname   -r`   |   grep   virtio 
   
   

   Assume that the virtual file system is initrd. The command output will be:

   sluo-ecs-30dc:~ # lsinitrd /boot/initrd-`uname -r` | grep xen
   -rw-r--r-- 1 root root 69575 Oct 26 2016 lib/modules/4.4.21-69-default/kernel/drivers/block/ xen-blkfront.ko 
   -rw-r--r-- 1 root root 53415 Oct 26 2016 lib/modules/4.4.21-69-default/kernel/drivers/net/ xen-netfront.ko 
   drwxr-xr-x 2 root root 0 Sep 28 10:21 lib/modules/4.4.21-69-default/updates/pvdriver/ xen-hcall 
   -rwxr-xr-x 1 root root 8320 Sep 28 10:21 lib/modules/4.4.21-69-default/updates/pvdriver/xen-hcall/ xen-hcall.ko 
   
   sluo-ecs-30dc:~ # lsinitrd /boot/initrd-`uname -r` | grep virtio
   -rw-r--r-- 1 root root 29335 Oct 26 2016 lib/modules/4.4.21-69-default/kernel/drivers/block/ virtio_blk.ko 
   -rw-r--r-- 1 root root 57007 Oct 26 2016 lib/modules/4.4.21-69-default/kernel/drivers/net/ virtio_net.ko 
   -rw-r--r-- 1 root root 32415 Oct 26 2016 lib/modules/4.4.21-69-default/kernel/drivers/scsi/ virtio_scsi.ko 
   drwxr-xr-x 2 root root 0 Sep 28 10:21 lib/modules/4.4.21-69-default/kernel/drivers/virtio
   -rw-r--r-- 1 root root 19623 Oct 26 2016 lib/modules/4.4.21-69-default/kernel/drivers/virtio/ virtio.ko 
   -rw-r--r-- 1 root root 38943 Oct 26 2016 lib/modules/4.4.21-69-default/kernel/drivers/virtio/ virtio_pci.ko 
   -rw-r--r-- 1 root root 24431 Oct 26 2016 lib/modules/4.4.21-69-default/kernel/drivers/virtio/ virtio_ring.ko 
   
   

   Note

   If you add built-in drivers to the initrd or initramfs file by mistake, the ECS will not be affected. The drivers cannot be found by running the lsinitrd command. You can run the following commands to check whether there are built-in drivers in the kernel:

    cat   /boot/config-`uname   -r`   |   grep   CONFIG_VIRTIO   |   grep   y 
    cat   /boot/config-`uname   -r`   |   grep   CONFIG_XEN   |   grep   y 
   
   

Delete log files, historical records, and other data.

1. Delete unnecessary key files.

    echo   >  /$path/$to/$root /.ssh/authorized_keys 
   Example:  echo > /root/.ssh/authorized_keys 
    echo   >  /$path/$to/$none-root /.ssh/authorized_keys 
   Example:  echo > /home/linux/.ssh/authorized_keys 
   
   

2. Delete log files from the /var/log directory.

    rm   -rf   /var/log/* 
   
   

   Note

   Before deleting log files, back up log directories and log files required by application startup. For example, if the default Nginx log directory /var/log/nginx is deleted, Nginx may fail to be started.

3. Delete historical records.

    echo   >   /root/.bash_history 
    history   -c