![]() | |
The drivers for SUSE Linux Enterprise are not included in the driver pack. They are available through the standard update channels. | |
This section provides instructions for running SUSE Linux Enterprise as a fully virtual guest with Xen drivers. Running SUSE Linux Enterprise requires a VM Host Server based on SUSE Linux Enterprise Server 10 SP2 or later.
The supported guest systems are SUSE Linux Enterprise Server 9 SP4 or later.
Create a new fully virtual machine or start an existing fully virtual machine. Use ++.
Get the latest updates for the operating system from your update channel.
Verify that the Xen drivers are installed.
Launch YaST by entering yast2 at a terminal.
Select +.
Search for xen-kmp and make sure that the
appropriate drivers are installed for your system.
If they are not selected, select them and click to complete the installation.
Setup your virtual machine to use the paravirtualized disk drivers:
In the VM Guest, edit the file
/boot/grub/menu.lst. At the kernel
line, append a parameter hdx=noprobe where
hdx is the drive designation
specified in the virtual machine configuration file.
For example, the disk specification in your configuration file
may look as follows:
disk=['file:/var/lib/xen/images/vm1/disk0,ioemu:hda,w', \ 'file:/var/lib/xen/images/vm1/disk1,ioemu:hdb,w' ]
In this example, the virtual machine configuration file
specifies two virtual disks hda and
hdb. If you want both disks to use the
Xen drivers, add the parameters
hda=noprobe and hdb=noprobe
to your kernel command line as follows:
kernel vmlinuz-kernel_ver <other_options> hda=noprobe hdb=noprobe
Now, the devices /dev/hda and
/dev/hdb are disabled, and the machine must
be prepared to use the paravirtualized disk drivers. At the
kernel line, change the root device to the paravirtualized disk
device. For example, if the kernel line contains
root=/dev/disk/by-id/xxx, change this entry
to root=/dev/hdaX, where
hdaX is the disk and partition of your root
partition. For example, this will look like
root=/dev/hda2.
Shutdown your VM Guest. The Xen paravirtualized disk driver will be used the next time you reboot this VM Guest.
If your VM Guest is running, first shut it down.
On the VM Host Server, open a terminal and enter xm delete vm_name to delete the virtual machine’s reference in the Xen store so it is no longer managed.
![]() | |
Enter xm list to see the name of the virtual
machine ( | |
Open the virtual machine configuration file located on virtualization
host server (/etc/xen/vm/vm_cfgfile, where
vm_cfgfile is usually the same as the name
of the virtual machine).
Remove all parameters from the vif= line except the mac=mac_address parameter. Make sure to leave the single quotes.
For example, change the line
vif=[ 'mac=00:16:3e:55:24:21,model=pcnet,type=ioemu', ]
to
vif=[ 'mac=00:16:3e:55:24:21,type=netfront', ]
At the terminal, enter xm new
vm_cfgfile to reference the
virtual machine in the Xen store so it is managed again.
Restart the virtual machine by using ++.
You can also restart the virtual machine by using xm start vm_cfgfile, but make sure to connect to it with a viewer.
The first time the virtual machine boots, you might see a message indicating that new hardware was found. This message can be safely canceled.
Run YaST.
Make sure you are logged in as root.
Open a terminal.
Enter YaST2.
In YaST, click .
Click , then select and delete each network card that is already configured.
Click , then change the ethx parameter to a network card number identified above. Repeat the process to add all virtual network cards.