Failed to acquire pid file : /var/local/run/libvirt/qemu/driver.pid
- Thread starter ziomario
- Start date
i haven't done a lot of work with apparmor. do you remember turning it off or disabling it at all?
understood. my point was more along the lines of do you have a package to replace all of those since they seem to be helpful or necessary.
though at this point if apparmor isn't starting, that seems like it could be the issue.
I made a progress. In :
/usr/share/polkit-1/actions/org.libvirt.unix.policy
I have changed this :
to this :
and boom : QEMU and KVM are connected now,but unfortunately,nothing happens when I try to create a virtual machine. When I click on "File / New Virtual Machine",nothing happens.
/usr/share/polkit-1/actions/org.libvirt.unix.policy
I have changed this :
Code:
<action id="org.libvirt.unix.manage">
<description>Manage local virtualized systems</description>
<message>System policy prevents management of local virtualized systems</message>
<defaults>
<!-- Any program can use libvirt in read/write mode if they
provide the root password -->
<allow_any>auth_admin_keep</allow_any>
<allow_inactive>auth_admin_keep</allow_inactive>
<allow_active>auth_admin_keep</allow_active>
</defaults>
</action>to this :
Code:
<action id="org.libvirt.unix.manage">
<description>Manage local virtualized systems</description>
<message>System policy prevents management of local virtualized systems</message>
<defaults>
<!-- Any program can use libvirt in read/write mode if they
provide the root password -->
<allow_any>yes</allow_any>
<allow_inactive>yes</allow_inactive>
<allow_active>yes</allow_active>
</defaults>
</action>and boom : QEMU and KVM are connected now,but unfortunately,nothing happens when I try to create a virtual machine. When I click on "File / New Virtual Machine",nothing happens.
Do you know what's the command to create a bridge called "virbr0" with the default assigned IP number ? Because I see that the virt-manager connection has it assigned,but from the terminal I see that it hasn't been created.
it says it is inactive. you could try verifying with
then i believe
will change that to Active.
editing to add: or if you make that window taller, there may be a > start button near the bottom left.
sudo virsh net-info defaultthen i believe
sudo virsh net-start defaultwill change that to Active.
editing to add: or if you make that window taller, there may be a > start button near the bottom left.
oh oh,a lot of shit came out from the manhole 
Code:
Error starting network 'default': internal error:
Failed to apply firewall rules /usr/sbin/iptables -w --table mangle --list-rules: iptables v1.8.9 (legacy):
can't initialize iptables table `mangle': Table does not exist (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
Traceback (most recent call last):
File "/usr/local/share/virt-manager/virtManager/asyncjob.py", line 71, in cb_wrapper
callback(asyncjob, *args, **kwargs)
File "/usr/local/share/virt-manager/virtManager/asyncjob.py", line 107, in tmpcb
callback(*args, **kwargs)
File "/usr/local/share/virt-manager/virtManager/object/libvirtobject.py", line 57, in newfn
ret = fn(self, *args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/share/virt-manager/virtManager/object/network.py", line 69, in start
self._backend.create()
File "/usr/lib/python3/dist-packages/libvirt.py", line 3547, in create
raise libvirtError('virNetworkCreate() failed')
libvirt.libvirtError: internal error: Failed to apply firewall rules /usr/sbin/iptables -w --table mangle --list-rules: iptables v1.8.9 (legacy): can't initialize iptables table `mangle': Table does not exist (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.marietto@chromarietto:~$ sudo virsh net-info default
Name: default
UUID: 7c4408b7-5125-4c98-9d53-f1fe109371e3
Active: no
Persistent: yes
Autostart: yes
Bridge: virbr0
marietto@chromarietto:~$ sudo virsh net-start default
error: Failed to start network default
error: internal error: Failed to apply firewall rules /usr/sbin/iptables -w --table mangle --list-rules: iptables v1.8.9 (legacy): can't initialize iptables table `mangle': Table does not exist (do you need to insmod?). Perhaps iptables or your kernel needs to be upgraded.
Name: default
UUID: 7c4408b7-5125-4c98-9d53-f1fe109371e3
Active: no
Persistent: yes
Autostart: yes
Bridge: virbr0
marietto@chromarietto:~$ sudo virsh net-start default
error: Failed to start network default
error: internal error: Failed to apply firewall rules /usr/sbin/iptables -w --table mangle --list-rules: iptables v1.8.9 (legacy): can't initialize iptables table `mangle': Table does not exist (do you need to insmod?). Perhaps iptables or your kernel needs to be upgraded.
i had a bit of trouble with the default network, but the second one i created didn't run into that. maybe check your version of iptables?
Code:
apt list '*iptables*' -i
Listing... Done
iptables/stable,now 1.8.9-2 amd64 [installed,automatic]i'm not sure about that. i haven't done much work at all with iptables.
Code:
lsmod | grep ip
ipt_REJECT 16384 2
nf_reject_ipv4 16384 1 ipt_REJECT
nf_defrag_ipv6 24576 1 nf_conntrack
nf_defrag_ipv4 16384 1 nf_conntrack
ip_tables 36864 0
x_tables 61440 7 xt_conntrack,nft_compat,xt_tcpudp,xt_CHECKSUM,ipt_REJECT,ip_tables,xt_MASQUERADE
multipath 20480 0
md_mod 192512 6 raid1,raid10,raid0,linear,raid456,multipath
Code:
/sbin/modinfo ip_tables
filename: /lib/modules/6.1.0-10-amd64/kernel/net/ipv4/netfilter/ip_tables.ko
alias: ipt_icmp
description: IPv4 packet filter
author: Netfilter Core Team <[email protected]>
license: GPL
depends: x_tables
retpoline: Y
intree: Y
name: ip_tablesi mean if you're feeling bold (and i would have a solid backup just in case), you could try running that command manually to see if it makes a difference.
yeah, it looks like something is missing somewhere:
Code:
deb12xfce@deb12xfce ~ [4]> sudo /usr/sbin/iptables -w --table mangle --list-rules
[sudo] password for deb12xfce:
-P PREROUTING ACCEPT
-P INPUT ACCEPT
-P FORWARD ACCEPT
-P OUTPUT ACCEPT
-P POSTROUTING ACCEPT
-N LIBVIRT_PRT
-A POSTROUTING -j LIBVIRT_PRT
-A LIBVIRT_PRT -o virbr1 -p udp -m udp --dport 68 -j CHECKSUM --checksum-fillthose were listed in the installed packages. some info about them:
Code:
apt show libvirt-daemon-config-network libvirt-daemon-config-nwfilter
Package: libvirt-daemon-config-network
Version: 9.0.0-4
Priority: optional
Section: admin
Source: libvirt
Maintainer: Debian Libvirt Maintainers <[email protected]>
Installed-Size: 43.0 kB
Breaks: libvirt-daemon-system (<< 6.9.0-2~)
Replaces: libvirt-daemon-system (<< 6.9.0-2~)
Homepage: https://libvirt.org/
Download-Size: 16.7 kB
APT-Manual-Installed: no
APT-Sources: http://deb.debian.org/debian bookworm/main amd64 Packages
Description: Libvirt daemon configuration files (default network)
Libvirt is a C toolkit to interact with the virtualization capabilities
of recent versions of Linux (and other OSes). The library aims at providing
a long term stable C API for different virtualization mechanisms. It currently
supports QEMU, KVM, XEN, OpenVZ, LXC, and VirtualBox.
.
This package contains the configuration for the 'default' libvirt network.
Package: libvirt-daemon-config-nwfilter
Version: 9.0.0-4
Priority: optional
Section: admin
Source: libvirt
Maintainer: Debian Libvirt Maintainers <[email protected]>
Installed-Size: 68.6 kB
Breaks: libvirt-daemon-system (<< 6.9.0-2~)
Replaces: libvirt-daemon-system (<< 6.9.0-2~)
Homepage: https://libvirt.org/
Download-Size: 19.4 kB
APT-Manual-Installed: no
APT-Sources: http://deb.debian.org/debian bookworm/main amd64 Packages
Description: Libvirt daemon configuration files (default network filters)
Libvirt is a C toolkit to interact with the virtualization capabilities
of recent versions of Linux (and other OSes). The library aims at providing
a long term stable C API for different virtualization mechanisms. It currently
supports QEMU, KVM, XEN, OpenVZ, LXC, and VirtualBox.
.
This package contains the configuration for the default set of nwfilters.
A very frustrating set of problems. Valiant effort expended by z7vl7abxc and OP.
I see that the same problem has been asked here:
and here:
unix.stackexchange.com
Hopefully something useful will emerge.
My own speculation is that the problems may have their origin in the independent compilation of the packages. It's not always the case that a user-compiled package is the same as the distribution's released compiled package. The matter is complicated by the compilation flags the distro has used to compile the source which may not be the same options that a user's compilation has invoked. For the user to discover and use the same flags that the distro has used, this link provides some information which may or may not be helpful:
unix.stackexchange.com
I see that the same problem has been asked here:
and here:
Failed to acquire pid file : /var/local/run/libvirt/qemu/driver.pid
I'm running Debian bookworm on my ARM Chromebook,model "xe303c12" and I've recompiled kernel to enable KVM,so now my system sounds like this : $ lsb_release -a No LSB modules are availabl...
unix.stackexchange.com
Hopefully something useful will emerge.
My own speculation is that the problems may have their origin in the independent compilation of the packages. It's not always the case that a user-compiled package is the same as the distribution's released compiled package. The matter is complicated by the compilation flags the distro has used to compile the source which may not be the same options that a user's compilation has invoked. For the user to discover and use the same flags that the distro has used, this link provides some information which may or may not be helpful:
How to get the compiler flags that are used to build the binaries in a (.deb) package?
I know that apt-get source <package_name> gives you the source package. It contains a debian folder with a file called rules. If I understand it correctly, this file describes how the source
unix.stackexchange.com
marietto@chromarietto:~$ apt show libvirt-daemon-config-network libvirt-daemon-config-nwfilter
Package: libvirt-daemon-config-network
Version: 9.0.0-4
Priority: optional
Section: admin
Source: libvirt
Maintainer: Debian Libvirt Maintainers <[email protected]>
Installed-Size: 43.0 kB
Breaks: libvirt-daemon-system (<< 6.9.0-2~)
Replaces: libvirt-daemon-system (<< 6.9.0-2~)
Homepage: https://libvirt.org/
Download-Size: 16.7 kB
APT-Sources: http://deb.debian.org/debian bookworm/main armhf Packages
Description: Libvirt daemon configuration files (default network)
Libvirt is a C toolkit to interact with the virtualization capabilities
of recent versions of Linux (and other OSes). The library aims at providing
a long term stable C API for different virtualization mechanisms. It currently
supports QEMU, KVM, XEN, OpenVZ, LXC, and VirtualBox.
.
This package contains the configuration for the 'default' libvirt network.
Package: libvirt-daemon-config-nwfilter
Version: 9.0.0-4
Priority: optional
Section: admin
Source: libvirt
Maintainer: Debian Libvirt Maintainers <[email protected]>
Installed-Size: 68.6 kB
Breaks: libvirt-daemon-system (<< 6.9.0-2~)
Replaces: libvirt-daemon-system (<< 6.9.0-2~)
Homepage: https://libvirt.org/
Download-Size: 19.4 kB
APT-Sources: http://deb.debian.org/debian bookworm/main armhf Packages
Description: Libvirt daemon configuration files (default network filters)
Libvirt is a C toolkit to interact with the virtualization capabilities
of recent versions of Linux (and other OSes). The library aims at providing
a long term stable C API for different virtualization mechanisms. It currently
supports QEMU, KVM, XEN, OpenVZ, LXC, and VirtualBox.
.
This package contains the configuration for the default set of nwfilters.
