. Flags like
>> *npt* &
>> >> *nrip-save* which are present when SVM is enabled.
>> >> Therefore, affected by kernel commit -- 52297436199d ("kvm: svm: Update
>> >> svm_xsaves_supported").
>> >> Additionally, the OS/Qemu versions also
-- 52297436199d ("kvm: svm: Update
> >> svm_xsaves_supported").
> >> Additionally, the OS/Qemu versions also do fit with what is reported on
> >> Ubuntu' qemu package "bug #1887490".
> >>
> >> Regards
> >>
> >>
briel Bräscher
Sent: Tuesday, December 7, 2021 9:41 AM
To: dev
Subject: Re: Live migration between AMD Epyc and Ubuntu 18.04 and 20.04
Just adding to the "qemu-ev 2.10" & "qemu-ev 2.12" point.
migration fails from qemu-ev 2.10 to qemu-ev 2.12, this is definitely
a bug in
> lists.
> >
> > -Original Message-----
> > From: Gabriel Bräscher
> > Sent: Tuesday, December 7, 2021 9:41 AM
> > To: dev
> > Subject: Re: Live migration between AMD Epyc and Ubuntu 18.04 and 20.04
> >
> > Just adding to the "qemu-ev
iling
> lists.
>
> -Original Message-
> From: Gabriel Bräscher
> Sent: Tuesday, December 7, 2021 9:41 AM
> To: dev
> Subject: Re: Live migration between AMD Epyc and Ubuntu 18.04 and 20.04
>
> Just adding to the "qemu-ev 2.10" & "qemu-ev
The qemu-ev 2.10 bug was first reported a year or two ago in the mailing lists.
-Original Message-
From: Gabriel Bräscher
Sent: Tuesday, December 7, 2021 9:41 AM
To: dev
Subject: Re: Live migration between AMD Epyc and Ubuntu 18.04 and 20.04
Just adding to the "qemu-ev 2.10&quo
-mail, any disclosure, copying, distribution or use of its contents
> is strictly prohibited, and you should please notify the sender immediately
> and then delete it (including any attachments) from your system. Thank you.
> Von: Gabriel Bräscher
> Datum: Dienstag, 7. Dezember 2021 um 09:57
&
gt; > > We were getting errors complaining that the ibpb CPU feature wasn't
> > > available when migrating to the updated OS hosts (even though identical
> > > hardware).
> > >
> > > Upgrading qemu-ev to 2.12 on the originating host, then stopping and
>
e stopping and starting the VMs.
> >
> > Paul.
> >
> > -Original Message-
> > From: Wido den Hollander
> > Sent: Monday, November 29, 2021 7:57 AM
> > To: dev@cloudstack.apache.org; Wei ZHOU
> > Subject: Re: Live migration between AMD E
onday, November 29, 2021 7:57 AM
> To: dev@cloudstack.apache.org; Wei ZHOU
> Subject: Re: Live migration between AMD Epyc and Ubuntu 18.04 and 20.04
>
>
>
> On 11/24/21 10:36 PM, Wei ZHOU wrote:
> > Hi Wido,
> >
> > I think it is not good to run an environment w
lander
Sent: Monday, November 29, 2021 7:57 AM
To: dev@cloudstack.apache.org; Wei ZHOU
Subject: Re: Live migration between AMD Epyc and Ubuntu 18.04 and 20.04
On 11/24/21 10:36 PM, Wei ZHOU wrote:
> Hi Wido,
>
> I think it is not good to run an environment with two ubuntu/qemu versi
On 11/24/21 10:36 PM, Wei ZHOU wrote:
> Hi Wido,
>
> I think it is not good to run an environment with two ubuntu/qemu versions.
> It always happens that some cpu features are supported in the higher
> version but not supported in the older version.
> From my experience, the migration from olde
Cant help, but I've seen this exact issue (if not mistaken) - a CPU flag
that DOES exist on the destination KVM host, but libvirt complaining it
doesn't - I would guess some kernel issue, as I've seen those.
On Wed, 24 Nov 2021 at 22:36, Wei ZHOU wrote:
> Hi Wido,
>
> I think it is not good to r
Hi Wido,
I think it is not good to run an environment with two ubuntu/qemu versions.
It always happens that some cpu features are supported in the higher
version but not supported in the older version.
>From my experience, the migration from older version to higher version
works like a charm, but
14 matches
Mail list logo
