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
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.ne
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 Ubunt
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/+s
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
Westmer
@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.lau
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
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 Ub
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 =>
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
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 B
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
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 righ
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 t
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
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
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:
libvi
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
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
19 matches
Mail list logo
