--- Begin Message ---
Hi,
El 6/6/23 a las 11:15, Fiona Ebner escribió:
Am 05.06.23 um 17:20 schrieb Eneko Lacunza:
If you like you can also test
qm set -args '-cpu
Nehalem,enforce,+aes,-svm,-vmx,+kvm_pv_eoi,+kvm_pv_unhalt,vendor="GenuineIntel"'
This was good for 1700, but I suspect it
Am 05.06.23 um 17:20 schrieb Eneko Lacunza:
> Hi,
>
> I'm sorry I could only test for Ryzen 1700, 2600X and 5950X - our 3700X
> is offline, pending some upgrades. I hope it will be back again in some
> days.
>
> Tested installation of Debian 11.1.0 ISO with GUI installer upto first
> boot to GUI
--- Begin Message ---
Hi,
I'm sorry I could only test for Ryzen 1700, 2600X and 5950X - our 3700X
is offline, pending some upgrades. I hope it will be back again in some
days.
Tested installation of Debian 11.1.0 ISO with GUI installer upto first
boot to GUI login to installed system:
El
Le samedi 03 juin 2023 à 16:14 +0200, Thomas Lamprecht a écrit :
> Am 01/06/2023 um 11:06 schrieb DERUMIER, Alexandre:
> > > Maybe the easiest would be to extract the aes flag out of the
> > > grid
> > > into
> > > the non-advanced part?
> > >
> > Couldn't be easier to keep aes enable by default
Am 02/06/2023 um 11:13 schrieb DERUMIER, Alexandre:
> at minimum, it could be interesting to expose the flag in the gui, for
> users really needed intel-amd migration.
acked also from my side, we can use the flag description for the a note
that it might benefit cross vendor migration (with some
Am 01/06/2023 um 11:06 schrieb DERUMIER, Alexandre:
>> Maybe the easiest would be to extract the aes flag out of the grid
>> into
>> the non-advanced part?
>>
> Couldn't be easier to keep aes enable by default in a single model
> (even if it's doesn't match the x86-64 spec). and allow user to
Am 01/06/2023 um 10:34 schrieb Fiona Ebner:
> Am 31.05.23 um 16:34 schrieb DERUMIER, Alexandre:
>> Le mercredi 31 mai 2023 à 13:36 +0200, Fiona Ebner a écrit :
>>> Am 22.05.23 um 12:25 schrieb Alexandre Derumier:
In addition to theses model, I have enabled aes too.
I think it's really
Thanks!
I'll try to upgrade to 6.2 kernel, this is the only difference
Le vendredi 02 juin 2023 à 18:09 +0200, Aaron Lauterer a écrit :
>
>
> On 6/2/23 16:15, DERUMIER, Alexandre wrote:
> > Thanks Aeron.
> >
> > I'll try to reproduce on my side on epyc milan.
> > AMD EPYC 7543 32-Core
On 6/2/23 16:15, DERUMIER, Alexandre wrote:
Thanks Aeron.
I'll try to reproduce on my side on epyc milan.
AMD EPYC 7543 32-Core Processor microcode patch_level=0x0a0011ce
(I just tried again with q35, but I'm still not able de reproduce)
can you share your full vmid.conf ? (numa ? vga
Thanks Aeron.
I'll try to reproduce on my side on epyc milan.
AMD EPYC 7543 32-Core Processor microcode patch_level=0x0a0011ce
(I just tried again with q35, but I'm still not able de reproduce)
can you share your full vmid.conf ? (numa ? vga ?..).
do you use debian graphical install or
For the record, I tested on:
AMD Ryzen 9 7900X 12-Core Processor
AMD EPYC 7302P 16-Core Processor (Rome)
AMD EPYC 7313 16-Core Processor (Milan)
VMs were all with 2 or 4 cores, q35 and UEFI boot.
>> qm set -args '-cpu
> >
> > at minimum, it could be interesting to expose the flag in the gui,
> > for
> > users really needed intel-amd migration.
> >
>
> I'm not opposed to that. We could also add a short note to the docs
> that
> it might be worth a try to disable the flag if you need cross-vendor
> migration
Am 02.06.23 um 11:13 schrieb DERUMIER, Alexandre:
>>
>> "catastrophic performance collapses" doesn't sound very promising :/
>>
>
> I have found another thread here:
> https://lore.kernel.org/all/0484ea3f-4ba7-4b93-e976-098c57171...@redhat.com/
> where paolo have done benchmark with only 3%
>
> Note that migration between CPUs of different vendors is not a
> supported
> use case (it will always depend on specific models, kernel versions,
> etc.), so we can only justify not adding it to the new default model
> if
> it doesn't make life worse for everybody else.
>
> And I'd be a bit
Am 01.06.23 um 23:15 schrieb DERUMIER, Alexandre:
> Hi,
> I found an interesting thread on the forum about kvm_pv_unhalt
>
> https://forum.proxmox.com/threads/live-migration-between-intel-xeon-and-amd-epyc2-linux-guests.68663/
>
>
> Sounds good. Please also take a look at the default flag
>
Hi,
I found an interesting thread on the forum about kvm_pv_unhalt
https://forum.proxmox.com/threads/live-migration-between-intel-xeon-and-amd-epyc2-linux-guests.68663/
Sounds good. Please also take a look at the default flag
"kvm_pv_unhalt". As I mentioned, it would cause a kernel crash in
Am 01.06.23 um 14:02 schrieb Eneko Lacunza:
> Hi,
>
> We have Ryzen 1700, 2600X, 3700 and 5950X machines here, I can test on
> them if that helps (please detail tests to perform).
>
> Thanks
>
Hi,
thank you for the offer. It would be interesting to see if you have any
issues with the
Am 01.06.23 um 15:53 schrieb DERUMIER, Alexandre:
>>>
>>> What AMD CPUs did you try it on?
>>>
>> epyc v2/v3 with last microcodes
>>
>>
>> does it work with x86-64-v3 ? (because the other patch of the series
>> could autofind the best new model if it's working)
>
> Looking at linux kernel code,
> >
> > What AMD CPUs did you try it on?
> >
> epyc v2/v3 with last microcodes
>
>
> does it work with x86-64-v3 ? (because the other patch of the series
> could autofind the best new model if it's working)
Looking at linux kernel code, they have some quirks based on cpu model
number &&
--- Begin Message ---
Hi,
We have Ryzen 1700, 2600X, 3700 and 5950X machines here, I can test on
them if that helps (please detail tests to perform).
Thanks
El 1/6/23 a las 13:37, DERUMIER, Alexandre escribió:
Le jeudi 01 juin 2023 à 11:34 +0200, Fiona Ebner a écrit :
Am 22.05.23 um 12:25
Le jeudi 01 juin 2023 à 11:34 +0200, Fiona Ebner a écrit :
> Am 22.05.23 um 12:25 schrieb Alexandre Derumier:> Nahelemn is a 2008
> cpu, so I think it's ok, we are in 2013 ;)
> > (and user can disable aes flag in gui too)
> >
> > That mean than the minimum compatible cpu for v2 is Intel Westmere
Am 22.05.23 um 12:25 schrieb Alexandre Derumier:> Nahelemn is a 2008
cpu, so I think it's ok, we are in 2013 ;)
> (and user can disable aes flag in gui too)
>
> That mean than the minimum compatible cpu for v2 is Intel Westmere (2010)
> and Amd Bulldozer (2011).
>
Unfortunately, it doesn't seem
Le jeudi 01 juin 2023 à 10:34 +0200, Fiona Ebner a écrit :
> Am 31.05.23 um 16:34 schrieb DERUMIER, Alexandre:
> > Le mercredi 31 mai 2023 à 13:36 +0200, Fiona Ebner a écrit :
> > > Am 22.05.23 um 12:25 schrieb Alexandre Derumier:
> > > > In addition to theses model, I have enabled aes too.
> > >
Am 31.05.23 um 16:34 schrieb DERUMIER, Alexandre:
> Le mercredi 31 mai 2023 à 13:36 +0200, Fiona Ebner a écrit :
>> Am 22.05.23 um 12:25 schrieb Alexandre Derumier:
>>> In addition to theses model, I have enabled aes too.
>>> I think it's really important, because a lot of users use default
>>>
Le mercredi 31 mai 2023 à 13:36 +0200, Fiona Ebner a écrit :
> Am 22.05.23 um 12:25 schrieb Alexandre Derumier:
> > In addition to theses model, I have enabled aes too.
> > I think it's really important, because a lot of users use default
> > values and have
> > bad performance with ssl and other
Am 22.05.23 um 12:25 schrieb Alexandre Derumier:
> In addition to theses model, I have enabled aes too.
> I think it's really important, because a lot of users use default values and
> have
> bad performance with ssl and other crypto stuffs.
>
So there is the answer to my aes question :) But
Hi,
we used kvm64 as default cpumodel since the begin of proxmox. (basically, it's
like a pentium4 cpu flags).
New distros like rhel9 are compiled to use more modern cpu flags.
(and windows already use new flags since year, and we already add some extra
cpu flags)
"
In 2020, AMD, Intel, Red
27 matches
Mail list logo
