[pve-devel] storage migrate

2013-02-08 Thread Michael Rasmussen
Hi all, Doing some extensive tests has shown that if the VM needs to be freezed for the migration to complete using: PVE::QemuServer::vm_suspend($vmid) PVE::QemuServer::vm_resume($vmid) Always results in the following error: 'unable to connect to VM 127 socket - timeout after 31 retries' which me

[pve-devel] Storage migrate: divide and conquer :-)

2013-01-17 Thread Michael Rasmussen
Hi all, As already mentioned by Alexandre the following subs should go into Plugin.pm: sub vm_name sub vol_format sub disk_name sub vol_name To the above I would also add: sub get_uri (get_target_uri) sub lock_disk (my $lock_source = sub) sub unlock_disk (my $unlock_source = sub) sub create_disk

Re: [pve-devel] Storage migrate: Implementation questions

2012-12-29 Thread Dietmar Maurer
> I am doing god progress but some issues need to be clarified: > 1) Should the feature be implemented in a separate modules? no, that is not necessary (until the code has to many LOCs). > 2) Should it be added as a new button and active when a harddisk is active > under: >a) Hardware tab >

[pve-devel] Storage migrate: Implementation questions

2012-12-29 Thread Michael Rasmussen
Hi all, I am doing god progress but some issues need to be clarified: 1) Should the feature be implemented in a separate modules? 2) Should it be added as a new button and active when a harddisk is active under: a) Hardware tab b) Content->images (NFS and LVM) 3) Should it be available for o