Hide Forgot
Created attachment 499314 [details] libvirt.log Description of problem: When trying start VM on the rhev-hypervisor-6.1-20110510.1.el6 , then the Audit log shows the same as libvirtd.log: internal error process exited while connecting to monitor: do_spice_init: starting 0.8.0 reds_init_ssl: Could not use private key file Full err msg in Add info. Workaround could be used: chown vdsm:kvm -R /etc/pki/vdsm/libvirt-spice/ Version-Release number of selected component (if applicable): rhev-hypervisor-6.1-20110510.1.el6 vdsm-4.9-63 libvirt-0.8.7-18 How reproducible: 100% Steps to Reproduce: 1. have VM with Spice console 2. try to run this VM on this rhev-h 3. Actual results: Expected results: Additional info: 10:02:26.097: 9865: warning : qemudStartVMDaemon:3336 : Executing /usr/libexec/qemu-kvm 10:02:26.099: 9865: warning : qemudStartVMDaemon:3346 : Executing done /usr/libexec/qemu-kvm 10:02:29.106: 9865: error : qemuMonitorOpenUnix:288 : monitor socket did not show up.: Connection refused 10:02:29.107: 9865: error : qemudWaitForMonitor:2314 : internal error process exited while connecting to monitor: do_spice_init: starting 0.8.0 reds_init_ssl: Could not use private key file
/etc/pki/vdsm/libvirt-spice is created during the host approval process with rhevm. This flow is specific to the vdsm component and not part of ovirt-node.
Pavel, what's ls -lR /etc/pki/vdsm/libvirt-spice before the workaround chmod?
Ok, that's clearly my bug, shutil.copy2 does not copy file ownership. http://gerrit.usersys.redhat.com/#change,439
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHEA-2011-1782.html