Re: [one-users] Problem in running VMs

2012-10-10 Thread shivay veer sharma
hi carlos, after that problem i have done single node installation that is working fin but i need to add more nodes that isn't working following error is still there i have shared the datastore directory and mounted it on other node but it still isn't working Wed Oct 10 12:10:47 2012 [DiM][I]:

Re: [one-users] Problem in running VMs

2012-09-13 Thread Carlos Martín Sánchez
True, the datastore 0 doesn't need to be mounted on the frontend. Back in the day, when we didn't have datastores, we used to document that you needed to share the whole /var/lib/one directory to make things easier, I guess the idea still lingers in my mind -- Carlos Martín, MSc Project Engineer

Re: [one-users] Problem in running VMs

2012-09-10 Thread shivay veer sharma
hi , i have shared the directory then after i am getting the same error then i have shared the hole datastore dir but the problem is still there now i have installed it in same node the after the problem is there... Can you please tell me the problem ASAP Mon Sep 10 11:53:32 2012 [DiM][I]:

Re: [one-users] Problem in running VMs

2012-09-07 Thread Carlos Martín Sánchez
Hi, If you are using the 'shared' Transfer Manager (TM) driver, then the directory /var/lib/one/var/datastores/0/0 should exist in both the front-end and the host. Please check if /var/lib/one/var/datastores/0 and /1 are correctly mounted, and have the right permissions so oneadmin can use them.

Re: [one-users] Problem in running VMs

2012-09-07 Thread Matthew Patton
On Fri, 07 Sep 2012 05:20:09 -0400, Carlos Martín Sánchez cmar...@opennebula.org wrote: If you are using the 'shared' Transfer Manager (TM) driver, then the directory /var/lib/one/var/datastores/0/0 should exist in both the front-end and the host. Huh? Why is the front-end involved at all?

[one-users] Problem in running VMs

2012-09-06 Thread shivay veer sharma
hi, i have just installed the openNebula and getting the following error. Thu Sep 6 13:13:53 2012 [DiM][I]: New VM state is ACTIVE. Thu Sep 6 13:13:53 2012 [LCM][I]: New VM state is PROLOG. Thu Sep 6 13:13:53 2012 [VM][I]: Virtual Machine has no context Thu Sep 6 13:13:54 2012 [TM][I]: