EOLing of qemu machine types
serge.hallyn at ubuntu.com
Mon Nov 3 15:52:17 UTC 2014
Quoting Robie Basak (robie.basak at ubuntu.com):
> On Thu, Oct 30, 2014 at 10:09:53PM +0000, Serge Hallyn wrote:
> > Does this seem sensible? Any suggestions/alternatives are
> > appreciated.
> Is it possible to have a lowest common denominator "LTS" machine type
> that is long term stable and doesn't need to change or be deprecated
> between releases? Or is this impractical to manage within qemu?
That's sort of what we have, depending on what you mean by 'between
releases'. In utopic, we have both pc-i440fx-trusty and pc-i440fx-utopic.
Are you asking whether we can keep pc-i440fx-trusty around past 18.04?
> I'm thinking of public cloud providers who probably don't want their
> customers to have to care or to require them to reboot every two years.
> I know most will, but I presume there's a "long tail" of non-rebooters.
Yeah I forget how I worded it in my initial email, but the intent would be to
keep the LTS machine type around for 2 LTS release. So pc-1.0-precise stays
around until and including 16.04, and be dropped in 16.10. pc-i440fx-trusty
stays until 18.04. So when you start a VM under trusty, you can migrate it
to a 16.04 host without changing the machine type. After that however you'd
need to give in and upgrade the machine type.
Keeping the LTS names around forever seems daunting, especially as we'd
also need to keep the pxe-roms around, and at some point we may end up with
toolchain headaches building the ipxe-precise packages in 18.04.
> Do we need to copy in the ubuntu-cloud and/or relevant OpenStack lists?
I'm not sure, please feel free to cc: them in.
More information about the ubuntu-server