On Mon, Feb 28, 2022 at 11:14 PM Michael Kelley (LINUX) <mikelley@xxxxxxxxxxxxx> wrote: > the wild to consume the new identifier. As a result, at this point Hyper-V > is not planning to change anything. > > It's a lousy state-of-affairs, but as mentioned previously in this thread, > it seems to be one that we will have to live with. I should note that QEMU and VMware also support this too. So, yea, I guess that boat has sailed. Should that Hyper-V team do the ECR thing Andy was talking about? Jason
