Rx100 suse

Embed Size (px)

Citation preview

  • 7/30/2019 Rx100 suse

    1/40

    Guest OS Installation for vBlades: SUSE LinuxEnterprise Server 10.1

    For BladeFrame BF400 S2 and BladeFrame BF200

    Document Number 432-SB0057

    August 2008

    vBlades Release VBXS2.1_BF

  • 7/30/2019 Rx100 suse

    2/40

    Copyright

    Copyright 2008 Egenera, Inc. All rights reserved.

    This document, and the product described in it, is furnished under license and may only be used in accordance

    with the terms of such license. The content of this document is furnished for information purposes only and is

    subject to change without notice.

    Egenera, Egenera stylized logos, BladeFrame, BladeLatch, BladeMate, BladePlane, cBlade, Control Blade,

    PAN Manager, pBlade, Processing Blade, sBlade, and Switch Blade are either registered trademarks or

    trademarks of Egenera, Inc. in the United States and/or other countries.

    PRIMERGY is a registered trademark of Fujitsu Siemens Computers.

    AMD, AMD Opteron, and AMD Athlon are trademarks of Advanced Micro Devices, Inc..

    EMC, CLARiiON, and Symmetrix are registered trademarks of EMC Corporation.

    The IBM Developer Kit for Linux, Java 2 Technology Edition contains software which is copyright IBM

    Corporation, Sun Microsystems Inc., Hewlett-Packard Co., and X Consortium.

    Intel and Itanium are registered trademarks and Xeon is a trademark of the Intel Corporation in the United States

    and other countries.

    Sun, Sun Microsystems, the Sun Logo, Solaris, and the Java logo are trademarks or registered trademarks of

    Sun Microsystems, Inc. in the United States and other countries.

    Linux is a registered trademark of Linus Torvalds.

    Microsoft and Windows are either registered trademarks or trademarks of Microsoft Corporation in the United

    States and/or other countries. The virtual VGA console uses Microsoft Terminal Services Advanced Client

    (TSAC), which is a copyright of Microsoft Corporation.

    MindTerm is copyright AppGate AB.

    Nero is a trademark of Nero AG.

    NetApp is a registered trademark and Network Appliance is a trademark of Network Appliance, Inc.

    Oracle9i is a trademark of Oracle Corporation.

    Red Hat is a registered trademark of Red Hat, Inc. in the United States and other countries.

    SUSE is a registered trademark of SUSE LINUX Products GmbH, a Novell business.

    VMware, Virtual SMP, and VMotion are registered trademarks or trademarks of VMware, Inc.

    Xen, XenSource, XenServer, and XenEnterprise are either registered trademarks or trademarks of CitrixSystems, Inc. in the United States and/or other countries.

    All other company and product names are trademarks or registered trademarks of their respective holders.

    Printed in the United States of America.

    Egenera, Inc., 165 Forest Street, Marlboro, Massachusetts 01752.

  • 7/30/2019 Rx100 suse

    3/40

    VBXS2.1_BF iii

    Contents

    Installing SLES10.1 for vBlade pServers

    About SLES10.1 as a Guest OS ............................................................................... 1-2

    Before You Install SLES10.1 ................................................................................... 1-3

    Setting Up the Install Media on a Server ......................................................... 1-4

    Preparing to Use the VNC Viewer ................................................................... 1-4

    Configuring Your vBlade and pServer............................................................. 1-5

    Installing SLES10.1 ................................................................................................. 1-8

    Booting SLES10.1 on Your vBlade pServer .......................................................... 1-12

    Installing the Xen Guest Agent .............................................................................. 1-12

    Non-interactive Installation for SLES10.1 Guests

    About Non-interactive Installs ................................................................................. 2-2

    Performing a Non-interactive Install ........................................................................ 2-2

    Creating SLES10.1 Guests from Root Disk Images

    About Root Disk Images .......................................................................................... 3-2Requirements.................................................................................................... 3-2

    Preparing a SLES10.1 Root Disk Image .................................................................. 3-3

    Packaging the Root Disk Image ....................................................................... 3-3

    Registering the Root Disk Image ..................................................................... 3-6

    http://rhel41_vbguest_preface.pdf/http://rhel41_vbguest_preface.pdf/
  • 7/30/2019 Rx100 suse

    4/40

    Guest OS Installation for vBlades: SUSE Linux Enterprise Server 10.1

    iv VBXS2.1_BF

    Using a SLES10.1 Root Disk Image for a vBlade pServer ...................................... 3-7

    Running SLES10.1 Guests in Rescue Mode

    Upgrading SLES10.1 Guests

  • 7/30/2019 Rx100 suse

    5/40

    VBXS2.1_BF v

    Preface

    If you have the vBlades option of PAN Manager, you can use this

    document to install SUSE Linux Enterprise Server 10.1

    (SLES10.1) as the guest operating system (OS) for a pServer on a

    vBlade.

    Audience This document is for PAN Administrators and LPAN

    Administrators.

    Topics This document provides information on the following

    topics:

    Installing SLES10.1 for vBlade pServers

    Non-interactive Installation for SLES10.1 Guests

    Creating SLES10.1 Guests from Root Disk Images

    Running SLES10.1 Guests in Rescue Mode

    Upgrading SLES10.1 Guests

    Other vBlades Documentation To learn about vBlades, see the

    following document included in the PAN Manager PM5.2_BF

    documentation:

    Using vBlades

    To learn about installing the hypervisor and related software

    required to support vBlades in your PAN, see this document:

    Installing the vBlades Media

  • 7/30/2019 Rx100 suse

    6/40

    Guest OS Installation for vBlades: SUSE Linux Enterprise Server 10.1

    vi VBXS2.1_BF

    To learn about installing other guest operating systems for vBlade

    pServers, see the following documents:

    Guest OS Installation for vBlades: Red Hat Enterprise Linux 3.8

    Guest OS Installation for vBlades: Red Hat Enterprise Linux 4.5

    (includes upgrading to 4.6)

    Guest OS Installation for vBlades: Red Hat Enterprise Linux 5.1

    Guest OS Installation for vBlades: SUSE Linux Enterprise

    Server 9.3

    Guest OS Installation for vBlades: Microsoft Windows

    All of the vBlades installation documents are provided on the

    vBlades Media.

    If you dont have the document you need, contact Fujitsu Siemens

    Computers customer support or your authorized support vendor for

    assistance.

    vBlades Release Notes For release notes related to vBlades,

    access the following documents from http://www.fujitsu-

    siemens.com/support:

    PAN Manager Release Notes: Release PM5.2_BF

    Hypervisor and Guest Release Notes for vBlades VBXS2.1_BF

    PAN Manager Documentation Set To learn about the other

    documents available in the PAN Manager documentation set, see

    thePAN Manager Feature Summary.

    PAN Manager Features To learn about the PAN Manager

    features available in the current release, see thePAN Manager

    Feature Summary.

  • 7/30/2019 Rx100 suse

    7/40

    Preface

    VBXS2.1_BF vii

    vBlades Media

    The term vBlades Media used in this document refers to thevBlade

    Hypervisor and Virtualization ToolsDVD, which contains the

    software distribution for the vBlades option of PAN Manager.

    Contents of the vBlades Media include:

    Contents Directory

    vBlades install documentation

    (for the media and guests)

    /egenera

    vBlades Media install program /egenera

    See the documentInstalling the

    vBlades Media for details.

    Supplementary files for specific

    guest installs

    ForRHEL3.8 guest installs:

    /egenera

    ForSLES9.3 guest installs:

    /egenera

    /linux

    ForSLES10.1 guest installs:

    /sles10_linux

    See the corresponding guest

    documentation for details.

  • 7/30/2019 Rx100 suse

    8/40

    Guest OS Installation for vBlades: SUSE Linux Enterprise Server 10.1

    viii VBXS2.1_BF

    Customer Support

    If you require customer support regarding this product, use the

    following contact information.

    Fujitsu Siemens Computers customer support

    Document Conventions

    Internet http://www.fujitsu-siemens.com/support

    Telephone See the Help Desk information at http://

    manuals.fujitsu-siemens.com/

    primergyservers.html under General

    Information, Warranty and Support.

    Convention Description

    > Directory-level delimiter used to navigate the left pane of the

    PAN Manager GUI.

    Example: Resources > Ethernet Connections

    Sans serif italics Variable text, such as a path, a filename, or an LPAN name.

    Example: lpan -c lpanname

    Sans serif Text that must be typed as shown.

    Example: Type root at the login prompt.

  • 7/30/2019 Rx100 suse

    9/40

    Preface

    VBXS2.1_BF ix

    Bold The name of a field or window element appearing in a GUI. It also

    highlights default values in PAN Manager man pages.

    Example: In the Users page...

    Italics Text that is emphasized.

    Example: Do notconnect the power.

    [text] Text that is optional to a command.

    {text} A set of choices, one of which is required.

    | Separation of mutually exclusive choices in syntax lines.

    Example: lpan [-aD | -rD]{switch| SCSI_ID} lpanname

    Note Information of importance or that may not fit in main text.

    Caution Failure to heed a caution could result in loss of data.

    Warning Failure to heed a warning could result in physical

    harm to the user or the hardware.

    Convention Description

    !

  • 7/30/2019 Rx100 suse

    10/40

    Guest OS Installation for vBlades: SUSE Linux Enterprise Server 10.1

    x VBXS2.1_BF

  • 7/30/2019 Rx100 suse

    11/40

    VBXS2.1_BF 1-1

    Chapter 1

    Installing SLES10.1 forvBlade pServers

    This chapter tells you how to install SUSE Linux Enterprise

    Server 10.1 (SLES10.1) as the guest OS for a pServer on a vBlade.

    Topics include:

    About SLES10.1 as a Guest OS

    Before You Install SLES10.1

    Installing SLES10.1

    Booting SLES10.1 on Your vBlade pServer

    Installing the Xen Guest Agent (to support migration

    operations)

    Important:

    You must have the vBlades option, which provides the Xen and

    guest OS software that you need from Fujitsu Siemens

    Computers.

    See the chapter Installing Guest Operating Systems for vBlade

    pServers in the Using vBlades book.

    You must be aware ofrestrictions that apply when you work

    with vBlades and this guest OS.

    See the chapter About vBlades in the Using vBlades book.

  • 7/30/2019 Rx100 suse

    12/40

    Guest OS Installation for vBlades: SUSE Linux Enterprise Server 10.1

    1-2 VBXS2.1_BF

    About SLES10.1 as a Guest OS

    Here are the basics about installing and using SLES10.1 as the

    guest OS for a pServer on a vBlade:

    Guest OS type SLES10.1 is supported as a paravirtualized

    guest OS.

    Install approach Youll install a paravirtualized (PV) kernel

    from the standard SLES10.1 distribution, with the help of a

    customized installer from Fujitsu Siemens Computers. The PV

    kernel is provided by the OS vendor and tailored to work with

    the Xen hypervisor.

    pBlade requirements You can run this guest OS on a vBladeregardless of whether the underlying pBlade provides hardware

    virtualization support (via its processor architecture and feature

    set).

    Mode support 32-bit only.

    For more background information on vBlades, the hypervisor, and

    how guest operating systems fit in, see the chapter About vBlades

    in the Using vBlades book.

  • 7/30/2019 Rx100 suse

    13/40

    Installing SLES10.1 for vBlade pServers

    VBXS2.1_BF 1-3

    Before You Install SLES10.1

    Before you start the SLES10.1 install, you must perform the

    following steps:

    1. Obtain the following:

    The standard install media for SUSE Linux Enterprise

    Server 10.1 from the operating system vendor (DVD or

    CDs)

    The vBlades Media from Fujitsu Siemens Computers

    2. Prepare to use that install media by copying the appropriate

    contents to a server in your network that is accessible from thetarget pServer via NFS or HTTP.

    For details, see Setting Up the Install Media on a Server on

    page 1-4.

    3. Set up the VNC viewer on your client machine, in preparation

    for accessing the YaST2 tool later during the SLES10.1 install.

    For details, see Preparing to Use the VNC Viewer on

    page 1-4.

    4. Set up the vBlade and pServer to be used for your SLES10.1guest.

    For details, see Configuring Your vBlade and pServer on

    page 1-5.

  • 7/30/2019 Rx100 suse

    14/40

    Guest OS Installation for vBlades: SUSE Linux Enterprise Server 10.1

    1-4 VBXS2.1_BF

    Setting Up the

    Install Media on a

    Server

    To install SLES10.1 for a guest, you must perform anetwork-

    based installation using either NFS or HTTP. That means you

    need to set up the SLES10.1 install media (and some Fujitsu

    Siemens Computers files) on an accessible NFS or HTTP server.

    Follow these steps:

    1. Copy the SLES10.1 install media to your NFS or HTTP server

    as you normally would:

    If you have a DVD (or DVD image), you copy its contents

    to a single directory.

    If you have CDs (or CD images), you copy their contents to

    separate subdirectories.

    2. From the vBlades Media, copy the directory

    (and all of its contents) to your NFS or HTTP server:

    If your server has a single SLES10.1 install media directory

    (from a DVD), copy the sles10_linux directory into it.

    If your server has separate SLES10.1 install media

    subdirectories (from a set of CDs), copy thesles10_linux

    directory into the subdirectory that corresponds to the first

    CD.

    3. Rename the sles10_linux directory on your NFS or HTTP

    server to:

    linux

    Preparing to Use

    the VNC Viewer

    Part of the SLES10.1 install process involves working with the

    YaST2 installation tool, which is typically used in conjunction with

    the VNC viewer. This section provides information about setting

    up the VNC viewer on your client machine so that youre ready to

    work with YaST2 later.

    SUSE recommends that you use a VNC (Virtual NetworkComputing) console rather than telnet when performing interactive

    SLES installations with the YaST2 tool on systems with no console

    graphics. The display in a telnet window can be hard to read and

    must be refreshed often with Ctrl-L. Also, YaST2 may not correctly

    identify a PAN Manager console window.

  • 7/30/2019 Rx100 suse

    15/40

    Installing SLES10.1 for vBlade pServers

    VBXS2.1_BF 1-5

    The instructions in this document assume that you are using VNC.

    To prepare for using VNC, you can do either of the following:

    Download VNC from www.realvnc.com

    Extract VNC from your SLES distribution (see the SUSE

    documentation for details)

    Because SLES10.1 includes the VNC server, you only need to

    install the VNC viewer on your client.

    During the SLES10.1 install, when the YaST2 installation tool

    starts, the console displays the following messages:

    starting VNC server...

    A log file will be written to: /var/log/YaST2/vncserver.log ...

    ***

    *** You can connect to nnn.nnn.nnn.nnn, display :1 now with vncviewer

    *** Or use a Java capable browser on http://nnn.nnn.nnn.nnn:5801/

    ***

    (When YaST2 is finished, close your VNC viewer and return to this window.)

    If you have trouble connecting with the VNC viewer, or if you

    choose not to use that viewer for some reason, use a Java-capable

    browser as described in the console messages. The appearance of

    the YaST2 screens may vary somewhat, but the content and stepsare the same.

    Configuring Your

    vBlade and

    pServer

    Perform the following steps:

    1. Check the hardware requirements for SLES10.1 (as specified

    by the operating system vendor) and vBlades (as specified in the

    chapter About vBlades in the Using vBlades book) to select

    an underlying pBlade with suitable memory and other

    characteristics.2. Configure and boot the hypervisor on your pBlade. For

    example, in the PAN Manager CLI:

    # blade --boot-hypervisor myplatform/p3

  • 7/30/2019 Rx100 suse

    16/40

    Guest OS Installation for vBlades: SUSE Linux Enterprise Server 10.1

    1-6 VBXS2.1_BF

    This powers on your pBlade and boots the default hypervisor.

    For details on configuring and booting the hypervisor, see one of

    the following:

    GUI users: the chapter Administering vBlades in the

    Using vBlades book

    CLI users: the chapter PAN Manager CLI Commands for

    vBlades in the Using vBlades book

    3. Configure a vBlade on your pBlade.

    For example, in the PAN Manager CLI, create your vBlade and

    give it the amount ofmemory and number ofCPUs you need:

    # blade -c -M 1"Gb" -P 2 myplatform/p3-1

    For details on configuring a vBlade, see one of the following:

    GUI users: the chapter Administering vBlades in the

    Using vBlades book

    CLI users: the chapter PAN Manager CLI Commands for

    vBlades in the Using vBlades book

    4. Configure your pServer on the vBlade. For example, in the

    PAN Manager CLI:

    a. Create the pServer in your LPAN:

    # pserver -c mylpan/sles10

    b. Assign your vBlade as the pServers primary blade:

    # pserver -B myplatform/p3-1 mylpan/sles10

    c. Specify the pServers default boot image as EVBS

    (Egenera Virtualized Boot Services):

    # pserver -I EVBSmylpan/sles10

    Your PAN contains one or more different versions of the

    EVBS boot image to choose from. EVBS is used after the

    install to boot the pServer into the installed SLES10.1operating system. (Youll learn more about EVBS and its

    use in Booting SLES10.1 on Your vBlade pServer on

    page 1-12.)

  • 7/30/2019 Rx100 suse

    17/40

    Installing SLES10.1 for vBlade pServers

    VBXS2.1_BF 1-7

    d. Connect the pServer to the same network as your NFS or

    HTTP server (where you copied the install media earlier) by

    adding a vEth to the pServer and connecting that vEth to an

    appropriate vSwitch:

    # pserver -a myvswitch mylpan/sles10 veth0

    If the NFS or HTTP server resides on an external network,

    your vSwitch must have a correspondinguplink.

    e. Attach a SAN disk(identified by its disk device ID) to be

    used as the pServers root disk:

    # pserver -a "(9.0.3.95)" mylpan/sles10 "(0.0)"

    This must be the pServers first disk specified as

    "(0.0)" here, which maps to xvda in the guest. Later, when

    you install SLES10.1, youll need to specify this disks first

    partition (/dev/xvda1) as the boot partition.

    5. Erase the partition table on that disk this is required to

    ensure a successful install. For example, in the PAN Manager

    CLI:

    # cat > /tmp/empty.part

  • 7/30/2019 Rx100 suse

    18/40

    Guest OS Installation for vBlades: SUSE Linux Enterprise Server 10.1

    1-8 VBXS2.1_BF

    Installing SLES10.1

    Make sure you have finished the steps inBefore You Install

    SLES10.1 on page 1-3.

    To perform the SLES10.1 install interactively, follow these steps:

    1. Boot your pServer, but override the default boot image to do a

    one-time boot ofVBXS21_SLES1010nnnnI_IA32, a customized

    SLES10.1 install kernel provided by Fujitsu Siemens

    Computers. (It should already be registered in your PAN as

    described in the documentInstalling the vBlades Media.) This

    starts the SLES10.1 install.

    For example, in the PAN Manager CLI:

    # pserver -b -I VBXS21_SLES1010nnnnI_IA32 -K"manual=1 vnc=1 vnc_password=mypassword" mylpan/sles10

    Notes:

    If you specify the boot arguments in the PAN ManagerGUI

    instead of the CLI, omit the surrounding quotes.

    Remember the password that you enter forvnc_password.Youll need it later to start the VNC console.

    VBXS21_SLES1010nnnnI_IA32 represents a tftp boot image file

    (/tftpboot/bzImage-Xen-SLES10-IA32-instl-10.1.0-

    nnnn.tftp). Replace nnnnwith the version number of this

    image in your PAN; for a list of registered images, enter:

    # pan -i

    2. Open the pServers console (with terminal type set to vt220, as

    described below). For example, in the PAN Manager CLI:

    # console mylpan/sles10

    Note: For optimal display of installer screens in the pServer

    console, set the consoles terminal type to vt220. (You may

    still notice some minor screen display and refresh issues.) If

    using the PAN Manager CLI, switch to vt220 before executing

  • 7/30/2019 Rx100 suse

    19/40

    Installing SLES10.1 for vBlade pServers

    VBXS2.1_BF 1-9

    the console command. If using the PAN Manager GUI, right-

    click in the console window and select Settings>Terminal to

    switch to vt220.

    You should eventually see the initial screen of the SLES10.1

    install:

    Select the language

    3. Follow the screen prompts to specify details of the SLES10.1

    install.

    As you proceed through the SLES10.1 install screens, note that

    some screens require specific responses to meet the needs of a

    vBlade pServer. Table 1.1 lists the first set of these screens and

    what you need to specify.

    Table 1.1 SLES10.1 Install Screens with SpecificRequirements for vBlade pServers

    Once you complete these screens (and a few other related

    prompts), the installation starts and start-up messages scroll by.

    4. The next several steps of the SLES10.1 install on your vBlade

    pServer involve using theYaST2 tool.When you see the following messages on the console, YaST2 is

    ready to access via the VNC viewer or a Java-capable browser

    (for details, see Preparing to Use the VNC Viewer on

    page 1-4):

    On This SLES10.1Install Screen

    Do This

    Main Menu Select Start Installation or System.

    Start Installation or

    System

    Select Start Installation or Update.

    Choose the sourcemedium

    Select Network.

    Choose the network

    protocol

    Select HTTP orNFS. (Only these protocols are currently supported

    for SLES10.1 on a vBlade pServer.)

  • 7/30/2019 Rx100 suse

    20/40

    Guest OS Installation for vBlades: SUSE Linux Enterprise Server 10.1

    1-10 VBXS2.1_BF

    starting VNC server...

    A log file will be written to: /var/log/YaST2/vncserver.log ...

    ***

    *** You can connect to nnn.nnn.nnn.nnn, display :1 now with vncviewer

    *** Or use a Java capable browser on http://nnn.nnn.nnn.nnn:5801/

    ***

    (When YaST2 is finished, close your VNC viewer and return to this window.)

    5. To access YaST2 via the VNC viewer:

    a. Open the VNC viewer on your client.

    b. When prompted forConnection Details, enter the vBlade

    pServers IP address and display information, in the format:

    nnn.nnn.nnn.nnn:1

    where nnn.nnn.nnn.nnnmatches the IP address displayed

    by the YaST2 message in Step 4.

    c. When prompted forAuthentication, enter the password

    that you passed as a boot argument to the install image in

    Step 1 on page 1-8.

    Once you connect, you begin a series ofYaST2 screens to

    configure the SLES10.1 installation.

    Note: If the VNC window loses the connection during the

    installation process, you can close it and open a new one toresume.

    6. When prompted forClock and Time Zone, make sure that the

    Hardware Clock Set To option specifies UTC.

    7. When prompted forInstallation Settings, make sure that your

    Partitioning specifications follow these guidelines:

    Use /dev/xvda (the pServers first SAN disk) as the root

    disk.

    Specify /dev/xvda1 (that disks first partition) as the boot

    partition. For example, you can create a single root partition

    for the disk (/dev/xvda1) that includes /boot, or create

    separate partitions for/boot (/dev/xvda1) and / (/dev/

    xvda2).

  • 7/30/2019 Rx100 suse

    21/40

    Installing SLES10.1 for vBlade pServers

    VBXS2.1_BF 1-11

    Specify Ext3, Ext2, orReiser as the file system type for the

    partition(s) that contain the root and boot file systems.

    Logical volumes are not supported for the first partition (/dev/

    xvda1).

    Swap partitions are supported, as usual.

    Note: If you plan to later make a root disk image from the

    pServer youre installing, you must adhere to the requirements

    listed in Chapter 3, Creating SLES10.1 Guests from Root Disk

    Images.

    8. Once youre done changing Installation Settings, clickAccept

    to perform the specified install. (Youll be prompted for

    confirmation before it starts.)

    When the basic installation is finished, the installer

    automatically reboots your vBlade pServer, this time using the

    default boot image (EVBS). YaST2 and the VNC viewerclose,

    and you return to the console.

    9. Look for these messages on the console:

    ***

    *** Please return to your X-Server screen to finish installation

    ***

    starting VNC server...

    A log file will be written to: /var/log/YaST2/vncserver.log ...

    ***

    *** You can connect to nnn.nnn.nnn.nnn, display :1 now with vncviewer

    *** Or use a Java capable browser on http://nnn.nnn.nnn.nnn:5801/

    ***

    (When YaST2 is finished, close your VNC viewer and return to this window.)

    Now reconnect to your vBlade pServer through the VNC

    viewer (just as you did in Step 5). This resumes your YaST2

    session so you can complete the SLES10.1 configuration.

    10. Proceed through the remaining YaST2 screens and specify

    SLES10.1 configuration settings according to your needs.

    11. When you reach the Installation Completed screen, click

    Finish.

  • 7/30/2019 Rx100 suse

    22/40

    Guest OS Installation for vBlades: SUSE Linux Enterprise Server 10.1

    1-12 VBXS2.1_BF

    YaST2 and the VNC viewer close. You return to the console and

    can now log in to your installed SLES10.1 guest.

    Booting SLES10.1 on Your vBlade pServer

    After the one-time boot of the SLES10.1 install kernel is over,

    subsequent boots of your vBlade pServer use thedefault boot

    image that you specified earlier (in Configuring Your vBlade and

    pServer on page 1-5). That image, EVBS, boots the pServer into

    the installed SLES10.1 operating system.

    EVBS flags PAN Manager to perform a disk boot of SLES10.1 for

    the vBlade pServer. The disk boot works by loading the appropriate

    kernel, boot options, and RAM disk (as needed) from the/boot

    partition (/dev/xvda1) of the pServers root disk (xvda).

    Installing the Xen Guest Agent

    If you plan to perform migration operations involving your

    installed vBlade pServer, you must also install theXen guest agent

    on it. The Xen guest agent provides the pServer with capabilities it

    requires to participate in these operations.

    To install the Xen guest agent, follow these steps:

    1. Make sure that yourguest OS is running on its vBlade pServer.

    2. Insert , a registered media image, in the VCD

    drive of the pServer. For example, in the PAN Manager CLI:

    # pserver --insert-vcd VBXS21_TOOLS mylpan/sles10

  • 7/30/2019 Rx100 suse

    23/40

    Installing SLES10.1 for vBlade pServers

    VBXS2.1_BF 1-13

    Note: If the VCD drive currently contains some other image,

    type this first: # pserver --eject-vcd mylpan/sles10.

    VBXS21_TOOLS contains an installer tool (/Linux/install.sh)

    for installing the Xen guest agent.

    3. Log on to the pServers console as root.

    4. Mount the VCD on the pServer:

    # mount /dev/hdd /mnt

    5. Run from the VCD on the pServer, and

    include the-k option (required to install just the Xen guest agent

    and skip kernel installation):

    # /mnt/Linux/install.sh -k

    For more information on migration operations, see theUsingvBlades book.

  • 7/30/2019 Rx100 suse

    24/40

    Guest OS Installation for vBlades: SUSE Linux Enterprise Server 10.1

    1-14 VBXS2.1_BF

  • 7/30/2019 Rx100 suse

    25/40

    VBXS2.1_BF 2-1

    Chapter 2

    Non-interactiveInstallation for SLES10.1

    Guests

    This chapter tells you how to perform a non-interactive install of a

    SUSE Linux Enterprise Server 10.1 (SLES10.1) guest for a vBlade

    pServer. Topics include:

    About Non-interactive Installs

    Performing a Non-interactive Install

    For general information on SLES10.1 guests and details on

    performing an interactive installation, seeChapter 1, Installing

    SLES10.1 for vBlade pServers.

  • 7/30/2019 Rx100 suse

    26/40

    Guest OS Installation for vBlades: SUSE Linux Enterprise Server 10.1

    2-2 VBXS2.1_BF

    About Non-interactive Installs

    In Chapter 1, Installing SLES10.1 for vBlade pServers, you

    learned how to install a SLES10.1 guest interactively. That

    approach is useful for your first SLES10.1 guest, because the

    installer:

    Walks you through the details of the install

    Creates a control file (AutoYaST profile) on the guests disk

    that captures information about how the installation is

    configured:

    /root/autoinst.xml

    If you have additional SLES10.1 guests to install, you may find it

    handy to install them non-interactively via this control file. That

    way, you can use the control file as a template for performing

    similar guest installs in an unattended manner.

    Performing a Non-interactive Install

    To perform a non-interactive install of a SLES10.1 guest, follow

    these steps:

    1. Examine the generated control file andedit it as needed for your

    target guest install.

    Make sure you follow the guidelines in Installing

    SLES10.1 on page 1-8 when editing installation settings.

    2. Copy your edited control file to an NFS server (on the same

    network as your target pServer).

    3. Go to Configuring Your vBlade and pServer on page 1-5(in

    Chapter 1, Installing SLES10.1 for vBlade pServers) and

    perform all of the steps in that section.

  • 7/30/2019 Rx100 suse

    27/40

    Non-interactive Installation for SLES10.1 Guests

    VBXS2.1_BF 2-3

    4. Go to Installing SLES10.1 on page 1-8and perform the first

    two steps to boot the pServer and open its console. The only

    difference is that your boot command must includespecial boot

    arguments (instead of the usual ones) to make this a non-

    interactive install (via NFS). For example, in the PAN Manager

    CLI:

    # pserver -b -I VBXS21_SLES1010nnnnI_IA32nnn.nnn.nnn.nnn nfs_pathnnn.nnn.nnn.nnn

    nfs_path_control_filescontrol_file mylpan/sles10

    Notes:

    The install keyword sets the install type and specifies

    where the installation content is to be found. The

    autoyast keyword sets the location of the control file.

    Make sure boot arguments do not exceed a combined

    length of 255 characters. Arguments that exceed this

    length may be truncated. If you need to shorten the strings

    above, one idea is to make a short symbolic link to the

    control file.

    If you specify these boot arguments in the PAN Manager

    GUI instead of the CLI, omit the surrounding quotes.

    The non-interactive SLES10.1 install begins.

  • 7/30/2019 Rx100 suse

    28/40

    Guest OS Installation for vBlades: SUSE Linux Enterprise Server 10.1

    2-4 VBXS2.1_BF

  • 7/30/2019 Rx100 suse

    29/40

    VBXS2.1_BF 3-1

    Chapter 3

    Creating SLES10.1Guests from Root Disk

    Images

    This chapter describes how you can use a root disk image (instead

    of the install process) to set up a new SUSE Linux Enterprise

    Server 10.1 (SLES10.1) guest for a vBlade pServer. Topics include:

    About Root Disk Images

    Preparing a SLES10.1 Root Disk Image Using a SLES10.1 Root Disk Image for a vBlade pServer

    For general information on SLES10.1 guests and details on

    performing an interactive installation, seeChapter 1, Installing

    SLES10.1 for vBlade pServers.

  • 7/30/2019 Rx100 suse

    30/40

    Guest OS Installation for vBlades: SUSE Linux Enterprise Server 10.1

    3-2 VBXS2.1_BF

    About Root Disk Images

    In Chapter 1, Installing SLES10.1 for vBlade pServers, you

    learned how to set up a SLES10.1 guest by stepping through the OS

    install process. That approach is recommended for your first

    SLES10.1 guest, but theres an alternative technique that can save

    you time and effort when creating additional guests of the same

    type.

    This technique involves preparing and using aroot disk image. It

    requires you to:

    1. Package directories and files copied from the root disk of an

    existing SLES10.1 guest into a root disk image

    2. Register that root disk image with PAN Manager

    3. Root one or more disks with that image, then associate each

    resulting SLES10.1 guest disk with a new vBlade pServer

    Requirements You must adhere to the following requirements when working with

    root disk images:

    Disk partitioning The guest root disk from which you createa root disk image must have exactly one partition for the OS.

    The root partition (/) should be /dev/xvda1.

    That root disk may also have a swap partition, and the /etc/

    fstab file in the root disk image will refer to it. In this scenario,

    after you root a new disk from your root disk image and boot the

    resulting guest OS, you must initialize the swap partition before

    use; for details, see Using a SLES10.1 Root Disk Image for a

    vBlade pServer on page 3-7.

    Do not use Reiser as the file system type when partitioning your

    root disk.

  • 7/30/2019 Rx100 suse

    31/40

    Creating SLES10.1 Guests from Root Disk Images

    VBXS2.1_BF 3-3

    Guest must not use LVM The root disk image must be

    created from a non-LVM guest (LVM is the Logical Volume

    Management feature of Linux). Make sure that guests root

    device is a SCSI device (/dev/xvda1), instead of an LVM

    device such as /dev/VolGroup00/LogVol00 .

    Preparing a SLES10.1 Root Disk Image

    Preparing a SLES10.1 root disk image for use involves:

    1. Packaging the Root Disk Image

    2. Registering the Root Disk Image

    Packaging the

    Root Disk Image

    Perform these steps in the PAN Manager CLI:

    1. Log on to the pServer console of your existing SLES10.1 guest:

    # console lpan_name/pserver_name

    2. Create a directory named /image_dir to use in making the

    root disk image:

    # mkdir /image_dir

    3. Create a temporary file named /tmp/ex_file to hold the list

    of directories and files that you want to exclude from the tar file

    youll be making for the root disk image.

    Note: All entries in the file must start with dot slash (./).

    Entries can contain wildcards (*).

    Insert the following entries in the /tmp/ex_file file:

    ./sys/*

    ./initrd/*

    ./tmp/*

    ./proc

    ./image_dir

  • 7/30/2019 Rx100 suse

    32/40

    Guest OS Installation for vBlades: SUSE Linux Enterprise Server 10.1

    3-4 VBXS2.1_BF

    4. Make sure that you are at the root directory:

    # cd /

    5. Create a tar file of the root disk and write the operation to a log

    file:

    # tar -cv -X /tmp/ex_file -f /image_dir/guest-root-SLES10-SP1-32bit.tar --preserve . > /tmp/tar.log2>&1

    Note: Be sure to use the dot character (.) after the --preserve

    option.

    If you do not have enough space in /image_dir, the tar

    operation fails with a message similar to /image_dir/guest-

    root-SLES10-SP1-32bit.tar Wrote only 46800 of 205574

    bytes. If this occurs, choose a different location (directory ormount point) to which to write the tar file, and change the

    /tmp/ex_file entry of./image_dir to be the name of the new

    directory or mount point; the name must start with dot slash

    (./).

    You can check for errors in the log files created by this

    procedure. Good practice is to usegrep; for example:

    # grep tar: /tmp/tar.log

    You can ignore tar: log entries that contain socket ignored.

    6. When you finish creating guest-root-SLES10-SP1-

    32bit.tar, open the file by using the following commands

    (assuming that your root disk image is in theimage_dir

    directory):

    # mkdir /image_dir/hold# cd /image_dir/hold# tar xvf /image_dir/guest-root-SLES10-SP1-32bit.tar--preserve > /tmp/tar.log2 2>&1

    7. Remove any unnecessary files (such as log files, history files,or ssh keys) from the extracted contents.

    8. Edit /etc/fstab (in the extracted contents) as follows:

    Replace each LABEL=valueentry that appears in the left-most

    column with a valid disk partition. For example, you would

    replace LABEL=/ with /dev/xvda1.

  • 7/30/2019 Rx100 suse

    33/40

    Creating SLES10.1 Guests from Root Disk Images

    VBXS2.1_BF 3-5

    9. Edit /boot/grub/menu.lst (in the extracted contents) as follows:

    Find the kernel argumentroot= for the Linux entry and replace

    the LABEL syntax with a valid disk partition (this root partition

    must be the same one you specified for/etc/fstab). For

    example, you would change:

    title Linuxkernel (hd0,0)/vmlinuz root= selinux=0splash=silent elevator=cfq showoptsinitrd (hd0,0)/initrd

    to:

    title Linuxkernel (hd0,0)/vmlinuz root= selinux=0splash=silent elevator=cfq showoptsinitrd (hd0,0)/initrd

    10. Edit /etc/sysconfig/network/ifcfg-eth-id:MACADDRESS (in

    the extracted contents) to replace -id:MACADDRESSof the

    filename with the number 0 (zero).

    You must replace this part of the filename to avoid MAC

    address problems with eth0 when booting.

    11. Remove the following rules files from the extracted contents so

    that any new eth devices created by PAN Manager will not be

    incremented from old device names (the ones from the original

    guest used to make the root disk image):

    /etc/udev/rules.d/30-net_persistent_names.rules

    12. Edit other configuration files (in the extracted contents), as

    needed.

    13. Change directory to /image_dir/hold (assuming that your

    root disk image is in the image_dir directory) if you arent

    already there:

    # cd /image_dir/hold

    14. Create a mount point for the egenera directory in the proc file

    system:

    # mkdir -p proc/egenera

    15. Remove the existing tar file:

    # rm /image_dir/guest-root-SLES10-SP1-32bit.tar

  • 7/30/2019 Rx100 suse

    34/40

    Guest OS Installation for vBlades: SUSE Linux Enterprise Server 10.1

    3-6 VBXS2.1_BF

    16. Recreate and compress the tar file:

    # tar -czvf /image_dir/guest-root-SLES10-SP1-32bit.tar.gz --numeric-owner --preserve . >/tmp/tar.log3 2>&1

    Note: Be sure to use the dot character (.) after the --preserveoption.

    17. Copy the root disk image to the /crash_dumps directory on

    one of your cBlades (specified by its IP address). For example:

    # scp /image_dir/guest-root-SLES10-SP1-32bit.tar.gz136.106.187.122:/crash_dumps

    18. To end the console session on the pServer, enter:

    # ~.

    Registering the

    Root Disk Image

    Perform these steps in the PAN Manager CLI:

    1. Log on to the same cBlade specified in Step 17 of the previous

    procedure.

    2. Register your new SLES10.1 root disk image with

    PAN Manager:

    # pan -a -R -C /crash_dumps/guest-root-SLES10-SP1-32bit.tar.gz -F fs_type-T os_type-P descriptionroot_image_name

    3. Delete your temporary copy of the root disk image

    (/crash_dumps/guest-root-SLES10-SP1-32bit.tar.gz).

  • 7/30/2019 Rx100 suse

    35/40

  • 7/30/2019 Rx100 suse

    36/40

    Guest OS Installation for vBlades: SUSE Linux Enterprise Server 10.1

    3-8 VBXS2.1_BF

  • 7/30/2019 Rx100 suse

    37/40

    VBXS2.1_BF 4-1

    Chapter 4

    Running SLES10.1Guests in Rescue Mode

    After you have installed a SUSE Linux Enterprise Server 10.1

    (SLES10.1) guest for a vBlade pServer, you have the option of

    running that guest in rescue mode when necessary. Rescue mode

    can help you access and repair your operating system when a

    problem occurs.

    To run a SLES10.1 guest in rescue mode:

    1. Boot your pServer from the customized SLES10.1 installkernel provided by Fujitsu Siemens Computers:

    VBXS21_SLES1010nnnnI_IA32 (as described in Chapter 1,

    Installing SLES10.1 for vBlade pServers).

    2. Use the SLES10.1 boot menu to start the Rescue System.

    3. When prompted, log on as root.

    While logged on to the SLES10.1 Rescue System, you can perform

    any rescue-related operations supported by this OS.

  • 7/30/2019 Rx100 suse

    38/40

    Guest OS Installation for vBlades: SUSE Linux Enterprise Server 10.1

    4-2 VBXS2.1_BF

  • 7/30/2019 Rx100 suse

    39/40

    VBXS2.1_BF 5-1

    Chapter 5

    Upgrading SLES10.1Guests

    After youve installed a SLES10.1 guest (according to the

    instructions earlier in this document), you can apply updates from

    the operating system vendor to the OS and kernel when needed.

    To apply such updates, use the OS vendors tools and

    procedures. No special steps are required.

    If you plan to perform migration operations involving an existingSLES10.1 guest, you must also install the latestXen guest agent on

    that vBlade pServer. For details, see Installing the Xen Guest

    Agent on page 1-12 (in Chapter 1, Installing SLES10.1 for

    vBlade pServers).

  • 7/30/2019 Rx100 suse

    40/40

    Guest OS Installation for vBlades: SUSE Linux Enterprise Server 10.1