For me, the *_bytes_sec qos properties don't work, while *_iops_sec 
seem to work (I haven't checked if IOPS are really limited), but at 
least the VMs are booting successfully.

Zitat von Eugen Block <eblock@nde.ag>:

> I can confirm this for Antelope as well. The VM is stuck in "GRUB is 
> loading" or something. I haven't found any errors yet in cinder or 
> nova, but I haven'T looked too closely yet.
> And as OP already mentioned, disassociating the qos from the volume 
> type isn't enough, even without a qos associated, the VM is stuck 
> booting. I haven't searched launchpad yet for existing bugs, will do 
> that next week.
>
>
> Zitat von Nguyễn Hữu Khôi <nguyenhuukhoinw@gmail.com>:
>
>> I set total_bytes_sec=300 so it causes this error. But when I remove this
>> parameter, this error still occurs.
>>
>> Nguyen Huu Khoi
>>
>>
>> On Wed, Apr 30, 2025 at 10:31 PM Nguyễn Hữu Khôi <nguyenhuukhoinw@gmail.com>
>> wrote:
>>
>>> Hello.
>>> I create a volume type with qos which uses frontend consumer then I create
>>> an instance which booted from a volume, however, It stucked it booting from
>>> hardisk.
>>>
>>> What could will be? Pls give me some ideas on this? Thank you.
>>> Env:
>>>
>>> Openstack 2025.1
>>> KollaAnsible 2025.1 master
>>> Ubuntu 2024.02
>>>
>>> Nguyen Huu Khoi
>>>
>>>