The problem is that every action out there assumes that VM computes are located inside HN computes' vms containers. So they try to access `self.context.__parent__` to get to that compute. The code below is basically adding VMs to hangar directly, instead of creating a VirtualizationContainer instance and adding VMs to that container. 

Now, next problem is that at this point we don't know which VirtualizationContainer backend can we support. Sure we can assume OpenVZ for now, but in a case where it's not true it will break. I'm having a hard time finding a generic solution to this issue right now.