This is a multi-part message in MIME format. --------------040900080003090001020907 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 8bit Hi all I'm running 3.2 on several Fedora 18 nodes One of them has a local storage running 4 VMs Today the UPS crashed and host was rebboted after UPS replacement None of the VM's were able to be started I tried to put the Host in maintenance and reinstalled it, but this didn't give any result Digging into the logs I discovered the following error: The first was of this kind (on every VM) File "/usr/lib64/python2.7/site-packages/libvirt.py", line 2630, in createXML if ret is None:raise libvirtError('virDomainCreateXML() failed', conn=self) libvirtError: errore interno process exited while connecting to monitor: ((null):5034): Spice-Warning **: reds.c:3247:reds_init_ssl: Could not use private key file qemu-kvm: failed to initialize spice server Thread-564::DEBUG::2013-09-06 11:31:32,814::vm::1065::vm.Vm::(setDownStatus) vmId=`49d84915-490b-497d-a3f8-c7dac7485281`::Changed state to Down: errore interno process exited while connecting to monitor: ((null):5034): Spice-Warning **: reds.c:3247:reds_init_ssl: Could not use private key file qemu-kvm: failed to initialize spice server The private key was marked 440 as permission owned by vdsm user and kvm group I had to change it to 444 to allow everyone to read it After that I had for every VM the following error: could not open disk image /rhev/data-center/3935800a-abe4-406d-84a1-4c3c0b915cce/6818de31-5cda-41d0-a41a-681230a409ba/images/54144c03-5057-462e-8275-6ab386ae8c5a/01298998-32d5-44c2-b5d1-91be1316ed19: Permission denied Disks were owned by vdsm:kvm with 660 permission I had to relax this to 666 to enable the VMs to start Has anyone faced this kind f problem before? Any hint about what may have caused this odd problem? Thank you Best regards -- SkyNet SRL Via Maggiate 67/a - 28021 Borgomanero (NO) - tel. +39 0322-836487/834765 - fax +39 0322-836608 http://www.skynet.it <http://www.skynet.it/> Autorizzazione Ministeriale n.197 Le informazioni contenute in questo messaggio sono riservate e confidenziali ed è vietata la diffusione in qualunque modo eseguita. Qualora Lei non fosse la persona a cui il presente messaggio è destinato, La invitiamo ad eliminarlo ed a distruggerlo non divulgandolo, dandocene gentilmente comunicazione. Per qualsiasi informazione si prega di contattare info@skynet.it (e-mail dell'azienda). Rif. D.L. 196/2003 --------------040900080003090001020907 Content-Type: text/html; charset=ISO-8859-15 Content-Transfer-Encoding: 8bit <html> <head> <meta http-equiv="content-type" content="text/html; charset=ISO-8859-15"> </head> <body bgcolor="#FFFFFF" text="#000000"> Hi all<br> <br> I'm running 3.2 on several Fedora 18 nodes<br> <br> One of them has a local storage running 4 VMs<br> <br> Today the UPS crashed and host was rebboted after UPS replacement<br> <br> None of the VM's were able to be started<br> <br> I tried to put the Host in maintenance and reinstalled it, but this didn't give any result<br> <br> Digging into the logs I discovered the following error:<br> <br> The first was of this kind (on every VM)<br> <br> File "/usr/lib64/python2.7/site-packages/libvirt.py", line 2630, in createXML<br> if ret is None:raise libvirtError('virDomainCreateXML() failed', conn=self)<br> libvirtError: errore interno process exited while connecting to monitor: ((null):5034): Spice-Warning **: reds.c:3247:reds_init_ssl: Could not use private key file<br> qemu-kvm: failed to initialize spice server<br> <br> Thread-564::DEBUG::2013-09-06 11:31:32,814::vm::1065::vm.Vm::(setDownStatus) vmId=`49d84915-490b-497d-a3f8-c7dac7485281`::Changed state to Down: errore interno process exited while connecting to monitor: ((null):5034): Spice-Warning **: reds.c:3247:reds_init_ssl: Could not use private key file<br> qemu-kvm: failed to initialize spice server<br> <br> The private key was marked 440 as permission owned by vdsm user and kvm group<br> <br> I had to change it to 444 to allow everyone to read it<br> <br> After that I had for every VM the following error:<br> <br> could not open disk image /rhev/data-center/3935800a-abe4-406d-84a1-4c3c0b915cce/6818de31-5cda-41d0-a41a-681230a409ba/images/54144c03-5057-462e-8275-6ab386ae8c5a/01298998-32d5-44c2-b5d1-91be1316ed19: Permission denied<br> <br> Disks were owned by vdsm:kvm with 660 permission<br> <br> I had to relax this to 666 to enable the VMs to start<br> <br> Has anyone faced this kind f problem before?<br> <br> Any hint about what may have caused this odd problem?<br> <br> Thank you<br> <br> Best regards<br> <br> <div class="moz-signature">-- <br> <meta http-equiv="CONTENT-TYPE" content="text/html; charset=ISO-8859-15"> <title></title> <meta name="generator" content="Bluefish 2.0.3"> <meta name="author" content="Alessandro Bianchi"> <meta name="CREATED" content="20100306;9474300"> <meta name="CHANGEDBY" content="Alessandro "> <meta name="CHANGED" content="20100306;10212100"> <style type="text/css"> <!-- P { font-family: "Arial", "Helvetica", sans-serif; font-size: 10pt } P.nome { color: #ff8000; font-family: "Arial", "Helvetica", sans-serif; font-size: 12pt; font-weight: bold; text-align: center } P.indirizzo { color: #0084d1; font-family: "Arial", "Helvetica", sans-serif; font-size: 10pt; font-weight: bold; line-height: 0.48cm; text-align: center } P.info { color: #b3b3b3; font-family: "Arial", "Helvetica", sans-serif; font-size: 9pt } A:link { color: #005dff; text-decoration: none } A:visited { color: #005dff; text-decoration: none } --> </style> <p class="nome">SkyNet SRL</p> <p class="indirizzo">Via Maggiate 67/a - 28021 Borgomanero (NO) - tel. +39 0322-836487/834765 - fax +39 0322-836608</p> <p align="CENTER"><a href="http://www.skynet.it/">http://www.skynet.it</a></p> <p class="indirizzo">Autorizzazione Ministeriale n.197</p> <p class="info">Le informazioni contenute in questo messaggio sono riservate e confidenziali ed è vietata la diffusione in qualunque modo eseguita.<br> Qualora Lei non fosse la persona a cui il presente messaggio è destinato, La invitiamo ad eliminarlo ed a distruggerlo non divulgandolo, dandocene gentilmente comunicazione. <br> Per qualsiasi informazione si prega di contattare <a class="moz-txt-link-abbreviated" href="mailto:info@skynet.it">info@skynet.it</a> (e-mail dell'azienda). Rif. D.L. 196/2003</p> </div> </body> </html> --------------040900080003090001020907--