[Bug 2084136] Re: Unable to get number of block I/O throttle parameters

2025-02-26 Thread Launchpad Bug Tracker
This bug was fixed in the package libvirt - 10.0.0-2ubuntu8.6 --- libvirt (10.0.0-2ubuntu8.6) noble; urgency=medium - d/p/u/lp-2084136-fix-get-number-block-io-throttle-params.patch: Fix issue preventing the user to obtain the number of block I/O parameters. (LP: #2084136)

[Bug 2084136] Re: Unable to get number of block I/O throttle parameters

2025-02-04 Thread Christian Ehrhardt
** Tags added: server-todo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2084136 Title: Unable to get number of block I/O throttle parameters To manage notifications about this bug go to: https://b

[Bug 2084136] Re: Unable to get number of block I/O throttle parameters

2025-01-27 Thread Sergio Durigan Junior
** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2084136 Title: Unable to get number of block I/O throttle parameters To manage notifications about this bug go to: htt

[Bug 2084136] Re: Unable to get number of block I/O throttle parameters

2025-01-27 Thread Jeffrey
** Tags removed: server-todo verification-needed verification-needed-noble ** Tags added: verification-done-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2084136 Title: Unable to get number of

[Bug 2084136] Re: Unable to get number of block I/O throttle parameters

2025-01-27 Thread Jeffrey
Hello Andreas, Just tested with version 10.0.0-2ubuntu8.6, and before the upgrade, `virsh blkdeviotune testvm sda` didn’t work. After the update, the same command gives me the expected iotune settings. This was tested on Ubuntu 24.04 (Noble). The fix seems to be working. Thanks! -- You received

[Bug 2084136] Re: Unable to get number of block I/O throttle parameters

2025-01-24 Thread Andreas Hasenack
Hello Jeffrey, or anyone else affected, Accepted libvirt into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libvirt/10.0.0-2ubuntu8.6 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https:

[Bug 2084136] Re: Unable to get number of block I/O throttle parameters

2025-01-20 Thread Sergio Durigan Junior
Uploaded to Noble. $ dput libvirt_10.0.0-2ubuntu8.6_source.changes Trying to upload package to ubuntu Checking signature on .changes gpg: /home/sergio/work/libvirt/libvirt_10.0.0-2ubuntu8.6_source.changes: Valid signature from 106DA1C8C3CBBF14 Checking signature on .dsc gpg: /home/sergio/work/lib

[Bug 2084136] Re: Unable to get number of block I/O throttle parameters

2025-01-20 Thread Sergio Durigan Junior
** Changed in: libvirt (Ubuntu Oracular) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2084136 Title: Unable to get number of block I/O throttle parameters To

[Bug 2084136] Re: Unable to get number of block I/O throttle parameters

2025-01-20 Thread Sergio Durigan Junior
** Description changed: + [ Impact ] + + Users of libvirt on Ubuntu Noble/Oracular are unable to query the I/O + throttle parameters of an image using virsh. + + [ Test plan ] + + TBD. + + [ Where problems could occur ] + + TBD. + + [ Original Description ] + Since Ubuntu 24.04, it is no

[Bug 2084136] Re: Unable to get number of block I/O throttle parameters

2025-01-20 Thread Sergio Durigan Junior
** Also affects: libvirt (Ubuntu Oracular) Importance: Undecided Status: New ** Also affects: libvirt (Ubuntu Plucky) Importance: Undecided Assignee: Sergio Durigan Junior (sergiodj) Status: Triaged ** Also affects: libvirt (Ubuntu Noble) Importance: Undecided S

[Bug 2084136] Re: Unable to get number of block I/O throttle parameters

2024-11-28 Thread Christian Ehrhardt 
Recreated in: - 10.6.0 from git - working - 10.0.0 from git - failing Bisecting from here ... commit 3a3f73ea9f1925ca5e256fa54c5aa451ddeaa19e Author: Michal Privoznik Date: Mon Jan 29 10:07:05 2024 +0100 remote_driver: Restore special behavior of remoteDomainGetBlockIoTune() In v

[Bug 2084136] Re: Unable to get number of block I/O throttle parameters

2024-11-28 Thread Christian Ehrhardt 
Tested on s390x to also check if this is cross arch - trying to recreate as reported. Jammy 8.0 Noble 10.0 Noble 10.6 backport Oracular 10.6 As guest I was using jammy, naming is j (jammy) -on- $release. They all are created with uvtool, like r=jammy; uvt-simplestreams-libvirt --verbose sync --s

[Bug 2084136] Re: Unable to get number of block I/O throttle parameters

2024-10-25 Thread Christian Ehrhardt 
Thanks for confirming, I think we need to find a bit of time to find or bisect what in between the versions 10.0 ->10.6 has fixed it. And once we know the change needed start considering a fix/backport. I've tagged it to come up in the next team bug sessions, but we are currently all travelling

[Bug 2084136] Re: Unable to get number of block I/O throttle parameters

2024-10-24 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libvirt (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2084136 Title: Un

[Bug 2084136] Re: Unable to get number of block I/O throttle parameters

2024-10-24 Thread Jeffrey
Thank you for your reply! I just tried the Oracular version (10.6.0-1ubuntu3) and the issue is not present there. I also tested the backport of 10.6.0-1ubuntu3 for Noble, and it works there without any issues as well. About the Debian libvirt package, I can only find versions 9.0.0 and 10.8, unfor

[Bug 2084136] Re: Unable to get number of block I/O throttle parameters

2024-10-23 Thread Mitchell Dzurick
Thank you for making this bug report Jeffrey, and making Ubuntu better! I'm curious if this is an issue with the Debian package or a delta we made, did you happen to try the debian libvirt package? I do see some historical bugs similar to this[0] but those patches are old and don't apply. Have y