On 3/19/25 4:15 AM, Peter Krempa via Devel wrote:
> On Tue, Mar 18, 2025 at 18:13:57 +0100, Ján Tomko via Devel wrote:
>> On a Thursday in 2025, Collin Walling wrote:
>>> From: David Judkovics
>>>
>>> Add new virsh command 'hypervisor-cpu-models'. Command pulls from the
>>> existing domcapabiliti
On 3/18/25 1:13 PM, Ján Tomko wrote:
> On a Thursday in 2025, Collin Walling wrote:
>> From: David Judkovics
>>
>> Add new virsh command 'hypervisor-cpu-models'. Command pulls from the
>> existing domcapabilities XML and uses xpath to parse CPU model strings.
>> By default, only models reported a
On a Thursday in 2025, Collin Walling wrote:
From: David Judkovics
Add new virsh command 'hypervisor-cpu-models'. Command pulls from the
existing domcapabilities XML and uses xpath to parse CPU model strings.
By default, only models reported as usable by the hypervisor on the
host system are p
On Tue, Mar 18, 2025 at 18:13:57 +0100, Ján Tomko via Devel wrote:
> On a Thursday in 2025, Collin Walling wrote:
> > From: David Judkovics
> >
> > Add new virsh command 'hypervisor-cpu-models'. Command pulls from the
> > existing domcapabilities XML and uses xpath to parse CPU model strings.
>
On 3/17/25 2:49 AM, Collin Walling wrote:
> On 3/6/25 2:07 PM, Collin Walling wrote:
>
> Ping and adding Daniel et al on CC :)
>
Take-two. Apparently my CC list didn't take Daniel's email. Apologies.
--
Regards,
Collin
On 3/6/25 2:07 PM, Collin Walling wrote:
Ping and adding Daniel et al on CC :)
> From: David Judkovics
>
> Add new virsh command 'hypervisor-cpu-models'. Command pulls from the
> existing domcapabilities XML and uses xpath to parse CPU model strings.
> By default, only models reported as usabl
