Page 1 of 2 12 LastLast
Results 1 to 10 of 11

Thread: After DUP, KVM, VM can't be started, failed to connect to monitor socket: Permission denied

  1. #1

    Default After DUP, KVM, VM can't be started, failed to connect to monitor socket: Permission denied

    Hello,
    last night I upgraded and, after problems with GNOME, I executed a distribution upgrade. Since then, I can not start VM. I have checked many web sites and some config files and the result is still the same.
    Thanks for the help!

    The error message after click on VM in Virtual Machine Manager and choosing Start VM:

    "Error of domain start" (- my translation): failed to connect to monitor socket: Permission denied

    Traceback (most recent call last):
    File "/usr/share/virt-manager/virtManager/asyncjob.py", line 89, in cb_wrapper
    callback(asyncjob, *args, **kwargs)
    File "/usr/share/virt-manager/virtManager/asyncjob.py", line 125, in tmpcb
    callback(*args, **kwargs)
    File "/usr/share/virt-manager/virtManager/libvirtobject.py", line 82, in newfn
    ret = fn(self, *args, **kwargs)
    File "/usr/share/virt-manager/virtManager/domain.py", line 1505, in startup
    self._backend.create()
    File "/usr/lib64/python2.7/site-packages/libvirt.py", line 1069, in create
    if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
    libvirtError: failed to connect to monitor socket: Permission denied

    opensuse:~ # virsh start win10
    error: Failed to start domain win10
    error: failed to connect to monitor socket: Permission denied

    opensuse:~ # ps aux | grep virt
    dnsmasq 1800 0.0 0.0 51196 2676 ? S 00:52 0:00 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/lib64/libvirt/libvirt_leaseshelper
    root 1801 0.0 0.0 51168 580 ? S 00:52 0:00 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/lib64/libvirt/libvirt_leaseshelper
    dnsmasq 1872 0.0 0.0 51196 2340 ? S 00:52 0:00 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/internal.conf --leasefile-ro --dhcp-script=/usr/lib64/libvirt/libvirt_leaseshelper
    root 1873 0.0 0.0 51196 588 ? S 00:52 0:00 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/internal.conf --leasefile-ro --dhcp-script=/usr/lib64/libvirt/libvirt_leaseshelper
    root 2207 0.0 0.0 171964 6948 ? Ssl 00:52 0:00 /usr/sbin/virtlogd
    martin 3364 0.1 0.5 1240280 97396 ? Ssl 00:53 1:01 python2 /usr/share/virt-manager/virt-manager
    root 6700 0.0 0.2 1674032 40084 ? Ssl 08:29 0:04 /usr/sbin/libvirtd --listen
    root 21366 0.0 0.0 7432 880 pts/1 S+ 10:02 0:00 grep --color=auto virt

    /etc/libvirt/qemu.conf:
    security_default_confined = 0
    user = "+0" (my attemtp without success)
    group = "+0" (my attemtp without success)
    namespaces = [] (i was try add # without success)

    /etc/libvirt/qemu.conf.rpmnew:
    security_default_confined = 0

    martin@opensuse:~> journalctl --since "now" -f
    Hint: You are currently not seeing messages from other users and the system.
    Users in the 'systemd-journal' group can see all messages. Pass -q to
    turn off this notice.
    -- Logs begin at Mon 2017-01-23 12:46:16 CET. --
    lis 24 10:26:46 opensuse gnome-software[2858]: no flatpak system helper is available, using user
    lis 24 10:26:46 opensuse gnome-software[2858]: running install with refine-flags=require-origin with failure-flags=use-events with timeout=60 on plugin=steam on apps user/*/*/*/remmina.desktop/* took 1ms
    lis 24 10:26:46 opensuse gnome-shell[2620]: Source ID 31623 was not found when attempting to remove it
    lis 24 10:26:46 opensuse gnome-software[2858]: no flatpak system helper is available, using user
    lis 24 10:26:46 opensuse gnome-software[2858]: running install with refine-flags=require-origin with failure-flags=use-events with timeout=60 on plugin=steam on apps user/*/*/*/remmina.desktop/* took 1ms
    lis 24 10:26:46 opensuse gnome-shell[2620]: Removing a network device that was not added
    lis 24 10:26:46 opensuse gnome-shell[2620]: Removing a network device that was not added
    lis 24 10:26:47 opensuse gnome-software[2858]: no flatpak system helper is available, using user
    lis 24 10:26:47 opensuse gnome-software[2858]: running install with refine-flags=require-origin with failure-flags=use-events with timeout=60 on plugin=steam on apps user/*/*/*/remmina.desktop/* took 1ms

  2. #2
    Join Date
    Aug 2008
    Location
    England
    Posts
    65

    Default Re: After DUP, KVM, VM can't be started, failed to connect to monitor socket: Permission denied

    I also get this error message. I am running Leap 42.3 with kernel-default 4.14.1-2.1 from Kernels.

    When I try to start a QEMU/KVM connection I just get the error message.
    libvirtd status gives:

    Code:
     # service libvirtd status
    * libvirtd.service - Virtualization daemon
       Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; vendor preset: disabled)
       Active: active (running) since Fri 2017-11-24 12:25:16 GMT; 10min ago
         Docs: man:libvirtd(8)
               http://libvirt.org
     Main PID: 1755 (libvirtd)
        Tasks: 16 (limit: 32768)
       CGroup: /system.slice/libvirtd.service
               `-1755 /usr/sbin/libvirtd --listen
    
    Nov 24 12:30:28 bardsey libvirtd[1755]: 2017-11-24 12:30:28.489+0000: 1819: error : virCgroupRemoveRecursively:3487 : Unable to remove /sys/fs/cgroup/cpu,cpuacct/machine.slice/machine-qemu\x2d2\x2dwin7.scope//emulator (16)
    Nov 24 12:30:28 bardsey libvirtd[1755]: 2017-11-24 12:30:28.489+0000: 1819: error : virCgroupRemoveRecursively:3487 : Unable to remove /sys/fs/cgroup/cpu,cpuacct/machine.slice/machine-qemu\x2d2\x2dwin7.scope/ (16)
    Nov 24 12:30:28 bardsey libvirtd[1755]: 2017-11-24 12:30:28.489+0000: 1819: error : virCgroupRemoveRecursively:3487 : Unable to remove /sys/fs/cgroup/cpuset/machine.slice/machine-qemu\x2d2\x2dwin7.scope//emulator (16)
    Nov 24 12:30:28 bardsey libvirtd[1755]: 2017-11-24 12:30:28.489+0000: 1819: error : virCgroupRemoveRecursively:3487 : Unable to remove /sys/fs/cgroup/cpuset/machine.slice/machine-qemu\x2d2\x2dwin7.scope/ (16)
    Nov 24 12:30:28 bardsey libvirtd[1755]: 2017-11-24 12:30:28.490+0000: 1819: error : virCgroupRemoveRecursively:3487 : Unable to remove /sys/fs/cgroup/memory/machine.slice/machine-qemu\x2d2\x2dwin7.scope/ (16)
    Nov 24 12:30:28 bardsey libvirtd[1755]: 2017-11-24 12:30:28.490+0000: 1819: error : virCgroupRemoveRecursively:3487 : Unable to remove /sys/fs/cgroup/devices/machine.slice/machine-qemu\x2d2\x2dwin7.scope/ (16)
    Nov 24 12:30:28 bardsey libvirtd[1755]: 2017-11-24 12:30:28.490+0000: 1819: error : virCgroupRemoveRecursively:3487 : Unable to remove /sys/fs/cgroup/freezer/machine.slice/machine-qemu\x2d2\x2dwin7.scope/ (16)
    Nov 24 12:30:28 bardsey libvirtd[1755]: 2017-11-24 12:30:28.490+0000: 1819: error : virCgroupRemoveRecursively:3487 : Unable to remove /sys/fs/cgroup/blkio/machine.slice/machine-qemu\x2d2\x2dwin7.scope/ (16)
    Nov 24 12:30:28 bardsey libvirtd[1755]: 2017-11-24 12:30:28.490+0000: 1819: error : virCgroupRemoveRecursively:3487 : Unable to remove /sys/fs/cgroup/net_cls,net_prio/machine.slice/machine-qemu\x2d2\x2dwin7.scope/ (16)
    Nov 24 12:30:28 bardsey libvirtd[1755]: 2017-11-24 12:30:28.490+0000: 1819: error : virCgroupRemoveRecursively:3487 : Unable to remove /sys/fs/cgroup/perf_event/machine.slice/machine-qemu\x2d2\x2dwin7.scope/ (16)
    When I first got this error I looked in /etc/libvirt and found that /etc/libvirt/qemu-lockd.conf was a broken link to a non-existent /etc/libvirt/libxl-lockd.conf so I loaded libvirt-daemon-driver-libxl package which fixed that.
    Still does not run virtual machines.

  3. #3

    Default Re: After DUP, KVM, VM can't be started, failed to connect to monitor socket: Permission denied

    And other log messages:
    martin@opensuse:~> sudo journalctl --system --since "now" -f
    -- Logs begin at Mon 2017-01-23 12:39:45 CET. --
    lis 24 14:13:06 opensuse systemd-udevd[8000]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
    lis 24 14:13:06 opensuse systemd-udevd[8000]: Could not generate persistent MAC address for vnet0: No such file or directory
    lis 24 14:13:06 opensuse acvpnagent[1633]: A new network interface has been detected.
    lis 24 14:13:06 opensuse acvpnagent[1633]: Function: logInterfaces File: ../../vpn/AgentUtilities/Routing/InterfaceRouteMonitorCommon.cpp Line: 477 IP Address Interface List: 172.24.146.154 10.254.184.103 FE80:0:0:0:E1C:42D8:FE8F:17F0 FE80:0:0:0:7DE6:A318:87EB:E500 FE80:0:0:0:FC54:FF:FE87:E35B FE80:0:0:0:FC54:FF:FE75:CE4D
    lis 24 14:13:06 opensuse acvpnagent[1633]: Function: netInterfaceNoticeCategoryHandler File: ../../vpn/Agent/MainThread.cpp Line: 7913 Network Interface change detected, refreshing physical MAC addresses
    lis 24 14:13:06 opensuse systemd-udevd[8003]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
    lis 24 14:13:06 opensuse kernel: virbr0: port 2(vnet0) entered blocking state
    lis 24 14:13:06 opensuse kernel: virbr0: port 2(vnet0) entered disabled state
    lis 24 14:13:06 opensuse kernel: device vnet0 entered promiscuous mode
    lis 24 14:13:06 opensuse kernel: virbr0: port 2(vnet0) entered blocking state
    lis 24 14:13:06 opensuse kernel: virbr0: port 2(vnet0) entered listening state
    lis 24 14:13:06 opensuse kernel: virbr1: port 2(vnet1) entered blocking state
    lis 24 14:13:06 opensuse kernel: virbr1: port 2(vnet1) entered disabled state
    lis 24 14:13:06 opensuse kernel: device vnet1 entered promiscuous mode
    lis 24 14:13:06 opensuse kernel: virbr1: port 2(vnet1) entered blocking state
    lis 24 14:13:06 opensuse kernel: virbr1: port 2(vnet1) entered listening state
    lis 24 14:13:06 opensuse NetworkManager[1524]: <info> [1511529186.6136] manager: (vnet0): new Tun device (/org/freedesktop/NetworkManager/Devices/15)
    lis 24 14:13:06 opensuse NetworkManager[1524]: <info> [1511529186.6185] device (vnet0): state change: unmanaged -> unavailable (reason 'connection-assumed', internal state 'external')
    lis 24 14:13:06 opensuse NetworkManager[1524]: <info> [1511529186.6217] manager: (vnet1): new Tun device (/org/freedesktop/NetworkManager/Devices/16)
    lis 24 14:13:06 opensuse libvirtd[1566]: 2017-11-24 13:13:06.622+0000: 1592: warning : virGetHostnameImpl:666 : getaddrinfo failed for 'opensuse': Name or service not known
    lis 24 14:13:06 opensuse NetworkManager[1524]: <info> [1511529186.6253] keyfile: add connection in-memory (07e7e423-e474-4db6-9b0c-6501712e1af5,"vnet0")
    lis 24 14:13:06 opensuse NetworkManager[1524]: <info> [1511529186.6297] device (vnet0): state change: unavailable -> disconnected (reason 'connection-assumed', internal state 'external')
    lis 24 14:13:06 opensuse NetworkManager[1524]: <info> [1511529186.6321] device (vnet0): Activation: starting connection 'vnet0' (07e7e423-e474-4db6-9b0c-6501712e1af5)
    lis 24 14:13:06 opensuse NetworkManager[1524]: <info> [1511529186.6330] device (vnet1): state change: unmanaged -> unavailable (reason 'connection-assumed', internal state 'external')
    lis 24 14:13:06 opensuse systemd[1]: Started Virtual Machine qemu-4-win10.
    lis 24 14:13:06 opensuse systemd-machined[2690]: New machine qemu-4-win10.
    lis 24 14:13:06 opensuse NetworkManager[1524]: <info> [1511529186.6449] device (vnet0): state change: disconnected -> prepare (reason 'none', internal state 'external')
    lis 24 14:13:06 opensuse NetworkManager[1524]: <info> [1511529186.6462] keyfile: add connection in-memory (eb18a3e9-1b7b-4698-b8ad-78492306fcc1,"vnet1")
    lis 24 14:13:06 opensuse NetworkManager[1524]: <info> [1511529186.6484] device (vnet1): state change: unavailable -> disconnected (reason 'connection-assumed', internal state 'external')
    lis 24 14:13:06 opensuse NetworkManager[1524]: <info> [1511529186.6501] device (vnet1): Activation: starting connection 'vnet1' (eb18a3e9-1b7b-4698-b8ad-78492306fcc1)
    lis 24 14:13:06 opensuse libvirtd[1566]: 2017-11-24 13:13:06.652+0000: 1592: error : qemuMonitorOpenUnix:377 : failed to connect to monitor socket: Permission denied
    lis 24 14:13:06 opensuse libvirtd[1566]: 2017-11-24 13:13:06.653+0000: 1592: error : virProcessKillPainfully:389 : Failed to terminate process 8010 with SIGTERM: Permission denied
    lis 24 14:13:06 opensuse kernel: virbr1: port 2(vnet1) entered disabled state
    lis 24 14:13:06 opensuse systemd[1]: Stopping Virtual Machine qemu-4-win10.
    lis 24 14:13:06 opensuse libvirtd[1566]: 2017-11-24 13:13:06.661+0000: 1592: error : virCgroupRemoveRecursively:3487 : Unable to remove /sys/fs/cgroup/cpu,cpuacct/machine.slice/machine-qemu\x2d4\x2dwin10.scope//emulator (16)
    lis 24 14:13:06 opensuse libvirtd[1566]: 2017-11-24 13:13:06.661+0000: 1592: error : virCgroupRemoveRecursively:3487 : Unable to remove /sys/fs/cgroup/cpu,cpuacct/machine.slice/machine-qemu\x2d4\x2dwin10.scope/ (16)
    lis 24 14:13:06 opensuse libvirtd[1566]: 2017-11-24 13:13:06.661+0000: 1592: error : virCgroupRemoveRecursively:3487 : Unable to remove /sys/fs/cgroup/cpu,cpuacct/machine.slice/machine-qemu\x2d4\x2dwin10.scope//emulator (16)
    lis 24 14:13:06 opensuse libvirtd[1566]: 2017-11-24 13:13:06.661+0000: 1592: error : virCgroupRemoveRecursively:3487 : Unable to remove /sys/fs/cgroup/cpu,cpuacct/machine.slice/machine-qemu\x2d4\x2dwin10.scope/ (16)
    lis 24 14:13:06 opensuse libvirtd[1566]: 2017-11-24 13:13:06.662+0000: 1592: error : virCgroupRemoveRecursively:3487 : Unable to remove /sys/fs/cgroup/cpuset/machine.slice/machine-qemu\x2d4\x2dwin10.scope//emulator (16)
    lis 24 14:13:06 opensuse libvirtd[1566]: 2017-11-24 13:13:06.662+0000: 1592: error : virCgroupRemoveRecursively:3487 : Unable to remove /sys/fs/cgroup/cpuset/machine.slice/machine-qemu\x2d4\x2dwin10.scope/ (16)
    lis 24 14:13:06 opensuse libvirtd[1566]: 2017-11-24 13:13:06.662+0000: 1592: error : virCgroupRemoveRecursively:3487 : Unable to remove /sys/fs/cgroup/memory/machine.slice/machine-qemu\x2d4\x2dwin10.scope/ (16)
    lis 24 14:13:06 opensuse libvirtd[1566]: 2017-11-24 13:13:06.662+0000: 1592: error : virCgroupRemoveRecursively:3487 : Unable to remove /sys/fs/cgroup/devices/machine.slice/machine-qemu\x2d4\x2dwin10.scope/ (16)
    lis 24 14:13:06 opensuse libvirtd[1566]: 2017-11-24 13:13:06.662+0000: 1592: error : virCgroupRemoveRecursively:3487 : Unable to remove /sys/fs/cgroup/freezer/machine.slice/machine-qemu\x2d4\x2dwin10.scope/ (16)
    lis 24 14:13:06 opensuse libvirtd[1566]: 2017-11-24 13:13:06.662+0000: 1592: error : virCgroupRemoveRecursively:3487 : Unable to remove /sys/fs/cgroup/blkio/machine.slice/machine-qemu\x2d4\x2dwin10.scope/ (16)
    lis 24 14:13:06 opensuse libvirtd[1566]: 2017-11-24 13:13:06.662+0000: 1592: error : virCgroupRemoveRecursively:3487 : Unable to remove /sys/fs/cgroup/net_cls,net_prio/machine.slice/machine-qemu\x2d4\x2dwin10.scope/ (16)
    lis 24 14:13:06 opensuse libvirtd[1566]: 2017-11-24 13:13:06.662+0000: 1592: error : virCgroupRemoveRecursively:3487 : Unable to remove /sys/fs/cgroup/perf_event/machine.slice/machine-qemu\x2d4\x2dwin10.scope/ (16)
    lis 24 14:13:06 opensuse kernel: device vnet1 left promiscuous mode
    lis 24 14:13:06 opensuse kernel: virbr1: port 2(vnet1) entered disabled state
    lis 24 14:13:06 opensuse acvpnagent[1633]: A network interface has gone down.
    lis 24 14:13:06 opensuse acvpnagent[1633]: Function: logInterfaces File: ../../vpn/AgentUtilities/Routing/InterfaceRouteMonitorCommon.cpp Line: 477 IP Address Interface List: 172.24.146.154 10.254.184.103 FE80:0:0:0:E1C:42D8:FE8F:17F0 FE80:0:0:0:7DE6:A318:87EB:E500 FE80:0:0:0:FC54:FF:FE87:E35B
    lis 24 14:13:06 opensuse acvpnagent[1633]: Function: netInterfaceNoticeCategoryHandler File: ../../vpn/Agent/MainThread.cpp Line: 7913 Network Interface change detected, refreshing physical MAC addresses
    lis 24 14:13:06 opensuse NetworkManager[1524]: <info> [1511529186.7013] device (vnet0): state change: prepare -> config (reason 'none', internal state 'external')
    lis 24 14:13:06 opensuse NetworkManager[1524]: <info> [1511529186.7017] device (vnet1): state change: disconnected -> prepare (reason 'none', internal state 'external')
    lis 24 14:13:06 opensuse NetworkManager[1524]: <info> [1511529186.7028] device (vnet1): state change: prepare -> unmanaged (reason 'unmanaged', internal state 'removed')
    lis 24 14:13:06 opensuse NetworkManager[1524]: <info> [1511529186.7028] device (vnet1): released from master device virbr1
    lis 24 14:13:06 opensuse NetworkManager[1524]: <info> [1511529186.7041] device (vnet0): state change: config -> ip-config (reason 'none', internal state 'external')
    lis 24 14:13:06 opensuse NetworkManager[1524]: <info> [1511529186.7042] device (virbr0): bridge port vnet0 was attached
    lis 24 14:13:06 opensuse NetworkManager[1524]: <info> [1511529186.7042] device (vnet0): Activation: connection 'vnet0' enslaved, continuing activation
    lis 24 14:13:06 opensuse NetworkManager[1524]: <info> [1511529186.7089] device (vnet0): state change: ip-config -> secondaries (reason 'none', internal state 'external')
    lis 24 14:13:06 opensuse NetworkManager[1524]: <info> [1511529186.7100] device (vnet0): state change: secondaries -> activated (reason 'none', internal state 'external')
    lis 24 14:13:06 opensuse NetworkManager[1524]: <info> [1511529186.7117] device (vnet0): Activation: successful, device activated.
    lis 24 14:13:06 opensuse kernel: virbr0: port 2(vnet0) entered disabled state
    lis 24 14:13:06 opensuse kernel: device vnet0 left promiscuous mode
    lis 24 14:13:06 opensuse kernel: virbr0: port 2(vnet0) entered disabled state
    lis 24 14:13:06 opensuse dbus[1500]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
    lis 24 14:13:06 opensuse systemd[1]: Starting Network Manager Script Dispatcher Service...
    lis 24 14:13:06 opensuse dbus[1500]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
    lis 24 14:13:06 opensuse systemd[1]: Started Network Manager Script Dispatcher Service.
    lis 24 14:13:06 opensuse nm-dispatcher[8020]: req:1 'up' [vnet0]: new request (4 scripts)
    lis 24 14:13:06 opensuse nm-dispatcher[8020]: req:1 'up' [vnet0]: start running ordered scripts...
    lis 24 14:13:06 opensuse acvpnagent[1633]: A network interface has gone down.
    lis 24 14:13:06 opensuse acvpnagent[1633]: Function: logInterfaces File: ../../vpn/AgentUtilities/Routing/InterfaceRouteMonitorCommon.cpp Line: 477 IP Address Interface List: 172.24.146.154 10.254.184.103 FE80:0:0:0:E1C:42D8:FE8F:17F0 FE80:0:0:0:7DE6:A318:87EB:E500
    lis 24 14:13:06 opensuse acvpnagent[1633]: Function: netInterfaceNoticeCategoryHandler File: ../../vpn/Agent/MainThread.cpp Line: 7913 Network Interface change detected, refreshing physical MAC addresses
    lis 24 14:13:06 opensuse NetworkManager[1524]: <info> [1511529186.7465] device (vnet0): state change: activated -> unmanaged (reason 'unmanaged', internal state 'removed')
    lis 24 14:13:06 opensuse NetworkManager[1524]: <info> [1511529186.7469] device (virbr0): bridge port vnet0 was detached
    lis 24 14:13:06 opensuse NetworkManager[1524]: <info> [1511529186.7472] device (vnet0): released from master device virbr0
    lis 24 14:13:06 opensuse nm-dispatcher[8020]: req:2 'down' [vnet0]: new request (4 scripts)
    lis 24 14:13:06 opensuse systemd[1]: Stopped Virtual Machine qemu-4-win10.
    lis 24 14:13:06 opensuse systemd-machined[2690]: Machine qemu-4-win10 terminated.
    lis 24 14:13:06 opensuse nmcli[8030]: gdbusobjectmanagerclient.c:1585: Processing InterfaceRemoved signal for path /org/freedesktop/NetworkManager/Devices/15 but no object proxy exists
    lis 24 14:13:06 opensuse nmcli[8030]: no object known for /org/freedesktop/NetworkManager/Settings/62
    lis 24 14:13:06 opensuse nmcli[8030]: no object known for /org/freedesktop/NetworkManager/ActiveConnection/13
    lis 24 14:13:06 opensuse netconfig[8063]: Executing 'modify -s NetworkManager -m ntp' for pid 8056
    lis 24 14:13:06 opensuse nm-dispatcher[8020]: <13>Nov 24 14:13:06 netconfig: Executing 'modify -s NetworkManager -m ntp' for pid 8056
    lis 24 14:13:06 opensuse nm-dispatcher[8020]: debug: lockfile created (/var/run/netconfig.pid) for PID 8062
    lis 24 14:13:06 opensuse nm-dispatcher[8020]: debug: lockfile created
    lis 24 14:13:06 opensuse nm-dispatcher[8020]: debug: write new STATE file /var/run/netconfig//NetworkManager.netconfig
    lis 24 14:13:06 opensuse nm-dispatcher[8020]: debug: Module order: dns-resolver dns-bind dns-dnsmasq nis ntp-runtime
    lis 24 14:13:06 opensuse nm-dispatcher[8020]: debug: dns-resolver module skipped
    lis 24 14:13:06 opensuse nm-dispatcher[8020]: debug: dns-bind module skipped
    lis 24 14:13:06 opensuse nm-dispatcher[8020]: debug: dns-dnsmasq module skipped
    lis 24 14:13:06 opensuse nm-dispatcher[8020]: debug: nis module skipped
    lis 24 14:13:06 opensuse nm-dispatcher[8020]: debug: ntp-runtime Module called
    lis 24 14:13:06 opensuse nm-dispatcher[8020]: debug: Resolved ntp-policy 'auto' for service 'NetworkManager' to 'STATIC_FALLBACK NetworkManager'
    lis 24 14:13:06 opensuse nm-dispatcher[8020]: debug: Static Fallback
    lis 24 14:13:06 opensuse nm-dispatcher[8020]: debug: Use NetworkManager policy merged settings
    lis 24 14:13:06 opensuse nm-dispatcher[8020]: debug: exec get_ntp_settings: /var/run/netconfig/NetworkManager.netconfig
    lis 24 14:13:06 opensuse nm-dispatcher[8020]: debug: get_ntp_settings: NTP_SERVER_LIST=''
    lis 24 14:13:06 opensuse nm-dispatcher[8020]: debug: exit get_ntp_settings: /var/run/netconfig/NetworkManager.netconfig
    lis 24 14:13:06 opensuse nm-dispatcher[8020]: req:2 'down' [vnet0]: start running ordered scripts...
    lis 24 14:13:07 opensuse nm-dispatcher[8020]: /etc/NetworkManager/dispatcher.d/nfs: line 40: reaches: bad array subscript
    lis 24 14:13:07 opensuse nm-dispatcher[8020]: /etc/NetworkManager/dispatcher.d/nfs: line 42: reaches: bad array subscript
    lis 24 14:13:07 opensuse nm-dispatcher[8020]: ping: : Name or service not known
    lis 24 14:13:07 opensuse nm-dispatcher[8020]: ping: : Name or service not known
    lis 24 14:13:07 opensuse nm-dispatcher[8020]: ping: : Name or service not known
    lis 24 14:13:07 opensuse nm-dispatcher[8020]: ping: : Name or service not known
    lis 24 14:13:07 opensuse nm-dispatcher[8020]: ping: : Name or service not known
    lis 24 14:13:07 opensuse nm-dispatcher[8020]: /etc/NetworkManager/dispatcher.d/nfs: line 49: reaches[$1]: bad array subscript

  4. #4
    Join Date
    Aug 2008
    Location
    England
    Posts
    65

    Default Re: After DUP, KVM, VM can't be started, failed to connect to monitor socket: Permission denied

    Before anyone else mentions it, it is preferable to wrap # code tags around machine output. I was pulled up on the very same matter a couple of months ago!

    Just a word to the wise.

  5. #5
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    32,316
    Blog Entries
    15

    Default Re: After DUP, KVM, VM can't be started, failed to connect to monitor socket: Permission denied

    Hi
    Wasn't there an issue a while back with AppArmor service (namespace) if you disable the apparmor systemd service and try starting libvirtd again, how does this go?

    Ahh, it needs updating by the looks, see: https://lists.opensuse.org/opensuse-.../msg00618.html
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  6. #6
    Join Date
    Aug 2008
    Location
    England
    Posts
    65

    Default Re: After DUP, KVM, VM can't be started, failed to connect to monitor socket: Permission denied

    Thanks Malcolm, right again...

    As super user I executed:
    Code:
    # systemctl stop apparmor
    # service libvirtd restart
    and the virtual connection started just fine.

    Changing a profile looks to be a simple matter. The difficulty lies in knowing which profile and which rule have to be changed.

    Peter

  7. #7

    Default Re: After DUP, KVM, VM can't be started, failed to connect to monitor socket: Permission denied

    Quote Originally Posted by pblewis View Post
    Before anyone else mentions it, it is preferable to wrap # code tags around machine output. I was pulled up on the very same matter a couple of months ago!

    Just a word to the wise.
    Ok, next time I'll use the # tags. Thanks

  8. #8

    Thumbs up Re: After DUP, KVM, VM can't be started, failed to connect to monitor socket: Permission denied

    It works. Thanks a lot!

    I'm going to read the AppArmor documentation to fix it definitively. Meanwhile, I will finish the job that depends on M$ Windows.

    Martin

  9. #9

    Default Re: After DUP, KVM, VM can't be started, failed to connect to monitor socket: Permission denied

    Yeah This happens because

    Users must opt-in to confine qemu instances if Apparmor is enabled on the host

    Editing
    /etc/libvirt/qemu.conf and adding the following after around line 356

    security_default_confined = 1

    You might also need to add

    security_driver = "apparmor"

    around line 342

    Save, exit and restart using
    service libvirtd restart

    KVM guests should now start without issue and without tinkering with Apparmor profiles and security settings.

    Don't know why this hasn't been addressed by anybody yet.



  10. #10
    Join Date
    Aug 2008
    Location
    England
    Posts
    65

    Default Re: After DUP, KVM, VM can't be started, failed to connect to monitor socket: Permission denied

    Thanks, that works for me!

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •