[GH-ISSUE #400] unsupported flags (0x1) in function storageVolumeCreateXML #301

Closed
opened 2026-02-27 16:38:47 +03:00 by kerem · 7 comments
Owner

Originally created by @goshlanguage on GitHub (Aug 28, 2014).
Original GitHub issue: https://github.com/retspen/webvirtmgr/issues/400

When attempting to create new VMs lately, I keep running into this:
"unsupported flags (0x1) in function storageVolumeCreateXML" at http://webvirtmgr/create/1/

In /var/log/libvirt/libvirtd.log I am getting the following:
2014-08-28 15:53:47.440+0000: 5986: error : storageVolumeCreateXML:1371 : unsupported flags (0x1) in function storageVolumeCreateXML
2014-08-28 15:53:56.013+0000: 5989: error : storageVolumeCreateXML:1371 : unsupported flags (0x1) in function storageVolumeCreateXML
2014-08-28 15:57:14.940+0000: 5990: error : storageVolumeCreateXML:1371 : unsupported flags (0x1) in function storageVolumeCreateXML

This same storage worked before running a recent git pull in webvirtmgr, it is not full, and it's not in Read Only.

I googled the error but it seems to not be present elsewhere. I can manually do things through virsh shell still, but not through the interface. Is anyone else having a similar issue?

I tried it on a fresh server installation, and it's doing the same thing. If you clone an image, or create the image in your storage manually, then create a custom VM, everything works fine.

Originally created by @goshlanguage on GitHub (Aug 28, 2014). Original GitHub issue: https://github.com/retspen/webvirtmgr/issues/400 When attempting to create new VMs lately, I keep running into this: "unsupported flags (0x1) in function storageVolumeCreateXML" at http://webvirtmgr/create/1/ In /var/log/libvirt/libvirtd.log I am getting the following: 2014-08-28 15:53:47.440+0000: 5986: error : storageVolumeCreateXML:1371 : unsupported flags (0x1) in function storageVolumeCreateXML 2014-08-28 15:53:56.013+0000: 5989: error : storageVolumeCreateXML:1371 : unsupported flags (0x1) in function storageVolumeCreateXML 2014-08-28 15:57:14.940+0000: 5990: error : storageVolumeCreateXML:1371 : unsupported flags (0x1) in function storageVolumeCreateXML This same storage worked before running a recent git pull in webvirtmgr, it is not full, and it's not in Read Only. I googled the error but it seems to not be present elsewhere. I can manually do things through virsh shell still, but not through the interface. Is anyone else having a similar issue? I tried it on a fresh server installation, and it's doing the same thing. If you clone an image, or create the image in your storage manually, then create a custom VM, everything works fine.
kerem closed this issue 2026-02-27 16:38:47 +03:00
Author
Owner

@retspen commented on GitHub (Aug 29, 2014):

Uncheck metadata when you are creating VM

<!-- gh-comment-id:53843800 --> @retspen commented on GitHub (Aug 29, 2014): Uncheck metadata when you are creating VM
Author
Owner

@goshlanguage commented on GitHub (Aug 29, 2014):

Thanks, why is this checked by default if it results in erroring? Is this for Ceph/LVM storages?

<!-- gh-comment-id:53884966 --> @goshlanguage commented on GitHub (Aug 29, 2014): Thanks, why is this checked by default if it results in erroring? Is this for Ceph/LVM storages?
Author
Owner

@retspen commented on GitHub (Aug 31, 2014):

This work only for dir storage and qcow2 images. You need update project.

<!-- gh-comment-id:53997402 --> @retspen commented on GitHub (Aug 31, 2014): This work only for dir storage and qcow2 images. You need update project.
Author
Owner

@goshlanguage commented on GitHub (Sep 2, 2014):

Thanks Anatoliy

<!-- gh-comment-id:54149420 --> @goshlanguage commented on GitHub (Sep 2, 2014): Thanks Anatoliy
Author
Owner

@leftalon commented on GitHub (Sep 4, 2014):

qcow raw is ok
qcow2 unsupported flags (0x1) in function storageVolumeCreateXML
How to solve?

<!-- gh-comment-id:54431571 --> @leftalon commented on GitHub (Sep 4, 2014): qcow raw is ok qcow2 unsupported flags (0x1) in function storageVolumeCreateXML How to solve?
Author
Owner

@goshlanguage commented on GitHub (Sep 4, 2014):

If you update your project with git pull, it will have unchecked metadata for you on instance creation. Or, as Retspen said already, you can just uncheck "metadata" while creating an instance to get past this.

<!-- gh-comment-id:54480907 --> @goshlanguage commented on GitHub (Sep 4, 2014): If you update your project with git pull, it will have unchecked metadata for you on instance creation. Or, as Retspen said already, you can just uncheck "metadata" while creating an instance to get past this.
Author
Owner

@Aiden-zyq commented on GitHub (Nov 13, 2018):

thx,My webvirtmgr is directory like, without page image display.

<!-- gh-comment-id:438115598 --> @Aiden-zyq commented on GitHub (Nov 13, 2018): thx,My webvirtmgr is directory like, without page image display.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/webvirtmgr#301
No description provided.