** Description changed:
+ [Impact]
+
+ * CPU definitions are added to libvirt as these CPUs are known
+and added to qemu for execution.
+ And due to that over time some are considered missing in
+former releases.
+
+ * To really benefit from the new features of these chips
+ they
libvirt changes accepted:
https://www.redhat.com/archives/libvir-list/2020-October/msg00493.html
And became
https://gitlab.com/libvirt/libvirt/-/commit/e06590f1708a599286f3ee3690b3dc50ee525d40
https://gitlab.com/libvirt/libvirt/-/commit/f941639f86f4bc66c106eb1291f1b58cf9e24680
https://gitlab.com/li
Everything else seems to be soon to be released into Focal.
I've seen v1 and v2 of the libvirt upstream series.
Please just ping here once the libvirt changes were accepted so we can revisit
the libvirt part of this.
Thanks in advance!
--
You received this bug notification because you are a mem
The new qemu version works as expected together with 5.4.0-49 kernel
required for xsaves
# grep -e 'model name' -e 'flags' /proc/cpuinfo
model name : AMD EPYC-Rome Processor
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush mmx fxsr sse sse2 h
Before:
qemu-system-x86_64 -cpu ? | grep EPYC
x86 EPYC (alias configured by machine type)
x86 EPYC-IBPB (alias of EPYC-v2)
x86 EPYC-v1 AMD EPYC Processor
x86 EPYC-v2 AM
Thanks. It does not look like the "regression" preventing proposed
migration is caused by the qemu changes.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1887490
Title:
Add/Backport EPY
FYI: Autopkgtest issues resolved
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1887490
Title:
Add/Backport EPYC-v3 and EPYC-Rome CPU model
Status in libvirt package in Ubuntu:
Incomp
Hello Markus, or anyone else affected,
Accepted qemu into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/qemu/1:4.2-3ubuntu6.7
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.u
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/qemu/+git/qemu/+merge/391348
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1887490
Title:
Add/Backport E
** Description changed:
+ ## Qemu SRU ##
+
+ [Impact]
+
+ * CPU definitions are added to qemu as these CPUs are known.
+And due to that over time are missing in former releases.
+
+ * To really benefit from the new features of these chips
+they have to be known, therefore new type add
SRU Template for qemu added and MP linked to fix this in Ubuntu 20.04
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1887490
Title:
Add/Backport EPYC-v3 and EPYC-Rome CPU model
Status i
** Changed in: qemu (Ubuntu Focal)
Status: Incomplete => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1887490
Title:
Add/Backport EPYC-v3 and EPYC-Rome CPU model
St
Thanks for the extra reports - I'll take a look at these qemu cases and in that
time you can try getting the libvirt Rome change upstream.
Once everything is in place we can SRU libvirt&qemu sort of together on this.
--
You received this bug notification because you are a member of Kernel
Packag
The second one is: https://bugs.launchpad.net/qemu/+bug/1849644
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1887490
Title:
Add/Backport EPYC-v3 and EPYC-Rome CPU model
Status in libv
Actually no. It builds and does not have any downsides, but does not
resolve the issue. Sorry for that. When I looked at the history of
cpu_map and this patch, I did not see that it would require further
patches to actually make it work.
So that would leave it at these four patches:
Add-pschange-m
@Markus - did the patch
5d6059f8ec cpu_map: Distinguish Cascadelake-Server from Skylake-Server
really work for you without the changes to support stepping applies?
Or does your own build have much more applied to make it work?
--
You received this bug notification because you are a member of Ke
I agree Markus.
Not only does the Focal qemu miss the related changes, I also dived deeper
through the "what exactly happened" to be sure.
The added patches I picked make it more obvious (test breaks) that we would
need cpu model "stepping" ranges to work. This would add the need for much more
Thanks for the update. It looks like your libvirt build fails.
Most likely due to the following patch missing:
https://github.com/libvirt/libvirt/commit/58691208e2063285d981a620873d48ddf8df8be5
That patch adds the CooperLake test data (wrongly as CascadeLake-
Server), which is later fixed in
ht
Hmm, I spoke too soon ... :-/
Some of the self tests failed due to the changes - I'll fix them up and ping
again once the builds complete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/188
Thanks for the test of the new kernel Markus!
I have respun the qemu build (the old one was outdated by a massive stable
update - too bad this wasn't part of 4.2.1 already) with the patches we had
before applied on top.
Further I have reviewed the suggested libvirt changes and added a build o
With the 5.4.0-49 from focal-proposed the xsaves flag can now be passed
into instances.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1887490
Title:
Add/Backport EPYC-v3 and EPYC-Rome C
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1887490
Title:
Add/Backport EPYC-v3 and EPYC-Rome CPU mod
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verificati
Correct Stefan, this is for Focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1887490
Title:
Add/Backport EPYC-v3 and EPYC-Rome CPU model
Status in libvirt package in Ubuntu:
Incom
** Changed in: linux (Ubuntu Focal)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1887490
Title:
Add/Backport EPYC-v3 and EPYC-Rome CPU model
If I understand the comments correctly this should be irrellevant for
groovy/devel using a v5.8 base.
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a
Thanks for Reminding Markus, it might have missed their triage completely
somehow.
I'll ping a few people directly about it and hopefully they will insert it into
the kernel queue and state here on the bug about it.
--
You received this bug notification because you are a member of Kernel
Packag
Is there anything I can do, regarding the backport of 52297436199d into
focal kernel?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1887490
Title:
Add/Backport EPYC-v3 and EPYC-Rome CPU
Plain qemu with the EPYC-Rome model works without any problems. I
already get xsave, xsaveopt, xsavec and xsaveerptr with the current
focal kernel, which also means that gcc finally uses znver1 (for v3) and
znver2 (for Rome) optimizations.
Libvirt would require cherrypicking a number of commits to
On Qemu I'm waiting on:
a) Kernel Teams statement on backporting the commit mentioned
b) some testing (by the reporter if possible) of the referred PPA builds of
Qemu.
Setting to incomplete until we have that.
** Changed in: qemu (Ubuntu Focal)
Status: Triaged => Incomplete
--
You recei
# Kernel
It lists a bunch of depending kernel changes
40bc47b08b6e ("kvm: x86: Enumerate support for CLZERO instruction")
504ce1954fba ("KVM: x86: Expose XSAVEERPTR to the guest")
6d61e3c32248 ("kvm: x86: Expose RDPID in KVM_GET_SUPPORTED_CPUID")
52297436199d ("kvm: svm: Update svm
# Libvirt
Depending on the case sometimes libvirt also needs changes - Focal
already has /usr/share/libvirt/cpu_map/x86_EPYC.xml which contains the
base version and v3 will plug in there. But for "Epic-Rome" there isn't
anything upstream in libvirt.
I think this will therefore be non-selectable t
32 matches
Mail list logo
