Linux. Configuring IBM PowerKVM on Power systems

Transcription

1 Linux Configuring IBM PowerKVM on Power systems

2

3 Linux Configuring IBM PowerKVM on Power systems

4 Note Before using this information and the product it supports, read the information in Notices on page 61. Second Edition (October 2014) Copyright IBM Corporation US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

5 Contents Configuring IBM PowerKVM on Power Systems Overview of installation steps for PowerKVM... 1 Download PowerKVM Burning a DVD from an ISO image using Linux. 2 Setting up a network boot server Connecting to the service processor Connecting using a PC or notebook Connecting using DHCP network Petitboot bootloader Configuring Petitboot Editing Petitboot configuration options Automated network installation The ibm-configure-system utility Kimchi management tool Intelligent Platform Management Interface (IPMI) on PowerKVM Installing IPMI Connecting to your system with IPMI Changing your IPMI password Common IPMI commands Creating guests Creating a guest with Kimchi Setting up a template using Kimchi Creating a guest with the virsh command Creating guests with the virt-install command 13 Common virsh command options PowerKVM storage Common virsh command options - Storage.. 14 Find storage pool sources with virsh Valid storage pools types Storage pool Setting up a storage pool with Kimchi Creating storage pool with virsh Networking on PowerKVM Common virsh command options - Networking 20 Setting up a network connection with Kimchi.. 21 Creating a network bridge with the ibm-configure-system utility Verifying the default virtual network Configuring KVM guests to use bridge Adding guest para-virtualized network devices with libvirt Using vhost-net for high-bandwidth applications 23 Hot-plugging a network connection VLAN segmentation Configuring VLAN segmentation Configuring 802.1q VLANs in Kimchi PowerKVM and Quality of Service Remote management of PowerKVM with libvirt.. 28 Overview of PowerKVM remote management.. 28 Remote management with SSH tunnels Managing PowerKVM guests remotely with the virsh command Displaying the remote PowerKVM VNC console with any VNC client Remote management with SASL authentication and encryption Remote management with TLS Step 1. Creating a CA key and certificate in your PowerKVM host Step 2. Creating the client and server keys and certificates in your PowerKVM host Step 3. Distributing keys and certificates to the PowerKVM host server Step 4. Distributing keys and certificates to clients or management stations Step 5. Editing the libvirtd daemon configuration Step 6. Changing the firewall configuration.. 38 Step 7. Verifying that remote management is working User management KVM guest migration Common virsh command options: Migrate Migrating live with virsh command Migrating a KVM guest offline with migrate option Migrating a KVM guest offline with dumpxml.. 42 The svirt service Overview of the svirt service Creating static svirt labels Verifying svirt labeling by examining the labels 44 Verifying svirt labeling by viewing the domain.xml file Manage PowerKVM resources Common virsh command options - Resources.. 46 Manage processors and memory Simultaneous Multi-Threading (SMT) Enabling micro-threading Processor pinning Over-committing processor and memory resources Configuring huge pages Memory ballooning Enabling Kernel Same-page Merge (KSM).. 51 Enabling PCI passthrough Update PowerKVM Updating PowerKVM with Kimchi Updating PowerKVM with yum Updating PowerKVM with the ibm-update-system utility Upgrade PowerKVM Updating the firmware Upgrading PowerKVM to a new release Monitor and debug information Install and update packages Migrating to IBM PowerKVM from IBM PowerVM 58 Migrating to IBM PowerVM from IBM PowerKVM 59 Copyright IBM Corp iii

6 Notices Privacy policy considerations Trademarks iv Linux: Configuring IBM PowerKVM on Power systems

7 Configuring IBM PowerKVM on Power Systems Use these instructions for installing and configuring PowerKVM on Power Systems. Overview of installation steps for PowerKVM IBM PowerKVM is available on specific Linux-only Power system servers that are built on POWER8 technology. For specific prerequisites and limitations, see PowerKVM concepts. Specific instructions for installing and configuring PowerKVM are available in quick start guides. To download a PDF, see Quick start guides for IBM PowerKVM. Table 1. Overview of installation steps Step Description Step 1: Download IBM PowerKVM Step 2: Connect to your server Step 3: Setting up the service processor Step 4: Powering on your server Step 5: Choose your boot options Step 6: Installing PowerKVM Step 7: Booting PowerKVM after installation Step 8: Use ibm-configuresystem utility to set your root password, network information, and other settings. Step 9: Connecting to Kimchi Download the IBM PowerKVM installer file. See Download PowerKVM. After you download the installer file, make it available to the system by either Burning a DVD from an ISO image using Linux on page 2 or Setting up a network boot server on page 2. Connect to the service processor of your server using either DHCP or by setting up a PC or notebook as a console. Set up your service processor to use OPAL for a hypervisor and create an IPMI password. After setting up the service processor, use IPMI as a console interface to power on your server. The Petitboot bootloader scans your system and finds boot options for you. Select your boot option and press Enter. If you option is not available, configure Petitboot. See Petitboot bootloader on page 6. PowerKVM provides an installation wizard to walk you through the installation process. At the end of the installation process, restart your server. Select PowerKVM as your boot option. If you have not yet added networking information to your server, use the ibm-configure-system utility to set that up. See The ibm-configure-system utility on page 9. Use Kimchi to manage your host server and guests. See Kimchi management tool on page 9. Download PowerKVM If your system is not preconfigured with PowerKVM, you need to download the installer file. PowerKVM installation files are available from the Entitled System Support site at ibm.com/servers/eserver/ess/index.wss. Fixpack files are available from Fix Central at Copyright IBM Corp

8 After you download the file, make it available to your server. To update your current PowerKVM release, see Update PowerKVM on page 55. To upgrade PowerKVM to a new release, see Upgrade PowerKVM on page 56. Burning a DVD from an ISO image using Linux Follow these instructions to burn a DVD from the ISO image using Linux 1. If it is not already installed, install the Linux package dvd+rw-tools. To determine whether the package is installed, enter the following command: rpm -qi dvd+rw-tools 2. Download the installer image for the IBM PowerKVM to your Linux system. You must have a DVD-Recorder drive installed on your system 3. Determine the DVD recorder device ID by running the following command: hwinfo -cdrom grep "Device File" In most cases, the output of this command is similar to this example: Device File: /dev/sr0 (/dev/hdc) 4. Insert a high-quality, blank DVD-R disk into the DVD recorder. Do not use DVD+R, DVD-RW, or DVD-RAM. 5. Run the following command: /usr/bin/growisofs -dvd-compat -Z /dev/hdc=file where file is the name of the file. What to do next You can use a different method to create a DVD from an ISO image. For example, if you have a PC with software that allows the creation of DVD media from an ISO image, then you can use that software to burn a DVD. Regardless of the method you use to create a DVD, use high-quality DVD-R media to ensure the best data transfer. Do not use DVD+R, DVD-RM, or DVD-RAM media Setting up a network boot server Optionally, you can set up a network boot server. About this task In this example setup, a network boot server is loaded with the PowerKVM ISO file and then made available through an HTTP server over a DHCP network for the target Power system to find. Your specific setup might vary from this example. You need a DHCP server on the same subnetwork as your target system and an HTTP server. v DHCP server on the same subnetwork as the target system v HTTP server network available to the target system v PowerKVM ISO image file 1. Upload the PowerKVM ISO file to the HTTP server. For example, to wwwroot/powerkvm. 2. Extract the ISO image file content. For example, to wwwroot/powerkvm/os. The following directories are created in wwwroot/powerkvm/os: LiveOS/ TRANS.TBL etc/ packages/ 2 Linux: Configuring IBM PowerKVM on Power systems

9 ppc/ 3. Create a boot configuration file for the target Power system. For example, to wwwroot/powerkvm/ pxe.conf. Edit it to include the following contents: label IBM PowerKVM Install kernel initrd append selinux=0 rd.dm=0 rd.md=0 root=live: IP/wwwroot/powerkvm/os/LiveOS/squashfs.img repo= IP/wwwroot/powerkvm/os/packages console=hvc0 console=tty0 4. Edit your DHCP server configuration file. This file is typically called /etc/dhcpd.conf. Add the following options that are bold: (...) option conf-file code 209 = text; subnet netmask { option routers ; (...) host your-system{ hardware ethernet system macaddr fixed-address system ip; option host-name "system hostname"; option conf-file " } } 5. Restart your DHCP server. Connecting to the service processor Plan your connection to your server. Connecting using a PC or notebook You can connect to the service processor using a PC or notebook. Before you begin Use this type of connection to configure a local network with a static IP address. 1. If your system belongs in a rack, install your system into that rack. For instructions, see IBM Power Systems Hardware information. Look for instructions specific to your system. 2. Remove the shipping brackets from the power supplies. Ensure that the power supplies are fully seated in the system. 1. Connect the power cables for the server. After the power cables are connected, the firmware starts. Wait for a few minutes for this process to complete. Look for the green power LED on the control panel to start flashing, indicating that it is ready to use, and for the prompt 01 N V=N to appear on the display. Note: You cannot connect to the service processor until this process is complete. 2. Connect an Ethernet cable from the PC or notebook to the Ethernet port labeled HMC1 on the back of the managed system. If HMC1 is occupied, connect an Ethernet cable from the PC or notebook to the Ethernet port labeled HMC2 on the back of the managed system. 3. Set your IP address on your PC or notebook to match the default values on your Power system. Use the table to determine your default values: Configuring IBM PowerKVM on Power Systems 3

10 Table 2. Network configuration information Server connector Subnet mask IP address of service processor IP address on PC or notebook HMC HMC To set your IP address in Linux, follow these steps: a. Log in as root. b. Start a terminal session c. Run the follow command: ifconfig -a. Record these values. d. Type ifconfig ethx xxx.xxx.x.xxx netmask nnn.nnn.nnn.n, where the xxx.xxx.xxx.xxx is the IP address and nnn.nnn.nnn.n is the Subnet mask. Replace ethx with either eth0 or eth1, depending on what your computer is using. To set your IP address in Windows 7, follow these steps: a. Click Start > Control Panel. b. Select Network and Sharing Center. c. Click the network that is displayed in Connections. d. Click Properties. e. If the security dialog box is displayed, click Continue. f. Select Internet Protocol Version 4. g. Click Properties. h. Select Use the following IP address. i. Complete the IP address, Subnet mask, and Default gateway fields by using from the Network configuration information table. j. Click OK > Close > Close 4. Open a web browser and go to where ip_address is the IP address that you set. 5. The first time that you connect to the service processor, enter the default user and password: On a preinstalled system, use this user name and password: v User ID: admin v Password: admin After you log in, you must change the password. Be sure to remember this password! After you change the password, the service processor main menu appears. 6. From the main menu, select System Configuration > Hypervisor Configuration. 7. Select KVM as your Hypervisor Mode and set up a password for IPMI session. 8. To use IPMI, you must configure Network access. From the main menu, select Network Services > Network Configuration. To configure network access, follow these steps: a. From the Network Configuration display, select IPv4 and Continue. b. Select Configure this interface? c. Verify that IPv4 is selected. d. Select Static for the type of IP address. e. Enter a name for the host system. f. Enter an IP address for the system. g. Enter a subnet mask. h. Enter a domain name. i. Enter the IP address for the DNS. 9. After you set the values for the Network configuration, click Continue. 4 Linux: Configuring IBM PowerKVM on Power systems

11 10. Click Save Settings. The network settings are configured for the system. You can remove the Ethernet cable from your PC or notebook and connect it to the network switch. What to do next You are now ready to power on your server! Go to Connecting to your system with IPMI on page 10 for instructions. Connecting using DHCP network If you connect your server to a DHCP network, you can access the service processor through the web interface. Before you begin 1. If your system belongs in a rack, install your system into that rack. For instructions, see IBM Power Systems Hardware information. Look for instructions specific to your system. 2. Remove the shipping brackets from the power supplies. Ensure that the power supplies are fully seated in the system. 1. Before you power on the service processor, connect an Ethernet cable from the eth0 port to a network that has a DHCP server. 2. Connect your power cords to the server and plug the power cords into the power source. Wait a few minutes for the process to complete. Look for the green power LED on the control panel to start flashing, indicating that it is ready to use, and for the prompt "01 N V=N" to appear on the display. 3. If you do not know what IP address your DHCP server that is assigned to the service processor, follow these steps to find it: a. Access the control panel for your server. b. Select 02 to enter the Mode menu. c. Change N to M to start Manual mode. d. Press Enter to exit mode menu. e. Scroll to function 30 using Increment or Decrement buttons. f. Press Enter to enter subfunction. g. Use the Increment or Decrement buttons to select a network device. 00 = SP A: ETH0 01 = SP A: ETH1 h. Press Enter to display the selected IP address. After you record the IP address, put the server back into Normal mode: i. Use the Increment or Decrement buttons to select subfunction exit. j. Press Enter to exit subfunction mode. k. Scroll to 02 using Increment or Decrement buttons. l. Select 02 to enter the Mode menu. m. Change M to N to return to Normal mode. n. Press Enter to exit mode menu. You can now access the service processor through the web interface. 4. Open a web browser and enter where ipaddress is the address you recorded. 5. The first time that you connect to the service processor, enter the default user and password: v User ID: admin v Password: admin Configuring IBM PowerKVM on Power Systems 5

12 After you log in, you must change the password. Be sure to remember this password! After you change the password, the service processor main menu appears. 6. From the main menu, select System Configuration > Hypervisor Configuration. 7. Select PowerKVM (or OPAL) as your Hypervisor Mode and set up a password for IPMI session. What to do next You are now ready to power on your server. Go to Connecting to your system with IPMI on page 10 for instructions. Petitboot bootloader After the system powers on, the Petitboot bootloader scans local boot devices and network interfaces to find boot options that are available to the system. Petitboot returns a list of boot options that are available to the system. If you set up a DHCP server and provided the boot arguments as outlined in Setting up a network boot server on page 2 or if you are using a media installation, your boot option is available. Select it and press Enter. If you are using a static IP or if you did not provide boot arguments in your network boot server, you must provide the details to Petitboot. Note: After approximately 10 seconds, Petitboot boots the first option. Configuring Petitboot You can configure Petitboot to find your boot options. Use these instructions if you did not set up your DHCP network boot server or if you are using a static IP address. About this task Follow these steps to configure Petitboot to find the IBM PowerKVM installer. 1. To provide your network information to Petitboot, follow these steps: a. On the Petitboot main menu, select System Configuration and press Enter to open the Petitboot System Configuration window. b. On the Petitboot System Configuration window, specify your network information. DHCP on all active interfaces Automatically assigns IP addresses to each network interface. DHCP on a specific interface Automatically assigns IP addresses to a selected network interface. Static IP configuration Use this option to manually specify an IPv4 network configuration. If you select this option, you must provide an IP address, netmask, gateway address, and optionally a DNS server address. Note: The network interface names, such as eth0, that Petitboot uses are not guaranteed to match the names that are used by IBM PowerKVM. To ensure that you are using the expected network interface, compare MAC addresses. When you are finished, select OK and press Enter. 2. Select e to open the Petitboot Option Editor for edit or n to create new options. 3. Use the Petitboot Option Editor window to edit or create boot options. 6 Linux: Configuring IBM PowerKVM on Power systems

13 v If your boot resources are on a local disk device, select the device from the list, enter your boot resources as paths to that device, and click Enter. v If you want to use full URLs to your boot resources, select Specify paths/urls manually and then enter your boot options: 4. In the Kernel field, enter the path to the kernel. This field is mandatory. For example, enter a path similar to this URL address: In this example, replace networkservername/path with your network server IP address and the path on that server to the kernel. 5. In the Initrd field, enter the path to the init ramdisk. For example, enter a path similar to this URL address: In this example, replace networkservername/path with your network server IP address and the path on that server to the initrd.img file. 6. In the Device tree field, enter the path to the device tree blob. This field is optional. 7. In the Boot arguments field, enter the kernel command-line arguments. For example, enter a path similar to this URL address: rd.dm=0 rd.md=0 root=live: repo= console=hvc0 console=tty0 In this example, replace networkservername/path with your network server IP address and the path on that server. If you are using a static IP address, include an argument for it. The argument looks like this example: ifname=net0:mac_address ip=static_ip_address::gateway:netmask:hostname:net0:none Replace the variables as follows: net0: The name that you are calling this connection. MAC_address: The MAC address of the network device. static_ip_address: The static IP address of the device. gateway: The gateway of the device. netmask: The netmask of the device. hostname: The host name of the server. hostname is not required for this connection. After you set your options, select OK and press Enter. 8. On the Petitboot main window, select your boot option and press Enter. Editing Petitboot configuration options You can change the default options of Petitboot to automatically boot the default option or to change the amount of time before Petitboot automatically boots the default option. v To change an existing option, type E (edit) v To add a boot option, type N (new) v To display information about the system, type I (information) or select System Information in the window. v To change to the system configuration, type C (configuration) or select System Configuration in the window. On the configuration window, you can edit the following options: Autoboot Configuring IBM PowerKVM on Power Systems 7

14 Don't autoboot Select to stop at the Petitboot bootloader window without continuing the boot. Autoboot from any disk/network device Select to allow Petitboot to automatically boot the default option. Petitboot quickly boots your system without changing any options. Only autoboot from a specific disk/network device Select to allow Petitboot to automatically boot from a specific disk or network device. Petitboot quickly boots your system without changing any options. Timeout Sets the length of time, in seconds, before Petitboot automatically boots the default option. Network options DHCP on all active interfaces Automatically assigns IP addresses to each network interface. DHCP on a specific interface Automatically assigns IP addresses to a selected network interface. Use Static IP configuration Use this option to manually specify an IPv4 network configuration. If you select this option, you must provide an IP address, netmask, gateway address, and optionally a DNS server address. Automated network installation You can install PowerKVM using an automated network installation file similar to a kickstart file and the boot option kvmp.inst.auto. The boot option kvmp.inst.auto supports HTTP, TFTP, and NFS network installations. Supported items for the installation file include the following options: v Pre-install scripts v Post-install scripts v Partition (required) v Network (required) v Root password v Timezone A typical installation file looks like the following example: partition / --ondisk=/dev/sda network --device enp3p6s0f0 --bootproto dhcp rootpw passw0rd timezone US/Chicago Note: You can also use /dev/disk/by-id or /dev/disk/by-path for the value of --ondisk. For example, partition / --ondisk=/dev/disk/by-id/1ibm_ipr-0_5exxxxxxxxxxxx. Running the command, ls -l on /dev/disk/by-id provides the corresponding values for sdx disks and if multipath is enabled. You can find paths by running the command ls -l /dev/disk/by-path/ To run the installation file, configure Petitboot to use it, similar to the following example: label IBM PowerKVM Automated Install (kickstart) kernel initrd append ksdevice=bootif lang= kssendmac text root=nfs: :/var/www/kvmonp_netboot/iso/ibm-powerkvm.iso rd.dm=0 8 Linux: Configuring IBM PowerKVM on Power systems

15 rd.md=0 ipv6.disable=1 kvmp.inst.auto=tftp:// /kickstart/powerkvm.ks ifname=net0:e4:1f:13:fd:cf:7d ip= :: : :powerkvm-host:net0:none The ibm-configure-system utility The ibm-configure-system utility is a command-line interface that you can use to change your root password, configure time zones, set the date and time, configure network interfaces, and set your DNS configuration. To use the ibm-configure-system utility, run ibm-configure-system from an IPMI console window that is connected to the server. Navigate the menu with the up and down arrow keys or TAB. To change the root password, select Root Password and press Enter. Type a new password and confirm it. Select OK and press Enter. To set your time zone, select Timezone Selection and press Enter. Select your time zone from the list. To set the system to use Coordinated Universal Time (UTC), navigate to it and then press Space bar. When you are finished, select OK and press Enter. To change your system date and time, select Date and Time and press Enter. Type your date and time. When you are finished, select OK and press Enter. To configure your network, select Configure Network. Select a device and then select OK and press Enter. On the Network Device Configuration window, define your network connection. Select Save and press Enter. To set your DNS server information, select DNS configuration. Enter your DNS configuration, select OK, and press Enter. When you are finished configuring your system options, press Tab to select Exit and press Enter. Confirm your Exit and press Enter again. Kimchi management tool Kimchi is a management tool, which is designed to get you started with IBM PowerKVM. Kimchi is an HTML5-based management tool that runs as a daemon on the hypervisor host and interfaces with underlying libvirt, QEMU, and KVM components. Use Kimchi to create and manage guests, monitor your host system, create networking interfaces, add storage, and update packages. To use Kimchi, open a browser and point it to where ip_address is the IP address of your KVM system. Log in using the admin user name and password. Note: When you connect to Kimchi, make sure that you enable SSL connections in your browser. For Firefox browsers, you might also be required to connect to where ip_address is the IP address of your host KVM system and accept the self-signed certificate. Connect using the HTTP secure (HTTPS). Use Kimchi to allocate storage, configure a network bridge, apply firmware updates, and install guests. Configuring IBM PowerKVM on Power Systems 9

16 Intelligent Platform Management Interface (IPMI) on PowerKVM The Intelligent Platform Management Interface (IPMI) tool is the default console to use with PowerKVM. Installing IPMI The IPMItool utility is available with most distributions of Linux. About this task If you do not have a version of IPMItool on your system, follow these steps: 1. Download a version from SourceForge at 2. Install the.tar file. What to do next v You must be logged in as root to use the IPMItool command works only for root user. v You can find your version of IPMI by running ipmitool -V v IPMI can be impacted by network traffic and will disconnect after seven attempts. The default retry-interval is 100 milliseconds. You can reset the default retry-interval to higher number by running the follow command: ipmitool -I lanplus -H myserver.example.com -P mypass sol set retry-interval 50 This command sets the retry-interval to 500 ms. Connecting to your system with IPMI To connect to your system with IPMI, you need to know the IP address of the server and have a valid password. To power on your Power server, run the following command: ipmitool -I lanplus -H fsp_ip_address -P ipmi_password power on where ipaddress is the IP address of the Power server and ipmi_password is the password set up for IPMI. To activate your IPMI console, run the following command: ipmitool -I lanplus -H ip_address -P ipmi_password sol activate For additional commands, see Common IPMI commands on page 11. Changing your IPMI password Learn how to change your IPMI password About this task Your IPMI password is set on the IBM PowerKVM host through the ASMI menus. To change your IPMI password, follow these steps: 1. Access the ASMI menu. 2. From the main menu, select Login Profile -> Change Passwords. 3. Select IPMI from the list of user IDs. 4. Enter the current password for the administrator and then enter and confirm a password for IPMI. 10 Linux: Configuring IBM PowerKVM on Power systems

17 5. Click Continue. Common IPMI commands You can use the IPMI command to perform several managing tasks for your Power system. Table 3. Common IPMI commands Command option ipmitool -I lanplus -H myserver.example.com -P mypass chassis power on ipmitool -I lanplus -H myserver.example.com -P mypass chassis power off ipmitool -I lanplus -H myserver.example.com -P mypass chassis status ipmitool -I lanplus -H myserver.example.com -P mypass chassis power cycle ipmitool -I lanplus -H myserver.example.com -P mypass sol activate ipmitool -I lanplus -H myserver.example.com -P mypass sol deactivate ipmitool -I lanplus -H myserver.example.com -P mypass sel list ipmitool -I lanplus -H myserver.example.com -P mypass sdr list ipmitool -I lanplus -H myserver.example.com -P mypass sol set retry-interval value ipmitool -I lanplus -H myserver.example.com -P mypass fru print ipmitool -I lanplus -H myserver.example.com -P mypass user list Description Powers on the server Powers off the server Checks the server status Power cycle the server Activates SOL system console Deactivates SOL system console Returns an error log Lists status of all sensors Sets the default retry-interval value in milliseconds. Prints the FRU information Lists the IPMI users Creating guests You can create guests by using Kimchi or by using the command line interfaces. Creating a guest with Kimchi Use Kimchi to create virtual machines, or guests. 1. Open a browser and go to where ip_address is the IP address of your KVM system. 2. Select the Guests page. 3. Click the green plus sign (+) to create a guest. 4. On the Guests page, enter a name for the virtual machine guest. Select a template from the list. If no templates exist, click Create a template. If you want a different template from the ones that are displayed, select the Templates page and create or edit one. 5. Select the source media for the template. 6. Select an ISO image. 7. Click Create. The guest is created but not started. 8. Start the guest by clicking the red power button or by selecting Start from the Actions menu. The button changes to green as the guest starts. 9. To connect to the remote console (Livetile), select Connect from the Action menu Configuring IBM PowerKVM on Power Systems 11

18 Results Note: v If you create a non-persistent guest outside of Kimchi and then use Kimchi to stop it, the guest will be deleted. In Kimchi, the Stop option calls the virsh destroy command, which deletes non-persistent guests. To avoid this issue, either use the virsh shutdown guest command where guest is the name of your virtual machine or the Kimchi console to shut down the guest within the guest operating system. v If you are using a logical storage pool for storage, creating a guest disk with the same capacity as the remaining pool capacity may fail. Libvirt does not report the exact number of extents required for a disk. Consider creating a guest that uses 1G less than what Kimchi and libvirt report as available. If you have trouble starting a guest that has storage allocated in a logical storage pool, check your system or Kimchi log files for the error libvirterror: internal error: Child process (/usr/sbin/lvcreate --name some_image.img -L [X]K some_pool_name) unexpected exit status 5: Volume group "some_pool_name" has insufficient free space ([X] extents): [X] required. Setting up a template using Kimchi You can use Kimchi to define templates for your guests. About this task To view the current templates available, start Kimchi and select Templates. From this page, you can perform the following actions: v Select Edit to edit the template. v Select Delete to delete the template. You can also add a template by following these steps: 1. On the Templates tab, click the plus (+) icon. 2. Select the location of the source media from the following options: Local ISO image Select to scan storage pools for installation ISO images available on the system. Remote ISO image Select to specify a remote location for an installation ISO image. If you selected Remote ISO image, the image is retrieved and loaded onto the system. If you selected Local ISO image, all ISO images available on the system are displayed. 3. To create a template from an ISO image, choose from the following options: v Select an ISO image from which to create a template, then click Create Templates from Selected ISO. v Select All to create a template from each listed ISO image, then click Create Templates from Selected ISO. If the ISO image that you want to use does not appear in the scan results, you can select from the following options: v Select I want to use a specific ISO file to specify a path to the ISO image. v Click Search more ISOs to search for more ISO images. 4. Click Create. Creating a guest with the virsh command The virsh command is a common command-line utility that can be used to create KVM guests. 12 Linux: Configuring IBM PowerKVM on Power systems

19 Run the virsh command as a single command or as a shell program. Most virsh commands require root privileges, although unprivileged users can use the virsh command for read-only operations. The virsh command uses the libvirt API. PowerKVM includes the libvirt package, but you can ensure that the libvirt daemon is running before you run virsh commands. To check the libvirt daemon status, run the following command: # systemctl status libvirtd If the service is running, output similar to this example is shown: libvirtd.service - Virtualization daemon Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled) Active: active (running) since Fri :32:43 GMT; 4 days ago Main PID: 3517 (libvirtd) If the output displays inactive, then start the libvirt daemon by running this command: # systemctl start libvirtd You can use the virsh command to create a virtual machine by creating a libvirt XML file that describes the virtual machine and then running the virsh create command. To create a libvirt XML file, you can create the xml file or else export an existing one and edit it to the parameters that you want. You can find more information about libvirt at Creating guests with the virt-install command The virt-install command is used to create new KVM guests. The virt-install command is useful for when you do not have access to a graphical desktop and, when given the necessary options, can run unattended. If some of the required options are omitted, the virt-install command runs interactively, prompting you for input when required. You must run the virt-install command as root. For more information about the options that you can use with the virt-install command, see In this example, create a guest with name test, using two virtual processors and 4 GB of RAM, connecting to default network, and using an ISO file as installation source. virt-install --machine=pseries --name=test --virt-type=kvm --boot cdrom,hd --network=default,model=virtio --disk path=/var/lib/libvirt/images/test.qcow2,size=10,format=qcow2,bus=virtio,cache=none --memory= vcpu=2 --cdrom=/var/lib/libvirt/images/rhel server-ppc64-dvd1.iso Common virsh command options You can use the virsh command to manage several tasks for your KVM system. Table 4. Common virsh command options. Command option virsh connect virsh create xmlfile.xml Description Connect to the KVM hypervisor Creates and starts a guest from an XML configuration file. Configuring IBM PowerKVM on Power Systems 13

20 Table 4. Common virsh command options. (continued) Command option virsh list --all virsh dumpxml guest_name virsh start guest_name virsh destroy guest_name virsh define xmlfile.xml virsh reboot guest_name virsh restore filename virsh resume guest_name virsh save guest_name filename virsh suspend guest_name virsh undefine guest_name virsh undefine guest_name --remove-all-storage virsh nodeinfo virsh dominfo guest_name Description Lists all the guests on a host. Creates an XML configuration file of the guest as an output file. Starts an inactive guest. Immediately stops the guest. Creates a guest from an XML configuration file. The guest is not started. Restarts the guest Restores a guest from a saved file Resumes a guest that was paused Save the state of the guest to a file Pauses the guest Deletes the guest, but not the image file Deletes the guest and all the associated storage Displays information about the host Displays information about a guest PowerKVM storage Storage for PowerKVM consists of storage volumes and storage pools. A storage pool is file, directory, or storage device that is available to the guests. Storage pools are divided into volumes that are then assigned to guests. Common virsh command options - Storage You can use the virsh command to manage your storage in PowerKVM. Table 5. Common virsh command options: storage Command option virsh find-storage-pool-sources virsh pool-define-as pool_name path mountpoint virsh pool-list virsh pool-build pool_name virsh pool-start pool_name virsh pool-autostart pool_name virsh pool-info pool_name virsh vol-create-as pool_name vol_name size --format format_type virsh vol-list pool_name Description Creates an XML definition file for all storage pools of a specific type. Create a storage pool. Provide the name, the path to the storage, and a mount point on the local system. Lists all storage pools. To include inactive storage pools, add --all. Creates a mount point for the storage pool. Starts the storage pool Causes the pool to be started every time that libvirt is started. To disable this option, run virsh pool-autostart pool_name --disable. Displays information about the pool. Creates a volume. Specify the pool where the volume is located, the name of the volume, size of the image (in K, M, G, T), and the format of the volume. Lists the volumes in a pool. To include inactive volumes, add --details. 14 Linux: Configuring IBM PowerKVM on Power systems

21 Table 5. Common virsh command options: storage (continued) Command option virsh vol-clone existing_vol_name new_vol_name --pool pool_name virsh vol-delete --pool pool_name vol_name virsh pool-destroy pool_name virsh pool-delete pool_name virsh pool-undefine pool_name Description Copies and creates a volume in a storage pool. Deletes a volume from a storage pool. Stops a pool. Deletes a pool directory from the host. Removes the pool definition. Find storage pool sources with virsh Use the virsh command to discover storage pool sources on your system. Discovery of storage pool sources is supported for the following pool types: v logical v netfs (requires NFS server IP address or hostname) v iscsi (requires iscsi server details) find-storage-pool-sources type [srcspec] Returns XML describing all storage pools of a given type that could be found. For netfs and iscsi types, provide an XML containing the required details (srcspec). In this example, create a query to find NFS storage pool sources on server Create an XML similar to the following: <source> <host name= /> <dir path= /> <format type= nfs /> </source> Provide the XML as an argument in the command: virsh find-storage-pool-sources netfs nfs.xml This command returns output similar to the following example: <sources> <source> <host name= /> <dir path= /nim/build_net /> <format type= nfs /> </source> <source> <host name= /> <dir path= /kvm_lpm /> <format type= nfs /> </source> </sources> find-storage-pool-sources-as type [host] [port] [initiator] Returns XML describing all storage pools of a given type that could be found. For netfs and iscsi type, provide the host or other details as appropriate In this example, create a query to find NFS storage pool sources on server Configuring IBM PowerKVM on Power Systems 15

22 virsh find-storage-pool-sources-as netfs This command returns output similar to the following example: <sources> <source> <host name= /> <dir path= /nim/build_net /> <format type= nfs /> </source> <source> <host name= /> <dir path= /kvm_lpm /> <format type= nfs /> </source> </sources> Valid storage pools types You can create and use several types of storage pools with PowerKVM. Directory pool (DIR) Specifies a directory pool. When you use a directory pool, the file must exist and you must provide the path to the volume within that pool. Specify directory in the XML format looks similar to this format: <pool type="dir"> <name>kvmstorageimage</name> <target> <path>/var/lib/virt/images</path> </target> </pool> Network file system pool (NFS) Specifies an NFS file system pool as a type of exported storage. When you specify NFS, the file system is mounted and files are managed from its mount point. To use NFS file system pool, you need the host name and path of the exported directory. PowerKVM attempts to mount the network file system. Specify NFS in the XML format looks similar to this format: <pool type="netfs"> <name>kvmstorageimage</name> <source> <host name="nfs.example.com"/> <dir path="/var/lib/virt/images"/> <format type= nfs /> </source> <target> <path>/var/lib/virt/images</path> </target>; </pool> iscsi server (iscsi) Specifies a pool that is based on a target that is allocated on an iscsi server. A iscsi volume pool must exist.. Consider configuring the pool to use /dev/disk/by-path or /dev/disk/by-id for the target path. These provide persistent stable naming for LUNs. You can also add iscsi authentication. The iscsi authentication uses CHAP protocol. Specify the user name and password when you define the pool. Specify iscsi in the XML format looks similar to this format: <pool type="iscsi"> <name>kvmstorageimage</name> <source> <host name="isci.example.com"/> <device path="path2target" /> 16 Linux: Configuring IBM PowerKVM on Power systems

23 <auth type= chap username= userid > <secret usage= mypassword /> </auth> </source> <target> <path>/var/lib/virt/images</path> </target> </pool> Logical volume storage pool (Logical) Specifies a logical volume (LVM) storage pool. For an existing LVM group, use the group name to identify it. If you are creating a new LVM group, specify the source devices to use. You must also provide a path to the LVM pool. Specifying logical in the XML format looks similar to this format: <pool type="logical"> <name>volgroup</name> <source> <device path="/dev/sda1"/> <device path="/dev/sdb1"/> <device path="/dev/sdc1"/> </source> <target> <path>/dev/volgroup</path> </target> </pool> SCSI Fibre Channel Specifies a pool that is based on a SCSI Fibre Channel. The SCSI Fibre Channel volume pool must exist. Consider configure the pool to use /dev/disk/by-path or /dev/disk/by-id for the target path. These provide persistent stable naming for LUNs. Specifying SCSI in the XML format looks similar to this format: <pool type="scsi"> <name>kvmstorageimage</name> <source> <adapter name="host0"/> </source> <target> <path>/dev/disk/by-path</path> </target> </pool> Storage pool Create a storage pool with the Kimchi interface or the virsh command. Setting up a storage pool with Kimchi You can use Kimchi to define storage pools for your guests. About this task To view the current storage pools available, start Kimchi and select Storage. From this page, you can perform the following actions: v Select Activate to activate the storage pool so that it can be used. v Select Deactivate to deactivate an active storage pool. v Select Undefine to remove an inactive storage pool. v Select the arrow at the end of a row to view details about a storage pool You can also define a storage pool by following these steps: Configuring IBM PowerKVM on Power Systems 17

24 1. On the Storage tab, click the plus (+) icon. 2. In the Storage pool name field, type the name to be used to identify the storage pool. 3. In the Storage pool type list, select the type. You can choose: DIR NFS iscsi Specifies a directory pool. When you select DIR, type the Storage path (file path to the storage pool). Specifies a network file system pool. When you select NFS, type the NFS server IP address and NFS path (path of the exported directory). Specifies a pool that is based on a target that is allocated on an iscsi server. When you select iscsi, type the iscsi server IP address and Target on the iscsi server. You can optionally select to add iscsi authentication. Logical Specifies a logical volume storage pool. Select the location to the device in Device path. Note: You must create the storage pool using a partition. At this time, you cannot create a logical pool from an existing volume using Kimchi. 4. Click Create. Creating storage pool with virsh Create a storage pool with the virsh command and a temporary XML configuration file About this task To create a storage pool by defining a temporary XML configuration file and then using the virsh command to add it, follow these steps: 1. Create an XML file for the storage device. In this example, define an iscsi device with authentication. <pool type="iscsi"> <name>storage_image</name> <source> <host name="isci.example.com"/> <device path="path2target" /> <auth type= chap username= userid > <secret usage= mypassword /> </auth> </source> <target> <path>/dev/disk/by-path</path> </target> </pool> 2. Add the XML file to the storage definition: virsh pool-define ~/storage_image.xml 3. Verify that the pool was created: virsh pool-list -all Name State Autostart default active yes storage_images inactive no 4. Start the storage pool: virsh pool-start storage_images Pool storage-images started 18 Linux: Configuring IBM PowerKVM on Power systems

25 5. Verify that the pool started: virsh pool-list --all Pool storage-images started Name State Autostart default active yes storage_images active no 6. Optional: Turn on autostart for the storage pool: virsh pool-autostart storage_images Pool storage-images marked as autostarted. 7. Verify that the storage pool was created correctly and is running: virsh pool-info storage_images Name: storage_images UUID: afcc e151-bcb3-847bc76c5e28 State: running Persistent: unknown Autostart: yes Capacity: GB Allocation: 0.00 Available: GB Networking on PowerKVM Networking in a virtualized environment can be seen as a number of independent physical and virtual network interfaces. By default, a KVM installation provides two network communication bridges. The first, virbr0, is a NAT virtual network. This bridge allows communication to an external system with a host IP address, to other guests, and to the host. The second, virbr1, is a bridge for local host network connectivity only. You can also create a network bridge. Using a bridge, guests can communicate with external systems and be contacted by external systems as if they were physical systems on the network. This type of access requires a physical network connection. To increase the security of the host, plan to configure one network interface for the host and a separate network interface for the guest operating systems. Configuring IBM PowerKVM on Power Systems 19

26 In this configuration, the network traffic for the host travels on a different subnet than the network traffic for the guest operating systems. This configuration increases security in the following ways: v Helps isolate the host from the guest operating systems. v Helps prevent malicious users with a lower security clearance from breaching a guest operating system and attacking the host or other guest operating systems. Common virsh command options - Networking You can use the virsh command to perform several tasks that are related to networking. Table 6. Common virsh command options: Network Command option virsh net-info network_name virsh net-list virsh net-start network_name virsh net-create xml_file virsh net-autostart network_name virsh net-define xml_file virsh net-dumpxml network_name virsh net-edit network_name virsh net-destroy network_name virsh net-undefine network_name Description Returns information about a network Returns a list of active networks. Can also add --all to return all defined network, including inactive ones. Starts a defined but inactive network. Creates a virtual network from an XML file Configures a network to automatically start. Defines a network from an XML file. The network is not started. Creates an xml file of the virtual network information of a guest. Opens the xml configuration file for editing. Stops a network. Undefines an inactive network. 20 Linux: Configuring IBM PowerKVM on Power systems

27 Setting up a network connection with Kimchi You can use Kimchi to define network connections for your guests. About this task To view the current network connections available, open Kimchi and select Network. From this page, you can perform the following actions: v Select Start to begin the network connection. v Select Stop to end the network connection. v Select Delete to delete the connection information. You can also create a network connection by following these steps: 1. From the Network window, click the plus (+) icon. 2. Enter the name of the network 3. Select the network type. You can choose: Isolated Isolated mode. Guests cannot send or receive communication to or from external systems. NAT Network Address Translation mode. Communication from guests to external systems uses the host IP address. External systems cannot initiate communication to guests. Bridged Bridged mode. Guests can communicate with external systems and be contacted by external systems as if they were physical systems on the network. For bridged mode, you must specify additional destination and VLAN information. 4. Click Create. Creating a network bridge with the ibm-configure-system utility You can set up a network bridge with the ibm-configure-system utility. About this task The ibm-configure-system utility is included in the PowerKVM package. To create a network bridge with the ibm-configure-system utility, follow these steps: 1. Connect to your system with IPMI. 2. Run ibm-configure-system. 3. Select Configure Network. Note: Navigate the menu with the up and down arrow keys or TAB. 4. On the Configure network window, select the device that you want to configure and select OK and press the Space bar. 5. On the Network Device Configuration window, verify the device configuration. Select Save and press Enter. Configuring IBM PowerKVM on Power Systems 21