Cisco CSR 1000V Series Cloud Services Router Software Configuration Guide
Installing the Cisco CSR 1000V in KVM Environments
Downloads: This chapterpdf (PDF - 281.0 KB) The complete bookPDF (PDF - 3.63 MB) | Feedback

Table of Contents

Installing the Cisco CSR 1000V in KVM Environments

Kernel Virtual Machine Support Information

KVM Support on OpenStack

Installation Requirements for KVM

Manually Creating the Cisco CSR 1000V VM Using the.iso File (KVM)

Creating the Cisco CSR 1000V KVM Instance on OpenStack Using the.qcow2 File

Creating the Instance Using the KVM Command

Creating the Instance Using the OpenStack Command Line Tool

Creating the Instance Using the OpenStack Dashboard

Increasing Performance on KVM Configurations

Notes and Troubleshooting — KVM Environments

Cloning the VM

Kernel Virtual Machine Support Information

Red Hat Enterprise Linux (RHEL), an enterprise virtualization product produced by Red Hat based on the Kernel-based Virtual Machine (KVM), is an open source, full virtualization solution for Linux on x86 hardware containing virtualization extensions. It consists of a loadable kernel module, kvm.ko that provides the core virtualization infrastructure and a processor-specific module, kvm-intel.ko or kvm-amd.ko.

The Cisco CSR 1000V also supports Red Hat Enterprise Virtualization, Red Hat’s commercially packaged virtualization platform. Beginning with Cisco IOS XE Release 3.11S, Ubuntu is also supported for KVM environments. For more information on the KVM products and versions supported, see the next section.

The Cisco CSR 1000V installation on KVM requires the manual creation of a VM and installation using the.iso file. Deploying the OVA template into a KVM environment is not supported.

The Cisco CSR 1000V supports the Virtio vNIC type on the KVM implementation. KVM supports a maximum of 26 vNICs.

KVM Support on OpenStack

Beginning with Cisco IOS XE 3.12S, the Cisco CSR 1000V supports installation of a KVM in the OpenStack environment. OpenStack support requires the.qcow2 installation file available on the Cisco.com download page. For more information, see the “Creating the Cisco CSR 1000V KVM Instance on OpenStack Using the.qcow2 File” section.

Installation Requirements for KVM

Table 6-1 lists the installation requirements for KVM environments. For installation procedures, see the “Manually Creating the Cisco CSR 1000V VM Using the.iso File (KVM)” section.

Table 6-1 Installation Requirements for KVM Environments

KVM Requirements
Cisco IOS XE Release 3.10S
Cisco IOS XE Release 3.11S
Cisco IOS XE Release 3.12S and 3.13S
Cisco IOS XE Release 3.14S
Cisco IOS XE Release 3.15S, 3.16S

KVM versions supported

  • Linux KVM based on Red Hat Enterprise Linux 6.31
  • Red Hat Enterprise Virtualization 3.1
  • Linux KVM based on Red Hat Enterprise Linux 6.31
  • Red Hat Enterprise Virtualization 3.1
  • Ubuntu 12.04.03 LTS Server 64 Bits2
  • Linux KVM based on Red Hat Enterprise Linux 6.31
  • Ubuntu 12.04.04 LTS Server 64 Bits 2
  • Linux KVM based on Red Hat Enterprise Linux 6.31
  • Ubuntu 14.04 LTS Server 64 Bits 2
  • Linux KVM based on Red Hat Enterprise Linux 6.63
  • Ubuntu 14.04 LTS Server 64 Bits 2

Supported vCPU configurations4

4 vCPUs: requires 4 GB RAM minimum allocation

  • 1 vCPU:
    requires minimum 2.5 GB RAM allocation
  • 2 vCPUs: requires minimum 2.5 GB RAM allocation
  • 4 vCPUs: requires minimum 4 GB RAM allocation
  • 1 vCPU:
    requires minimum 2.5 GB RAM allocation
  • 2 vCPUs: requires minimum 2.5 GB RAM allocation
  • 4 vCPUs: requires minimum 4 GB RAM allocation
  • 1 vCPU:
    requires minimum 4 GB RAM allocation
  • 2 vCPUs: requires minimum 4 GB RAM allocation
  • 4 vCPUs: requires minimum 4 GB RAM allocation
  • 1 vCPU:
    requires minimum 4 GB RAM allocation
  • 2 vCPUs: requires minimum 4 GB RAM allocation
  • 4 vCPUs: requires minimum 4 GB RAM allocation

Virtual CPU cores required

1

1

1

1

1

Virtual hard disk size

8 GB minimum

8 GB minimum

8 GB minimum5

8 GB minimum6

8 GB minimum7

Supported vNICs

Virtio

Virtio

Virtio

Virtio

Virtio

Minimum number of vNICs required

3

3

3

3

3

Maximum number of vNICs supported per VM instance

26

26

26

26

26

Virtual CD/DVD drive installed

Required

Required

Required

Required

Required

1.Requires Kernel version 2.6.3.2 and QEMU 0.12.1.2.

2.Requires QEMU-x86_64 version 1.0 (qemu-kvm-1.0), Copyright (c) 2003-2008 Fabrice Bellard

3.Requires Kernel version 2.6.32-504 and QEMU 0.12.1.2.

4.The required vCPU configuration depends on the throughput license and technology package installed. See the data sheet for your release for more information.

5.Applies only to creating the VM using the.iso file. If using the.qcow2 file to install in an OpenStack environment, the hard disk size must be set to 0.

6.Applies only to creating the VM using the.iso file. If using the.qcow2 file to install in an OpenStack environment, the hard disk size must be set to 0.

7.Applies only to creating the VM using the.iso file. If using the.qcow2 file to install in an OpenStack environment, the hard disk size must be set to 0.

Manually Creating the Cisco CSR 1000V VM Using the.iso File (KVM)

Although the following procedure provides a general guideline for how to manually create the VM for the Cisco CSR 1000V, the exact steps that you need to perform may vary depending on the characteristics of your KVM environment and setup. For more information, see the Red Hat Linux documentation.

See Table 6-1 for the requirements to install the Cisco CSR 1000V on a VM in a KVM environment.


Note The Cisco CSR 1000V does not support deploying the OVA file in KVM environments.


The following steps are performed using the KVM console on your server.


Step 1 Download the.iso file from the Cisco CSR 1000V software installation image package and copy it onto a local or network device.

Step 2 Access the KVM console.

Step 3 Choose Application > System Tools.

Step 4 Open the VM Manager. Select the New VM screen to create a new VM.

Step 5 Enter the name of the VM.

Step 6 Select the method of installation based on where you copied the Cisco CSR 1000V.iso file:

  • Local install media (ISO image or CD-ROM)

Note If you plan to install from the CD-ROM, you must also map the.iso file image to the virtual CD-ROM.


  • Network install
  • Network boot (PXE)

Click Forward.

Step 7 On the next screen, locate the install media by selecting from the following:

  • Use CD-ROM or DVD.

Enter the CD-ROM name that the.iso file was mapped to.

  • Use ISO image

Browse to the.iso file image location. Select the image and click Open.

Step 8 Use the OS Type and Version for the.iso file that is displayed.

Click Forward.

Step 9 Enter the memory and CPU settings.

See Table 6-1 for the memory requirements and supported number of CPUs for your release.

Click Forward.

Step 10 On the next screen, select the checkbox to enable storage for the VM.

Step 11 Choose the method for storing the VM:

  • Create a disk image on the computer’s hard drive. Select the memory allocation. For the required memory allocation in your software version, see Table 6-1.
  • Select the managed or other existing storage by browsing to the storage location.

Click Forward. The Ready to Begin Installation screen for the selected VM displays.

Step 12 Click Advanced options.

Step 13 On the Overview screen, add a description to the VM.


Note While this step is optional, adding a description is recommended if you will create multiple VMs on your host.


Click Apply.

Step 14 Verify that the processor, memory, and boot option settings are correct.

Step 15 Under Processor, do the following:

  • Verify the CPU configuration and enter the values for the current allocation and maximum allocation. The following is the required CPU configuration:

Sockets = 4

Cores = 1

Threads = 1

  • Select the Configuration option, and then select the Model from the drop-down menu. The Nehalem model is required for the Cisco CSR 1000V.

Note Select the “Nehalem” option to obtain the minimum set of features supported, although newer models can be selected. We recommend to choose the “Copy host CPU configuration” option to ensure that more advanced features of newer processors are used.


Click Apply.

Step 16 Under Boot Options, you can select the boot device order, to determine which device to boot from first, and which devices to boot from subsequently.

Step 17 Under NIC, configure the first vNIC for the VM.

Step 18 For the Device Model, select Virtio.

This is the only vNIC type supported on the Cisco CSR 1000V for the KVM-based hypervisor.


Note (Cisco IOS XE Release 3.10S and earlier) This first vNIC created is mapped to the Gigabit Ethernet 0 management interface on the Cisco CSR 1000V.


Step 19 To create additional vNICs before installing the VM, click the Add Hardware button. All vNICs must be the Virtio Disk device type.


Note You can add more vNICs after the VM is installed and the Cisco CSR 1000V has booted. You do not need to power down the VM or the router to add vNICs. See Table 6-1 for the number of vNICs supported on the hypervisor for your release.



Note You can also create a serial port interface before creating the VM if you want to access the Cisco CSR 1000V using a serial console. See the “Booting the Cisco CSR 1000V and Accessing the Console” section. You must select the option to use the serial console when booting the Cisco CSR 1000V.


Step 20 Click the Begin Installation button to create the VM.

The VM is created. Once the VM is created, the Cisco CSR 1000V begins the first-time boot process. See the “Booting the Cisco CSR 1000V and Accessing the Console” section to continue the bootup.


 

Creating the Cisco CSR 1000V KVM Instance on OpenStack Using the.qcow2 File

Creating the Instance Using the KVM Command

Although the following procedure provides a general guideline for how to create the Cisco CSR 1000V tenant instance, the exact steps that you need to perform may vary depending on the characteristics of your KVM environment and setup. For more information, see the OpenStack documentation.

The following steps are performed using the Nova (OpenStack Compute) console on your server.


Note To configure the KVM to run with config-drive, you must use the procedure described in the “Creating the Instance Using the OpenStack Command Line Tool ” section.



Step 1 Download the.qcow2 file from the Cisco CSR 1000V software installation image package and copy it onto a local or network device.

Step 2 In the Nova console, create the Cisco CSR 1000V KVM instance where you specify the parameters for the instance, as shown in the following example:

/usr/bin/kvm -S -M pc-1.0 -enable -kvm -m 2560 -smp 1,sockets=4,cores=1,threads=1 -nographic -nodefconfig -nodefaults -no-shutdown -boot order=c,menu=on -device lsi,id=scsi0,bus=pci.0,addr=0x6 -drive file=csr.qcow2,if=none,id=drive-ide0-0-0,format=qcow2 -serial telnet:127.0.0.1:3548,server,nowait

See Table 6-1 for the installation requirements. The disk size should be set to 0 for the Cisco CSR 1000V to boot.

Make sure to specify the installation file name, and that the format is set to “qcow2”. You can configure the vNICs when you enter the command above before booting the Cisco CSR 1000V, or you can configure the vNICs later. For information about other options for configuring the KVM instance, see the KVM documentation.

Step 3 When you have configured the parameters for the KVM instance, you can boot the instance using the boot command. Use the -serial option to set the serial console access.

See the “Booting the Cisco CSR 1000V and Accessing the Console” section.


 

Creating the Instance Using the OpenStack Command Line Tool

Although the following procedure provides a general guideline for how to create the Cisco CSR 1000V tenant instance, the exact steps that you need to perform may vary depending on the characteristics of your KVM environment and setup. For more information, see the OpenStack documentation. See Table 6-1 for the requirements to install the Cisco CSR 1000V on a VM in a KVM environment.

The following steps are performed using the Nova (OpenStack Compute) console on your server.


Step 1 Download the.qcow2 file from the Cisco CSR 1000V software installation image package and copy it onto a local or network device.

Step 2 Create the Nova flavor using the following command syntax:

nova flavor-create < flavor_name > < flavor_id > < ram size MB > < disk size GB > < num_ vCPUs >

See Table 6-1 for the installation requirements. The disk size should be set to 0 for the Cisco CSR 1000V to boot. The following command example creates a KVM instance with 4096 MB RAM, a disk size of 0 and 2 vCPUs configured:

nova flavor-create csr_flavor 6 4096 0 2

Step 3 Enter the nova flavor-list command to verify that the nova flavor created the previous step is available.

Step 4 Using the glance command, create the OpenStack image using the following syntax:

glance image-create -- name < image_name > -- disk-format qcow2 --container-format bare --file < Location-of-img-file >

The following example creates an OpenStack image using the Cisco CSR 1000V installation file:

glance image-create --namecsr_image --disk-format qcow2 --container-format bare --file /opt/stack/csr/files/images/csr1000v-universalk9.03.12.00.S.154-2.S-std.qcow2
 

Step 5 Using the nova boot command, create the instance and boot using the following syntax:

nova boot < instance_name > -- image < image_id > -- flavor < flavor_id > -- nic net-id= < uuid > --config-drive= < true / false > --file < configuration_file_name >

The --config-drive option can be used to specify that the configuration is loaded on the Cisco CSR 1000V when it comes up. Set the --config-drive option to “true” and specify the name of the configuration file in which you enter the router configuration to be booted. There are two possible formats for the configuration file:

  • “ovf-env.xml” (OVF format)
  • “iosxe_config.txt”

Note These file names are hard-coded and required for the config-drive settings to boot.


Prior to Cisco IOS XE 3.16S, one could specify only one of the two configuration files in the nova boot command. Beginning with Cisco IOS XE 3.16S, one can specify both configuration files in the nova boot command line—for example:

nova boot csr-vm-316 --image csr-316 --flavor csr.2vcpu.4gb --nic port-id=6773be11-7b95-48cd-b372-fb8a3cae2b50 --config-drive=true --file ovf-env.xml=/home/stack/conf_files/ut/ovf-env.xml --file iosxe_config.txt=/home/stack/conf_files/ut/iosxe_config.txt

 

Table 6-2 Bootstrap Properties

Property
Description

domain-name

Domain name of the router.

enable-scp-server

Enables the IOS SCP feature.

enable-ssh-server

Enables remote login using SSH and disables remote login via Telnet. Requires that the login username and password are set.

hostname

Hostname of the router.

license

Configures the license technology level that is available when the Cisco CSR 1000V boots.

login-password

Login password for the router.

login-username

Login username for the router.

mgmt-interface

Designates the management interface for the Cisco CSR 1000V. The format must be GigabitEthernetx or GigabitEthernetx.xxx.

Note Beginning with Cisco IOS XE 3.11S, the GigabitEthernet0 interface is no longer supported.

mgmt-ipv4-addr

Management gateway address/mask in IPv4 format for the GigabitEthernet0 management interface.

mgmt-ipv4-gateway

IPv4 management default gateway address. If using DHCP, enter “dhcp” in the field.

mgmt-ipv4-network

Configures the IPv4 Network (such as “192.168.2.0/24” or “192.168.2.0 255.255.255.0”) that the management gateway should route to. If not specified, the default route (0.0.0.0/0) is used.

mgmt-vlan

Configures the dot1Q VLAN interface. Requires the management interface to be configured using the GigabitEthernetx.xxx format.

pnsc-agent-local-port

(Optional) Configures the Cisco Prime Network Services Controller service agent SSL port on the local Cisco CSR 1000V to receive policies from the service manager.

This setting is used if you plan to remotely manage the Cisco CSR 1000V using the Cisco Prime Network Services Controller.

pnsc-ipv4-addr

Configures the IP address of the Cisco Prime Network Services Controller.

This setting is used if you plan to remotely manage the Cisco CSR 1000V using the Cisco Prime Network Services Controller.

pnsc-shared-secret-key

Configures the Cisco Prime Network Services Controller shared secret key for the Cisco Prime Network Services Controller agent to set the SSL certificate from the controller.

This setting is used if you plan to remotely manage the Cisco CSR 1000V using the Cisco Prime Network Services Controller.

privilege-password

Configures the password for privileged (enable) access.

remote-mgmt-ipv4-addr

(Optional) Configures the IP address used for remote management of the Cisco CSR 1000V by the REST API or by the Cisco Prime Network Services Controller. The address must be in the same subnet as the management interface address.

Note Beginning with Cisco IOS XE 3.13S, this option is not used if configuring the shared management interface to support REST API.

ios-config

Enables execution of a Cisco IOS command.

To execute multiple commands, use multiple instances of ios-config, with a number appended to each instance—for example, ios-config-1, ios-config-2. The commands are executed in numerical order according to the appended number.

Example

ios-config-1="username cisco priv 15 pass ciscoxyz"
ios-config-2="ip scp server enable"
ios-config-3="ip domain lookup"
ios-config-4="ip domain name cisco.com”

Example ovf-env.xml File

<?xml version="1.0" encoding="UTF-8"?>
<Environment
xmlns:oe="http://schemas.dmtf.org/ovf/environment/1">
<PropertySection>
<Property oe:key="com.cisco.csr1000v.license.1" oe:value="security"/>
 
<Property oe:key="com.cisco.csr1000v.config-version.1" oe:value="1.0"/>
<Property oe:key="com.cisco.csr1000v.domain-name.1" oe:value=""/>
<Property oe:key="com.cisco.csr1000v.enable-scp-server.1" oe:value="False"/>
<Property oe:key="com.cisco.csr1000v.enable-ssh-server.1" oe:value="False"/>
<Property oe:key="com.cisco.csr1000v.hostname.1" oe:value="lab"/>
<Property oe:key="com.cisco.csr1000v.license.1" oe:value="ax"/>
<Property oe:key="com.cisco.csr1000v.login-password.1" oe:value=""/>
<Property oe:key="com.cisco.csr1000v.login-username.1" oe:value="lab"/>
<Property oe:key="com.cisco.csr1000v.mgmt-interface.1" oe:value="GigabitEthernet1"/>
<Property oe:key="com.cisco.csr1000v.mgmt-ipv4-addr.1" oe:value="172.25.223.251/25"/>
<Property oe:key="com.cisco.csr1000v.mgmt-ipv4-gateway.1" oe:value="172.25.223.129"/>
<Property oe:key="com.cisco.csr1000v.mgmt-ipv4-network.1" oe:value=""/>
<Property oe:key="com.cisco.csr1000v.mgmt-vlan.1" oe:value=""/>
<Property oe:key="com.cisco.csr1000v.pnsc-agent-local-port.1" oe:value=""/>
<Property oe:key="com.cisco.csr1000v.pnsc-ipv4-addr.1" oe:value=""/>
<Property oe:key="com.cisco.csr1000v.pnsc-shared-secret-key.1" oe:value=""/>
<Property oe:key="com.cisco.csr1000v.privilege-password.1" oe:value=""/>
<Property oe:key="com.cisco.csr1000v.remote-mgmt-ipv4-addr.1" oe:value=""/>
<Property oe:key="com.cisco.csr1000v.ios-config-0001" oe:value="logging buffered 10000"/>
<Property oe:key="com.cisco.csr1000v.ios-config-0002" oe:value="hostname uut-ovf"/>
<Property oe:key="com.cisco.csr1000v.ios-config-0003" oe:value="ip domain-name cisco.com"/>
<Property oe:key="com.cisco.csr1000v.ios-config-0004" oe:value="crypto key generate rsa modulus 1024"/>
<Property oe:key="com.cisco.csr1000v.ios-config-0005" oe:value="interface GigabitEthernet2"/>
<Property oe:key="com.cisco.csr1000v.ios-config-0006" oe:value="ip address 10.0.0.5 255.255.255.0"/>
<Property oe:key="com.cisco.csr1000v.ios-config-0007" oe:value="no shut"/>
<Property oe:key="com.cisco.csr1000v.ios-config-0008" oe:value="exit"/>
<Property oe:key="com.cisco.csr1000v.ios-config-0009" oe:value="ip route 0.0.0.0 0.0.0.0 10.0.0.1"/>
</PropertySection>
</Environment>

Example of iosxe_config.txt File

hostname ultra-ios_cfg
license smart enable
username lab privilege 15 password lab
ip domain-name cisco.com
crypto key generate rsa modulus 1024
 
interface GigabitEthernet1
ip address 10.0.0.5 255.255.255.0
no shut
exit
 
ip route 0.0.0.0 0.0.0.0 10.0.0.1
 
line vty 0 4
login local
exit

Additional Examples

The following example boots the Cisco CSR 1000V image on OpenStack with the “ovf-env.xml” file containing the router configuration:

nova boot csr_instance --image csr_image --flavor 6 --nic net-id=546af738-bc0f-43cf-89f2-1e2c747d1764 --config-drive=true --file ovf-env.xml=/opt/stack/csr/files/ovf-env.xml
 

The following example boots the Cisco CSR 1000V image on OpenStack with the “iosxe_config.txt” file containing the router configuration:

nova boot csr_instance --image csr_image --flavor 6 --nic net-id=546af738-bc0f-43cf-89f2-1e2c747d1764 --config-drive=true --file iosxe_config.txt=/opt/stack/iosxe_config.txt

The Cisco CSR 1000V begins the boot process. See the “Booting the Cisco CSR 1000V and Accessing the Console” section.

After the OpenStack image is created, you can access the instance on your OpenStack dashboard.

Creating the Instance Using the OpenStack Dashboard

Perform the following steps to create the instance using the OpenStack dashboard.


Note To configure the KVM to run with config-drive, you must use the procedure described in the “Creating the Instance Using the OpenStack Command Line Tool ” section.



Step 1 Download the.qcow2 file from the Cisco CSR 1000V software installation image package and copy it onto a local or network device.

Step 2 From the OpenStack dashboard, access the OpenStack console.

Step 3 Login as the admin onto the OpenStack console.

Step 4 Create a new flavor using the Flavor Create tab on the screen, and specify the < flavor_name > < flavor_id > < ram size MB > < disk size GB > < num_ vCPUs >.

See Table 6-1 for the installation requirements. The disk size should be set to 0 for the Cisco CSR 1000V to boot. as in the tables 6-1 and 6-2.

Select the System Panel > Flavors tab. The flavor should show up in the list of flavors displayed on the screen.

Step 5 Create a new image using the Image Create tab on the screen.

Specify the location of the image, the disk format (qcow2) and container-format (raw).

Select the System Panel > Images tab. The image should show up on the list of images shown on the screen.

Step 6 Create a new instance using the Instance Create tab on the screen.

Specify the image, the flavor, and the appropriate network interfaces to be attached to the instance.

Select the System Panel > Instances tab. The instance should show up on the list of instances shown on the screen, and you should be able to access the console by clicking on the instance name.

Step 7 To launch the instance, select the instance and select Launch Instance.

Click the Details tab. Review the instance information to ensure it is correct. When you ready to launch the instance, click the Launch button.

The instance is launched and the Cisco CSR 1000V begins the boot process. See the “Booting the Cisco CSR 1000V and Accessing the Console” section.

Increasing Performance on KVM Configurations

Beginning with Cisco IOS XE Release 3.11S, you can increase the performance for a Cisco CSR 1000V in a KVM environment by changing settings on the KVM host. These settings are independent of the Cisco IOS XE configuration settings on the Cisco CSR 1000V. This option is available in Red Hat Enterprise Linux 6.3 KVM environment running Kernel version 2.6.32 and QEMU version 0.12.1.2.


Note The Cisco CSR 1000V does not support jumbo packets larger than 1518 bytes for KVM on a Virtio interface in Cisco IOS XE Release 3.11S. Packets larger than that are dropped.


You can improve performance on KVM configurations by performing the following:

  • Enabling CPU Pinning

To increase performance for KVM environments, you can use the KVM CPU Affinity option to assign a virtual machine to a specific processor. To use this option, you configure CPU pinning on the KVM host.

In the KVM host environment, verify the host topology to find out how many vCPUs are available for pinning by using the following command:

virsh nodeinfo

Use the following command to verify the available vCPU numbers:

virsh capabilities

Use the following command to pin the virtual CPUs to sets of processor cores:

virsh vcpupin < vmname > < vcpu# > < host core# >

This KVM command must be executed for each vCPU on your Cisco CSR 1000V. The following example pins virtual CPU 1 to host core 3:

virsh vcpupin csr1000v 1 3

The following example shows the KVM commands needed if you have a Cisco CSR 1000V configuration with four vCPUs and the host has eight cores:

virsh vcpupin csr1000v 0 2

virsh vcpupin csr1000v 1 3

virsh vcpupin csr1000v 2 4

virsh vcpupin csr1000v 3 5

The host core number can be any number from 0 to 7. For more information, see the KVM documentation.


Note When configuring CPU pinning, carefully consider the CPU topology of the host server. If using a Cisco CSR 1000V configured with multiple cores, do not configure CPU pinning across multiple sockets.


  • Enabling the vhost-net Driver

To improve performance in KVM environments, we recommend that you enable the LINUX vhost-net driver. Make sure the vhost-net driver is loaded by entering the following command on the KVM host:

modprobe vhost-net

For more information, see the KVM documentation.


Note The vhost-net setting is enabled by default on KVM Ubuntu installations. If using Red Hat Enterprise Linux, you must specify which devices will use the XML definition file.


Notes and Troubleshooting — KVM Environments

Cloning the VM

In a KVM environment, cloning the CSR1000V virtual machine using the virt-manager virtual machine manager creates a CSR1000V virtual machine that may be un-bootable.

The issue is caused by an increase in the size of the cloned image size created by virt-manager, compared with the original CSR1000V VM image. The extra bytes (in the KB range) cause the boot failure.

This problem is described in bug CSCuo56920. (If you have an account on Cisco.com, you can also use the Bug Search tool to find view bugs/caveats. If the defect that you have requested is not displayed, it may be that the defect does not provide a description.)

Workarounds

There are three workarounds:

  • Use the virt-clone command to clone the CSR VM image.
  • For a cloned CSR VM image created by virt-manager, during the bootup, select the GOLDEN image to boot instead of packages.conf.
  • In the “Create a new virtual machine” window, deselect “Allocate entire disk now” before the new CSR1000V VM is created. This ensures that the cloned CSR image will be able to boot up. However, this workaround does not support nested cloning. Use this method only on the first cloned CSR1000V VM image.