27.12.2012 Views

The Virtualization Cookbook for SLES 10 SP2 - z/VM - IBM

The Virtualization Cookbook for SLES 10 SP2 - z/VM - IBM

The Virtualization Cookbook for SLES 10 SP2 - z/VM - IBM

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

This allows the cloner to initiate an encrypted SSH connection to the Linux server without the<br />

need to type the root password.<br />

8.2.8 Changing the order of the swap disks<br />

It is likely that the order of swap space priority is not optimal. Per<strong>for</strong>m the following<br />

commands:<br />

► View your order with the swapon -s command:<br />

# swapon -s<br />

Filename Type Size Used Priority<br />

/dev/dasda2 partition 524296 0 -1<br />

/dev/dasdb1 partition 262132 0 -2<br />

/dev/dasdc1 partition 524276 0 -3<br />

This shows that the minidisk swap space will be used be<strong>for</strong>e the VDISK. As VDISKs are<br />

in-memory, they should be first in the priority, from smallest to largest.<br />

► Make a backup of the /etc/fstab file:<br />

# cd /etc<br />

# cp fstab fstab.orig<br />

► Modify the order by moving the line in /etc/fstab. with the minidisk swap space below<br />

the lines with VDISK swap spaces:<br />

# vi fstab<br />

...<br />

/dev/disk/by-path/ccw-0.0.0300-part1 swap swap defaults 0 0<br />

/dev/disk/by-path/ccw-0.0.0301-part1 swap swap defaults 0 0<br />

/dev/disk/by-path/ccw-0.0.0<strong>10</strong>0-part2 swap swap defaults 0 0<br />

...<br />

After a reboot, the minidisk swap space should come back with the lowest priority.<br />

8.2.9 Other configuration changes<br />

You may consider other configuration changes. Of course you can take an iterative approach:<br />

start with this set of changes, clone some Linux images and test, then bring the golden image<br />

back up, make more changes and re-clone.<br />

Whether you’re on the first pass of configuration or not, refer to the following sections to<br />

consider other changes <strong>for</strong> per<strong>for</strong>mance and availability related issues:<br />

► 12.1, “Registering your system with RHN” on page 187<br />

► 13.6, “Setting up Memory Hotplugging” on page 208<br />

► 13.8, “Hardware cryptographic support <strong>for</strong> OpenSSH” on page 213<br />

8.2.<strong>10</strong> Rebooting the system<br />

Now reboot to test your changes:<br />

# reboot<br />

Broadcast message from root (pts/0) (Sun Nov 19 08:57:32 2006):<br />

<strong>The</strong> system is going down <strong>for</strong> reboot NOW!<br />

142 <strong>The</strong> <strong>Virtualization</strong> <strong>Cookbook</strong> <strong>for</strong> RHEL 6

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!