My Oracle Support Banner

OLVM : Unable to start the vdsm service with One of the modules is not configured to work with VDSM (Doc ID 2931766.1)

Last updated on AUGUST 11, 2023

Applies to:

Linux OS - Version Oracle Linux 7.9 with Unbreakable Enterprise Kernel [5.4.17] and later
Linux x86-64

Symptoms

Unable to start the vdsmd service on the KVM

[root@kvm-host-x ~]# systemctl status vdsmd.service
● vdsmd.service - Virtual Desktop Server Manager
  Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled; vendor preset: enabled)
  Active: failed (Result: start-limit) since Tue 2023-02-28 13:21:41 GMT; 4s ago
  Process: 30338 ExecStartPre=/usr/libexec/vdsm/vdsmd_init_common.sh --pre-start (code=exited, status=1/FAILURE)

Feb 28 13:21:40 olvm.in.oracle.com systemd[1]: Failed to start Virtual Desktop Server Manager.
Feb 28 13:21:40 olvm.in.oracle.com systemd[1]: Unit vdsmd.service entered failed state.
Feb 28 13:21:40 olvm.in.oracle.com systemd[1]: vdsmd.service failed.
Feb 28 13:21:41 olvm.in.oracle.com systemd[1]: vdsmd.service holdoff time over, scheduling restart.
Feb 28 13:21:41 olvm.in.oracle.com systemd[1]: Stopped Virtual Desktop Server Manager.
Feb 28 13:21:41 olvm.in.oracle.com systemd[1]: start request repeated too quickly for vdsmd.service
Feb 28 13:21:41 olvm.in.oracle.com systemd[1]: Failed to start Virtual Desktop Server Manager.
Feb 28 13:21:41 olvm.in.oracle.com systemd[1]: Unit vdsmd.service entered failed state.
Feb 28 13:21:41 olvm.in.oracle.com systemd[1]: vdsmd.service failed.

From the logs it looks like the vdsm modules needed to be re-configured for the sebool module.


From the var/log/messages from the KVM host we see:

Feb 28 15:24:57 kvm-host-x systemd: [daemon.info] Starting Virtual Desktop Server Manager...
Feb 28 15:24:57 kvm-host-x vdsmd_init_common.sh: vdsm: Running mkdirs
Feb 28 15:24:57 kvm-host-x vdsmd_init_common.sh: [daemon.info] vdsm: Running mkdirs
Feb 28 15:24:57 kvm-host-x vdsmd_init_common.sh: vdsm: Running configure_coredump
Feb 28 15:24:57 kvm-host-x vdsmd_init_common.sh: [daemon.info] vdsm: Running configure_coredump
Feb 28 15:24:57 kvm-host-x vdsmd_init_common.sh: vdsm: Running configure_vdsm_logs
Feb 28 15:24:57 kvm-host-x vdsmd_init_common.sh: [daemon.info] vdsm: Running configure_vdsm_logs
Feb 28 15:24:57 kvm-host-x vdsmd_init_common.sh: vdsm: Running wait_for_network
Feb 28 15:24:57 kvm-host-x vdsmd_init_common.sh: [daemon.info] vdsm: Running wait_for_network
Feb 28 15:24:57 kvm-host-x vdsmd_init_common.sh: vdsm: Running run_init_hooks
Feb 28 15:24:57 kvm-host-x vdsmd_init_common.sh: [daemon.info] vdsm: Running run_init_hooks
Feb 28 15:24:57 kvm-host-x vdsmd_init_common.sh: vdsm: Running check_is_configured
Feb 28 15:24:57 kvm-host-x vdsmd_init_common.sh: [daemon.info] vdsm: Running check_is_configured
Feb 28 15:24:58 kvm-host-x vdsmd_init_common.sh: Error:
Feb 28 15:24:58 kvm-host-x vdsmd_init_common.sh: [daemon.info] Error:
Feb 28 15:24:58 kvm-host-x vdsmd_init_common.sh: One of the modules is not configured to work with VDSM. <<<<<<<<<<
Feb 28 15:24:58 kvm-host-x vdsmd_init_common.sh: [daemon.info] One of the modules is not configured to work with VDSM.<<<<<
Feb 28 15:24:58 kvm-host-x vdsmd_init_common.sh: To configure the module use the following:
Feb 28 15:24:58 kvm-host-x vdsmd_init_common.sh: [daemon.info] To configure the module use the following:
Feb 28 15:24:58 kvm-host-x vdsmd_init_common.sh: 'vdsm-tool configure [--module module-name]'. <<<<<<<<<
Feb 28 15:24:58 kvm-host-x vdsmd_init_common.sh: [daemon.info] 'vdsm-tool configure [--module module-name]'.
Feb 28 15:24:58 kvm-host-x vdsmd_init_common.sh: If all modules are not configured try to use:
Feb 28 15:24:58 kvm-host-x vdsmd_init_common.sh: [daemon.info] If all modules are not configured try to use:
Feb 28 15:24:58 kvm-host-x vdsmd_init_common.sh: 'vdsm-tool configure --force'
Feb 28 15:24:58 kvm-host-x vdsmd_init_common.sh: [daemon.info] 'vdsm-tool configure --force'
Feb 28 15:24:58 kvm-host-x vdsmd_init_common.sh: (The force flag will stop the module's service and start it
Feb 28 15:24:58 kvm-host-x vdsmd_init_common.sh: [daemon.info] (The force flag will stop the module's service and start it
Feb 28 15:24:58 kvm-host-x vdsmd_init_common.sh: afterwards automatically to load the new configuration.)
Feb 28 15:24:58 kvm-host-x vdsmd_init_common.sh: [daemon.info] afterwards automatically to load the new configuration.)
Feb 28 15:24:58 kvm-host-x vdsmd_init_common.sh: abrt is already configured for vdsm
Feb 28 15:24:58 kvm-host-x vdsmd_init_common.sh: [daemon.info] abrt is already configured for vdsm
Feb 28 15:24:58 kvm-host-x vdsmd_init_common.sh: Managed volume database is already configured
Feb 28 15:24:58 kvm-host-x vdsmd_init_common.sh: [daemon.info] Managed volume database is already configured
Feb 28 15:24:58 kvm-host-x vdsmd_init_common.sh: lvm is configured for vdsm
Feb 28 15:24:58 kvm-host-x vdsmd_init_common.sh: [daemon.info] lvm is configured for vdsm
Feb 28 15:24:58 kvm-host-x vdsmd_init_common.sh: libvirt is already configured for vdsm
Feb 28 15:24:58 kvm-host-x vdsmd_init_common.sh: [daemon.info] libvirt is already configured for vdsm
Feb 28 15:24:58 kvm-host-x vdsmd_init_common.sh: Current revision of multipath.conf detected, preserving
Feb 28 15:24:58 kvm-host-x vdsmd_init_common.sh: [daemon.info] Current revision of multipath.conf detected, preserving
Feb 28 15:24:58 kvm-host-x vdsmd_init_common.sh: Modules sebool are not configured <<<<<<<<<<
Feb 28 15:24:58 kvm-host-x vdsmd_init_common.sh: [daemon.info] Modules sebool are not configured <<<<<<
Feb 28 15:24:58 kvm-host-x vdsmd_init_common.sh: vdsm: stopped during execute check_is_configured task (task returned with error code 1).
Feb 28 15:24:58 kvm-host-x vdsmd_init_common.sh: [daemon.info] vdsm: stopped during execute check_is_configured task (task returned with error code 1).
Feb 28 15:24:58 kvm-host-x systemd: vdsmd.service: control process exited, code=exited status=1
Feb 28 15:24:58 kvm-host-x systemd: [daemon.notice] vdsmd.service: control process exited, code=exited status=1
Feb 28 15:24:58 kvm-host-x systemd: Failed to start Virtual Desktop Server Manager.
Feb 28 15:24:58 kvm-host-x systemd: [daemon.err] Failed to start Virtual Desktop Server Manager.
Feb 28 15:24:58 kvm-host-x systemd: Dependency failed for MOM instance configured for VDSM purposes.
Feb 28 15:24:58 kvm-host-x systemd: [daemon.warning] Dependency failed for MOM instance configured for VDSM purposes.
Feb 28 15:24:58 kvm-host-x audispd: node=olvm.in.oracle.com type=SERVICE_START msg=audit(1677597898.028:386): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=vdsmd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Feb 28 15:24:58 kvm-host-x systemd: Job mom-vdsm.service/start failed with result 'dependency'.
Feb 28 15:24:58 kvm-host-x systemd: [daemon.notice] Job mom-vdsm.service/start failed with result 'dependency'.
Feb 28 15:24:58 kvm-host-x systemd: Unit vdsmd.service entered failed state.

Changes

 Hardening was performed on the KVM host and the KVM host was rebooted

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.