From: abenson <abenson@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] libvirt when trying to create a new storage pool (in virFileSetCOW)
Date: Wed, 19 Aug 2020 03:00:44 +0200 [thread overview]
Message-ID: <20200819010044.4azVbi_9OrJL_13Ij4SOa0QAyenvImYLXHoPKnluzMY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24347@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1246 bytes --]
Closed issue by LucaTony on void-packages repository
https://github.com/void-linux/void-packages/issues/24347
Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System
* xuname:
`Void 5.7.15_1 x86_64 GenuineIntel uptodate rFF`
* package:
`virt-manager-2.2.1_2`
` --libvirt-6.6.0_1`
### Expected behavior
It is possible to create a new storage pool with virt-manager.
### Actual behavior
It is not possible to create a new storage pool due to the following error:
`Error creating pool: Could not build storage pool: unable to control COW flag on '/var/lib/libvirt/images/pool', not btrfs: Function not implemented.`
### Steps to reproduce the behavior
1. Open `virt-manager` and create a new virtual machine.
2. Choose ISO or CD-ROM
3. Browse
4. Add new storage pool
5. Finish
This is already a known bug: (https://bugzilla.redhat.com/show_bug.cgi?id=1866157).
And there is also a patch for it: https://www.redhat.com/archives/libvir-list/2020-August/msg00259.html
Commit: https://gitlab.com/libvirt/libvirt/-/commit/2edd63a0dbd445112db23596ee0128521e8f1ff5
prev parent reply other threads:[~2020-08-19 1:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-18 19:50 [ISSUE] " LucaTony
2020-08-19 1:00 ` abenson [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200819010044.4azVbi_9OrJL_13Ij4SOa0QAyenvImYLXHoPKnluzMY@z \
--to=abenson@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).