[GH-ISSUE #194] Missing format type on LVM volumes (logical pools) #150

New issue

Closed

opened 2026-02-27 16:38:09 +03:00 by kerem · 0 comments

kerem commented

2026-02-27 16:38:09 +03:00

Owner

Originally created by @jansauerbrey on GitHub (Jan 19, 2014).
Original GitHub issue: https://github.com/retspen/webvirtmgr/issues/194

Hi,

I have encountered the following issue:

In the storate pool view showing all the volumes the format type is None. The reason for this is that also the command
virsh vol-dumpxml /dev/pool/test
shows no

This itself is not such a big issue for me, but it results in the problem, that when I create a new machine its created with the xml lines for the disk:

this then results in a problem with libvirt and AppArmor:

error: Failed to start domain test
error: internal error cannot load AppArmor profile 'libvirt-b37fd5ff-0ad8-3bc4-8bb7-4378672582b6'

I do not know if my configuration is somehow problematic and somehow new volumes are missing this format type tag in their xml configuration. If this is always the case I would suggest to change the function get_volume_type to address this issue.

Thanks a lot

Jan

Originally created by @jansauerbrey on GitHub (Jan 19, 2014). Original GitHub issue: https://github.com/retspen/webvirtmgr/issues/194 Hi, I have encountered the following issue: In the storate pool view showing all the volumes the format type is None. The reason for this is that also the command virsh vol-dumpxml /dev/pool/test shows no <format type='raw'/> This itself is not such a big issue for me, but it results in the problem, that when I create a new machine its created with the xml lines for the disk: <driver name='qemu' type='None'/> this then results in a problem with libvirt and AppArmor: error: Failed to start domain test error: internal error cannot load AppArmor profile 'libvirt-b37fd5ff-0ad8-3bc4-8bb7-4378672582b6' I do not know if my configuration is somehow problematic and somehow new volumes are missing this format type tag in their xml configuration. If this is always the case I would suggest to change the function get_volume_type to address this issue. Thanks a lot Jan