Description of problem:
In the times of rhn-kickstart package (pre Satellite 5.3.0 era), after
successful virtual guest provisioning and reboot, client code running
on virtualization host used to create configuration file for the new
guest in /etc/sysconfig/rhn/virt directory.

This approach had one nice benefit: the configuration file was later
used by rhn-virtualization-host code to start the guest from inside
Satellite / rhn.redhat.com webui.

This is no longer true with spacewalk-koan: no configuration file
is written out after guest provisioning.

Version-Release number of selected component (if applicable):
spacewalk-koan-0.1.11-12

How reproducible:
Always

Steps to Reproduce:
1. Satellite 5.3.0, create KVM guest kickstart profile
2. Register KVM host to your satellite (RHEL5.4, x86_64, full hardware
virtualization support).
3. Stop crond on your KVM virtualization host.
4. Kickstart new KVM guest from inside Satellite webui
5. After successful guest installation and reboot, check
/etc/sysconfig/rhn/virt directory whether corresponding config file was
created (it will have uuid-of-the-guest.xml form)

  
Actual results:
No config file is created.

Expected results:
Guest config file is created.

Additional info:
N/A