Op 28-04-2020 om 07:39 schreef Peter Krempa:
On Mon, Apr 27, 2020 at 20:58:19 +0200, Paul van der Vlis wrote:
> Op 27-04-2020 om 10:41 schreef Peter Krempa:
>> On Mon, Apr 27, 2020 at 10:13:37 +0200, Paul van der Vlis wrote:
>
>>> A point is that I have to create disk(s) on the other side with
>>> qemu-img, I did not found a way to do that automatically. My question
>>
>> We are able to pre-create the storage given that a full copy is
>> requested (copy-storage-all, not copy-storage-inc) and the images reside
>> in a location covered by a libvirt 'directory' storage pool at least on
>> the destination of the migration.
>
> Really interesting. I see an option "--migrate-disks" and I guess this
> will do this. Something like:
>
> virsh migrate --live --p2p --copy-storage-all --persistent \
> --undefinesource --verbose ----migrate-disks vda \
> $vm qemu+ssh://$other/system
>
> Is there a way to simply migrate all writeable disks without specifying
> them?
Yes. --copy-storage-all without actually using --migrate-disks.
What I see here, is that this migrates a qcow2 image to it's theoretical
size. So if it's a 1000G disk with 200G on it, it creates an 1000G file
on the other host. Is it possible to copy the image(s) in the "growable
way" like a qcow2 image normally is?
With regards,
Paul
--
Paul van der Vlis Linux systeembeheer Groningen
https://www.vandervlis.nl/