Problem wth KVM in ParrotOS

KVM
#1

Srarting Whonix-Gateway or Whonix-Workstation VMs produces the following error.:

Error starting domain: Requested operation is not valid: blkio device weight is valid only for bfq or cfq scheduler

Traceback (most recent call last):
File “/usr/share/virt-manager/virtManager/asyncjob.py”, line 75, in cb_wrapper
callback(asyncjob, *args, **kwargs)
File “/usr/share/virt-manager/virtManager/asyncjob.py”, line 111, in tmpcb
callback(*args, **kwargs)
File “/usr/share/virt-manager/virtManager/object/libvirtobject.py”, line 66, in newfn
ret = fn(self, *args, **kwargs)
File “/usr/share/virt-manager/virtManager/object/domain.py”, line 1279, in startup
self._backend.create()
File “/usr/lib/python3/dist-packages/libvirt.py”, line 1234, in create
if ret == -1: raise libvirtError (‘virDomainCreate() failed’, dom=self)
libvirt.libvirtError: Requested operation is not valid: blkio device weight is valid only for bfq or cfq scheduler

Following these steps seems to fix the issue.
Notice that ParrotOS is a Debian-based distribution.Does the documentation need updating or is this in fact a bug?

#2

Is parrot on stable or testing? I guess we’ll soon find out if this is a problem on 11 and I will just have to throw this setting out, but I’d rather not because it provides resource restrictions against DoS attacks.

#3

ParrotOS is based on Testing. Can you share your sources about Dos attacks?

#4

Don’t have it on hand, but by the rationale of putting 2 and 2 together, limiting a common resource on a machine (whether RAM, CPU or iops in this case) would limit potential for abuse by a compromised VM and also help security by not affecting other processes in visible ways - which can act as a sidechannel.

#5

I see.Maybe setting and flags might he4lp the issue.As mentioned here and here.

#6

Ok. If I run into this problem on Bullseye I will remove it.

1 Like