Red Hat Bugzilla – Bug 608811
Provisioning Xen paravirt lacks virt bridge
Last modified: 2010-08-19 04:24:56 EDT
Created attachment 427467 [details]
Xen guest lacking vif
Description of problem: When trying to provision a Xen paravirt guest on a host it fails to create the virtual NIC interface with the guest. The Kickstart profile has the "Virtual Bridge" set to xenbr0, however that value is not getting pushed down to Cobbler when reporting the system profile leading to the Kickstart to fail due to lack of network communication to the Spacewalk server.
Version-Release number of selected component (if applicable):
This bug is reproducible with every attempt to provision a Xen paravirt guest.
Steps to Reproduce:
1. Create a Kickstart profile with the following attributes:
Virtualization Type = Xen Para-Virtualized Guest
Virtual Bridge: xenbr0
2. In the Systems view in the WebUI select a host that is running Xen with Provisioning/Virtualization entitlements, then navigate to Virtualization->Provisioning
3. Enter a Guest Name and choose the option to Schedule Kickstart and Finish
The Xen configuration file under /etc/xen/<Guest Name> on the Xen host contains no line with vif = [ XXXXX ] when xenbr0 is specified in the Kickstart profile.
The Xen para-virt guest should have a virtual NIC in the configuration file when provisioning it through Spacewalk.
Additional info: Attached to the bug are the configurations when provisioning the guest and a quick hack to the Cobbler system profile to get the guest functional to be Kickstarted.
Created attachment 427468 [details]
Xen guest cobbler modification to allow system to Kickstart
FYI, as discussed on the spacewalk list, this also affects KVM provisioning from Spacewalk, so it's not just an issue seen when using Xen. The workaround works for KVM provisioning too.
Cobbler apparently at some point broke api compatibility by making the modify-interface not work (instead modify_interface should be used).
Gonna see about backporting to 1.0.
Spacewalk 1.1 has been released.