Hi, well Firmware is a broad term - let me split it up into two cases: 1) boot <installer> from CD or FTP server (e.g. 'Load from Removeable Media and Server' task), then install to disk and reboot from that disk - possible in classic HMC mode and DPM 2) boot <installer> from network server (PXE-like), then install to disk and reboot from that disk afaik DPM mode only
Obviously both requires firmware support - but probably different components. The MAC address should not change (in the above examples) between the 1st boot (e.g. installer) and the 2nd (re-)boot (e.g. a post-install restart of the system from disk). Having MAAS in mind we particularly require the 2nd case (network- booting an LPAR in DPM, installing to disk and restarting from that disk and always having the same unique MAC address). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1646805 Title: MAC address needs to be unique and unchanged during entire netboot process Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Currently the MAC address is not solely used to id the machine or system. It is at the moment used to id the interface that the MAC represents. (At a very early state in the process the MAC address is missing or only available from inside the partition.) The minimum PXE boot requirements need to be satisfied in general. The boot loader is part of the firmware and not loaded from the server. So that means the firmware needs to provide the MAC address. But the MAC address is not available at that time, so it's not available upfront. MaaS is using the same MAC address for the initial DHCP request as for the network boot. Hence an initially known MAC address is required that needs to be static and doesn't change (on subsequent boots for that instance). There might be an IBM internal ticket already open for this - please check. Furthermore the firmware needs to requests files like this: pxelinux.cfg/01-88-99-aa-bb-cc-dd pxelinux.cfg/default And BOOTIF support is required: See 'petitboot doesn't handle ipappend in pxelinux.cfg' https://bugs.launchpad.net/tasty-taco/+bug/1322307 for reference. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1646805/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
