Hi, this is a rather scattered issue with creating VMware virtual machiens via Foreman and fog-vsphere.
The problem is that any VM that has been created from Foreman has its Boot Order locked which in turn cannot be changed from the VMs BIOS afterwards. The process of reversing this on the VMware side is rather clunky and involves shutting down affected VMs, unregistering them from vCenter and manually editing the .vmx file before reversing all those steps. The VMware people on site tell me that this is caused by the fact that "foreman" (they mean the system foreman runs on) tells their vSphere system to add the values bios.hddOrder = "scsi0:0, scsi0:1" and bios.bootOrder = "cdrom,hdd" to the vmx file. VMware then locks the boot order to what is in the VMX file. Since the toolchain from Foreman goes via the foreman-vmware provider which in turn uses fog-vsphere which in turn talks to the vCenter server is rather long, I would like to ask whether anyone knows whether one has a possibility to influence this process. Additionally, is it possible in VMware to set the initial boot order of a VM created via API without locking the VM to this boot order for all eternity. Any thoughts, ideas or experiences about this? Greetings Marc -- ----------------------------------------------------------------------------- Marc Haber | "I don't trust Computers. They | Mailadresse im Header Leimen, Germany | lose things." Winona Ryder | Fon: *49 6224 1600402 Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421 -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
