Re: recommendations for handling Hyper-V version number

2020-09-28 Thread Daniel P . Berrangé
On Sat, Sep 26, 2020 at 06:03:41PM -0400, Matt Coleman wrote: > > On Sep 25, 2020, at 4:42 AM, Daniel P. Berrangé > > wrote: > > > > IOW we could stuff both the hyper-v major + minor version digits > > into the libvirt major digits. Then we can split the hyperv micro

Re: recommendations for handling Hyper-V version number

2020-09-26 Thread Matt Coleman
> On Sep 25, 2020, at 4:42 AM, Daniel P. Berrangé > wrote: > > IOW we could stuff both the hyper-v major + minor version digits > into the libvirt major digits. Then we can split the hyperv micro > digits across the libvirt minor + micro. > > ie pack it using > >

Re: recommendations for handling Hyper-V version number

2020-09-25 Thread Daniel P . Berrangé
On Thu, Sep 24, 2020 at 06:43:56PM -0400, Matt Coleman wrote: > >> For example, the Windows Server 2016 Hyper-V version is 10.0.14393.0, > >> so its “micro” is over 14 times larger than the encoding allows. > >> > >> My current workaround is to truncate it to something that works (E.G. > >>

Re: recommendations for handling Hyper-V version number

2020-09-24 Thread Matt Coleman
>> For example, the Windows Server 2016 Hyper-V version is 10.0.14393.0, >> so its “micro” is over 14 times larger than the encoding allows. >> >> My current workaround is to truncate it to something that works (E.G. >> 10.0.143), but that's clearly less than ideal. > The problem here is the

Re: recommendations for handling Hyper-V version number

2020-09-24 Thread Ján Tomko
On a Wednesday in 2020, Matt Coleman wrote: Hello again, Hyper-V version numbers are not compatible with the encoding used in virParseVersionString: https://gitlab.com/libvirt/libvirt/-/blob/master/src/util/virutil.c#L246 For example, the Windows Server 2016 Hyper-V version is 10.0.14393.0, so

recommendations for handling Hyper-V version number

2020-09-24 Thread Matt Coleman
Hello again, Hyper-V version numbers are not compatible with the encoding used in virParseVersionString: https://gitlab.com/libvirt/libvirt/-/blob/master/src/util/virutil.c#L246 For example, the Windows Server 2016 Hyper-V version is 10.0.14393.0, so its “micro” is over 14 times larger than

Re: recommendations for handling Hyper-V version number

2020-09-23 Thread Chris Murphy
On Wed, Sep 23, 2020 at 8:36 PM Matt Coleman wrote: By the way, due to your domain's DMARC policy, gmail puts your emails into spam. Therefore it's possible quite a lot of list subscribers aren't seeing them. ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain