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

[Javier Fontan]

I've benn testing againg the scripts and work nice for me. Check this
explanation:

http://dev.opennebula.org/issues/445#note-4


On Sat, Feb 19, 2011 at 7:00 AM, 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.
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>
>



-- 
Javier Fontan, Grid & Virtualization Technology Engineer/Researcher
DSA Research Group: http://dsa-research.org
Globus GridWay Metascheduler: http://www.GridWay.org
OpenNebula Virtual Infrastructure Engine: http://www.OpenNebula.org