User manual NOVELL SUSE LINUX ENTERPRISE DESKTOP 11 SP1 8-18-2010 VIRTUALIZATION WITH ZEN

[. . . ] SUSE Linux Enterprise Desktop 11 SP1 August 18, 2010 www. novell. com Virtualization with Xen Virtualization with Xen All content is copyright © 2006­2010 Novell, Inc. Legal Notice This manual is protected under Novell intellectual property rights. By reproducing, duplicating or distributing this manual you explicitly agree to conform to the terms and conditions of this license agreement. This manual may be freely reproduced, duplicated and distributed either as such or as part of a bundled package in electronic and/or printed format, provided however that the following conditions are fulfilled: That this copyright notice and the names of authors and contributors appear clearly and distinctively on all reproduced, duplicated and distributed copies. [. . . ] In most configurations, this means that you should use the bonding configuration only in Domain0. Only if you have multiple network cards assigned to a VM Guest system it may also be useful to set up the bond in a VM Guest. Virtual Networking 55 To configure a bonding device, use the following procedure: 1 Run YaST > Network Devices > Network Settings. 2 Use Add and change the Device Type to Bond. Proceed with Next. 3 Select how to assign the IP address to the bonding device. Three methods are at your disposal: · No IP Address · Dynamic Address (with DHCP or Zeroconf) · Statically assigned IP Address Use the method that is appropriate for your environment. 4 Select the Ethernet devices that should be included into the bond by activating the check box in front of the respective Bond Slave. The modes that are available for configuration are the following: · balance-rr · active-backup 56 Virtualization with Xen · balance-xor · broadcast · 802. 3ad · balance-tlb · balance-alb 6 Make sure that the parameter miimon=100 is added to the Bond Driver Options. Without this parameter, the data integrity is not checked regularly. 7 Click Next and leave YaST with OK to create the device. All modes, and lots of more options are explained in detail in the Linux Ethernet Bonding Driver HOWTO found at /usr/src/linux/Documentation/ networking/bonding. txt after installing the package kernel-source. 6. 5. 4 Using VLAN Interfaces Sometimes, it is necessary to create a private connection either between two Xen hosts or between a number of VM Guest systems. For example, if you want to migrate VM Guest to hosts in a different network segment, or if you want to create a private bridge that only VM Guest systems may connect to, even when running on different VM Host Server systems. An easy way to build such connections is to set up VLAN networks. VLAN interfaces are commonly set up on the VM Host Server and either just interconnect the different VM Host Server systems, or they may be set up as physical interface to an otherwise virtual only bridge. It is even possible to create a bridge with a VLAN as physical interface that has no IP address in the VM Host Server. That way, the guest systems have no possibility to access Domain0 over this network. Run the YaST module Network Devices > Network Settings. Follow this procedure to actually set up the VLAN device: Procedure 6. 3 Setting up VLAN Interfaces with YaST 1 Press Add to create a new network interface. Virtual Networking 57 2 In the Hardware Dialog, select Device Type VLAN. 3 Change the value of Configuration Name to the ID of your VLAN. Note that VLAN ID 1 is commonly used for managing purposes. 5 Select the interface that the VLAN device should connect to below Real Interface for VLAN. If the desired interface does not appear in the list, first set up the this interface without IP Address. 6 Select the desired method for assigning an IP address to the VLAN device. [. . . ] If not set, the value from the XAUTHORITY environment variable is used. Example: (xauthority /root/. Xauthority) 126 Virtualization with Xen maxmem Defines how much memory in MB can be assigned to the VM Guest while running. Example: (maxmem 1024) memory Defines the initial amount of memory in MB of the VM Guest. Example: (memory 512) name The name of the VM Guest as it appears in different managing utilities. [. . . ]