[Bug 1861643] Re: libvirt CPU model selection missing
The Eoan Ermine has reached end of life, so this bug will not be fixed for that release ** Changed in: libvirt (Ubuntu Eoan) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861643 Title: libvirt CPU model selection missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1861643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861643] Re: libvirt CPU model selection missing
The Eoan Ermine has reached end of life, so this bug will not be fixed for that release ** Changed in: qemu (Ubuntu Eoan) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861643 Title: libvirt CPU model selection missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1861643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861643] Re: libvirt CPU model selection missing
Thank Enoch, that indeed is bug 1853200 then which I fixed in Focal. Security Team is considering to backport the new CPU types that can work without hle/rtm, but I've seen nothing move yet in that regard. Marking as a dup. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861643 Title: libvirt CPU model selection missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1861643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861643] Re: libvirt CPU model selection missing
sorry for delays. for both of my machines, kvm-ok => INFO: /dev/kvm exists KVM acceleration can be used and for QMP output, pls. see attachments. ** Attachment added: "amp output for both machines" https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1861643/+attachment/5350843/+files/qmp.zip -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861643 Title: libvirt CPU model selection missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1861643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861643] Re: libvirt CPU model selection missing
Thanks Rafael - from another Eoan AMD system:
...
x86_64
Opteron_G5
...
...
qemu64
qemu32
phenom
pentium3
pentium2
pentium
n270
kvm64
kvm32
coreduo
core2duo
athlon
Westmere-IBRS
Westmere
Skylake-Server-IBRS
Skylake-Server
Skylake-Client-IBRS
Skylake-Client
SandyBridge-IBRS
SandyBridge
Penryn
Opteron_G5
Opteron_G4
Opteron_G3
Opteron_G2
Opteron_G1
Nehalem-IBRS
Nehalem
IvyBridge-IBRS
IvyBridge
Icelake-Server
Icelake-Client
Haswell-noTSX-IBRS
Haswell-noTSX
Haswell-IBRS
Haswell
EPYC-IBPB
EPYC
Conroe
Cascadelake-Server
Broadwell-noTSX-IBRS
Broadwell-noTSX
Broadwell-IBRS
Broadwell
486
And the matching probe reflects just that:
{
"QMP": {
"version": {
"qemu": {
"micro": 0,
"minor": 0,
"major": 4
},
"package": "Debian 1:4.0+dfsg-0ubuntu9.4"
},
"capabilities": [
"oob"
]
}
}
{
"return": {
}
}
{
"return": [
{
"name": "max",
"typename": "max-x86_64-cpu",
"unavailable-features": [
],
"static": false,
"migration-safe": false
},
{
"name": "host",
"typename": "host-x86_64-cpu",
"unavailable-features": [
],
"static": false,
"migration-safe": false
},
{
"name": "base",
"typename": "base-x86_64-cpu",
"unavailable-features": [
],
"static": true,
"migration-safe": true
},
{
"name": "qemu64",
"typename": "qemu64-x86_64-cpu",
"unavailable-features": [
"vmx"
],
"static": false,
"migration-safe": true
},
{
"name": "qemu32",
"typename": "qemu32-x86_64-cpu",
"unavailable-features": [
],
"static": false,
"migration-safe": true
},
{
"name": "phenom",
"typename": "phenom-x86_64-cpu",
"unavailable-features": [
"3dnowext",
"3dnow"
],
"static": false,
"migration-safe": true
},
{
"name": "pentium3",
"typename": "pentium3-x86_64-cpu",
"unavailable-features": [
],
"static": false,
"migration-safe": true
},
{
"name": "pentium2",
"typename": "pentium2-x86_64-cpu",
"unavailable-features": [
],
"static": false,
"migration-safe": true
},
{
"name": "pentium",
"typename": "pentium-x86_64-cpu",
"unavailable-features": [
],
"static": false,
"migration-safe": true
},
{
"name": "n270",
"typename": "n270-x86_64-cpu",
"unavailable-features": [
"ss",
"movbe"
],
"static": false,
"migration-safe": true
},
{
"name": "kvm64",
"typename": "kvm64-x86_64-cpu",
"unavailable-features": [
],
"static": false,
"migration-safe": true
},
{
"name": "kvm32",
"typename": "kvm32-x86_64-cpu",
"unavailable-features": [
],
"static": false,
"migration-safe": true
},
{
"name": "coreduo",
"typename": "coreduo-x86_64-cpu",
"unavailable-features": [
"ss"
],
"static": false,
"migration-safe": true
},
{
"name": "core2duo",
"typename": "core2duo-x86_64-cpu",
"unavailable-features": [
"ss"
],
"static": false,
"migration-safe": true
},
{
"name": "athlon",
"typename": "athlon-x86_64-cpu",
"unavailable-features": [
"3dnowext",
"3dnow"
],
"static": false,
"migration-safe": true
},
{
"name": "Westmere-IBRS",
"typename": "Westmere-IBRS-x86_64-cpu",
"unavailable-features": [
"spec-ctrl"
],
"static": false,
"migration-safe": true
},
{
"name": "Westmere",
"typename":
[Bug 1861643] Re: libvirt CPU model selection missing
@Enoch - I'd really like to see your probing result. Actually the instructions in comment #9 are better as it also includes kvm-ok. Please run those and report back here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861643 Title: libvirt CPU model selection missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1861643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861643] Re: libvirt CPU model selection missing
Wow the amd case even has all the models as usable='no'. I still miss the qmp probing matching the XML output. Please again see comment #8 and provide that as hopefully that will uncover why so many are "unusable" for you. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861643 Title: libvirt CPU model selection missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1861643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861643] Re: libvirt CPU model selection missing
Here's the other machine's info as requested with AMD CPU. ** Attachment added: "b450m_pro4_ryzen_3600.zip" https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1861643/+attachment/5335713/+files/b450m_pro4_ryzen_3600.zip -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861643 Title: libvirt CPU model selection missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1861643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861643] Re: libvirt CPU model selection missing
This needs the info I asked for in comment #8 to go forward. Marking tasks incomplete for now. ** Changed in: qemu (Ubuntu) Status: New => Fix Released ** Changed in: qemu (Ubuntu Eoan) Status: Confirmed => Incomplete ** Changed in: libvirt (Ubuntu Eoan) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861643 Title: libvirt CPU model selection missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1861643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861643] Re: libvirt CPU model selection missing
I'll keep this bug to your specific case, while I'll bump bug 1853200 to add -noTSX cpu maps to libvirt as needed going forward. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861643 Title: libvirt CPU model selection missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1861643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861643] Re: libvirt CPU model selection missing
Recreated the list with a better container :-/
#1 Bionic - as-is (libvirt 4.0 qemu 2.11) - Container -> Big List
#2 Bionic + Stein (libvirt 5.0 qemu 2.11) - Container ->
#3 Bionic + Train (libvirt 5.4 qemu 2.11) - Container ->
#4 Bionic + Focal-Binaries (libvirt 6.0 qemu 4.2) - Container ->
#5 Bionic - as-is (libvirt 4.0 qemu 2.11) - on Host -> Big List
#6 Focal - (libvirt 6.0 qemu 4.2) - Container - -> Big List
All confusion gone!
Ok that were a lot of checks to realize a simple truth.
The Eoan container I had initially thought I see your problem had no KVM as
well :-/
But that might still help us as now I know rather exactly what to ask for.
Maybe your system doesn't detect KVM or some cpu flags correctly.
1. please provide the output of
$ kvm-ok
2. please provide the output of
$ sudo qemu-system-x86_64 --enable-kvm --nographic --nodefaults -S
-qmp-pretty stdio
{"execute":"qmp_capabilities"}
{"execute":"query-cpu-definitions"}
In my systems case I can't select Skylake as well and the report tells me:
{
"name": "Skylake-Client-IBRS",
"typename": "Skylake-Client-IBRS-x86_64-cpu",
"unavailable-features": [
"hle",
"rtm"
],
"static": false,
"migration-safe": true
},
Which is a known limitation due to
https://people.canonical.com/~ubuntu-security/cve/2019/CVE-2019-11135.html
As discussed in https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1853200
this is a Won't Fix at the moment. But we could bump that bug and report this
case "symptom" to reconsider adding e.g. a reduced Skylake type.
Waiting for your data first ...
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-11135
** Also affects: qemu (Ubuntu)
Importance: Undecided
Status: New
** Changed in: qemu (Ubuntu Eoan)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1861643
Title:
libvirt CPU model selection missing
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1861643/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861643] Re: libvirt CPU model selection missing
Back on this for a bit.
After some abstraction levels the probing is in libvirt around:
virQEMUDriverGetDomainCapabilities
-> virQEMUCapsFillDomainCaps
...
-> virQEMUCapsGetCPUModels
...
-> virQEMUCapsGetAccel(qemuCaps, type)->cpuModels
That is of the kvm struct that represents qemu-kvm
The struct contains mostly what we see in domcaps:
1106 struct _qemuMonitorCPUDefInfo {
1107 virDomainCapsCPUUsable usable;
1108 char *name;
1109 char *type;
1110 char **blockers; /* NULL-terminated string list */
};
This is filled formerly by:
virQEMUCapsFetchCPUModels
-> virQEMUCapsFetchCPUDefinitions
-> qemuMonitorGetCPUDefinitions - pokes qemu monitor to get info
-> virQEMUCapsCPUDefsToModels - adds probed models to structure
And that uses the common QMP query-cpu-definitions
So libvirt reports what qemu tells it ... oh I get a feeling I actually know
this case ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1861643
Title:
libvirt CPU model selection missing
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1861643/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861643] Re: libvirt CPU model selection missing
Ok it is different, when spawning my focal guest I used my usual LXD
profile (which can run KVM) but the bionic guest to test this was from
scratch and didn't have that. So I actually checked a non-kvm capable
bionic system.
I have to retest the list in comment #6
When doing so we can almost right away go for qemu probing:
$ sudo qemu-system-x86_64 --enable-kvm --nographic --nodefaults -S -qmp-pretty
stdio
{"execute":"qmp_capabilities"}
{"execute":"query-cpu-definitions"}
That will list all known CPUs and if they are not usable for e.g.
missing a CPU feature
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1861643
Title:
libvirt CPU model selection missing
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1861643/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861643] Re: libvirt CPU model selection missing
Using the backports of libvirt we have in the Ubuntu Cloud Archive I was upgrading through different versions and comparing the behavior: Note: Clearing /var/cache/libvirt/qemu/capabilities/ manually to be sure between every test. Interestingly I used LXD containers to do my test and that seems to have an effect as well. Whatever container protection/isolation takes place here might be related to this. Also libvirt probes things from qemu, so the qemu version can be important as well. #1 Bionic - as-is (libvirt 4.0 qemu 2.11) - Container -> Small List #2 Bionic + Stein (libvirt 5.0 qemu 2.11) - Container -> Small List #3 Bionic + Train (libvirt 5.4 qemu 2.11) - Container -> Small List #4 Bionic + Focal-Binaries (libvirt 6.0 qemu 4.2) - Container -> Small List #5 Bionic - as-is (libvirt 4.0 qemu 2.11) - on Host -> Big List #6 Focal - (libvirt 6.0 qemu 4.2) - Container - -> Big List What "§$%&/(! Two mysteries to solve: - What might make #4 differ from #6? - What might make #1 differ from #5? Small List: qemu32 pentium3 pentium2 pentium n270 kvm64 kvm32 coreduo core2duo athlon Westmere Penryn Opteron_G2 Opteron_G1 Nehalem Conroe 486 Big List: qemu32 pentium3 pentium2 pentium n270 kvm64 kvm32 coreduo core2duo Westmere Westmere-IBRS SandyBridge SandyBridge-IBRS Penryn Opteron_G1 Nehalem Nehalem-IBRS IvyBridge IvyBridge-IBRS Haswell-noTSX Haswell-noTSX-IBRS Conroe Broadwell-noTSX Broadwell-noTSX-IBRS 486 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861643 Title: libvirt CPU model selection missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1861643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861643] Re: libvirt CPU model selection missing
Hrm, virt-manager between Eoan and Focal doesn't really differ enough to be the reason for this. Maybe it is a libvirt issue after all. I need to debug what exactly virt-manager probes to make up this list ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861643 Title: libvirt CPU model selection missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1861643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861643] Re: libvirt CPU model selection missing
Yeah so it might come down to: $ virsh domcapabilities | grep "model usable='yes'" This list matches what I can select on my system in virt-manager. And it is tremendously shorter between Eoan and Focal (on the same system). Also applying the same Filter to your XML confirms that there Skylake is missing which was your initial bug report (unable to select that). Your list at least has Broadwell, Haswell, Sandy, Westmere ... ** Changed in: libvirt (Ubuntu Eoan) Status: Invalid => Confirmed ** Changed in: virt-manager (Ubuntu Eoan) Status: Incomplete => Invalid ** Changed in: libvirt (Ubuntu) Status: Invalid => Fix Released ** Changed in: virt-manager (Ubuntu) Status: Fix Released => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861643 Title: libvirt CPU model selection missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1861643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861643] Re: libvirt CPU model selection missing
Thank you for the update. Please be sure to switch the bug status back to "new" once you have attached the rest of the information. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861643 Title: libvirt CPU model selection missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1861643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861643] Re: libvirt CPU model selection missing
Here's the one with my L470 (xml + txt). I will provide the ones with my Ryzen later. ** Attachment added: "l470_i3_7100u.zip" https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1861643/+attachment/5332646/+files/l470_i3_7100u.zip -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861643 Title: libvirt CPU model selection missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1861643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861643] Re: libvirt CPU model selection missing
Issue confirmed on Eoan, but not existing on Bionic nor on Focal. On Focal I get Broadwell, Haswell, Ivy and Nehalem types in addition to the old set (my real chip is a i7-8550U so that seems ok for my case). It seems to contain only the <=core2duo chips which means it most likely filters out on some feature that it considers required for all the other more modern types. I don't see the mistake in libvirt - the detection is correct and mostly based on cpu features and cpuids. I was trying to force a new chip which you could try as well. To do so either use virsh-edit or in virt-manager "preferences"->"enable XML editing" and then set a new type like the "SkyLake-Client" you look for. If you then afterwards try to start the guest it will list you which features it is missing. Please report those back to compare with the definition. Also could you attach a full: $ virsh capabilities $ virsh domcapabilities $ cat /proc/cpuinfo ** Also affects: libvirt (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: libvirt (Ubuntu) Status: New => Fix Released ** Changed in: libvirt (Ubuntu Eoan) Status: New => Incomplete ** Package changed: libvirt (Ubuntu) => virt-manager (Ubuntu) ** Also affects: libvirt (Ubuntu) Importance: Undecided Status: New ** Changed in: libvirt (Ubuntu) Status: New => Invalid ** Changed in: libvirt (Ubuntu Eoan) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861643 Title: libvirt CPU model selection missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1861643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
