Issues starting VM's in KVM.

I’m new to KVM and I was trying to set it up. After following the instructions, I get this error message. I did extract the qcow images on an external drive since my host machine doesn’t have much space. Not sure if that would effect anything since I moved them as in the instructions for KVM. Any idea?

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

https://www.oilandfish.com/posts/practical-anonymity-political-religious-dissidents.html#10-7

1 Like

Thank you! This may be a dumb question, but what is the command to edit the xml files? Everything I’ve tried just shows the file as empty and no lines to remove. I tried sudo edit /etc/apt/Whonix-Gateway-XFCE-15.0.1.3.9.xml for example.

sudo virsh edit Whonix-Workstation

or Whonix-Gateway

Thank you! It worked!

Now the only issue I’m having is that after I resize the VMs, the tool bar is on top instead of bottom and it doesn’t show the little Tor globe so I know I’m connected to Tor. Any ideas? Thanks for your help. I’m brand new to KVM.

Yes so the xfce toolbar and the start menu is set to show on top of the window. If you want to change that you can look at the general xfce settings. @Patrick any idea where we set that (if we do)?

As for the Tor globe you won’t see it in TBB in Whonix by design so this info isn’t leaked to attackers in the WS.

Thanks. I was referring to the little green globe in the right corner once it connects. Im just curious because it shows there in virtual box, but not on KVM.

Tor Browser Essentials

find . -type f -not -iwholename '*.git*' | grep -i xfce

./security-misc/etc/skel/.config/xfce4/xfconf/xfce-perchannel-xml/thunar.xml
./security-misc/etc/sudoers.d/xfce-security-misc
./usability-misc/etc/skel/.config/xfce4/terminal/terminalrc
./anon-gw-base-files/etc/skel/.config/xfce4/xfconf/xfce-perchannel-xml/xfce4-desktop.xml.anondist
./whonix-xfce-desktop-config/GPLv3
./whonix-xfce-desktop-config/usr/share/livecheck/livecheck.sh
./whonix-xfce-desktop-config/usr/share/lintian/overrides/whonix-xfce-desktop-config
./whonix-xfce-desktop-config/changelog.upstream
./whonix-xfce-desktop-config/debian/control
./whonix-xfce-desktop-config/debian/compat
./whonix-xfce-desktop-config/debian/whonix-xfce-desktop-config.maintscript
./whonix-xfce-desktop-config/debian/source/format
./whonix-xfce-desktop-config/debian/source/lintian-overrides
./whonix-xfce-desktop-config/debian/changelog
./whonix-xfce-desktop-config/debian/watch
./whonix-xfce-desktop-config/debian/copyright
./whonix-xfce-desktop-config/debian/whonix-xfce-desktop-config.install
./whonix-xfce-desktop-config/debian/rules
./whonix-xfce-desktop-config/etc/skel/.config/xfce4/xfconf/xfce-perchannel-xml/xfce4-panel.xml
./whonix-xfce-desktop-config/etc/skel/.config/xfce4/xfconf/xfce-perchannel-xml/xsettings.xml
./whonix-xfce-desktop-config/etc/skel/.config/xfce4/xfconf/xfce-perchannel-xml/xfce4-session.xml
./whonix-xfce-desktop-config/etc/skel/.config/xfce4/xfconf/xfce-perchannel-xml/xfce4-desktop.xml
./whonix-xfce-desktop-config/etc/skel/.config/xfce4/xfconf/xfce-perchannel-xml/xfwm4.xml
./whonix-xfce-desktop-config/etc/skel/.config/xfce4/panel/launcher-5/15404745781.desktop
./whonix-xfce-desktop-config/etc/skel/.config/xfce4/panel/launcher-6/15404746372.desktop
./whonix-xfce-desktop-config/etc/skel/.config/xfce4/panel/whiskermenu-1.rc
./whonix-xfce-desktop-config/etc/skel/.config/xfce4/panel/launcher-7/15404746583.desktop
./whonix-xfce-desktop-config/etc/skel/.config/xfce4/panel/genmon-12.rc
./whonix-xfce-desktop-config/etc/sudoers.d/whonix-xfce-desktop-config
./whonix-xfce-desktop-config/CONTRIBUTING.md
./whonix-xfce-desktop-config/COPYING
./whonix-xfce-desktop-config/README.md
./vm-config-dist/etc/skel/.config/xfce4/xfconf/xfce-perchannel-xml/displays.xml
./anon-ws-base-files/etc/skel/.config/xfce4/xfconf/xfce-perchannel-xml/xfce4-desktop.xml.anondist

Yes, task bar position can be freely changed as per usual Xfce use as per Free Support for Whonix ™

1 Like

Hello, I updated Debian to the testing version on the host system, I got the same error, but after deleting the lines, I get the following on startup:
[ 1.349298] general protection fault: 0000 [#1] SMP PTI
[ 1.349749] CPU: 0 PID: 10 Comm: rcu_sched Not tainted 4.19.0-10-amd64 #1 Debian 4.19.132-1
[ 1.350404] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.14.0-1 04/01/2014
[ 1.351074] RIP: 0010:switch_mm_irqs_off+0x2a5/0x4f0
[ 1.351512] Code: 41 5c 41 5d 41 5e 41 5f c3 65 48 8b 05 9c 42 9b 77 48 3b 87 18 04 00 00 0f 84 ed fd ff ff b9 49 00 00 00 b8 01 00 00 00 31 d2 <0f> 30 48 8b 87 18 04 00 00 65 48 89 05 72 42 9b 77 e9 cb fd ff ff
[ 1.353169] RSP: 0000:ffffb34b0011bd88 EFLAGS: 00010046
[ 1.353173] RAX: 0000000000000001 RBX: ffff9c7896381340 RCX: 0000000000000049
[ 1.353173] RDX: 0000000000000000 RSI: ffff9c7896381340 RDI: ffff9c78962b4a00
[ 1.353173] RBP: ffffffff8967ccc0 R08: ffff9c789fa22ae0 R09: 0000000000000000
[ 1.353173] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
[ 1.353173] R13: ffff9c78962b4a00 R14: ffff9c7896381340 R15: ffff9c7896381340
[ 1.353173] FS: 0000000000000000(0000) GS:ffff9c789fa00000(0000) knlGS:0000000000000000
[ 1.353173] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 1.353173] CR2: 00007f5057e24486 CR3: 000000000760a001 CR4: 0000000000360ef0
[ 1.353173] Call Trace:
[ 1.353173] __schedule+0x263/0x870
[ 1.353173] schedule+0x28/0x80
[ 1.353173] schedule_timeout+0x16b/0x390
[ 1.353173] ? __next_timer_interrupt+0xc0/0xc0
[ 1.353173] rcu_gp_kthread+0x40d/0x850
[ 1.353173] ? call_rcu_sched+0x20/0x20
[ 1.353173] kthread+0x112/0x130
[ 1.353173] ? kthread_bind+0x30/0x30
[ 1.353173] ret_from_fork+0x35/0x40
[ 1.353173] Modules linked in:
[ 1.353173] —[ end trace 7e86a46bf8972822 ]—
[ 1.353173] RIP: 0010:switch_mm_irqs_off+0x2a5/0x4f0
[ 1.353173] Code: 41 5c 41 5d 41 5e 41 5f c3 65 48 8b 05 9c 42 9b 77 48 3b 87 18 04 00 00 0f 84 ed fd ff ff b9 49 00 00 00 b8 01 00 00 00 31 d2 <0f> 30 48 8b 87 18 04 00 00 65 48 89 05 72 42 9b 77 e9 cb fd ff ff
[ 1.353173] RSP: 0000:ffffb34b0011bd88 EFLAGS: 00010046
[ 1.353173] RAX: 0000000000000001 RBX: ffff9c7896381340 RCX: 0000000000000049
[ 1.353173] RDX: 0000000000000000 RSI: ffff9c7896381340 RDI: ffff9c78962b4a00
[ 1.353173] RBP: ffffffff8967ccc0 R08: ffff9c789fa22ae0 R09: 0000000000000000
[ 1.353173] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
[ 1.353173] R13: ffff9c78962b4a00 R14: ffff9c7896381340 R15: ffff9c7896381340
[ 1.353173] FS: 0000000000000000(0000) GS:ffff9c789fa00000(0000) knlGS:0000000000000000
[ 1.353173] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 1.353173] CR2: 00007f5057e24486 CR3: 000000000760a001 CR4: 0000000000360ef0

I tried searching for your error but I can’t find anything helpful. Try sticking with stable on the host for a better experience. Some years back I was running testing because it had newer packages and had some close calls for reinstalling my system because an update fucked something up like crippling DE startup. I saw some random bugs show up then go away on their own during the release cycle and so went with stable for a more predictable workflow.

randomwhonixuser via Whonix Forum:

[    1.351074] RIP: 0010:switch_mm_irqs_off+0x2a5/0x4f0

Looks like a kernel panic. Search the web for “kernel rip”. Issue not
caused by Whonix and should be resolved as per

Hello I installed KVM Whonix on a new machine and for some reason I can’t edit the files using virsh. It won’t let me remove the lines so I can start the vms. Any idea why? My host is Kali.

Are you starting the virsh command with sudo/su? It needs privileges to work.

What error do you see when you save the modified file? Maybe you forget to save it and so it doesn’t take effect? I need more details.

1 Like