[HOME] [DOWNLOAD] [DOCS] [NEWS] [SUPPORT] [TIPS] [ISSUES] [DONATE]

cannot set CPU affinity on process 1994: invalid argument

Well, now I’m sure, that something went wrong.

I installed kvm and imported the whonix vms, but I can’t start the workstation. Interestingly, the gateway vm works without any visible problems, but when I start the workstation vm, I get this message:

Error during the start of the domain: cannot set CPU affinity on process 1994: invalid argument

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/libvirtobject.py”, line 66, in newfn
ret = fn(self, *args, **kwargs)
File “/usr/share/virt-manager/virtManager/domain.py”, line 1400, in startup
self._backend.create()
File “/usr/lib/python3/dist-packages/libvirt.py”, line 1080, in create
if ret == -1: raise libvirtError (‘virDomainCreate() failed’, dom=self)
libvirt.libvirtError: cannot set CPU affinity on process 1994: invalid argument

I don’t know, what exactly went wrong. Maybe I should have installed kicksecure-cli on top of headless debian.

Please apply this change to both VMs and try again:

1 Like

I just had this same problem when I reinstalled a minimalist debian install with kicksecure as a host when I tried to run a whonix vm.

I removed cpuset=‘1’ and it fixed it, but I’m not quite sure why this was necessary as I haven’t did anything custom with the cpu.

I did this to minimize impact of sidechannel attacks on crypto operations if the WS is compromised.

Yeah thats why I wish I didnt have to remove it for it to work

[Imprint] [Privacy Policy] [Cookie Policy] [Terms of Use] [E-Sign Consent] [DMCA] [Investors] [Priority Support] [Professional Support]