[02:49] <mup> Bug #1737464 opened: PXE boot always boots hd0 regardless of which drive is selected as the boot drive. <MAAS:New> <https://launchpad.net/bugs/1737464>
[09:05] <thim> Hi! We are having trouble with commissioning with MAAS and ProLiant DL360 Gen10 machines. After upgrading to the latest firmware, MAAS is changing the boot to legacy BIOS which makes the deploys to fail because after commissioning the machines reboots as usual but then with UEFI mode. Is there any way to force UEFI in MAAS? We are using IPMI 2.0 power option. Anyone heard of this type of problem before?
[09:07] <thim> The only working way we have discovered is when MAAS starts the machines to go into BIOS and change the boot to UEFI before the PXE boot starts.
[12:41] <mup> Bug #1733688 opened: virsh nodeinfo doesn't report CPU frequency on s390x <architecture-s39064> <bugnameltc-161610> <severity-high> <targetmilestone-inin1604> <Ubuntu on IBM z Systems:Triaged by bugproxy> <libvirt (Ubuntu):New> <maas (Ubuntu):New> <https://launchpad.net/bugs/1733688>
[13:02] <v92> thim: try to do force uefi boot in curtin's last_command option using ipmitool command. Should look like: ipmitool chassis bootdev disk options=efiboot,persistent
[15:26] <roaksoax> thim: maas is not changing the boot to legacy BIOS, the new firmware is
[15:27] <roaksoax> thim: maas, the only thing it tells it is to PXE boot, and PXE boot can be done via EFI or legacy
[19:35] <torontoyes> Can someone point me to the documentation for imaging windows?  I already have a sysprep windows 10 image
[19:35] <torontoyes> I'm not understaanding if I'm supposed to create a bootable iso from the sysprep image, or is there a process I follow from MAAS?
[21:00] <torontoyes> is thre any documentation for creating custom windows 10 image for deployment with maas.
[21:00] <torontoyes> I have not found anything explicit
[22:41] <torontoyes> Why does nobody have answers for this?  Does MAAS not do windows?
[22:41] <torontoyes> am i asking a crazy question?