Thanks for the kickstart file! I'll check it.
Indeed it sounds like a bug, I'll try to reproduce it myself
Yes, looks good. It could have shown up inside any other hardware node, but since "find" showed just one - you're good to go
Yes, of course you can. This .migrated is just for safety - to allow one to bring up old VM on vz6 fast if anything went wrong.
Following mount option should be pointing to the file:
However, in your output we can clearly see it's a...
Recreating the file manually would've been the next step I'd suggest :)
Good job on figuring this out.
Note, there's a chance that this VM still...
It is most likely the reason for failed relocation.
"Roles" can be changed manually in the config file:
Well, yes... Apparently resource is broken.
try disabling ha_enable and enabling back.
If it doesn't we'll have to fix it manually.
Mixed cluster should not be a problem. Most likely resource is broken for some reason.
Can you check if current VM location matches one listed in...
That is not a bug, but rather unclear display. Style will change in Update 4, for now, please bear with this style :)
Take a closer...
There is no limitation within shaman for OSes, it doesn't matter for HA what is inside of the VM.
Is VM configured for HA? You can check...
It's a bit difficult to discuss such issues over the forum board - there're too many variables you have to check on the server itself :) I'd...
Arp announcement is performed using "arping".
It is invoked from a bash "library" with common functions for containers, /etc/vz/conf/vz-functions...
pmigrate itself does not perform arp announcement. Arp is announced when container is started.
To help you I need to know few...
6.8 here is not a Virtuozzo version, but a "Virtuozzo Linux" version, OS underneath the virtualization, rhel-based.
You can migrate suspended container, but you won't be able to resume it, only to start (which will drop the memory dump and perform a clean boot)....
Separate names with a comma.