Bug 530583

Description of problem:
rhn-virtualization-host package installs on a host (KVM / Xen) system
a cron job that scans the hypervisor every two minutes for running
domains and creates an xml configuration file for every running,
*non-installing* domain (in case the configuration does not exist).

This configuration file is placed into /etc/sysconfig/rhn/virt
directory and is named according to the uuid of a particular
domain (ab89b8324d878e30a619a089b869e9f5.xml for example).

There are situations though, when this cron job creates configuration
files even for domains that are in fact installing.


Version-Release number of selected component (if applicable):
rhn-virtualization-5.3.0-12

How reproducible:
Always

Steps to Reproduce:
1. Install Satellite 5.3.0, register a Xen (not KVM!) host to your
satellite.
2. Create a paravirtualized kickstart profile in your satellite
3. On your host, stop crond service (so that you can launch the
job manually)
4. From satellite webui, provision a new xen guest on your host.
5. On your host, run rhn_check -v (to actually execute the kickstart
task) and see that the installation has started.
6. As the installation of xen guest is running, n your host run as root:
   # ls /etc/sysconfig/rhn/virt
   # python /usr/share/rhn/virtualization/poller.py
   # ls /etc/sysconfig/rhn/virt
  
Actual results:
New configuration XML file is created for installing domain.

Expected results:
No configuration XML file should be created for installing domain.

Additional info:
domain_config.py tries to detect installing domain by the presence of
method=... argument in the kernel command line of installing guest.
This is not always true: koan does not pass this argument to paravirtualized
xen guests for installation.