This bug was fixed in the package libvirt - 6.6.0-1ubuntu3.1
---
libvirt (6.6.0-1ubuntu3.1) groovy; urgency=medium
* d/p/ubuntu/lp-1901242-util-Fix-logic-in-virFileSetCOW.patch: fix dir pool
handling on non BTRFS affecting virt-manager, api and commandline pool
handling (LP:
Wanted to confirm that I have installed 6.6.0-1ubuntu3.1 from groovy-
proposed and can now create pools!
Thank you everyone for the work to fix this!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901
Prio to the fix
root@g:~# dpkg -l libvirt-daemon-system
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name VersionArchitecture Descript
Hello Lukasz,
Thank you for your great work. I already tested this, enabled groovy-
proposed, updated and restarted system. I saw libvirt updates and apt-
cache confirmed version 6.6.0-1ubuntu3.1
After reboot, I created a local storage repository with virt-manager and
it worked right away. No mor
Hello Mauro, or anyone else affected,
Accepted libvirt into groovy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/libvirt/6.6.0-1ubuntu3.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://
This bug was fixed in the package libvirt - 6.6.0-1ubuntu4
---
libvirt (6.6.0-1ubuntu4) hirsute; urgency=medium
* d/p/ubuntu/lp-1901242-util-Fix-logic-in-virFileSetCOW.patch: fix dir pool
handling on non BTRFS affecting virt-manager, api and commandline pool
handling (LP: #1
FYI - Uploaded the fix to Hirsute (a bit slow due to the test queue
being rather full atm) and to groovy-unapproved for the SRU process.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901242
Title:
I have prepared merge-requests for the required packaging changes and a PPA [1].
But right now builders are all kind of stuck so the PPA doesn't have much to
try yet :-/
[1]: https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/4320/+packages
--
You received this bug notification becaus
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/libvirt/+git/libvirt/+merge/392921
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/libvirt/+git/libvirt/+merge/392922
--
You received this bug notification because you are a member o
** Description changed:
[Impact]
- * An upstream change in libvirt 6.6 [1] broke logic if creating a pool
-without an explicit yes/now for COW handling.
+ * An upstream change in libvirt 6.6 [1] broke the logic of creating a
+pool without an explicit yes/no for COW handling.
- *
** Changed in: libvirt (Ubuntu)
Assignee: (unassigned) => Christian Ehrhardt (paelzer)
** Tags added: server-next
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901242
Title:
virt-manager lo
Thanks @ Christian for the thorough investigation.
I also tried virsh commands and found exactly the same issue as you described.
It is good that we at least for now have workarounds to create and enabled
storage repository.
--
You received this bug notification because you are a member of Ubun
Already added an SRU Template to the bug description to be ready for SRU
processing asap then.
** Description changed:
+ [Impact]
+
+ * An upstream change in libvirt 6.6 [1] broke logic if creating a pool
+without an explicit yes/now for COW handling.
+
+ * Another upstream patch in libvi
Ok, now that I knew what to look for I guess I found it.
#1 Workaround (other than installing cockpit) for now can be a commandline call
like:
$ virsh pool-create-as --name home --type dir --target /home
#2 testing without virt-manager
$ virsh pool-define-as --name home --type dir --target /home
Tracing libvirtd and checking what really "appears int he request" I see
that:
the console request (that works) has:
debug : virStoragePoolCreateXML:564 : conn=0x7f39640040b0,
xmlDesc=
home
/home
, flags=0x0
The request from virt-manager for what should be the same has:
debug : vir
I found that with libvirt 6.0 this works and libvirt 6.6 fails (when
driven from virt-manager). This isn't a virt-manager but a libvirt issue
** Also affects: libvirt (Ubuntu)
Importance: Undecided
Status: New
** Changed in: libvirt (Ubuntu)
Status: New => Confirmed
** Changed i
Good case (commandline):
2020-10-26 08:08:15.210+: 941251: debug : virStoragePoolDefineXML:607 :
conn=0x7efd580040a0, xml=
home
/home
, flags=0x0
2020-10-26 08:08:15.210+: 941251: debug : virFileMakePathHelper:3038 :
path=/etc/libvirt/storage mode=0777
2020-10-26 08:08:15.22
I was switching my commandline to use a more equivalent sequence which
is using define+start instead of a direct create:
$ virsh pool-define-as --name home --type dir --target /home --print-xml
$ virsh pool-start home
$ virsh pool-destroy home
$ virsh pool-undefine home
But now I get it still wor
Confirmed:
Okt 26 08:49:04 Keschdeichel libvirtd[931584]: unable to control COW flag on
'/home', not btrfs: Function not implemented
** Changed in: virt-manager (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
The XML virt-manager creates is listed as (in virt-manager XML view when
creating it):
home
/home
That is the same as:
$ virsh pool-create-as --print-xml --name home --type dir --target /home
home
/home
But interestingly the command to create it works fine:
$ virsh p
Interesting workaround found to keep using virt-manager:
1. Install cockpit-machines
2. Login to https://localhost:9090
3. Create the storage pool from cockpit, on same ext4 file system
The storage pool is added successfully, and immediately available on
virt-manager too.
--
You received this b
21 matches
Mail list logo
