On 2/7/22 09:10, Alessio wrote:
Oh, well, it was plain "kvm64". Selecting "Nehalem", "SandyBridge" or
"Westmere", it works.
If you plan to live-migrate VMs from host to host, selecting a specific
CPU which is the oldest generation CPU among the possible hosts which
will run the VM is a good
On Mon, 2022-02-07 at 17:56 +0100, Peter Georg wrote:
>
> In this case your VM is misconfigured. Please check your configured
> KVM
> CPU model. A list of all CPU models and support x86-64 levels can be
> found here:
> https://qemu-project.gitlab.io/qemu/system/qemu-cpu-models.html
Oh, well,
On 07/02/2022 17.40, Alessio wrote:
On Mon, 2022-02-07 at 16:58 +0100, Peter Georg wrote:
On 07/02/2022 16.28, Alessio wrote:
On Mon, 2022-02-07 at 16:20 +0100, Peter Georg wrote:
glibc-2.34-20 includes a fix to more reliable detect CPU
compatibility.
See Bug
CentOS Errata and Security Advisory 2022:0442 Important
Upstream details at : https://access.redhat.com/errata/RHSA-2022:0442
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
x86_64:
On Mon, 2022-02-07 at 16:58 +0100, Peter Georg wrote:
> On 07/02/2022 16.28, Alessio wrote:
> > On Mon, 2022-02-07 at 16:20 +0100, Peter Georg wrote:
> > > glibc-2.34-20 includes a fix to more reliable detect CPU
> > > compatibility.
> > > See Bug
Once upon a time, Simon Matter said:
> Is there an easy way to figure out if a CPU does support x86-64-v2?
> Something like a list of CPU families or a list of flags to check?
Run "/lib64/ld-linux-x86-64.so.2 --help" - the output should include:
> On 07/02/2022 16.01, Alessio wrote:
>> Hello.
>> I had a CentOS Stream 9 installation in a KVM VM.
>> Today a "dnf upgrade" lead to an unusable system: dnf, rpm commands
>> complain that "glibc cpu does not support x86-64-v2" or "CPU ISA level
>> is lower than required".
>> The updates leading
On 07/02/2022 16.28, Alessio wrote:
On Mon, 2022-02-07 at 16:20 +0100, Peter Georg wrote:
glibc-2.34-20 includes a fix to more reliable detect CPU
compatibility.
See Bug https://bugzilla.redhat.com/show_bug.cgi?id=2040657
Does your CPU support x86-64-v2?
The KVM version I'm using doesn't
On Mon, 2022-02-07 at 16:20 +0100, Peter Georg wrote:
> glibc-2.34-20 includes a fix to more reliable detect CPU
> compatibility.
> See Bug https://bugzilla.redhat.com/show_bug.cgi?id=2040657
>
> Does your CPU support x86-64-v2?
The KVM version I'm using doesn't support that? Could it be?
On 07/02/2022 16.01, Alessio wrote:
Hello.
I had a CentOS Stream 9 installation in a KVM VM.
Today a "dnf upgrade" lead to an unusable system: dnf, rpm commands
complain that "glibc cpu does not support x86-64-v2" or "CPU ISA level
is lower than required".
The updates leading to this state seem
Hello.
I had a CentOS Stream 9 installation in a KVM VM.
Today a "dnf upgrade" lead to an unusable system: dnf, rpm commands
complain that "glibc cpu does not support x86-64-v2" or "CPU ISA level
is lower than required".
The updates leading to this state seem to be: python3 3.9.10-1, glibc
The instructions on https://centos.org/download/ have been updated
accordingly.
On 2/4/22 10:10, Leon Fauster via CentOS wrote:
Am 04.02.22 um 14:25 schrieb Götz Reinicke:
Hi,
is it still possible to migrating / upgrading CentOS Linux 8 to CentOS
Stream release 8 ? Any hint is welcome!
> Am 04.02.2022 um 12:10 schrieb Leon Fauster via CentOS :
>
> Am 04.02.22 um 14:25 schrieb Götz Reinicke:
>> Hi,
>> is it still possible to migrating / upgrading CentOS Linux 8 to CentOS
>> Stream release 8 ? Any hint is welcome!
>> Right now I do get errors:
>> dnf install
13 matches
Mail list logo
