Red Hat NETWORK SATELLITE 5.1.1 Reference Manual page 182

Chapter 8. Virtualization
2. To schedule a kickstart for a guest system, go to the Virtualization
system's profile. For the Guest Name field choose guest1. For the Memory Allocation, Virtual
CPUs, and Storage fields, the default values should be fine. Feel free to change these as desired,
taking note of the advice provided for each field in the interface. For the Kickstart Profile field,
select the guest system profile we created in the last step.
3. Finally, click on the Schedule Kickstart and Finish button in the lower-right corner of the screen.
You will be taken to the Kickstart Status page where you can follow along with the guest's kickstart
progress. After ten to fifteen minutes the status screen should indicate the kickstart successfully
completed. To view your new guest, click on the Virtualization tab of the host system's profile on
the Satellite. To view a list of virtual host systems indicating which guest systems are hosted on
each, navigate to Systems
Note
If you do not see the Initiate a kickstart for a Xen guest message on the Kickstart
Status page shortly after scheduling the kickstart of the guest, you may be missing
osad on your host.
Host systems require the osad package in order to be responsive to commands
sent from the Satellite, such as start, pause, resume, and shutdown. If osad is not
installed and running, the host system will not receive these commands from the web
interface for 2.5 hours, or the next time that the RHN daemon runds.
You can check whether or not osad is installing and running by checking the OSA
Status field in the host system's profile on the Satellite. If the field does not exist or
indicates a failure of that the system has not contact Satellite in several minutes,
then you will need to install yum (using the command yum install -y osad)
before you can successfully provision a guest on the host.
Tip
You may receive the following message from the Kickstart Status page during
the guest's kickstart:
The install process on the guest system has not communicated
to RHN in
the past n minutes.
process, or it
may just be due to a slow install because of hardware
constraints.
log of the installation process is available, you may wish
to review
it to troubleshoot this issue.
Be patient and do not worry if you see this message unless more than twenty
minutes have passed. To check if the kickstart is continuing, check the installation
log to make sure there are no errors, and as you reload the Kickstart Status page
check to see that the Last File Request field continues to be updated.
170
Systems Virtual Systems.
This may be due to a hung install
A
Provisioning tab in the host