<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 6-9-2013 12:34, Alessandro Bianchi
wrote:<br>
</div>
<blockquote cite="mid:5229AFAB.7070101@skynet.it" type="cite">
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
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>
</blockquote>
Yes, me.<br>
<blockquote cite="mid:5229AFAB.7070101@skynet.it" type="cite"> Any
hint about what may have caused this odd problem?<br>
<br>
</blockquote>
yum update.<br>
<br>
I updated one of my hosts and after that that host couldn't start
VMs anymore with exact the same errors. See thread 'Starting VM
error' by Shaun Glass. I tried a couple of things but not making
world readable those files. Will probably restore a backup and try
it.<br>
I added the virt-preview repo for F18 and updated qemu/libvirt which
also solved the problem.<br>
The difference between the updated and not updated host were really
minimal. See the thead for logs.<br>
<br>
Regards,<br>
<br>
Joop<br>
<br>
</body>
</html>