Comment 13 for bug 2023243
Revision history for this message
| bugproxy (bugproxy) wrote Comment bridged from LTC Bugzilla | #13 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
7020100
(Get the code!)
------- Comment From <email address hidden> 2023-08-10 11:35 EDT-------
(In reply to comment #29)
>
> Somehow between bionic/18.04 and focal/20.04 there was not much activity and
> not a lot of updates on the powerpc-utils package, indeed:
> $ rmadison powerpc-utils
> powerpc-utils | 1.2.18+
> ppc64el
> powerpc-utils | 1.3.1-2 | xenial | source, powerpc,
> ppc64el
> powerpc-utils | 1.3.1-2ubuntu0.3 | xenial-updates | source, powerpc,
> ppc64el
> powerpc-utils | 1.3.4-0ubuntu2 | bionic | source, ppc64el
> powerpc-utils | 1.3.4-0ubuntu2 | focal | source, ppc64el
> powerpc-utils | 1.3.9-1ubuntu1 | jammy | source, ppc64el
> powerpc-utils | 1.3.9-1ubuntu2 | kinetic | source, ppc64el
> powerpc-utils | 1.3.10-2 | lunar | source, ppc64el
> powerpc-utils | 1.3.10-2 | mantic | source, ppc64el
>
> We are happy to take requests to upgrade to the latest version, always as
> part of the current development release (always before Feature Freeze) - and
> we will consider updating powerpc-utils to latest v1.3.11 for mantic/23.10,
> the release that is currently in development.
> I've now also subscribed myself to GH powerpc-utils for all new tags
> (releases) to get a notification.
>
> Please notice that there is no P10 support in 20.04 (nor P11) and there will
> be never support for it - in 20.04, since it would mean that we have to lift
> the architectural level that we compile for.
> That can only be done in the release that is currently in development.
> And even trying to install will end up in an illegal instruction error -
> it's just not compiled for it (except one emulates an older architecture or
> runs in compat mode - if possible).
I think you have misunderstood what I meant when I said "support for P10 and P11". I was not referring to architectural features, e.g. new machine instructions. I was referring to new hypervisor features only available on hypervisor versions shipped for newer hardware.
> For P9 and P10 one actually has to migrate to the latest 22.04 LTS:
> https:/
> 20.04 is only still an option in case of P8.
>
> I know that getting the commits to fix something in an older release can be
> painful, esp. if cherry-picking does not work cleanly and backports are
> needed - but it's due to the Ubuntu SRU process, that only allows important
> and critical fixes anyway, so not meant for version bumps, bigger patches or
> major new features.
This fix is critical and important. If drmgr is misbehaving then the NovaLink partition cannot reliably orchestrate hotplug operations on the other LPARs. This cripples the machine's ability to interoperate with other machines in the cloud.
> We can of course (re-)build the latest version we have in the archive
> (currently v1.3.10) for focal in a PPA - and that is what I just did:
> https:/
> But this is also not ideal, since this version may for example have support
> for some P10 hardware features, but the underlying 20.04 has no support for
> this level - so the door is even more open for further issues one may run
> into.
Most of powerpc-utils is written in C. It does not depend on architectural features specific to P9, P10, or P11.
Again, this is about ensuring that a given 20.04 LPAR can interoperate with the broader cloud. Working hotplug is, by definition, crucial for reassigning resources without downtime.