Search results

"works for us" => means it propably depends on "purpose" and "usage" - if the use case does not bother about "ssh keys" or whatever besides "IP", a cloning functionality could still be useful even if not being 'perfect'. Even in case of VMs running flavours of "Windows" this might be true - yes...

For us, it would be really useful even with the restriction of the to-be-cloned-vm having to be shut down. Clone, start new vm, change settings, start original vm. And for OpenVZ vms, it should not be a problem anyway - IP is set "from outside", doing it with simple scripts works for us...

Hi, we're running a setup allowing "hot migrations" for kvm and also OpenVZ - we created 2 DRBD devices (active/active, for 2 nodes) as suggested here and afaik also in wiki (which basically eliminates the split-brain-risk), and additionally each node gets a LV mounted below /var/lib/vz. In...

ssh slave1-ip 'vzctl stop 105'

...for me this worked out of the box: - install orginal Storman package on a standard x64_86 system (CentOS5 in my case) - tar czf storman.tgz /usr/Storman /etc/init.d/stor_agent - unpack this on proxmox host: tar xzf storman.tgz -C / - modify init script like below - that's it, systems show up...