Cari di RHE Linux 
     RHE Linux User Manual
Daftar Isi ☛
(Sebelumnya) 14 : Chapter 4. Installation - ...15 : DM Multipath (Berikutnya)

Hypervisor Deployment Guide

Chapter 5. Configuration

5.1. Logging In
5.2. Status
5.3. Network
5.4. Security
5.5. Keyboard
5.6. SNMP (Simple Network Management Protocol)
5.7. Logging
5.8. Kernel Dump
5.9. Remote Storage
5.10. CIM (Common Information Model)
5.11. RHEV-M
5.12. Plugins
5.13. Red Hat Network

5.1. Logging In

The Hypervisor allows local console logins to facilitate post-installation configuration. The login prompt used is displayed once the Hypervisor has booted:
Please login as 'admin' to configure the nodelocalhost login:
Type admin at the prompt and press Enter. When prompted enter the password which was set during the installation process and press Enter again to log in.
The Hypervisor configuration menu will then be displayed. The menu facilitates interactive configuration of the Hypervisor. Throughout the remainder of this chapter it will be referred to as the main menu. The main menu provides access to multiple screens which report on the status and configuration of the hypervisor. They also provide the ability to change the hypervisor configuration.
The configuration interface is similar to that of the installation script. The same keys are used to navigate the menu and associated screens. Refer to Menu Actions to review the list of possible actions.

5.2. Status

The status screen displays a brief overview of the current state of the Hypervisor. The information displayed consists of:
  • the current status of the network connection, including the logical network, the device, and the MAC address;
  • the destination(s) of logs and reports;
  • the number of active virtual machines; and
  • the option to press F8 to access the Support menu.
The status screen also provides a number of buttons to change the state of the Hypervisor. They are:
<View Host Key>
Displays the RSA Host Key of the host machine, allowing you to validate that the correct machine is being used.
<View CPU Details>
Displays information about the CPU of the host machine.
<Lock>
Locks the Hypervisor. The username and password must be entered to unlock the Hypervisor.
<Log off>
Log off from the Hypervisor.
<Restart>
Restarts the Hypervisor.
<Power Off>
Turns the Hypervisor off.

5.3. Network

The Network screen is used to configure:
  • the Hypervisor's hostname,
  • the DNS server(s) to use,
  • the NTP server(s) to use, and
  • the network interface to use.
The <Ping Test> button allows you to test network access to a specified host address.

Procedure 5.1. Hostname Configuration

  1. To set or change the hostname select the Hostname field and enter the new hostname.
  2. Select <Apply>, and press Enter to save changes to the hostname.
The hostname is updated.

Procedure 5.2. DNS Configuration

The Hypervisor supports the manual specification of one or more Domain Name System (DNS) servers to use when resolving host and domain names. Where the DNS server(s) chosen do not validate they will be blanked out and ignored.
  1. To set or change the primary DNS server select the DNS Server 1 field and enter the IP address of the new primary DNS server to use.
  2. To set or change the secondary DNS server select the DNS Server 2 field and enter the IP address of the new secondary DNS server to use.
  3. Select <Apply>, and press Enter to save changes to the DNS configuration.
The primary and secondary DNS servers queried by the Hypervisor are updated.

Procedure 5.3. NTP Configuration

The Hypervisor supports the specification of one or more Network Time Protocol (NTP) servers with which the Hypervisor should synchronize the system clock. It is important that the Hypervisor is synchronized with the same time source as the Red Hat Enterprise Virtualization Manager. This ensures accurate time keeping across the Red Hat Enterprise Virtualization environment.
  1. To set or change the primary NTP server select the NTP Server 1 field and enter the IP address or hostname of the new primary NTP server to use.
  2. To set or change the secondary NTP server select the NTP Server 2 field and enter the IP address or hostname of the new secondary NTP server to use.
  3. Select <Apply>, and press Enter to save changes to the NTP configuration.
The primary and secondary NTP servers queried by the Hypervisor are updated.

Procedure 5.4. Network Interface Configuration

For each network interface detected the Hypervisor will display the:
  • Device,
  • Status,
  • Model, and
  • MAC Address.
At least one network interface must be configured before the Hypervisor is able to connect to the Red Hat Enterprise Virtualization Manager.

  1. Device Identification

    Select the network interface to be configured from the list and press Enter.
    In some cases it may be unclear which physical device an entry in the list refers to. Where this is the case the Hypervisor is able to blink the physical device's network traffic lights to assist with identification. To make use of this facility select the entry from the list and, then select the <Flash Lights to Identify> button. Press Enter and, take note of which physical device's lights start blinking. The configuration screen for the selected device will be displayed.

  2. IPv4 Settings

    The Hypervisor supports both dynamic (DHCP), and static IPv4 network configuration.

    • Dynamic (DHCP) Network Configuration

      Dynamic network configuration allows the Hypervisor to be dynamically assigned an IP address via DHCP. To enable dynamic IPv4 network configuration select the DHCP option under IPv4 Settings and press Space to toggle it to enabled.

    • Static Network Configuration

      Static network configuration allows the Hypervisor to be manually assigned an IP address. To enable static IPv4 network configuration select the Static option under IPv4 Settings and press Space to toggle it to enabled.
      Selection of the Static option enables the IP Address, Netmask, and Gateway fields. The IP Address, Netmask, and Gateway fields must be populated to complete static network configuration.
      In particular it is necessary that:
      • the IP Address is not already in use on the network,
      • the Netmask matches that used by other machines on the network, and
      • the Gateway matches that used by other machines on the network.
      Where it is unclear which value should be used for the IP Address, Netmask, or Gateway field, consult the network's administrator or consider a dynamic configuration.

      Example 5.1. Static IPv4 Networking Configuration

      IPv4 Settings[ ] Disabled [ ] DHCP [*] StaticIP Address: 192.168.122.100_ Netmask: 255.255.255.0___Gateway 192.168.1.1_____

  3. VLAN Configuration

    If VLAN support is required then populate the VLAN ID field with the VLAN identifier for the selected device.

  4. Save Network Configuration

    When you are satisfied that your configuration details are correct, you must apply and save the network configuration.
    1. Select the <Apply> button and press Enter to save the network configuration.
    2. The Confirm Network Settings dialog box will appear. Ensure that the Ok button is selected and press Enter to confirm.
The Network screen is displayed. The device is listed as Configured.

5.4. Security

The Security screen is used to change the admin password for both local and remote access. SSH password authentication is also enabled or disabled via this screen.

Procedure 5.5. Change Security Configuration

  1. Enable SSH Password Authentication

    To enable SSH password authentication for remote access select the Enable ssh password authentication option and press Space to toggle it to enabled.

    Important

    SSH password authentication is disabled by default and is not supported unless enabled at the request of Red Hat support.

  2. Disable Advanced Encryption Standard

    The Intel Advanced Encryption Standard (AES) New Instructions (AES-NI) engine is available for certain Intel processors, and allows for extremely fast hardware encryption and decryption. Further information is available from http://software.intel.com/en-us/articles/intel-advanced-encryption-standard-instructions-aes-ni/
    To disable AES-NI, select Disable AES-NI and press Space.
    If AES-NI is enabled, you can set the length of the encryption key used by entering a value in the Bytes Used field.

  3. Change admin Password

    1. Enter the desired admin password in the Password field. You should use a strong password.
      Strong passwords contain a mix of uppercase, lowercase, numeric and punctuation characters. They are six or more characters long and do not contain dictionary words.
    2. Enter the desired admin password in the Confirm Password field. Ensure that the value entered in the Confirm Password field matches the value entered in the Password field exactly. Where this is not the case an error message will be displayed to indicate that the two values are different.
  4. Select <Apply> and press Enter to save the security configuration.
The security configuration has been updated.

5.5. Keyboard

The Keyboard screen allows you to configure the appropriate keyboard layout for your locale. Use the arrow keys to highlight the appropriate option. To save your selection, use Tab to move to Apply, and press Enter.

Example 5.2. Keyboard Layout Configuration

Keyboard Layout Selection| Swiss German (latin1) || Slovak (qwerty)  || Slovenian || Serbian  || Serbian (latin)  || Swedish  || Turkish  || Ukrainian || United Kingdom   || *** U.S. English ******************* |  <Apply>   <Reset>

5.6. SNMP (Simple Network Management Protocol)

The SNMP screen allows you to enable and configure a password for Simple Network Management Protocol.
To enable SNMP, press Tab until [ ] Enable SNMP is highlighted, and press Space to toggle Enable SNMP to enabled.
[*] Enable SNMP
Press Tab to move to the Password field, and type your desired password. Press Tab to move to the Confirm Password field and type the same password again, to confirm that no typographical error has been made. Then use Tab to move to Apply, and press Enter.

Example 5.3. SNMP Configuration

SNMP[ ] Enable SNMPSNMP PasswordPassword: _______________Confirm Password: _______________  <Apply>   <Reset>

5.7. Logging

The Hypervisor creates and updates a number of log files. The Logging screen allows configuration of a daemon to automatically export these log files to a remote server.

Procedure 5.6. Change Logging Configuration

  1. Logrotate Configuration

    The logrotate utility simplifies the administration of log files. The Hypervisor uses logrotate to rotate logs when they reach a certain file size.
    Log rotation involves renaming the current log(s) and starting new ones in their place. The Logrotate Max Log Size value set on the Logging screen is used to determine when a log should be rotated.
    Enter the Logrotate Max Log Size in kilobytes. The default maximum log size is 1024 kilobytes.

  2. Rsyslog Configuration

    The rsyslog utility is a multithreaded syslog daemon. The Hypervisor is able to use rsyslog to transmit log files over the network to a remote syslog daemon. For information on setting up the remote syslog daemon consult the Red Hat Enterprise Linux Deployment Guide.
    1. Enter the remote Rsyslog server address in the Server Address field.
    2. Enter the remote Rsyslog server port in the Server Port field. The default port is 514.

  3. netconsole Configuration

    The netconsole module allows kernel messages to be sent to a remote machine. The Hypervisor uses netconsole to transmit kernel messages over the network.
    1. Enter the Server Address.
    2. Enter the Server Port. The default port is 6666.

  4. Save Configuration

    To save the logging configuration select <Apply> and press Enter.
The logging configuration has been updated. Logs will be exported to the remote Rsyslog server specified, and kernel messages will be sent to the specified netconsole server.

5.8. Kernel Dump

Red Hat Enterprise Virtualization Hypervisor hosts generate a kernel dump (a kdump file) in the event of a system failure. These kdump files are essential for debugging and support.
The Hypervisor supports the export of kernel dumps by kdump using NFS or SSH so that they can be analyzed at a later date. Alternatively the hypervisor is able to store the kernel dumps locally. The Kernel Dump screen provides for configuration of this facility.

  1. Kernel Dump Configuration

    Crash dumps generated by kdump are exported over NFS or SSH. Select the desired transfer method and press Space to enable it. Alternatively, to keep the kernel dumps on the hypevisor's local storage, select Restore (local) and press Space to enable it. This action also disables any previously configured kernel dump export options.
    Where export of the kernel dumps over NFS or SSH is chosen a location to which the kdump files will be exported to must also be specified.

    1. NFS location

      Set the NFS location to which crash logs should be exported in the NFS Location field. The NFS Location should be the full NFS path which includes fully qualified domain name and directory path.

      Example 5.4. NFS Location

      example.redhat.com:/var/crash

    2. SSH location

      Set the SSH location to which crash logs should be exported in the SSH Location field. The SSH Location should be the full SSH login which includes the fully qualified domain name and username.

      Example 5.5. SSH Location

      [email protected]

  2. Save Configuration

    To save the configuration the user must select <Apply> and press Enter.
The Kernel Dump configuration has been updated and kernel dumps will be exported to the remote server(s) specified.

5.9. Remote Storage

The Hypervisor supports the use of a remote iSCSI initiator for storage. The iSCSI initiator to use is set on the Remote Storage screen.

Procedure 5.7. Remote Storage Configuration

  1. iSCSI Initiator Name

    Enter the initiator name in the iSCSI Initiator Name field. The iSCSI initiator name is expected to take the form of an iSCSI Qualified Name (IQN). This format is defined by RFC 3720, which is available at http://tools.ietf.org/html/rfc3720.
    The IQN is made up of the following elements, separated by the . character:
    • the literal string iqn,
    • the date that the naming authority took control of the domain in yyyy-mm format,
    • the reversed domain name - demo.redhat.com becomes com.redhat.demo, and
    • optionally, a storage target name as specified by the naming authority - preceded by a colon.

    Example 5.6. iSCSI Initiator Name

    iqn.2011-08.com.redhat.demo:target1

  2. Set the NFSv4 Domain

    Defines the local NFSv4 domain name. An NFSv4 domain is a namespace with a unique username to user identifier and groupname to group identifier mapping.

  3. Save Configuration

    To save the configuration the user must select <Apply> and press Enter.
The Remote Storage configuration has been updated.

5.10. CIM (Common Information Model)

Enabling and configuring CIM attaches the Hypervisor to your pre-existing CIM management infrastructure, allowing your infrastructure to monitor this Hypervisor's virtual machines.

Example 5.7. CIM Configuration

CIM Configuration[ ] Enable CIMCIM AccessPassword: ______________Confirm Password: ______________   <Apply> <Reset>

5.11. RHEV-M

To configure the Hypervisor to connect to the Red Hat Enterprise Virtualization Manager, you must provide the details of the server on which the manager resides. The settings entered on the Hypervisor must match those that were used during installation of the Red Hat Enterprise Virtualization Manager.

Important

Setting a password on the RHEV-M configuration screen sets the hypervisor's root password and enables SSH password authentication. Once the hypervisor has successfully been added to the manager it is recommended that SSH password authentication is disabled.

Procedure 5.8. RHEV-M Configuration

    • Configuration Using a Management Server Address

      1. Enter the IP address or fully qualified domain name of the manager in the Management Server field.
      2. Enter the management server port in the Management Server Port field. The default value is 443. Where a different port was selected during Red Hat Enterprise Virtualization Manager installation then it should be specified here, replacing the default value.
      3. Enable the Verify RHEVM Certificate option if you wish to verify that the finger print of the certificate retrieved from the management server you specified is correct. The value that the certificate finger print should be compared against is returned at the end of Red Hat Enterprise Virtualization Manager installation.
      4. Leave the Password and Confirm Password fields blank. These fields are not required if the address of the management server is known.

    • Configuration Using a Password

      1. Enter a password in the Password field. It is recommended that you use a strong password. Strong passwords contain a mix of uppercase, lowercase, numeric and punctuation characters. They are six or more characters long and do not contain dictionary words.
      2. Re-enter the password in the Confirm Password field.
      3. Leave the Management Server and Management Server Port fields blank. As long as a password is set, allowing the hypervisor to be added to the manager later, these fields are not required.

  2. Save Configuration

    To save the configuration the user must select <Apply> and press Enter.
The RHEV-M configuration has been updated.
If you need further assistance with this task, refer to the Red Hat Enterprise Virtualization Administration Guide chapter on Red Hat Enterprise Virtualization Hosts.

5.12. Plugins

This screen lists any modifications made with edit-node prior to installation, such as driver update packages. Select <View Details> to view more details about the available plugins.

5.13. Red Hat Network

Virtual machines running on the hypervisor may need to consume Red Hat Enterprise Linux virtualization entitlements. Where this is the case the hypervisor must be registered to Red Hat Network or a Satellite server. The hypervisor is able to connect to these services via a HTTP proxy where one is in use.
Note that when new versions of the hypervisor itself become available they are installed from the Red Hat Enterprise Virtualization Manager, not Red Hat Network.

Procedure 5.9. Register with Red Hat Network

  1. Authentication

    Enter your Red Hat Network username in the Login field.
    Enter your Red Hat Network password in the Password field.

  2. Profile Name

    Enter the profile name to be used for the system in the Profile Name field. This is the name that the system will appear under when viewed via the Red Hat Network.

  3. Update Source

    Virtual machines running on the hypervisor may need to consume Red Hat Enterprise Linux virtualization entitlements. Where this is the case the hypervisor must be registered to Red Hat Network or, if available, either a Satellite installation or a Subscription Asset Manager. The hypervisor can connect to these services via a HTTP proxy where one is in use. Proxy configuration is described in Step 4.

    • To Connect Directly to RHN

      Select the RHN option and press Space to toggle it to enabled. The URL and CA values do not need to be provided.

      Example 5.8. Red Hat Network Configuration

      [*] RHN [ ] Satellite [ ] Subscription Asset Manager   URL:  ________________________________________ CA :  ________________________________________

    • To Connect via Satellite

      1. Select the Satellite option and press Space to toggle it to enabled.
      2. Enter the URL of the Satellite server in the URL field.
      3. Enter the URL of the Certificate Authority for the Satellite server in the CA field.

      Example 5.9. Satellite Configuration

      [ ] RHN [*] Satellite [ ] Subscription Asset ManagerURL:   https://your-satellite.example.comCA :   https://your-satellite.example.com/pub/RHN-ORG-TRUSTED-SSL-CERT

    • To Connect via Subscription Asset Manager

      1. Select the Subscription Asset Manager option and press Space to toggle it to enabled.
      2. Enter the URL of the Subscription Asset Manager server in the URL field.
      3. Enter the URL of the Certificate Authority for the Subscription Asset Manager server in the CA field.

      Example 5.10. Subscription Asset Manager Configuration

      [ ] RHN [ ] Satellite [*] Subscription Asset Manager   URL:  https://subscription-asset-manager.example.com CA :  https://subscription-asset-manager.example.com/pub/RHN-ORG-TRUSTED-SSL-CERT

  4. HTTP Proxy

    Where a HTTP proxy is in use the details to connect to it must be provided. To connect to the Red Hat Network or a Satellite server via a proxy you must enter:
    • the proxy Server's network address,
    • the Port to connect to the proxy on, and
    • optionally, the Username and Password to use to connect to the proxy.
    In environments where a HTTP proxy is not in use, it is safe to ignore this step.

    Example 5.11. HTTP Proxy Configuration

    HTTP ProxyServer: proxy.example.com__ Port: 80_Username: puser________ Password: ******_______

  5. Save Configuration

    To save the configuration the user must select <Apply> and press Enter.
The Red Hat Network configuration has been updated.

Chapter 6. Upgrading Red Hat Enterprise Virtualization Hypervisors

6.1. Upgrading a Hypervisor with the Manager
6.2. Upgrading a Red Hat Enterprise Virtualization Hypervisor with local media
6.3. Re-installing Hypervisors with the Manager
Red Hat Enterprise Virtualization Hypervisors can be updated to get the latest features, bug fixes and security patches.

6.1. Upgrading a Hypervisor with the Manager

You can upgrade and reinstall a Red Hat Enterprise Virtualization Hypervisor host from an ISO image stored on the Red Hat Enterprise Virtualization Manager. Upgrading and reinstalling means that you are stopping and restarting the host. Virtual machines are automatically migrated to a different host, however it is recommended that the upgrade is performed at a time when usage of the system is at its lowest. Ensure that the cluster contains more than one host before performing an upgrade.
It is recommended that administrators update Red Hat Enterprise Virtualization Hypervisors regularly. Important bug fixes and security updates are included in updates. Hypervisors which are not up to date may be a security risk.

Warning

Upgrading Hypervisor hosts involves shutting down and deactivating virtual machines, and restarting the physical server. If any virtual machines are running on the Hypervisor, all data and configuration details may be destroyed if they are not shut down. Upgrading Hypervisors must be carefully planned and executed with care and consideration.
Prerequisites
Before upgrading a Hypervisor:
  1. Download the latest Red Hat Enterprise Virtualization Hypervisor package from Red Hat Network. It is available at https://rhn.redhat.com/rhn/channels/PackageList.do?cid=12564. Install the package on the Red Hat Enterprise Virtualization Manager server.

Important

Ensure that the cluster contains more than one host before performing an upgrade. Do not attempt to re-install or upgrade all the hosts at the same time, as one host must remain available to perform Storage Pool Manager (SPM) tasks.

Procedure 6.1. Upgrading a Red Hat Enterprise Virtualization Hypervisor

  1. Click the Hosts tab. A list of hosts displays. Select the host that you intend to upgrade.
    If the host is not displayed, or the list of hosts is too long to filter visually, perform a search to locate the host.
  2. On the Details pane, click the General Tab.
    An Alert Message indicates that a new version of the Red Hat Enterprise Virtualization Hypervisor is available. The Upgrade link is disabled if the host is has a status of Up. A tooltip directs you to switch to maintenance mode to enable upgrade.
  3. Select the host and click the Maintenance button. This will cause any virtual machines running on the host to be migrated to other hosts. If the host is the SPM, this function will be moved to another host. The status of the host changes as it enters maintenance mode. When the host status is Maintenance, the message in the general tab changes, providing you with a link which when clicked will re-install or upgrade the host.
  4. Click the link. The Install Host dialog displays.
  5. Select the appropriate file from the list of available ISOs to upgrade the host. This is usually rhev-hypervisor.iso.
  6. Click OK to upgrade and re-install the host. The dialog closes, the details of the host are updated in the Hosts tab, and the status changes appropriately.
    The host status transitions through the following stages: Installing, Reboot, Non Responsive, and Up. These are all expected, and each stage will take some time.
  7. Once successfully upgraded, the host displays a status of Up. Any virtual machines that were migrated off the host can now be migrated back onto the upgraded host.

6.2. Upgrading a Red Hat Enterprise Virtualization Hypervisor with local media

It is possible to upgrade to new versions of the Hypervisor using local media. Before commencing the upgrade process it is necessary to prepare the local media with the latest version of the Hypervisor.
Once prepared the local media is used to boot the Hypervisor with the upgrade parameter as described in Procedure 6.2, "Upgrading the Hypervisor with local media".

Procedure 6.2. Upgrading the Hypervisor with local media

  1. Insert the installation media, and start the system.
  2. Start the system. When the automatic boot prompt appears, press Enter.
    Automatic boot in 30 seconds...
  3. Select the Install or Upgrade option, and press Tab to enter edit mode.
  4. The kernel parameters in use are displayed. Append the upgrade parameter to the list.
    vmlinuz0 initrd=initrd0.img root=live:CDLABEL=rhev-hypervisor rootfstype=auto ro liveimg nomodeset check rootflags=ro crashkernel=512M-2G:64M,2G-:128M elevator=deadline processor.max_cstate=1 install rhgb rd_NO_LUKS rd_NO_MD rd_NO_DM upgrade
The Red Hat Enterprise Virtualization Hypervisor is upgraded.

6.3. Re-installing Hypervisors with the Manager

Re-installing Red Hat Enterprise Virtualization Hypervisors is the same procedure as upgrading, refer to Procedure 6.1, "Upgrading a Red Hat Enterprise Virtualization Hypervisor" for details on upgrading.
To reset settings, remove the existing Hypervisor installation, as documented in Appendix C, Uninstallation, and then re-install the Hypervisor.

Security topics

The Red Hat Enterprise Virtualization Hypervisor has various security features enabled. Security-Enhanced Linux (SELinux) and the iptables firewall are fully configured and on by default.
Administrators can receive the latest security advisories from the Red Hat Enterprise Virtualization watch list. Subscribe to the Red Hat Enterprise Virtualization watch list to receive new security advisories for Red Hat Enterprise Virtualization products by email. Subscribe by completing this form: http://www.redhat.com/mailman/listinfo/rhev-watch-list/.
Red Hat Enterprise Virtualization uses various network ports for management and other virtualization features. These ports must be open for Red Hat Enterprise Linux to function as a host with Red Hat Enterprise Virtualization. The list below covers ports and their usage by Red Hat Enterprise Virtualization:
  • ICMP requests must be accepted. ICMP packets are used for network testing by the Manager.
  • Port 22 should be open for SSH access and the initial installation.
  • Port 161 is used for SNMP (Simple Network Management Protocol).
  • Ports 5634 to 6166 are used for guest console access.
  • Ports 80 or 443 (depending on the security settings on the Manager) are used by the vdsm-reg service to communicate information about the host.
  • Port 16514 is used to support migration communication generated by libvirt.
  • Ports 49152 to 49216 are used for migrations. Migration may use any port in this range depending on the number of concurrent migrations occurring.
  • Port 54321 is used by default, by VDSM for management, storage and inter-host communication. This port can be modified.
  • Port 5989 is the default port used to communicate with Common Information Model (CIM) management infrastructure, if configured.

Filesystem layout

This appendix provides an overview of the file system layout used by the Red Hat Enterprise Virtualization Hypervisor. The hypervisor directory layout provides a number of top level directories in addition to those provided by a standard Red Hat Enterprise Linux installation.
/config
The /config directory contains all persistent configuration files for the Red Hat Enterprise Virtualization Hypervisor. These files control passwords, storage configuration, security and networking.
The /config directory must be at least 8 MB in size.
/boot
The /boot directory contains the configuration files, kernel and initramfs used to boot the system.
/liveos
As of Red Hat Enterprise Linux 6.3, this directory is no longer used. Previously, this directory contained a compressed Red Hat Enterprise Virtualization Hypervisor live CD image, and was not normally visible on the running system.
/var/log
Contains all the logs for the Hypervisor.
The log directory must be at least 2048 MB. The default size of the log directory is 2048 MB.
/var/log/core
Contains core dumps from the Hypervisor which can be used for debugging and support.
/var/run/vdsm/
The /var/run/vdsm/ is used by the vdsmd daemon for storing volatile data.
/var/lib/vdsm/
The /var/lib/vdsm/ is used by the vdsmd daemon for storing data that should survive reboot.
/rhev/data-center
Contains links to Storage Domains.
/data
This directory contains virtual machine cache data and other miscellaneous files.
The data partition must be at least as large as the RAM on the host system plus an additional 512 MB in size. A data partition at least one and a half times as large as the RAM on the host system is recommended.
The default size for the data partition is the remaining available disk space.

Uninstallation

This appendix covers uninstallation of the Red Hat Enterprise Virtualization Hypervisors from local storage devices.

Warning

All data on the selected storage device(s) will be destroyed.

Procedure C.1. Removing Red Hat Enterprise Virtualization Hypervisors

  1. Boot the Hypervisor. Refer to Chapter 3, Preparing Red Hat Enterprise Virtualization Hypervisor Installation Media for details on booting Red Hat Enterprise Virtualization Hypervisors.
  2. Start the system. When the automatic boot prompt appears, press Enter.
    Automatic boot in 30 seconds...
  3. Select the Uninstall option, and press Tab to enter edit mode.
  4. The kernel parameters in use are displayed. These are the parameters passed to the kernel when starting the Hypervisor.
    vmlinuz0 initrd=initrd0.img root=live:CDLABEL=rhev-hypervisor rootfstype=auto ro liveimg nomodeset check rootflags=ro crashkernel=512M-2G:64M,2G-:128M elevator=deadline processor.max_cstate=1 install rhgb rd_NO_LUKS rd_NO_MD rd_NO_DM uninstall
    The uninstall parameter is added automatically and specifies that the Hypervisor is to be uninstalled.
  5. Optionally, add the storage_init parameter to the end of the kernel command string.
    The storage_init parameter specifies the device on which the Hypervisor resides. During uninstallation, it specifies the device from which the Hypervisor should be removed. If the Hypervisor is installed to the /dev/sda/ device, you can specify that this device is cleaned by including the following at the end of the kernel command string:
    storage_init=/dev/sda
    If this parameter is not included, the Hypervisor's location is detected automatically.
  6. Press Enter to save any changes to the kernel string, for this boot only, and display the previous screen.
  7. Press Enter to boot the Hypervisor. The Hypervisor will uninstall itself immediately. Once the Hypervisor has been removed the system will reboot.
The Red Hat Enterprise Virtualization Hypervisor has been removed from the specified device.

Revision History

Revision History
Revision 4.0-24Mon Feb 18 2013Tahlia Richardson
Version for 6.4 GA release.
Revision 4.0-23Mon Feb 18 2013Tahlia Richardson
Changed author tags to fix glitch.
Revision 4.0-22Mon Feb 18 2013Tahlia Richardson
Changed "8443" to "443" and "8080" to "80" in Security_Topics.xml and "8080" to "80" in Configuration.xml (BZ#908142).
Revision 4.0-21Thurs Feb 14 2013Tahlia Richardson
Changed the default Management Server Port from "8443" to "443" in Configuration.xml and Installation.xml (BZ#908142).
Revision 4.0-20Wed Feb 6 2013Tahlia Richardson
Changed "component" to "product" in Feedback.xml as requested in BZ#907700.
Revision 4.0-19Thu Jan 17 2013Laura Bailey
Added ata to the list of valid storage_init values, corrected command syntax (BZ#889086).
Revision 4.0-17Wed Nov 21 2012Laura Bailey
Added description of the local_boot_trigger parameter (BZ#875019).
Removed Hypervisor Requirements section from PressGang CCMS to work around a bug in topic imports and update terms for consistency (BZ#813622).
Revision 4.0-15Mon Nov 05 2012Laura Bailey
Ensuring that the rhn_org parameter is visible (BZ#867042).
Revision 4.0-14Tue Oct 22 2012Laura Bailey
Applied QE feedback for BZ#853293.
Corrected CIM parameter name (BZ#869515).
Added details about the new edit-node tool BZ#839774.
Revision 4.0-13Thu Oct 18 2012Laura Bailey
Added iSCSI boot parameters (BZ#853313).
Added information about Driver Update Package injection, and adjusted details about the Plugin screen of the configuration TUI accordingly BZ#839774>
Revision 4.0-11Thu Oct 18 2012Laura Bailey
Updated screenshots and added new installation options (BZ#830678).
Updated tool and package names (BZ#857534).
Added description of new TUI configuration screens and added details about previously undocumented portions of the TUI (BZ#853293).
Added new rhn_org parameter (BZ#867042).
Revision 4.0-9Mon Oct 15 2012Laura Bailey
Removed duplicate section.
Applied QE feedback regarding word usage (BZ#813622).
Revision 4.0-8Wed Oct 10 2012Laura Bailey
Applied QE feedback regarding command syntax (BZ#834223).
Applied SME feedback regarding installation parameters (BZ#830715).
Revision 4.0-7Tue Oct 09 2012Laura Bailey
Applied SME feedback regarding RHEV-H file layout (BZ#831171).
Applied QE feedback regarding UEFI (BZ#830696).
Revision 4.0-6Fri Sep 21 2012Laura Bailey
Updated storage_vol parameter description to reflect new syntax (BZ#831166).
Revision 4.0-4Wed Sep 19 2012Laura Bailey
Corrected directory descriptions (BZ#831171).
Added the View Host Key option to the description of the Status configuration screen (BZ#829680).
Corrected typographical errors (BZ#830696, BZ#830674).
Added parameters to the Installation chapter (BZ#834223).
Revision 4.0-3Tue Sep 11 2012Laura Bailey
Updated default value of the rhn_type parameter (BZ#854092).
Corrected description of the dns parameter (BZ#834286).
Added default port used by CIM (BZ#831891).
Corrected the default port used by netconsole (BZ#830719).
Revision 4.0-2Tue Sep 4 2012Laura Bailey
Updating URLs that referred to docs.redhat.com to reflect the move to access.redhat.com/knowledge/docs and removing pubsnumber
Revision 4.0-1Wednesday June 06 2012Laura Bailey
Updated virtual machine support limits and transferred xref to new topic repository (BZ#757630).
Added CIM configuration screen to the configuration chapter (BZ#821105).
Updated parameter description for firstboot/reinstall (BZ#753727).
Replaced cdrecord usage with the replacement package, wodim (BZ#790452).
Corrected misleading statement about possible update sources in configuration chapter (BZ#803440)
Ensured consistent use of guest virtual machine vs guest operating system (BZ#813622).
Minor changes to underlying document structure to improve cohesion (BZ#826828).
Added detail to the Required Parameters section (BZ#829456)
Revision 3.0-10Tuesday May 08 2012Laura Bailey
Added details about the UEFI Technology Preview (BZ#813852).
Revision 3.0-9Thursday March 08 2012Laura Bailey
Added admonition about the admin credential requirement when subscribing to channels via command line (BZ#772031).
Revision 3.0-8Wednesday March 07 2012Laura Bailey
Added new Subscription Asset Manager option to the text install procedure (BZ#734515).
Added SNMP Configuration screen to the Configuration chapter (BZ#795527).
Added Keyboard Layout Configuration screen to the Configuration chapter (BZ#800494).
Revision 3.0-7Monday March 05 2012Laura Bailey
Added details of a new kernel parameter, rhn_type (BZ#734515).
Documented the use of F8 to access support menu after Hypervisor installation (BZ#734515).
Added details and corrected minor style issues in existing Section 3.3, "Deploying Hypervisors with PXE and tftp" (BZ#745209).
Updated automated installation requirements and management_server parameter details (BZ#772716).
Added missing title to procedure (BZ#784626)
Revision 2-2Friday December 21 2011Stephen Gordon
Corrected Red Hat Network download links for hypervisor packages.
Revision 2-1Thursday December 20 2011Laura Bailey
Added additional port required for SNMP.
Updated the port used by libvirt.
Updated the list of options available to users in the Status menu.
Minor changes to improve consistency throughout the document.
Revision 2-0Friday December 02 2011Laura Bailey
Release for GA of Red Hat Enterprise Linux 6.2
Updated Preparation instructions for Red Hat Enterprise Linux 6.2.
Documented new workflow to add a Hypervisor node, and related password parameter.
Revision 1-0Thursday June 23 2010Stephen Gordon
Updated USB boot media creation instructions.
Updated PXE boot media creation instructions.
Updated installation instructions to match new UI.
Updated configuration instructions to match new UI.
Added documentation of new kernel parameters.
(Sebelumnya) 14 : Chapter 4. Installation - ...15 : DM Multipath (Berikutnya)