GitHub user yyzkevin added a comment to the discussion: NAS B&R KVM (ACS 4.20)
Restore & Attach Issue
I do not receive any error, everything looks as expected the backup is used to
create a volume on the primary storage and it is attached to the instance
(running or stopped). I initially noticed that the attached disk had no
partition table, and when I looked at start of the device (vdb) I could see
it was actually a qcow2 label seen from within the guest.
This is what is seen on the hypervisor, which is Ubuntu 24.04.2 LTS.
`root@cs-node1:/# virsh qemu-monitor-command i-2-89-VM --hmp 'info block'
libvirt-2-format:
/mnt/12490f2a-e712-308b-9479-0bcc3d465d8b/67f72268-35b4-4964-98d3-a5298bd958c8
(qcow2)
Attached to: /machine/peripheral/virtio-disk0/virtio-backend
Cache mode: writeback
ide0-1-0: [not inserted]
Attached to: ide0-1-0
Removable device: not locked, tray closed
libvirt-5-format:
/mnt/12490f2a-e712-308b-9479-0bcc3d465d8b/63423044-52bd-40ef-9d7c-ec1939ceaf04
(raw)
Attached to: /machine/peripheral/virtio-disk1/virtio-backend
Cache mode: writeback, direct
`
When I look in the volumes table I see its format is NULL.
`+----+---------------------------+--------+
| id | name | format |
+----+---------------------------+--------+
| 93 | ROOT-89 | QCOW2 |
| 94 | RestoredVol-THE GOOD DISK | NULL |
| 95 | RestoredVol-THE GOOD DISK | NULL |
| 96 | RestoredVol-ROOT-86 | NULL |
+----+---------------------------+--------+
`
GitHub link:
https://github.com/apache/cloudstack/discussions/10829#discussioncomment-13074041
----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]
