We've done some digging on this. It turns out that we can fairly easily request VSphere to deploy the best version it knows about (ESXi 5.5 supports 10, 6.0 supports 11, 6.5 supports 13). It is fairly easy to change our descriptor to request any of them, and we saw that 6.0 picked 11 and ignored 13.
However, there seems to be a problem with the ubuntu image when booted in version 11. We've filed a bug with the people generating the images, but it starts to boot, but fails to get to a login prompt. So while it is fairly easy for Juju to start requesting newer hardware versions, there is a potential issue with the actual images not supporting them. John =:-> On Wed, Feb 7, 2018 at 11:32 AM, Mark Shuttleworth <m...@ubuntu.com> wrote: > > Seems we should support a range of widely used versions, rather than > only the latest. > > Mark > > On 02/07/2018 04:24 AM, Ian Booth wrote: > > Hi Daniel > > > > The Juju vSphere provider currently only supports hardware version 10, > but 14 is > > now the most recent according to the VMWare website. If we were simply > to track > > and support the most recent hardware version, would that work for you? > > > > On 05/02/18 12:38, Daniel Bidwell wrote: > >> Is there anyway to make the vsphere controller to deploy vms with > >> hardware vm version 13 instead of version 10? > >> > > > -- > Juju-dev mailing list > Juju-dev@lists.ubuntu.com > Modify settings or unsubscribe at: https://lists.ubuntu.com/ > mailman/listinfo/juju-dev >
-- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
