** Description changed: When trying to launch an instance in OpenStack Queens on Ubuntu 18.04 with the new kernels, this error happens: Error: Failed to perform requested operation on instance "david", the instance has an error status: Please try again later [Error: Exceeded maximum number of retries. Exceeded max scheduling attempts 3 for instance bf8dc8b8-37dd-43fa-ace0-90fe18c1d63b. Last exception: the CPU is incompatible with host CPU: Host CPU does not provide required features: hle, rtm]. This seems to be caused by the new kernels disabling the tsx cpu feature as per https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/TAA_MCEPSC_i915 Disabling tsx also disables hle and rtm, and /usr/share/libvirt/cpu_map.xml has hle and rtm configured for many cpu models: - ubuntu@cloud3:~$ grep -e "model name" -e hle -e rtm -e tsx + ubuntu@cloud3:~$ grep -e "model name" -e hle -e rtm -e tsx [...] - <model name='Haswell'> - <feature name='hle'/> - <feature name='rtm'/> - <model name='Haswell-IBRS'> - <feature name='hle'/> - <feature name='rtm'/> + <model name='Haswell'> + <feature name='hle'/> + <feature name='rtm'/> + <model name='Haswell-IBRS'> + <feature name='hle'/> + <feature name='rtm'/> [...] - <model name='Broadwell'> - <feature name='hle'/> - <feature name='rtm'/> - <model name='Broadwell-IBRS'> - <feature name='hle'/> - <feature name='rtm'/> - <model name='Skylake-Client'> - <feature name='hle'/> - <feature name='rtm'/> - <model name='Skylake-Client-IBRS'> - <feature name='hle'/> - <feature name='rtm'/> - <model name='Skylake-Server'> - <feature name='hle'/> - <feature name='rtm'/> - <model name='Skylake-Server-IBRS'> - <feature name='hle'/> - <feature name='rtm'/> + <model name='Broadwell'> + <feature name='hle'/> + <feature name='rtm'/> + <model name='Broadwell-IBRS'> + <feature name='hle'/> + <feature name='rtm'/> + <model name='Skylake-Client'> + <feature name='hle'/> + <feature name='rtm'/> + <model name='Skylake-Client-IBRS'> + <feature name='hle'/> + <feature name='rtm'/> + <model name='Skylake-Server'> + <feature name='hle'/> + <feature name='rtm'/> + <model name='Skylake-Server-IBRS'> + <feature name='hle'/> + <feature name='rtm'/> [...] + This only happens when configuring cpu_mode and cpu_model in + /etc/nova/nova.conf: - Additional info: + [libvirt] + cpu_mode = custom + cpu_model = Skylake-Server-IBRS + + In my case, this was done by setting the cpu-mode and cpu-model nova- + compute charm options. + + + [Additional info] I see this issue with the following kernel and libvirt versions: Linux cloud3 4.15.0-70-generic #79-Ubuntu SMP Tue Nov 12 10:36:11 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux - ubuntu@cloud3:~$ dpkg -l | grep -e libvirt -e nova ii libvirt-clients 4.0.0-1ubuntu8.13 amd64 Programs for the libvirt library ii libvirt-daemon 4.0.0-1ubuntu8.13 amd64 Virtualization daemon ii libvirt-daemon-driver-storage-rbd 4.0.0-1ubuntu8.13 amd64 Virtualization daemon RBD storage driver ii libvirt-daemon-system 4.0.0-1ubuntu8.13 amd64 Libvirt daemon configuration files ii libvirt0:amd64 4.0.0-1ubuntu8.13 amd64 library for interfacing with different virtualization systems ii nova-common 2:17.0.11-0ubuntu1 all OpenStack Compute - common files ii nova-compute 2:17.0.11-0ubuntu1 all OpenStack Compute - compute node base ii nova-compute-kvm 2:17.0.11-0ubuntu1 all OpenStack Compute - compute node (KVM) ii nova-compute-libvirt 2:17.0.11-0ubuntu1 all OpenStack Compute - compute node libvirt support ii python-libvirt 4.0.0-1 amd64 libvirt Python bindings ii python-nova 2:17.0.11-0ubuntu1 all OpenStack Compute Python libraries ii python-novaclient 2:9.1.1-0ubuntu1 all client library for OpenStack Compute API - Python 2.7 - ubuntu@cloud3:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.3 LTS Release: 18.04 Codename: bionic + + + [Workaround] + + A workaround is to remove the cpu_mode and cpu_model lines in the + libvirt section of /etc/nova/nova.conf. + + This can be done with juju like this: + + juju config nova-compute-kvm --reset cpu-model + juju config nova-compute-kvm --reset cpu-mode + + + Apparently another workaround would be to re-enable the tsx cpu feature on the host with tsx=yes on the boot command line, but I have not tested that workaround.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853200 Title: cpu features hle and rtm disabled for security are present in /usr/share/libvirt/cpu_map.xml To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1853200/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
