Hi Nick, I resolved my problem. The issue was due to NFS v4 domain configuration. I set correctly the domain on the KVM hosts but I forgot to configure the domain on the NFS server : /etc/idmapd.conf => Domain = FqdnDomainName
Regards -----Message d'origine----- De : COCHE Sébastien [mailto:sco...@sigma.fr] Envoyé : mardi 23 avril 2013 14:34 À : users@cloudstack.apache.org Objet : RE: System VM on KVM failed to start... Thank you Nick, I will test your script ASAP. I'll come back if not ;-) -----Message d'origine----- De : Nick Wales [mailto:n...@nickwales.co.uk] Envoyé : samedi 20 avril 2013 05:34 À : users@cloudstack.apache.org Objet : Re: System VM on KVM failed to start... I have had similar issues when I was rebuilding hosts regularly while starting out with cloudstack. I wrote a script that cleaned them up which might help. entries in /etc/mtab were the things I forgot about most often! Here's the script, hope it helps: https://github.com/nickwales/cloudstack-scripts/blob/master/host-clean-up.sh On 19 April 2013 04:44, COCHE Sébastien <sco...@sigma.fr> wrote: > Hi all, > > I have an issue when I try to start a vRouter on a KVM cluster (No > problem with instance or System VM on vSphere) I have the following > messages in /var/log/message : > Apr 19 11:32:32 lnxkvm-01 libvirtd: 13800: error : > virFileOpenForceOwnerMode:796 : cannot chown > '/mnt/0cbee891-bbcc-3289-9f78-0affceae4341/r-357-VM-patchdisk' to (0, 0): > Invalid argument > Apr 19 11:32:32 lnxkvm-01 libvirtd: 13800: error : > virStorageBackendCreateRaw:401 : cannot create path > '/mnt/0cbee891-bbcc-3289-9f78-0affceae4341/r-357-VM-patchdisk': > Invalid argument > > I look for posts on internet and I did not find any resolution :-( > > OS version : CentOS release 6.3 > Libvirt version : libvirtd (libvirt) 0.9.10 > > Regards > > > >
