It made sense to implement things that way at the time, but things have diverged such that the bits our implementation uses are either being deprecated or dramatically changed in hostd itself (which itself only prioritizes vSphere).
We essentially have a fork of the ESXi host manager ( 'hostd' for those following along at home), and keeping it in alignment with the upstream parent while ensuring it works for this use case is REALLY resource-intensive. The feature is really expensive to maintain and there's a mountain of tech debt associated with it. I should really look at find time to get an alternate that doesn't waste my work time. It certainly doesn't tell me what to expect to see after I trash a working development system downgrading to a later release. On this 16.1 what they mean looks as deliberately deceitfully ambiguous as a US presidential press secretary. On the 16.0 release it took me a while to burrow down to the short paragraph that said they're dropped shared VMs. I'm going to presume that I have to reboot this system to get sharing back (that will have to wait a while - there is a very long repo running).Īssuming that works, which after the wasted time with the last release reverting my windows laptop back to 15.5.x to get shared VMs back, how do I upgrade my downgraded license key from 15.5 to 16.x before I try this out on windows.īasically vmware appear to be useless at communicating crucial information about releases. It currently doesn't show a Manage / Shared option for the local test. It come up on the 16.0 license that I briefly had on the day that I downgraded from 15.5 to 16.0 (I had to go back and downgrade my license. I just downloaded the linux trial of workstation pro 16.1.0-17 and dropped on my kubuntu 20.04 test system.
0 kommentar(er)
