Currently the ovz driver doesn't support shared TM for system and default datastores - try changing them to ssh
Regards, Nikita 2013/12/2 Catalina Quinde <[email protected]> > Hi Nikita, > > Thanks for your help > > I do this changes: > > 1. In the /etc/default/nfs-kernel-server, I inactivated nfsv4 in this line > RPCMOUNTDOPTS="--manage-gids --no-nfs-version 4" > > 2. My /etc/exports file contains: > /var/lib/one/datastores > 192.168.147.0/255.255.255.0(rw,anonuid=1001,anongid=1001) > > 3. In /etc/fstab file in openvz node contains: > 192.168.147.129:/var/lib/one/datastores /var/lib/one/datastores nfs > _netdev,auto 0 0 > > 4. output onedatastore command is > > ID NAME SIZE AVAIL CLUSTER IMAGES TYPE DS > TM > 0 system - - - 0 sys - > shared > 1 default 23.6G 10% - 2 img fs > shared > 2 files 23.6G 10% - 0 fil fs ssh > 102 ssh_dsEsxi - - Esxiclus 0 sys - vmfs > 103 ssh_diEsxi 0M - Esxiclus 0 img vmfs vmfs > 104 ssh_dsOpvz - - OpenVZclus 0 sys - ssh > 105 ssh_diOpvz 23.6G 10% OpenVZclus 2 img fs ssh > > the datastores 104 and 105 are by openvz node. > > 5. I deploy VM but errors are same: > oneadmin@ubuntuOpNeb:~$ cat /var/log/one/67.log > Sun Dec 1 23:52:20 2013 [DiM][I]: New VM state is ACTIVE. > Sun Dec 1 23:52:20 2013 [LCM][I]: New VM state is PROLOG. > Sun Dec 1 23:52:20 2013 [VM][I]: Virtual Machine has no context > Sun Dec 1 23:52:40 2013 [LCM][I]: New VM state is BOOT > Sun Dec 1 23:52:40 2013 [VMM][I]: Generating deployment file: > /var/lib/one/vms/67/deployment.0 > Sun Dec 1 23:52:40 2013 [VMM][I]: ExitCode: 0 > Sun Dec 1 23:52:40 2013 [VMM][I]: Successfully execute network driver > operation: pre. > Sun Dec 1 23:52:45 2013 [VMM][I]: Command execution fail: cat << EOT | > /var/tmp/one/vmm/ovz/deploy '/var/lib/one/datastores/104/67/deployment.0' > 'ubuntu' 67 ubuntu > Sun Dec 1 23:52:45 2013 [VMM][I]: deploy: Executed "/usr/bin/sudo mv > "/var/lib/vz/template/cache/debian-7.0-x64.tar.gz" > "/var/lib/vz/template/cache/debian-7.0-x64.tar.gz.1385959963" 2> /dev/null; > true". > Sun Dec 1 23:52:45 2013 [VMM][I]: deploy: Executed "/usr/bin/sudo ln -sf > "/var/lib/one/datastores/104/67/disk.0" > "/var/lib/vz/template/cache/debian-7.0-x64.tar.gz"". > Sun Dec 1 23:52:45 2013 [VMM][E]: deploy: Command "/usr/bin/sudo > /usr/sbin/vzctl create 1067 --layout ploop --ostemplate "debian-7.0-x64" > --private "/var/lib/one/datastores/104/67/private" --root > "/var/lib/one/datastores/104/67/root"" failed. > Sun Dec 1 23:52:45 2013 [VMM][E]: deploy: Error in do_lock (lock.c:136): > Error in > flock(/var/lib/one/datastores/104/67/private.tmp/root.hdd/DiskDescriptor.xml.lck): > Bad file descriptor > Sun Dec 1 23:52:45 2013 [VMM][I]: Failed to create image: Error in > do_lock (lock.c:136): Error in > flock(/var/lib/one/datastores/104/67/private.tmp/root.hdd/DiskDescriptor.xml.lck): > Bad file descriptor [23] > Sun Dec 1 23:52:45 2013 [VMM][I]: Creation of container private area > failed > Sun Dec 1 23:52:45 2013 [VMM][E]: Error in do_lock (lock.c:136): Error in > flock(/var/lib/one/datastores/104/67/private.tmp/root.hdd/DiskDescriptor.xml.lck): > Bad file descriptor > Sun Dec 1 23:52:45 2013 [VMM][E]: Failed to create image: Error in > do_lock (lock.c:136): Error in > flock(/var/lib/one/datastores/104/67/private.tmp/root.hdd/DiskDescriptor.xml.lck): > Bad file descriptor [23] > Sun Dec 1 23:52:45 2013 [VMM][E]: Creation of container private area > failed > Sun Dec 1 23:52:45 2013 [VMM][E]: > Sun Dec 1 23:52:45 2013 [VMM][I]: ExitCode: 151 > Sun Dec 1 23:52:45 2013 [VMM][I]: Failed to execute virtualization driver > operation: deploy. > Sun Dec 1 23:52:45 2013 [VMM][E]: Error deploying virtual machine: Error > in do_lock (lock.c:136): Error in > flock(/var/lib/one/datastores/104/67/private.tmp/root.hdd/DiskDescriptor.xml.lck): > Bad file descriptor > Sun Dec 1 23:52:45 2013 [DiM][I]: New VM state is FAILED > > 6. I used VE_LAYOUT="simfs" in template but the result in state is fail, > with errors command tar, I attached the 68.log file. > > I'm doing wrong?? > > Regards, Caty. > > ---------------------------------------------------------------------- >> >> Message: 1 >> Date: Sun, 01 Dec 2013 14:38:26 +0400 >> >> From: knawnd <[email protected]> >> To: [email protected] >> Subject: Re: [one-users] VM in Opennebula for OpenVZ failed >> Message-ID: <[email protected]> >> Content-Type: text/plain; charset=ISO-8859-1; format=flowed >> >> >> Hi Caty, >> >> On 11/30/2013 06:28 PM, Catalina Quinde wrote: >> > Hi Nikita, excuse me by previous mail, it?s was incorrectly, well, I >> > revised >> > https://bugzilla.openvz.org/show_bug.cgi?id=2730, but, don?t >> >> > understand where I have to change, >> > >> > The ploop version with command: aptitude show ploop, present Version: >> > 1.9-10 and vzctl --version displays 4.6 >> What is your datastore (DS) configuration? Do you use nfs-shared DS? >> What is the output of the 'onedatastore list' command? >> >> If you are running nfs shared datastore there are several ways you can >> follow: >> 1) configure your nfs server to NFSv3 and not NFSv4 since according to >> [1] and [2] NFSv4 is not supported yet for ploop VMs; >> 2) switch from ploop-based containers to simfs ones. >> In that case you have to specify in VM config (or VM template config) >> VE_LAYOUT="simfs" >> >> 3) reconfigure datastore to use ssh transfer driver instead of shared >> one (see info [3]). >> >> Regards, >> Nikolay. >> >> [1] https://bugzilla.openvz.org/show_bug.cgi?id=2730 >> [2] https://bugzilla.openvz.org/show_bug.cgi?id=2734 >> [3] >> >> http://opennebula.org/documentation:rel4.2:system_ds#using_the_ssh_transfer_driver >> >> >> > >> > Thanks Nikita, please guide me. >> > >> > Regards, Caty. >> >> >> ------------------------------ >> >> >
_______________________________________________ Users mailing list [email protected] http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
