Foreman-xen, Windows VM infinite loop

Nico · July 7, 2015, 11:00pm

Hi,

Using foreman-xen to create Windows VM require a manual step in order to
modify the boot order to avoid the VM to indefinitely boot on PXE.

github.com

theforeman/foreman-xen/blob/master/app/models/foreman_xen/xenserver.rb#L252


  nil
end


create_network(vm, args)


args['xenstore']['vm-data']['ifs']['0']['mac'] = vm.vifs.first.mac
xenstore_data                                  = xenstore_hash_flatten(args['xenstore'])


vm.set_attribute('xenstore_data', xenstore_data)
if vm.memory_static_max.to_i < mem_max.to_i
  vm.set_attribute('memory_static_max', mem_max)
  vm.set_attribute('memory_dynamic_max', mem_max)
  vm.set_attribute('memory_dynamic_min', mem_min)
  vm.set_attribute('memory_static_min', mem_min)
else
  vm.set_attribute('memory_static_min', mem_min)
  vm.set_attribute('memory_dynamic_min', mem_min)
  vm.set_attribute('memory_dynamic_max', mem_max)
  vm.set_attribute('memory_static_max', mem_max)
end

which define the boot order as:
DVD, Network, Disk
The issue is when a build request is generated the VM is created, then the
PXElinux file is generated, the VM boot into WinPE which then request the
proper script and provisioning template.
Then when the image/files are deployed for Windows the VM reboot onto
Windows. However since the PXElinux config is not updated until the
/unattended/built is requested the VM keep rebooting into WinPE.
Not sure what would be the best choice but either:
Foreman can update the PXElinux config boot file earlier in the process,
maybe after /unattented/script is requested?
Foreman-xen set the boot order to "dcn" (DVD, Disk, Network)
Foreman-xen allow to edit the boot order

Let me know if I can help in anyway, thanks in advance