Debian Bug report logs - #979859
libvirt0: Starting virtual pc with virtManager cause raise libvirtError setCpusetMemoryMigrate' not supported

Reply or subscribe to this bug.

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Sven Jörns <debianbug@sven-joerns.de>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: libvirt0: Starting virtual pc with virtManager cause raise libvirtError setCpusetMemoryMigrate' not supported

Date: Tue, 12 Jan 2021 03:20:06 +0100

Package: libvirt0
Version: 5.0.0-4+deb10u1
Severity: important

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
        Starting any virtual pc with virtManager
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
   * What was the outcome of this action?
Error report VirtManager:
        Fehler beim Starten der Domain: Operation not supported: operation
'setCpusetMemoryMigrate' not supported

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 1080, in create
    if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirt.libvirtError: Operation not supported: operation
'setCpusetMemoryMigrate' not supported

   * What outcome did you expect instead?
        Just starting the VM like day before.

*** End of the template - remove these template lines ***



-- System Information:
Debian Release: 10.7
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.6 (SMP w/12 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libvirt0 depends on:
ii  libacl1             2.2.53-4
ii  libapparmor1        2.13.2-10
ii  libaudit1           1:2.8.4-3
ii  libavahi-client3    0.7-4+b1
ii  libavahi-common3    0.7-4+b1
ii  libc6               2.28-10
ii  libcap-ng0          0.7.9-2
ii  libcurl3-gnutls     7.64.0-4+deb10u1
ii  libdbus-1-3         1.12.20-0+deb10u1
ii  libdevmapper1.02.1  2:1.02.155-3
ii  libgcc1             1:8.3.0-6
ii  libgnutls30         3.6.7-4+deb10u5
ii  libnl-3-200         3.4.0-1
ii  libnl-route-3-200   3.4.0-1
ii  libnuma1            2.0.12-1
ii  libsasl2-2          2.1.27+dfsg-1+deb10u1
ii  libselinux1         2.8-1+b1
ii  libssh2-1           1.8.0-2.1
ii  libxml2             2.9.4+dfsg1-7+deb10u1
ii  libyajl2            2.1.0-3

Versions of packages libvirt0 recommends:
ii  lvm2  2.03.02-3

libvirt0 suggests no packages.

-- no debconf information

Message #10 received at 979859@bugs.debian.org (full text, mbox, reply):

From: Системные администраторы ЦИСТ <sa_staff@volgatech.net>

To: "979859@bugs.debian.org" <979859@bugs.debian.org>

Date: Thu, 21 Jan 2021 11:58:11 +0000

[Message part 1 (text/plain, inline)]

Same issue. Buster-backports enabled.

[Message part 2 (text/html, inline)]

Message #15 received at 979859@bugs.debian.org (full text, mbox, reply):

From: Manuel Espina <m.espina@gmail.com>

To: 979859@bugs.debian.org

Subject: Re: libvirt0: Starting virtual pc with virtManager cause raise libvirtError setCpusetMemoryMigrate' not supported

Date: Thu, 21 Jan 2021 17:47:32 +0100

The workaround mentioned in bug #935734 seems to work: configuring
cgroup_controllers = [ ] in /etc/libvirt/qemu.conf and restarting
libvirtd makes the virtual machines boot again.

Message #20 received at 979859@bugs.debian.org (full text, mbox, reply):

From: Eloi Coutant-Flexer <eloi@anbuco.fr>

To: 979859@bugs.debian.org

Subject: Re: libvirt0: Starting virtual pc with virtManager cause raise

Date: Tue, 16 Feb 2021 17:25:23 +0100

I can confirm this on a Debian Buster with backports enabled, workaround 
mentioned is working.

A similar issue was pushed to redhat tracker, and it seems that 
libvirt5.1 might fix the issue: 
https://bugzilla.redhat.com/show_bug.cgi?id=1688736

Send a report that this bug log contains spam.