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.
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.