This bug was fixed in the package libvirt - 6.0.0-0ubuntu8.9
---
libvirt (6.0.0-0ubuntu8.9) focal; urgency=medium
* d/p/u/lp-1921754*: add EPYC-Rome-v2 as v1 missed IBRS and thereby fails
on some HW/Guest combinations e.g. Windows 10 on Threadripper
(LP: #1921754)
*
The regression tests are good as well with the only hiccups being the
known postcopy-after-precopy denial and a known bug in hirsute guest
kernels on s390x. Nothing new introduced by the changes as far as I can
see.
prep (x86_64): Pass 20 F/S/N 0/0/0 - RC 0 (10 min 38961 lin)
migrate
Thank Markus you for chiming in as well here with your impressive set of
chips available to you.
I've also not seen the detection change on cascade lakes I've got.
Regression tests are still running, I'll mark verified once completed.
--
You received this bug notification because you are a
Testing before with libvirt 6.0.0-0ubuntu8.8 on Xeon 6130 (Skylake):
Cascadelake-Server
Intel
With 6.0.0-0ubuntu8.9
Skylake-Server-IBRS
Hello Rascal, or anyone else affected,
Accepted libvirt into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/libvirt/6.0.0-0ubuntu8.9 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
A few associated SRUs completed - now is the time.
This was uploaded to focal-unapproved for consideration by the SRU team.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922907
Title:
Unable to
> The lscpu output was added in the first two comments to this bug. These
> were 4114 and 4214 silver processors.
I didn't remember or read back all the former content :-/
Thanks for providing the answer before I asked :-)
For completeness here the `lscpu` and `cpuid -1` of my test system.
**
The lscpu output was added in the first two comments to this bug. These
were 4114 and 4214 silver processors.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922907
Title:
Unable to use Skylake
I was now able to get hold of a cascade lake chip (there are many types)
that was formerly already correctly recognized and working. In this case
I can confirm that the change didn't have any negative impact.
It was before:
Cascadelake-Server
Intel
@Rascal - might I ask you which cpu type exactly you were using on your
old hosts?
In my case it was an (lscpu) "Xeon(R) Gold 6252" with microcode (dmesg)
"0x4003003, date = 2020-06-18".
It is not required, but could be useful later on or for other affected users to
know where the different
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/libvirt/+git/libvirt/+merge/401371
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922907
Title:
Unable to use
** Description changed:
[Impact]
- * To avoid bugs with newer Hardware and to allow users/admins to control
-the KVM guests correctly we usually try to backport major CPU-
-detect/control features back to at least the last LTS (currently Focal)
-In SRU Terms this is under the
** Description changed:
+ [Impact]
+
+ * To avoid bugs with newer Hardware and to allow users/admins to control
+the KVM guests correctly we usually try to backport major CPU-
+detect/control features back to at least the last LTS (currently Focal)
+In SRU Terms this is under the
FYI First regression tests LGTM, but the feature freeze on Hirsute is to
hard atm to push this right now.
Therefore this will likely be an early change in 21.10 and then SRUs for
Focal/Groovy/Hirsute.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
For Focal, yes, I can help with testing, though not so fast :)
And thank you for handling this bug very quickly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922907
Title:
Unable to use Skylake
Yeah I agree that the patch would still be helpful,
and thanks for your prompt responses all the time!
I'd keep bug 1853200 separate for any further discussion on TSX, and
this bug here open to evaluate backporting the ability to process
stepping and thereby better differentiate these CPU types.
I solved the problems without a patch, but the patch would make life
much easier by correctly defining the CPU on old servers
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922907
Title:
Unable to
I can see that both servers (without patch) identify themselves the
same, although they are not. The only difference is in the instruction
set avx512vnni
Old host
virsh domcapabilities kvm
Cascadelake-Server
Intel
But I see another problem, I can't migrate server back for old-host with error:
Instance launched has CPU info: {"arch": "x86_64", "model":
"Cascadelake-Server", "vendor": "Intel", "topology": {"cells": 2, "sockets": 1,
"cores": 12, "threads": 2}, "features": ["ss", "invpcid", "vme", "sse4.2",
I'm sorry, the problem was really only in TSX
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922907
Title:
Unable to use Skylake capability on Cascadelake server
To manage notifications about this
FYI as links
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1853200
https://ubuntu.com/blog/ubuntu-updates-to-mitigate-latest-intel-hardware-vulnerabilities
https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/tsx_async_abort.html
--
You received this bug notification because you
That tsx issue is orthogonal to the sky-/cascade-lake detection.
It is due to all the spectre/meltdown/l1tf/... fixes, one of them had to more
or less turn TSX off (by default) and is discussed in 1853200. There isn't a
neat works-for-all solution yet - and admins have to decide to either adapt
I added `tsx=on tsx_async_abort=off` for kernel cmdline and it worked
virsh cpu-compare /tmp/old_host.xml
Host CPU is a superset of CPU described in /tmp/old_host.xml
Also successfully migrated a virtual machine to a new host
--
You received this bug notification because you are a member of
I rechecked the flags and it seems that the new CPU have't support for
TSX
virsh domcapabilities |grep "Skylake"
Skylake-Server-noTSX-IBRS
Skylake-Server-IBRS
Skylake-Server
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I tried
dpkg -l |grep libvirt
ii libvirt-clients 6.0.0-0ubuntu8.9~focalppa3
amd64Programs for the libvirt library
ii libvirt-daemon 6.0.0-0ubuntu8.9~focalppa3
amd64Virtualization
I have a first stab at this ready in a PPA [1] and would appreciate it
very much if you could test that in regard to your reported case. If it
works in general for you I'd be very interested if you could also try a
migration between a normal and an updated host as that can sometimes
also expose
I will be happy to check the assembly as soon as it is ready, because
this is the only option for us now to expand the cluster
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922907
Title:
Unable to
Hi,
what a coincidence - I was just about backporting these changes for a special
build.
Thereby I know that one more or less needs the full series that is seen in that
link.
Many are reworks of the allocation which is rather safe as Focal already
had started the glib allocation - so everything
** Attachment added: "Cascadelake"
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1922907/+attachment/5485200/+files/lscpu_4214.txt
** Description changed:
Hi.
- We have OpenStack cluster with old Skylake (Skylake-Server-IBRS) Intel
- CPU, and try to extend cluster with new
Upstream fixes https://listman.redhat.com/archives/libvir-
list/2020-March/msg01197.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922907
Title:
Unable to use Skylake capability on Cascadelake
30 matches
Mail list logo
