GitHub user abh1sar added a comment to the discussion: NAS B&R KVM (ACS 4.20)
Restore & Attach Issue
There is a bug in CloudStack where the disk format isn’t correctly set in the
volumes table. As a result, the domain XML generated by CloudStack specifies
raw, which causes virsh qemu-monitor-command to report the format as raw, even
though the actual image is qcow2 (as confirmed by you and qemu-img info below).
I’ve been able to reproduce this and will raise a PR to fix the incorrect DB
entry. Just to confirm—do you see any other issues related to this?
```
[root@dev1-b-kvm-host1 ~]# virsh qemu-monitor-command i-2-6-VM --hmp 'info
block'
libvirt-3-format:
/mnt/67bf274c-346c-35ac-badb-afb6857dcb9e/287ede4b-1308-4fde-984b-9b5c3f4f532e
(qcow2)
Attached to: ide0-0-0
Cache mode: writeback, direct
Backing file:
/mnt/67bf274c-346c-35ac-badb-afb6857dcb9e/a1cf2027-2593-4295-a373-a7dc03f60299
(chain depth: 1)
libvirt-7-format:
/mnt/79a4ac66-84c9-36c0-ac98-9b29c9c827e1/4c69665d-19b4-4f57-8788-0cd1cef0af07
(raw)
Attached to: /machine/peripheral/virtio-disk2/virtio-backend
Cache mode: writeback, direct
```
```
[root@dev1-b-kvm-host1 ~]# qemu-img info
/mnt/79a4ac66-84c9-36c0-ac98-9b29c9c827e1/4c69665d-19b4-4f57-8788-0cd1cef0af07
image:
/mnt/79a4ac66-84c9-36c0-ac98-9b29c9c827e1/4c69665d-19b4-4f57-8788-0cd1cef0af07
file format: qcow2
virtual size: 5 GiB (5368709120 bytes)
disk size: 169 MiB
cluster_size: 65536
Format specific information:
compat: 1.1
compression type: zlib
lazy refcounts: false
refcount bits: 16
corrupt: false
extended l2: false
```
GitHub link:
https://github.com/apache/cloudstack/discussions/10829#discussioncomment-13074423
----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]
