stx-openstack: Unable to open /dev/kvm No such file or directory
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
High
|
Thales Elero Cervi |
Bug Description
Brief Description
-----------------
Initial tests of stx-openstack on Debian, using the stx-libvirt image based on stx-debian and the .deb packages for libvirt and qemu failed.
The libvirt pod initializes successfully and starts the host libvirtd, but on the host the log shows that the kvm device was not open.
Severity
--------
Major: stx-openstack virtualization functions are degraded
Steps to Reproduce
------------------
* Upload stx-openstack (Debian stx)
* Helm-override libvirt image to use a custom built stx-libvirt
* Apply stx-openstack
Expected Behavior
------------------
libvirt log should not show a failure when opening /dev/kvm
Actual Behavior
----------------
libvirt log should shows a failure when opening /dev/kvm
Reproducibility
---------------
Reproducible
System Configuration
-------
AIO-SX
Branch/Pull Time/Commit
-------
master:
* starlingx/
+ https:/
Last Pass
---------
N/Aq
Timestamp/Logs
--------------
$ sudo head -n 5 /var/log/
2022-12-06 10:55:40.938+0000: 3356907: info : libvirt version: 7.0.0, package: 3.stx.3 (STX Builder <email address hidden> Thu, 01 Dec 2022 21:21:14 +0000)
2022-12-06 10:55:40.938+0000: 3356907: info : hostname: controller-0
2022-12-06 10:55:40.938+0000: 3356907: error : virHostCPUGetTs
2022-12-06 10:55:42.400+0000: 3356907: error : virHostCPUGetTs
2022-12-06 10:55:42.406+0000: 3356907: error : virHostCPUGetTs
Test Activity
-------------
Developer Testing
Workaround
----------
N/A
Changed in starlingx: | |
assignee: | nobody → Thales Elero Cervi (tcervi) |
tags: | added: stx.8.0 stx.distro.openstack |
Changed in starlingx: | |
importance: | Undecided → High |
This might only be happening on virtual deployments (Nested Virtualization). Need to get a physical environment to install and check.
I noticed that previously, on CentOS, my vbox test vms did not have the option "Enable VT-x/AMD-V" enabled and with stx-openstack applied the kvm character device (/dev/kvm) was there.
Now, on Debian, my vbox test vms did not have the kvm character device (/dev/kvm) even after the application is successfully applied. When I enable the option "Enable VT-x/AMD-V" though, the kvm device is there.
Will investigate it further.