[Users] after upgrade of vz7: Failed to get VM config: The virtual machine could not be found.

[justin at albstmeijer.nl]

> Or, how about - /prlctl register 1ab0f712-3bc4-45d6-b215-49247fb93934/
>
That would result in "Unable to get full path for 
/1ab0f712-3bc4-45d6-b215-49247fb93934" if the current working directory 
is not /vz/private, it expects a path.
/


//prlctl register /vz/private//////1ab0f712-3bc4-45d6-b215-49247fb93934 
could work.///

///In my case, even though '/////prlctl list' tells me it can not 
retrieve the config and therefore is not able to list any container.
When you try to register the container through ////prlctl it claims://

Container registration failed: Container is already registered with id 
0580c3b9-da91-40b3-92c2-6de9a4cc31a3

///Tried it with --force but this seems to assign a new UUID, which is 
not what I want.
///

///Then back to the procedure with vzctl I used;
///

///In my case, even though '/////prlctl list' tells me it can not 
retrieve the config and therefore is not able to list any container.
When you try to register the container through ////vzctl it claims://

Container registration failed: Container is already registered with id 
0580c3b9-da91-40b3-92c2-6de9a4cc31a3

So I had two options;

- stop container with vzctl
- unregister container with vzctl
- register container with vzctl
- start container with vzctl

But I needed the container to stay up, so I choose to

- use a forced container registration with "--force"/with 
/////////vzctl///////. ////////vzctl keeps the orginal 
/////////////////UUID as needed.
//////////





///
///

///
///

/
/


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvz.org/pipermail/users/attachments/20190606/641f72e6/attachment.html>