This content has been marked as final. Show 5 replies
From release notes:
"8.3.1. Virtual Machines Using Resources in an OCFS2 Repository Cannot be Migrated To The Unassigned Virtual Machines Folder
Any virtual machine which has resources in ocfs2 repository cannot be migrated to Unassigned Virtual Machines folder, the only exception is if the ownership of this OCFS2 repository has already been released. "
can you explain more on this?
This functionality was replaced with the ability to assign the VM(s) to the Server Pool itself, thereby the VM(s) is/are not assigned to any server.
Same problem here.
I can't figure out how that VM could be using OCSF2 resources.
If the repo of a VM is OCFS2 (then that VM uses "OCFS2"), then in 3.2+ you can no longer move it to the Unassigned VM Folder. Instead you can drag that VM to the "Server pool" and thereby it is no longer assigned to any server, it is assigned to the server pool itself instead.
If this is not enough, you could open an Enhancement Request and specify the needs.