> On Oct 6, 2020, at 4:21 AM, Daniel P. Berrangé wrote:
>
> On Mon, Oct 05, 2020 at 09:13:29PM -0400, Matt Coleman wrote:
>>> On Oct 5, 2020, at 8:54 PM, Neal Gompa wrote:
>>>
>>> Should we require a bump to openwsman 2.6 for this?
>>
>> That won’t make any difference: openwsman 2.6+ supports
On Mon, Oct 05, 2020 at 09:13:29PM -0400, Matt Coleman wrote:
> > On Oct 5, 2020, at 8:54 PM, Neal Gompa wrote:
> >
> > Should we require a bump to openwsman 2.6 for this?
>
> That won’t make any difference: openwsman 2.6+ supports specifying the
> locale, but Windows ignores it. So, this
> On Oct 5, 2020, at 8:54 PM, Neal Gompa wrote:
>
> Should we require a bump to openwsman 2.6 for this?
That won’t make any difference: openwsman 2.6+ supports specifying the
locale, but Windows ignores it. So, this patch changes the queries to
not use localized strings.
--
Matt
On Mon, Oct 5, 2020 at 9:13 PM Matt Coleman wrote:
>
> > On Oct 5, 2020, at 8:54 PM, Neal Gompa wrote:
> >
> > Should we require a bump to openwsman 2.6 for this?
>
> That won’t make any difference: openwsman 2.6+ supports specifying the
> locale, but Windows ignores it. So, this patch changes
On Mon, Oct 5, 2020 at 12:21 PM Matt Coleman wrote:
>
> There are two specific WQL queries we're using to get either a list of
> virtual machines or the hypervisor host itself from Msvm_ComputerSystem.
> Those queries rely on filtering results based on the "Description"
> field. Since the
There are two specific WQL queries we're using to get either a list of
virtual machines or the hypervisor host itself from Msvm_ComputerSystem.
Those queries rely on filtering results based on the "Description"
field. Since the "Description" field is locale sensitive, the queries
will fail if the
