Seems to me like we're at the point where considering a straight revert of the SRU would be in order (and I'm certainly considering it for the short term), in order to move forward again at a later time when this is more solid -- not that the end goal is still going to be happening (though maybe not in 16.04), that is to gradually remove klibc from the initramfs. That *will* require changes, such as we see here. If you never fail, it's because you're not innovating...
The changes here were motivated by providing IPv6 support for MaaS deployments in v6-only and mixed networks.
From my understanding of things, we've now fixed (in 0.122ubuntu8.4) the issues with ip=dhcp and some other ip= forms being parsed incorrectly.
There are still two outstanding issues:
- boot speed (I suspect there is only a limited amount of things we can do about this, given the use of dhclient).
- "portfast behavior", which is how we handle delays in getting a response from a DHCP server. There was definitely a regression there, for which I have a fix in my ppa at ppa:cyphermox/maas.
Are there any other outstanding issues? If so, what kernel command-line are you using, and please include the exact messages on screen (or in logs) so we can know what we're dealing with.
Seems to me like we're at the point where considering a straight revert of the SRU would be in order (and I'm certainly considering it for the short term), in order to move forward again at a later time when this is more solid -- not that the end goal is still going to be happening (though maybe not in 16.04), that is to gradually remove klibc from the initramfs. That *will* require changes, such as we see here. If you never fail, it's because you're not innovating...
The changes here were motivated by providing IPv6 support for MaaS deployments in v6-only and mixed networks.
From my understanding of things, we've now fixed (in 0.122ubuntu8.4) the issues with ip=dhcp and some other ip= forms being parsed incorrectly.
There are still two outstanding issues:
- boot speed (I suspect there is only a limited amount of things we can do about this, given the use of dhclient).
- "portfast behavior", which is how we handle delays in getting a response from a DHCP server. There was definitely a regression there, for which I have a fix in my ppa at ppa:cyphermox/maas.
Are there any other outstanding issues? If so, what kernel command-line are you using, and please include the exact messages on screen (or in logs) so we can know what we're dealing with.