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 --source 
http://cloud-images.ubuntu.com/daily arch=s390x label=daily release=${r}
uvt-kvm create --password=ubuntu --ssh-public-key-file 
/home/ubuntu/.ssh/authorized_keys j-on-j release=${r] arch=s390x label=daily

That by default has only virtio disks

virsh domblklist j-on-j
 Target   Source
---------------------------------------------------------
 vda      /var/lib/uvtool/libvirt/images/j-on-j.qcow
 vdb      /var/lib/uvtool/libvirt/images/j-on-j-ds.qcow


    <disk type='file' device='disk'>
      <driver name='qemu' type='qcow2'/>
      <source file='/var/lib/uvtool/libvirt/images/j-on-j.qcow' index='2'/>
      <backingStore type='file' index='3'>
        <format type='qcow2'/>
        <source 
file='/var/lib/uvtool/libvirt/images/x-uvt-b64-Y29tLnVidW50dS5jbG91ZC5kYWlseTpzZXJ2ZXI6MjIuMDQ6czM5MHggMjAyNDEwMDQ='/>
        <backingStore/>
      </backingStore>
      <target dev='vda' bus='virtio'/>
      <alias name='virtio-disk0'/>
      <address type='ccw' cssid='0xfe' ssid='0x0' devno='0x0000'/>
    </disk>


This is intentionally (for the mentioned cross check) quite different
- virtio instead of the assumed scsi or ide you have behind sda
- ccw bus connection
- architecture

And gladly still I can reproduce it

root@j-lp2084136:~# virsh blkdeviotune j-on-j vda
total_bytes_sec: 0
...

root@n-lp2084136:~# virsh blkdeviotune j-on-n vda
error: Unable to get number of block I/O throttle parameters
error: An error occurred, but the cause is unknown

root@o-lp2084136:~# virsh blkdeviotune j-on-o vda
total_bytes_sec: 0
...


Noble upgraded to the 10.6 backport 
10.6.0-1ubuntu3~backport24.04.202410200032~ubuntu24.04.1
root@n-lp2084136:~# virsh blkdeviotune j-on-n vda
total_bytes_sec: 0
...


So confirming all that Jeffrey reported,
the issue seems to be pretty generic in regard to disk types
and can easily be reproduced.

** Changed in: libvirt (Ubuntu)
       Status: Confirmed => Triaged

-- 
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://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/2084136/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to