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
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
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
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 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
** 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
Public bug reported:
Hi.
We have OpenStack cluster (ubuntu 20.04 ussuri) with old Skylake
(Skylake-Server-IBRS) Intel CPU, and try to extend cluster with new
Cascadelake (Cascadelake-Server-noTSX) servers with backward
compatibility mode in nova.conf
cpu_mode = custom
cpu_models =
I have some problem
--
usb0 network not enabled with Prolific Technology, Inc. PL25A1 Host-Host Bridge
https://bugs.launchpad.net/bugs/516923
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
14 matches
Mail list logo
