For the Kernel Support:
---
commit 28c1c9fabf48d6ad596273a11c46e0d0da3e14cd
Author: KarimAllah Ahmed
Date: Thu Feb 1 19:59:44 2018
KVM/VMX: Emulate MSR_IA32_ARCH_CAPABILITIES
Disco: OK - https://bugs.launchpad.net/bugs/1823060
Bionic: OK -
+1 on your summary, looks very good.
I will review kernel changes (if they are present or not) and change
status accordingly.
+1 on the team update.
o/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Rafael,
thanks for giving it try. We knew it might be complex when we first saw the
changes.
And I consider it wise to - at some point - step back and realize this won't be
SRUable.
I'll summarize what we know about the libvirt portion of this:
## SRUability ##
The changes are rather
@Christian,
I'm flagging the libvirt SRUs as Opinion. So far I have done quite a lot
cherry-picks and backports identifying all the structures that have
changed and I'm not currently seeing how this can be done as a SRU (even
for Disco). There are quite a few data model changes to how libvirt was
** Changed in: libvirt (Ubuntu Disco)
Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco)
** Changed in: libvirt (Ubuntu Bionic)
Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco)
** Changed in: qemu (Ubuntu Disco)
Assignee: Rafael David Tinoco (rafaeldtinoco)
I was by accident changing the kernel task, fixed now.
** Changed in: linux (Ubuntu Eoan)
Status: Fix Released => In Progress
** Changed in: libvirt (Ubuntu Eoan)
Status: In Progress => Fix Released
** Changed in: libvirt (Ubuntu Eoan)
Assignee: Christian Ehrhardt (paelzer)
Tests confirmed that the recent libvirt did in fact work fine.
FYI - this was analyzed in bug 1841066 which will also be the bug to track this
little qemu addition which has to go alongside the libvirt portion of this once
considering SRUs.
** Changed in: linux (Ubuntu Eoan)
Status: In
Another bunch of related changes might be important.
Not sure how much of that will go into SRUs - I hope not all of it.
Already in Eoan we should try to use a reduced set or we could go directly to
5.5 which has other known issues.
63acb7bf qemu_process: Prefer generic qemuMonitorGetGuestCPU
Definitely! Will provide feedback soon!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828495
Title:
[KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM.
To manage notifications about
I started a test PPA [1] and an MP [2] to get this into Eoan.
@Rafael could you test this on the same system you used last time and review
the MP?
[1]: https://launchpad.net/~paelzer/+archive/ubuntu/bug-1828495-archcap-eoan
[2]:
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/libvirt/+git/libvirt/+merge/371504
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828495
Title:
[KVM][CLX]
Recent libvirt versions (5.5) added more for arch_capabilities.
Lets get that into Eoan before considering the SRUs back to Bionic afterwards.
commit ver subject
2674d00e 5.5 qemu: Drop MSR features from host-model with old QEMU
8eb4a89f 5.5 qemu: Forbid MSR features with old QEMU
c8ec678f 5.5
** Changed in: libvirt (Ubuntu Disco)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
** Changed in: libvirt (Ubuntu Bionic)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
** Changed in: libvirt (Ubuntu Eoan)
Status: Fix Released => In Progress
**
This bug was fixed in the package qemu - 1:2.11+dfsg-1ubuntu7.17
---
qemu (1:2.11+dfsg-1ubuntu7.17) bionic; urgency=medium
* {Ice,Cascade}Lake IA32_ARCH_CAPABILITIES support (LP: 1828495)
Needed patch is in d/p/u/lp1828495-:
- 0017-target-i386-add-MDS-NO-feature.patch:
Hello Rafael,
Testing results to share, Bit 5 Arch Capability is verified implemented.
See below for details, please feel free to let me know if you need more
information.
Thanks.
Regards, Ai B.
+++
Tested on
This bug was fixed in the package qemu - 1:3.1+dfsg-2ubuntu3.3
---
qemu (1:3.1+dfsg-2ubuntu3.3) disco; urgency=medium
[ Christian Ehrhardt ]
* d/p/ubuntu/lp-1830243-s390-bios-Skip-bootmap-signature-entries.patch:
tolerate guests with secure boot loaders (LP: #1830243)
[
>From the MR:
https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/qemu/+git/qemu/+merge/368804/+index?
I'm testing now the Bionic version in -proposed: 7.17
Containing the missing MDS-NO arch-capabilities flag.
Running the following command:
$ sudo /usr/bin/qemu-system-x86_64 -name
Thanks Rafael, I reviewed the MP, thanks for the fixup.
I sponsored it into bionic-unapproved.
It would be great if the SRU Team could evaluate and accept this minor update
to the Former upload.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I'll wait for the next SRU for bionic to be in -proposed to provide
Bionic full verification just like I did to Disco. It shall not take too
long and the version currently in -proposed will be superseded by the
one we have in the merge request right now.
--
You received this bug notification
# Disco verification:
ubuntu@disco:~$ sudo /usr/bin/qemu-system-x86_64 -name guest="guest"
-machine accel=kvm -cpu host,+arch-capabilities,+ssbd,+md-clear,+rdctl-
no,+ibrs-all,+skip-l1dfl-vmentry,+mds-no -m 2048 -realtime mlock=off
-smp 1,sockets=1,cores=1,threads=1 -uuid 7e55c71a-558f-
Okay,
So said in the merge requests, Bionic needed a new version with:
e6891e7... by Rafael David Tinoco 3 minutes ago
changelog
c27fa94... by Rafael David Tinoco on 2019-08-02
- 0017-target-i386-add-MDS-NO-feature.patch (LP: #1828495):
target/i386: add MDS-NO feature
Alright, working on it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828495
Title:
[KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM.
To manage notifications about this bug go to:
@Ai Lim, it would be great to get your testing on the PPA asap.
@Rafael - we already have the fixup. I have provided feedback on the MP,
I think we can quickly sponsor something new. That means we don't need
to go the full verification-failed, reject, new upload path - instead we
will ask to
Hello Ai Lim,
I have just uploaded a new version (~ppa2) to the same PPA:
https://launchpad.net/~rafaeldtinoco/+archive/ubuntu/lp1828495
for Bionic. Could you test this version and let me know if it presents
MDS_NO MSR flag ?
I'll test on my side (as soon as the package is compiled in the PPA)
Hello Ai Lim,
Thanks for your feedback.. indeed we have not backported the following
patch:
commit 20140a82c67467f53814ca197403d5e1b561a5e5
Author: Paolo Bonzini
Date: Thu May 16 15:53:20 2019
target/i386: add MDS-NO feature
Microarchitectural Data Sampling is a hardware
Hello Rafael,
Testing results to share, looks like the exposure of eIBRS into the
Guest is complete. Don't see Bit 5 implemented yet for MDS bit for Arch
Capability.
See below for details and let me know if you need any specific based on
these configuration.
Regards, Ai B.
## USING HOST CPU ONLY:
sudo /usr/bin/qemu-system-x86_64 -name guest="guest" -machine accel=kvm
-cpu host -m 2048 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1
-uuid 7e55c71a-558f-412c-8445-db0e95fc549f -display none -no-user-config
-nodefaults -rtc base=utc,driftfix=slew -global kvm-
I still have to check if default CascadeLake CPU with no flags will
enable the features by default (should not) and verify Disco SRU.
Unfortunately I have shutdown the remote machine (virsh console's fault
:o) and will come back to this as soon as it is up again.
--
You received this bug
I still need to verify this for the SRUs. There are no - up to now -
regressions being showed in excuses for Disco and/or Bionic. Will
provide verification soon.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hello quanxian, or anyone else affected,
Accepted qemu into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/qemu/1:2.11+dfsg-
1ubuntu7.16 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Changed in: libvirt (Ubuntu Bionic)
Importance: Undecided => Wishlist
** Changed in: libvirt (Ubuntu Cosmic)
Importance: Undecided => Wishlist
** Changed in: libvirt (Ubuntu Disco)
Importance: Undecided => Wishlist
** Changed in: libvirt (Ubuntu Eoan)
Importance: Undecided =>
Hello quanxian, or anyone else affected,
Accepted qemu into disco-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/qemu/1:3.1+dfsg-
2ubuntu3.3 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Some updates to libvirt:
- we already have ssbd/md-clear through security updates
- rdctl-no, ibrs-all, skip-l1dfl-vmentry, mds-no are part of
c8ec678f cpu_map: Introduce IA32_ARCH_CAPABILITIES MSR features
- arch_capabilities itself comes in 511df17a
There are also updates to the
Tags pushed and uploaded to B/D unapproved for the SRU Team to do a
final review and accept.
I also marked Cosmic as Won't Fix as it will be out of support before
this SRU completes.
Further I added libvirt Tasks where the next step is for rafaeldtinoco
to find if/what we'd need to make the
And qemu 4.0 is in Eoan, so this release is "fix released" (for the
scope of adding the features, not the just discussed versioned CPUs)
** Changed in: qemu (Ubuntu Eoan)
Status: In Progress => Fix Released
** Changed in: qemu (Ubuntu Eoan)
Assignee: Christian Ehrhardt (paelzer) =>
The series was merged in 3a1acf5d47295d22ffdae0982a2fd808b802a7da as a prep to
qemu 4.1.
But the changes are rather invasive and after a review I think for the SRU we
will not add them.
For example the changes around:
"model runnability guarantees won't apply to unversioned CPU models
Expected results is:
HOST and Guest should enable IA32_ARCH_CAPABILITIES MSR.
MDS_NO is bit 5 of ARCH_CAPABILITIES. Expose this bit to guest.
##cpuid -r
0x0007 0x00: eax=0x ebx=0xd19f4fb9 ecx=0x0818 edx=0x8400
edx's 29 bit should be 1.
#rdmsr 0x10a -f 5:5
return value should
Hello quanxian,
Could you clarify exactly what is the expected behaviour and what wasn't
achieved ?
We'd like to understand better the requirements, rather than having patches
pointed out only. Mainly because there are some rules we usually follow for
already released versions and some of them
we have verified that on 18.04.2 with Rafael David Tinoco
(rafaeldtinoco)'s PPA qemy packages. And get that guest doesn't work as
expected. After detailed discussion with Intel Upstream, there still
needs some patches. But they are under review. Keep watch the process of
process.
** Merge proposal linked:
https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/qemu/+git/qemu/+merge/369470
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828495
Title:
[KVM][CLX]
** Changed in: qemu (Ubuntu Disco)
Status: Confirmed => In Progress
** Changed in: qemu (Ubuntu Cosmic)
Status: Confirmed => In Progress
** Changed in: qemu (Ubuntu Eoan)
Assignee: Rafael David Tinoco (rafaeldtinoco) => Christian Ehrhardt
(paelzer)
** Changed in: qemu
https://www.mail-archive.com/qemu-devel@nongnu.org/msg626552.html
On the first patch of the set, Eduardo says:
"""
The last patch in the series demonstrates how the new feature can
be used to update a CPU model: it adds a Cascadelake-Server-4.1.1
CPU model, including "arch-capabilities=on" and
** Changed in: qemu (Ubuntu Eoan)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu Eoan)
Status: Confirmed => In Progress
** Changed in: qemu (Ubuntu Disco)
Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco)
** Changed in: qemu (Ubuntu Cosmic)
@rafael - One more question about Stepping 5/6.
I have formerly read your explanation that stepping 6 would be
required to be able to enable arch_capabilities.
And we planned to add all SRUs with stepping 6 right away and keep the
Delta to consider all versions to be stepping 6.
But then I have
> ssbd
> md-clear
> bpb
> ibrs-all
> rdctl-no
> rsba
> skip-l1dfl-vmentry
>
> I guess that we will have to backport this support in libvirt, in order
> to allow QEMU to pick specific CPU mitigation flags.
Those are not all missing at least. I have seen ssbd and md-clear for
sure in Bionic e.g.
Alright. I had in mind that (for bionic/cosmic) but we definitely have
to mention what you said (for started guests). About the migration, will
cause the issue and report back after cosmic/disco backport.
About needed CPU features. I could get the following... these are the
needed cpuflags to
@rafaeldtinoco: I found some forther more ugly detail for the stepping change
from 5 to 6.
Qemu 3.1 as in Disco had Cascade lake with the stepping 5.
So for Disco the SRU will change the definition.
Which is different to Bionic/Cosmic where we can say "our Cascade definition
will just always
This also affects "Cascadelake-Server" defined guests migrating from
patched Bionic to unpatched Disco - that will fail. But requiring
updates being applied is fine, only the enforced guest restart (which
doesn't apply to the just mentioned use-case) is the thing that is
really bad.
Overall maybe
3) NEW QEMU (w/ backport) GUEST: Bionic
REGULAR QEMU GUEST IN NEW QEMU
Spectre and Meltdown mitigation detection tool v0.42-1-g91d0699
Checking for vulnerabilities on current system Kernel is Linux
4.18.0-23-generic #24~18.04.1-Ubuntu SMP Thu Jun 13 17:08:52 UTC 2019 x86_64
CPU is Intel(R)
*) SUMMARY:
In between the old and new QEMU, changed results for the mitigations
checker was:
DIFF between old QEMU and this new one
Hardware check
* Hardware support (CPU microcode) for mitigation techniques
* Enhanced IBRS (IBRS_ALL)
* CPU indicates ARCH_CAPABILITIES MSR
TL;DR:
HOST MITIGATION FEATURES REPORT:
https://bugs.launchpad.net/intel/+bug/1828495/comments/15
OLD QEMU GUEST MIT FEATURES REPORT:
https://bugs.launchpad.net/intel/+bug/1828495/comments/16
NEW QEMU GUEST MIT FEATURES REPORT:
https://bugs.launchpad.net/intel/+bug/1828495/comments/17
MIT
2) OLD QEMU GUEST (Bionic)
REGULAR QEMU GUEST IN OLD QEMU
Spectre and Meltdown mitigation detection tool v0.42-1-g91d0699
Checking for vulnerabilities on current system Kernel is Linux
4.18.0-23-generic #24~18.04.1-Ubuntu SMP Thu Jun 13 17:08:52 UTC 2019 x86_64
CPU is Intel(R) Xeon(R) Gold
1) HOST (Bionic)
CASCADE LAKE HOST INFORMATION:
Spectre and Meltdown mitigation detection tool v0.42-1-g91d0699
Checking for vulnerabilities on current system Kernel is Linux
4.18.0-23-generic #24~18.04.1-Ubuntu SMP Thu Jun 13 17:08:52 UTC 2019 x86_64
CPU is Intel(R) Xeon(R) Gold 6252 CPU
Alright, so we are still testing the version we're working on but here
are some test results...
The merge request can be found here:
https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/qemu/+git/qemu/+merge/368804
with code reviews and comments in between the backport attempts.
PPA
** Description changed:
- This is a bug.
+ [Impact]
- Test Environment:
+ * QEMU does not support IceLake and CascadeLake CPUs specific features.
+ * Most important feature to be supported is: IA32_ARCH_CAPABILITIES MSR.
+ * With IA32_ARCH_CAPABILITIES, QEMU is able to advertise HW
Hi pragyansri,
If you track the progress on the merge proposal that is linked this looks good
atm and will soon be in a PPA [2] with proposed changes for pre-evaluation with
Bionic/Cosmic/Disco/Eoan.
>From there the next steps are:
- test the new feature from the PPA on cascade lake machines
-
Rafael - Is this completed for Bionic releases?
Thank you
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828495
Title:
[KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM.
To manage
** Also affects: qemu (Ubuntu Eoan)
Importance: Wishlist
Assignee: Rafael David Tinoco (rafaeldtinoco)
Status: Confirmed
** Also affects: linux (Ubuntu Eoan)
Importance: Wishlist
Status: Confirmed
** Also affects: qemu (Ubuntu Disco)
Importance: Undecided
** Merge proposal linked:
https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/qemu/+git/qemu/+merge/368804
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828495
Title:
[KVM][CLX]
I just realized that from my previous comment I said:
(2)
There is *no current request* to allow following features to be
reported by EAX_7H_ECX_0_EDX QEMU/KVM right now:
* CPUID.(EAX=7H,ECX=0):EDX[27] STIBP support flag.
* CPUID.(EAX=7H,ECX=0):EDX[28] L1D_FLUSH support flag.
*
WORKING
This is a comment summarising a bit the statement of work in this bug:
Bellow are the commits (and the merge requests they came from) that I
could identify by the previous comments. Judging by the selected
commits, the intent is to allow MSR supportability to be queried by
guest through
Sorry, last comment was posted 3 timex due to bad wrapping and mix of
chars because of that. Fixed now, I've hidden 2 broken comments. Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828495
WORKING
This is a comment summarising a bit the statement of work in this bug:
Bellow are the commits (and the merge requests they came from) that I
could identify by the previous comments. Judging by the selected
commits, the intent is to allow MSR supportability to be queried by
guest through
This is a comment summarising a bit the statement of work in this bug:
Bellow are the commits (and the merge requests they came from) that I could
identify by the previous comments. Judging by the selected commits, the intent
is to allow MSR supportability to be queried by guest through CPUID MSR
This patch is also needed for kernels before 4.18
cd28325249 KVM: VMX: support MSR_IA32_ARCH_CAPABILITIES as a feature
MSR ( 25-6-18)
This patchset populates the structure in arch/x86/kvm/x86.c:
msr_based_features{}
With out this patch, qemu asserts at
The top three qemu patches are in qemu 4.0 which we plan as minimum for Ubuntu
19.10.
Tagging up to be part of the Qemu work in Ubuntu 19.10.
The rest of the qemu patches is already in qemu 3.1 which is in Ubuntu
19.04
** Tags added: qemu-19.10
** Changed in: qemu (Ubuntu)
Status:
** Also affects: qemu (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: qemu (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
List of commits needed to enable ARCH_CAPABILITIES:
Kernel:
commit 2bdb76c015df7125783d8394d6339d181cb5bc30
Author: Xiaoyao Li
Date: Fri Mar 8 15:57:20 2019 +0800
kvm/x86: Move MSR_IA32_ARCH_CAPABILITIES to array emulated_msrs
QEMU:
commit 014018e19b3c54dd1bf5072bc912ceffea40abe8
Commit:2bdb76c015df7125783d8394d6339d181cb5bc30
git tag --contains 2bdb76c015df7125783d8394d6339d181cb5bc30
v5.1
v5.1-rc3
v5.1-rc4
v5.1-rc5
v5.1-rc6
v5.1-rc7
** Description changed:
This is a bug.
Test Environment:
Repro Steps:
1. Boot up guest using: -cpu Cascadelake-Server
69 matches
Mail list logo
