You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cloudstack.apache.org by "gpordeus (via GitHub)" <gi...@apache.org> on 2024/06/11 17:51:44 UTC
Re: [I] migrateVolume does not copy the template [cloudstack]
gpordeus commented on issue #5759:
URL: https://github.com/apache/cloudstack/issues/5759#issuecomment-2161312066
@DaanHoogland @rohityadavcloud @GutoVeronezi
I tried reproducing the problem with the latest main, in an ubuntu+kvm environment, but wasn't able to.
Any missing template inconsistencies with `migrateVirtualMachineWithVolume` should be solved by #8911, since it standardizes always merging the backing file into the volume.
As for `migrateVolume`:
- Deployed a VM, its volume on NFS primary storage. It went up with the backing file. I stopped the VM, migrated the volume to SMP primary storage and it resulted in a merged backing file.
```
scc@local:/mnt/pri-storage-smp$ qemu-img info 9eb27ca6-d721-45f0-a334-144e29377fc5
image: 9eb27ca6-d721-45f0-a334-144e29377fc5
file format: qcow2
virtual size: 8 GiB (8589934592 bytes)
disk size: 3.09 GiB
cluster_size: 65536
Format specific information:
compat: 1.1
compression type: zlib
lazy refcounts: false
refcount bits: 16
corrupt: false
extended l2: false
```
- Deployed another VM with a new template, its volume on NFS primary storage. It went up with the backing file. I stopped the VM, migrated the volume to another NFS primary storage and it resulted in a merged backing file.
```
scc@local:/mnt/a548af6a-abff-3541-8130-bfe19ff1cb7d$ qemu-img info 8daf78fe-202b-481d-93c9-aa1299dd43b9
image: 8daf78fe-202b-481d-93c9-aa1299dd43b9
file format: qcow2
virtual size: 8 GiB (8589934592 bytes)
disk size: 1.41 GiB
cluster_size: 65536
Format specific information:
compat: 1.1
compression type: zlib
lazy refcounts: false
refcount bits: 16
corrupt: false
extended l2: false
```
- Deployed another VM with yet another template, its volume on local storage. I stopped the VM, migrated the volume to another local storage and it resulted in a merged backing file. Started the VM back up and migrated it and its volume back to the first local storage. The VM ran normally, its volume without any mention of a backing file.
```
scc@host-local:/var/lib/libvirt/images$ qemu-img info -U 1bbcd0df-747d-4bfd-9680-b8dff1f1a97e
image: 1bbcd0df-747d-4bfd-9680-b8dff1f1a97e
file format: qcow2
virtual size: 8 GiB (8589934592 bytes)
disk size: 1.41 GiB
cluster_size: 65536
Format specific information:
compat: 1.1
compression type: zlib
lazy refcounts: false
refcount bits: 16
corrupt: false
extended l2: false
```
- Deployed another VM with the same template as last test, its volume on local storage. I stopped the VM, migrated the volume to another local storage that already had the same template and it resulted in a merged backing file. Started the VM back up and migrated it and its volume back to the first local storage. The VM ran normally, its volume without any mention of a backing file.
```
scc@local:/var/lib/libvirt/images$ qemu-img info -U d8dd43db-f798-404e-9de1-0914308c8cd0
image: d8dd43db-f798-404e-9de1-0914308c8cd0
file format: qcow2
virtual size: 8 GiB (8589934592 bytes)
disk size: 1.41 GiB
cluster_size: 65536
backing file: /var/lib/libvirt/images/318bc978-1e0f-4ab2-8b04-7fad5dc183cd
backing file format: qcow2
Format specific information:
compat: 1.1
compression type: zlib
lazy refcounts: false
refcount bits: 16
corrupt: false
extended l2: false
```
The local storage problem looks the same as #7942 and seem to have been solved by #7945.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org