When I mapped my first NFS storage everthing worked fine, I may have done it wrong but its working and live migration works. Now that storage backend is having some kernel errors and I need to migrate off it. So I created a new shared datastore and mapped it for opennebula and my 2 hypervisors. I just did a offline migration and I see that it created the VM id on the new DS So the VM id is 148 and the new storage id is 102 for reference. Here is a ls -la of the new dir where the VM was supposed to be created. You can see that it still points to the DS of 1, it didn’t move the disk. Of course this wont work. I’m sure its something that I did wrong on the first DS and how I have them mapped but I need to get offline migration as soon as I can so I don’t have an outage.
mmidgett@elf2:/mnt/nebula/one/datastores/102/148$ ls -la
total 380
drwxrwxr-x 2 9869 9869 4096 Mar 9 19:24 .
drwxr-xr-x 3 9869 9869 4096 Apr 16 14:24 …
-rw-rw-r-- 1 9869 9869 1135 Mar 9 18:39 deployment.0
-rw-rw-r-- 1 9869 9869 1136 Mar 9 19:24 deployment.1
lrwxrwxrwx 1 9869 9869 58 Mar 9 18:39 disk.0 -> /var/lib/one/datastores/1/4c3aecd52bafdc3eff8a69f4aed8dae2
-rw-r–r-- 1 9869 9869 372736 Mar 9 19:24 disk.1