[one-users] Context disk location problem when VM_DIR !=$ONE_LOCATION/var

[Shi Jin]

The same problem is in vm_clone.sh and we should probably comment out
the*fix_paths
* command.

On Fri, Feb 18, 2011 at 11:00 PM, Shi Jin <jinzishuai at gmail.com> wrote:

> Hi there,
>
> I used to let the VM_DIR to be the default of $ONE_LOCATION/var.
> Now I set it to something else. But I am having problem with the context
> disk.
>
> When I specify the context, the disk.1 is still in the $ONE_LOCATION/var
> while disk.0 and the deployment.0 are already in the VM_DIR and most
> importantly deployment.0 still assumes the disk.1 in the same place as
> disk.1.
>
> I traced down the problem to be the tm_context.sh script which called*fix_dst_path
> * to actually change the output file from in VM_DIR to $ONE_LOCATION/var
> in the case of the two being different. Is this a bug? Simply comment out
> this line would get it working again.
>
> I am using the tm_nfs driver.
>
> Thank you very much.
> Shi
>
> --
> Shi Jin, Ph.D.
>
>


-- 
Shi Jin, Ph.D.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opennebula.org/pipermail/users-opennebula.org/attachments/20110222/8e3b17e0/attachment-0003.htm>