Oh, I'm really sorry.
It doesn't work as you said, and it should be throttle-node instead of
qcow2-node.
On the other hand, is it difficult to apply and manage throttle using
the QMP command?
Sincerely,
2025년 1월 27일 (월) 오후 7:42, Alberto Garcia <be...@igalia.com>님이 작성:
>
> On Thu, Jan 09, 2025 at 11:02:46AM +0900, Henry lol wrote:
> > scenario where throttle works as expected
> >
> > 2-1 execute the qemu process with
> > ...
> > -object throttle-group,id=tg,x-bps-total=10485760 \
> > -blockdev
> > '{"driver":"throttle","throttle-group":"tg","node-name":"throttle-node","file":{
> >
> > "driver":"qcow2","node-name":"qcow2-node","file":{"driver":"file","filename":"/path/to/file.qcow2"}
> > }}' \
> > -device
> > virtio-blk-pci,scsi=off,drive=qcow2-node,id=did,bootindex=1,bus=pci.0,addr=0x05,serial=1234
>
> How is this supposed to work as expected when the guest sees
> qcow2-node (which is the unfiltered qcow2 file) instead of
> throttle-node (which is the one that applies the limits that you set)?
>
> -device virtio-blk-pci,scsi=off,drive=qcow2-node
> ^^^^^^^^^^
>
> If I run that example the x-bps-total limit is ignored.
>
> Berto
>
