#!/bin/sh

# network-xen-custom

# Exit if anything goes wrong

set -e

# First arg is operation.

OP=$1

shift

script=/etc/xen/scripts/network-bridge

case ${OP} in

        start)

                $script start vifnum=0 bridge=xenbr0 netdev=eth0

                $script start vifnum=1 bridge=xenbr1 netdev=eth1

                ;;

        stop)

                $script stop vifnum=0 bridge=xenbr0 netdev=eth0

                $script stop vifnum=1 bridge=xenbr1 netdev=eth1

                ;;

        status)

                $script status vifnum=0 bridge=xenbr0 netdev=eth0

                $script status vifnum=1 bridge=xenbr1 netdev=eth1

                ;;

        *)

                echo "Unknown command:${OP}"

                echo 'Valid commands are: start, stop, status'

                exit 1

esac

===============================================



2. Make Excute Table Set 



    chmod 755 /etc/xend/scripts/network-custom





3. Edit /etc/xen/xend-config-bridge

   

  (network-script network-xen-custom)



4. Restart System or XED Deamon 



   service xend restart

To resolve this issue, Grub must be reinstalled. To reinstall Grub on the multipath device perform the following procedure.

Note: This method has been validated on Red Hat Enterprise Linux 5.1 and 5.2.

1. leave only the mpath0 lun masked. Remove the other luns. This is very important, as writing to the other luns must be avoided.

2. Boot the system in rescue mode.

3. When rescue mode starts, do not search for any partitions, click on 'skip'

4. When the shell is spawned do the following:

   
   
    # mkdir /mnt/sysimage
   
    # mkdir /mnt/sysimage/boot
   
    # multipath -F
   
    # multipath -v0
   
    # multipath -l

    

5. Check to see if the mpath0 device is now there, then continue:

   
   
    # kpartx -a /dev/mapper/mpath0
   
    # lvm vgscan --config 'devices{ filter = [ "a/mapper/", "r/.*/" ] }'
   
    # lvm vgchange -ay --config 'devices{ filter = [ "a/mapper/", "r/.*/" ] }'
   
    # mount -t ext3 /dev/mapper/VolGroup00-LogVol00 /mnt/sysimage/
   
    # mount -t ext3 /dev/mapper/mpath0p1 /mnt/sysimage/boot/
   
    # mount -t proc none /mnt/sysimage/proc
   
    # chroot /mnt/sysimage
   
    # dmsetup mknodes mpath0
   
    # dmsetup mknodes mpath0p1
   
    # dmsetup mknodes mpath0p2 

    

6. In the chrooted environment, verify if /boot/grub/grub.conf is present and corresponds to the correct grub configuration. Also, verify if /boot/grub/devices.map contains the line:

   (hd0) /dev/mapper/mpath0

   If this is the case, run:

   # grub-install /dev/mapper/mpath0

    

7. Reboot the system and verify if it reboots properly.

In order to use the 'worker' MPM, you will need to create the file: /etc/sysconfig/httpd as teh root user and add the following line to that file:

HTTPD=/usr/sbin/httpd.worker

This will tell the httpd service to use the binary that is compiled to use the 'worker' MPM. (For more information, you will want to look at: /etc/rc.d/init.d/httpd)

Please keep in mind that the 'worker' MPM is a threaded environment andthat PHP is not considered thread-safe. Thus, if you have the followingfile: /etc/httpd/conf.d/php.conf then Apache will protest when you attempt to start it.

The work-around for this behavior (if you do not need PHP), is to rename the file to something that does not end in '.conf'.

So the following command (after making the above change to /etc/sysconfig/httpd):

mv /etc/httpd/conf.d/php.conf /etc/httpd/conf.d/php.conf.old

should allow you to start up Apache with this:

service httpd start

Important: For Red Hat Enterprise Linux 4 fully-virtualized guests install the latest version of up2date.

This procedure will work for both fully-virtualized and para-virtualized guests.

1. Thehost system (dom0) must be registered with Red Hat Network. Followstandard procedures to register this system with Red Hat Network (RHN).

2. Underthe System Properties page, subscribe the base system to theappropriate Virtualization Channel. Virtualization allows for up to 4Xen guest registrations, while Virtualization Platform allows for anunlimited number of Xen guest registrations.

3. Make sure that the virtualization add on entitlement is checked "Add-On Entitlements: Virtualization (0 open entitlements)".This is available via rhn.redhat.com --> Systems (Top Red Bar)--> Click on the host system --> Click Edit These Properties--> Check the add on entitlements box (Virtualization) --> Clickupdate properties. If you have Advanced Platform entitlement you cancheck the "Virtualization Platform" box instead to be able to registeran unlimited number of guests for this host.

4. Make sure that rhn-virtualization-common and rhn-virtualization-host are installed on the Host system. If they are not installed, run:

 yum install rhn-virtualization-common rhn-virtualization-host

1. Install the Xen guest.

2. Make sure that the Xen guest is running. Please note that xenguest is the name of the Xen guest.

   
   
    xm create xenguest
   
    

    

3. From the command line on the Host system, run:

   
   
    rhn_check
   
    

    

4. From the command line on the Host system, run:

   
   
    rhn-profile-sync
   
    

    

5. From the Xen guest, run:

   
   
    rhn_register
   
    

   Now the Xen Guest will show up as a registered, Virtualized system.