Hide Forgot
Description of problem: libvirt service fail to start in case vdsm-hook-faqemu is installed, libvirt error says there is a problem with 'usr/bin/qemu' which is not an executable (or permission error). when removing (rpm -e) package, everything goes back to normal. 10:36:01.632: 4293: debug : virCommandRun:1049 : Result stdout: '' stderr: 'Traceback (most recent call last): File "/usr/bin/qemu", line 13, in <module> os.execv(qemu_bin, qemu_argv) OSError: [Errno 13] Permission denied ' 10:36:01.632: 4293: error : virStateInitialize:1022 : Initialization of QEMU state driver failed [root@rhev-i32c-03 ~]# ls -l /usr/bin/qemu ls: cannot access /usr/bin/qemu: No such file or directory repro steps: 1) make sure package is installed 2) stop libvirt 3) start vdsm
Could you provide the output for this command? (with vdsm-hook-faqemu installed) rpm -V vdsm-hook-faqemu qemu-kvm Thanks.
Haim please provide above info.
Cannot reproduce, and no comment for 2 weeks, closing.
reproduced (again - easy to repro): output of the command is empty. its related to fact i'm working with selinux on: [root@rhev-i32c-01 /]# getenforce Enforcing when moving selinux to permissive, it works, and libvirt starts. libvirt log: 16:12:28.461: 11136: error : main:3305 : Driver state initialization failed 16:12:28.317: 11136: info : qemudSecurityInit:1420 : Initialized security driver selinux 16:12:28.326: 11136: debug : virCommandRunAsync:1148 : About to run LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin /usr/bin/qemu -M ? 16:12:28.326: 11136: debug : virExecWithHook:713 : LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin /usr/bin/qemu -M ? 16:12:28.327: 11136: debug : virCommandRunAsync:1164 : Command result 0, with PID 11245 16:12:28.383: 11136: debug : virCommandRun:1049 : Result stdout: '' stderr: 'Traceback (most recent call last): File "/usr/bin/qemu", line 13, in <module> os.execv(qemu_bin, qemu_argv) OSError: [Errno 13] Permission denied ' 16:12:28.383: 11136: error : virStateInitialize:1022 : Initialization of QEMU state driver failed
The problem is not reproducible with the latest selinux policy (3.7.19-70).