> On 18. 5. 2022, at 1:11, Colin Coe wrote:
>
> Hi all
>
> I'm just putting in some new servers to be used as hosts in RHV 4.3 (soon to
> go to v4.4 or v4.5) but I'm having problems with the cluster CPU.
>
> These are HPE DL360 Gen10 with "Xeon Gold 6338N". Google tells me these are
> "Ice
On Sun, Jan 5, 2020 at 4:24 PM Strahil wrote:
> Just a question from curiosity.
> Can't we just define second cluster and move each VM from old cluster to
> the new one ?
>
You can
If you want the VMs to be run on the new cluster host you should
1) add the new cluster
2) have at least 1 run
Just a question from curiosity.
Can't we just define second cluster and move each VM from old cluster to the
new one ?
Best Regards,
Strahil NikkolovOn Jan 5, 2020 12:29, Eli Mesika wrote:
>
> This is the right way to do that IMO
>
> On Sat, Jan 4, 2020 at 3:09 AM Morris, Roy wrote:
>>
>> H
This is the right way to do that IMO
On Sat, Jan 4, 2020 at 3:09 AM Morris, Roy wrote:
> Hello,
>
> I'm running a 4.3 cluster with 56 VMs all set to default cluster and the
> cluster itself is set to Intel Westmere Family. I am getting a new server
> and retiring 3 old ones which brings me to my
Hi Roy
> To make this change, I assume the process would be to turn off all VMs, set
> cluster cpu type to broadwell, then turn on VMs to get the new CPU flags?
Exactly, you can only reliably change the CPU type for a cluster once
the last Westmere-based host is gone.
That's what I had to do whe
5 matches
Mail list logo
