Virt Manager: libvirtd connection closed due to keepalive timeout

Hi,
i have a problem with virt manager losing the connection to my vm guest os after login into the guest. It happened occasionally in the past, but now it seems to be permanent.
I followed all guides i found so far:
added my user to libvirt-qemu and kvm in addition to libvirt,
uncomment the two lines in /etc/libvirt/libvirtd.conf

keepalive_interval = 5
keepalive_count = 5

Here the output of systemclt libvirtd and inxi:

systemctl status libvirtd
● libvirtd.service - libvirt legacy monolithic daemon
     Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; preset: disabled)
     Active: active (running) since Sat 2024-10-12 19:39:01 CEST; 1h 1min ago
 Invocation: 845930430d944396bdb818196e0ab1b3
TriggeredBy: ● libvirtd-ro.socket
             ● libvirtd.socket
             ● libvirtd-admin.socket
       Docs: man:libvirtd(8)
             https://libvirt.org/
   Main PID: 2280 (libvirtd)
      Tasks: 25 (limit: 32768)
     Memory: 17M (peak: 45.7M swap: 17M swap peak: 17.1M zswap: 2.5M)
        CPU: 1.782s
     CGroup: /system.slice/libvirtd.service
             ├─ 750 /usr/bin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
             ├─ 751 /usr/bin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
             └─2280 /usr/bin/libvirtd --timeout 120

Okt 12 19:42:51 alexander-ms7589 libvirtd[2280]: hostname: alexander-ms7589
Okt 12 19:42:51 alexander-ms7589 libvirtd[2280]: Interner Fehler: connection closed due to keepalive timeout
Okt 12 19:51:34 alexander-ms7589 dnsmasq-dhcp[750]: DHCPDISCOVER(virbr0) 192.168.122.165 52:54:00:75:16:66
Okt 12 19:51:34 alexander-ms7589 dnsmasq-dhcp[750]: DHCPOFFER(virbr0) 192.168.122.165 52:54:00:75:16:66
Okt 12 19:51:34 alexander-ms7589 dnsmasq-dhcp[750]: DHCPREQUEST(virbr0) 192.168.122.165 52:54:00:75:16:66
Okt 12 19:51:34 alexander-ms7589 dnsmasq-dhcp[750]: DHCPACK(virbr0) 192.168.122.165 52:54:00:75:16:66 mx
Okt 12 19:54:01 alexander-ms7589 libvirtd[2280]: Interner Fehler: connection closed due to keepalive timeout
Okt 12 19:54:44 alexander-ms7589 libvirtd[2280]: Interner Fehler: connection closed due to keepalive timeout
Okt 12 20:21:34 alexander-ms7589 dnsmasq-dhcp[750]: DHCPREQUEST(virbr0) 192.168.122.165 52:54:00:75:16:66
Okt 12 20:21:34 alexander-ms7589 dnsmasq-dhcp[750]: DHCPACK(virbr0) 192.168.122.165 52:54:00:75:16:66 mx
inxi
System:
  Kernel: 6.10.13-3-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.10-x86_64
    root=UUID=9dc4ed12-cf8e-41b5-a31c-9de5f50e8dc6 rw
    resume=UUID=9dc4ed12-cf8e-41b5-a31c-9de5f50e8dc6 resume_offset=30074880
    apparmor=1 security=apparmor udev.log_priority=3 sysrq_always_enabled=1
    nvidia_drm.modeset=1 nvidia_drm.fbdev=1
    NVreg_PreserveVideoMemoryAllocations=1 NVreg_TemporaryFilePath=/var/tmp
    modprobe.blacklist=nouveau systemd.setenv=GPUMOD=nvidia nowatchdog
    intel_iommu=on iommu=pt
  Desktop: KDE Plasma v: 6.2.0 tk: Qt v: N/A info: frameworks v: 6.6.0
    wm: kwin_x11 vt: 2 dm: SDDM Distro: Manjaro base: Arch Linux
Machine:
  Type: Desktop Mobo: MSI model: P55-GD55 (MS-7589) v: 1.0
    serial: <superuser required> uuid: <superuser required>
    BIOS: American Megatrends v: 1.9 date: 03/02/2011
Battery:
  Message: No system battery data found. Is one present?
Memory:
  System RAM: total: 8 GiB available: 7.75 GiB used: 5.34 GiB (68.9%)
  Message: For most reliable report, use superuser + dmidecode.
  Array-1: capacity: 8 GiB slots: 4 modules: 4 EC: None
    max-module-size: 2 GiB note: est.
  Device-1: DIMM1 type: SDRAM detail: synchronous size: 2 GiB
    speed: 1333 MT/s volts: N/A width (bits): data: 64 total: 64
    manufacturer: N/A part-no: N/A serial: N/A
  Device-2: DIMM2 type: SDRAM detail: synchronous size: 2 GiB
    speed: 1333 MT/s volts: N/A width (bits): data: 64 total: 64
    manufacturer: N/A part-no: N/A serial: N/A
  Device-3: DIMM3 type: SDRAM detail: synchronous size: 2 GiB
    speed: 1333 MT/s volts: N/A width (bits): data: 64 total: 64
    manufacturer: N/A part-no: N/A serial: N/A
  Device-4: DIMM4 type: SDRAM detail: synchronous size: 2 GiB
    speed: 1333 MT/s volts: N/A width (bits): data: 64 total: 64
    manufacturer: N/A part-no: N/A serial: N/A
CPU:
  Info: model: Intel Core i7 860 bits: 64 type: MT MCP arch: Nehalem
    gen: core 1 level: v2 built: 2008-10 process: Intel 45nm family: 6
    model-id: 0x1E (30) stepping: 5 microcode: 0xA
  Topology: cpus: 1x dies: 1 clusters: 4 cores: 4 threads: 8 tpc: 2
    smt: enabled cache: L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB
    desc: 4x256 KiB L3: 8 MiB desc: 1x8 MiB
  Speed (MHz): avg: 1200 min/max: 1200/2801 boost: enabled scaling:
    driver: acpi-cpufreq governor: schedutil cores: 1: 1200 2: 1200 3: 1200
    4: 1200 5: 1200 6: 1200 7: 1200 8: 1200 bogomips: 44923
  Flags: acpi aperfmperf apic arch_perfmon bts clflush cmov constant_tsc
    cpuid cx16 cx8 de ds_cpl dtes64 dtherm dts ept est flexpriority flush_l1d
    fpu fxsr ht ibpb ibrs ida lahf_lm lm mca mce mmx monitor msr mtrr
    nonstop_tsc nopl nx pae pat pbe pdcm pebs pge pni popcnt pse pse36 pti
    rdtscp rep_good sep smx ssbd sse sse2 sse4_1 sse4_2 ssse3 stibp syscall tm
    tm2 tpr_shadow tsc vme vmx vnmi vpid xtopology xtpr
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: KVM: Split huge pages
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT
    vulnerable
  Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode;
    SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data status: Unknown: No mitigations
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: Retpolines; IBPB: conditional; IBRS_FW;
    STIBP: conditional; RSB filling; PBRSB-eIBRS: Not affected; BHI: Not
    affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: NVIDIA GM204 [GeForce GTX 970] vendor: Micro-Star MSI
    driver: nvidia v: 550.120 alternate: nouveau,nvidia_drm non-free: 550.xx+
    status: current (as of 2024-09; EOL~2026-12-xx) arch: Maxwell code: GMxxx
    process: TSMC 28nm built: 2014-2019 pcie: gen: 2 speed: 5 GT/s lanes: 16
    ports: active: none off: DVI-I-1 empty: DP-1,DVI-D-1,HDMI-A-1
    bus-ID: 01:00.0 chip-ID: 10de:13c2 class-ID: 0300
  Display: x11 server: X.Org v: 21.1.13 with: Xwayland v: 24.1.2
    compositor: kwin_x11 driver: X: loaded: nvidia gpu: nvidia,nvidia-nvswitch
    display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 95 s-size: 513x292mm (20.20x11.50")
    s-diag: 590mm (23.24")
  Monitor-1: DVI-I-1 note: disabled model: Samsung SyncMaster
    serial: <filter> built: 2010 res: 1920x1080 hz: 60 dpi: 96 gamma: 1.2
    size: 510x287mm (20.08x11.3") diag: 585mm (23") ratio: 16:9 modes:
    max: 1920x1080 min: 640x480
  API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2
    drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia x11: drv: nvidia
    inactive: wayland,device-1
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 550.120
    glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce GTX 970/PCIe/SSE2
    memory: 3.91 GiB
  API: Vulkan v: 1.3.295 layers: 6 device: 0 type: discrete-gpu
    name: NVIDIA GeForce GTX 970 driver: nvidia v: 550.120 device-ID: 10de:13c2
    surfaces: xcb,xlib
Audio:
  Device-1: Intel 5 Series/3400 Series High Definition Audio
    vendor: Micro-Star MSI driver: snd_hda_intel v: kernel bus-ID: 00:1b.0
    chip-ID: 8086:3b56 class-ID: 0403
  Device-2: NVIDIA GM204 High Definition Audio vendor: Micro-Star MSI
    driver: snd_hda_intel v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 16
    bus-ID: 01:00.1 chip-ID: 10de:0fbb class-ID: 0403
  API: ALSA v: k6.10.13-3-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: PipeWire v: 1.2.5 status: active with: 1: pipewire-pulse
    status: active 2: pipewire-media-session status: active 3: pipewire-alsa
    type: plugin 4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli
Network:
  Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    vendor: Micro-Star MSI driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
    lanes: 1 port: d800 bus-ID: 03:00.0 chip-ID: 10ec:8168 class-ID: 0200
  IF: enp3s0 state: up speed: 100 Mbps duplex: full mac: <filter>
  IP v4: <filter> type: dynamic noprefixroute scope: global
    broadcast: <filter>
  IF-ID-1: virbr0 state: up speed: 10000 Mbps duplex: unknown mac: <filter>
  IP v4: <filter> type: noprefixroute scope: global broadcast: <filter>
  IF-ID-2: vnet1 state: unknown speed: 10000 Mbps duplex: full mac: <filter>
  IP v6: <filter> virtual: proto kernel_ll scope: link
  Info: services: NetworkManager,systemd-timesyncd
  WAN IP: <filter>
Bluetooth:
  Message: No bluetooth data found.
Logical:
  Message: No logical block device data found.
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 3.18 TiB used: 220.67 GiB (6.8%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Samsung model: HD103SJ size: 931.51 GiB
    block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s tech: HDD
    rpm: 7200 serial: <filter> fw-rev: 00E4 scheme: MBR
  ID-2: /dev/sdb maj-min: 8:16 vendor: Samsung model: SSD 870 EVO 500GB
    size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 2B6Q scheme: MBR
  ID-3: /dev/sdc maj-min: 8:32 vendor: Hitachi model: HDS5C3020ALA632
    size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s
    tech: HDD rpm: 5940 serial: <filter> fw-rev: A580 scheme: MBR
  Message: No optical or floppy data found.
Partition:
  ID-1: / raw-size: 371.09 GiB size: 364.2 GiB (98.14%) used: 65.98 GiB (18.1%)
    fs: ext4 dev: /dev/sdb1 maj-min: 8:17 label: SSDRoot
    uuid: 9dc4ed12-cf8e-41b5-a31c-9de5f50e8dc6
  ID-2: /home raw-size: 489.27 GiB size: 480.51 GiB (98.21%)
    used: 154.69 GiB (32.2%) fs: ext4 dev: /dev/sda6 maj-min: 8:6 label: home
    uuid: c5fcc6d4-1db5-4ec5-8ede-0f76cd6ee4ab
Swap:
  Kernel: swappiness: 50 (default 60) cache-pressure: 100 (default) zswap: yes
    compressor: zstd max-pool: 20%
  ID-1: swap-1 type: file size: 11 GiB used: 2.98 GiB (27.1%) priority: -2
    file: /swapfile
Unmounted:
  ID-1: /dev/sda1 maj-min: 8:1 size: 100 MiB fs: ntfs label: System-reserviert
    uuid: 583E97273E96FD66
  ID-2: /dev/sda2 maj-min: 8:2 size: 199.39 GiB fs: ntfs label: System
    uuid: 0A12C25D12C24CFF
  ID-3: /dev/sda3 maj-min: 8:3 size: 527 MiB fs: ntfs label: N/A
    uuid: 34862028861FE95E
  ID-4: /dev/sda4 maj-min: 8:4 size: 1 KiB fs: <superuser required>
    label: N/A uuid: N/A
  ID-5: /dev/sda5 maj-min: 8:5 size: 242.25 GiB fs: ntfs label: Daten
    uuid: 7024BEAB24BE73A6
  ID-6: /dev/sdb2 maj-min: 8:18 size: 94.66 GiB fs: ext4 label: SSDDaten
    uuid: b9358f37-9f4f-4c92-a7e7-034e046fa0f8
  ID-7: /dev/sdc1 maj-min: 8:33 size: 1.15 TiB fs: ntfs label: Daten3
    uuid: 86E470A6E47099DF
  ID-8: /dev/sdc2 maj-min: 8:34 size: 100.18 GiB fs: ext4 label: Backup
    uuid: ff56fbe9-6e09-4569-8fa8-8b97d1c923f1
  ID-9: /dev/sdc3 maj-min: 8:35 size: 439.45 GiB fs: ext4
    label: manjaro-gnome uuid: ba16c9d4-46e2-475f-acfb-453275b5b42a
  ID-10: /dev/sdc4 maj-min: 8:36 size: 146.48 GiB fs: ext4 label: Testsys
    uuid: afafb774-fda7-444d-b5f3-8ded4befe91c
USB:
  Hub-1: 1-0:1 info: full speed or root hub ports: 2 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-2: 1-1:2 info: Intel Integrated Rate Matching Hub ports: 6 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 8087:0020
    class-ID: 0900
  Device-1: 1-1.5:3 info: Cooler Master Masterkeys Lite L Combo RGB Keyboard
    type: keyboard,mouse driver: hid-generic,usbhid interfaces: 2 rev: 1.1
    speed: 1.5 Mb/s (183 KiB/s) lanes: 1 mode: 1.0 power: 100mA
    chip-ID: 2516:0042 class-ID: 0301
  Device-2: 1-1.6:4 info: USB OPTICAL MOUSE type: mouse
    driver: hid-generic,usbhid interfaces: 1 rev: 1.1 speed: 1.5 Mb/s (183 KiB/s)
    lanes: 1 mode: 1.0 power: 100mA chip-ID: 30fa:0400 class-ID: 0301
  Hub-3: 2-0:1 info: full speed or root hub ports: 2 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-4: 2-1:2 info: Intel Integrated Rate Matching Hub ports: 8 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 8087:0020
    class-ID: 0900
  Device-1: 2-1.3:3 info: Genesys Logic USB 2.0 Card Reader
    type: mass storage driver: usb-storage interfaces: 1 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 500mA
    chip-ID: 05e3:070e class-ID: 0806 serial: <filter>
Sensors:
  System Temperatures: cpu: 42.0 C mobo: 34.0 C gpu: nvidia temp: 45 C
  Fan Speeds (rpm): cpu: 1083 fan-1: 792 fan-3: 859 gpu: nvidia fan: 0%
  Power: 12v: N/A 5v: N/A 3.3v: 3.33 vbat: 3.26
Info:
  Processes: 296 Power: uptime: 56m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 3.08 GiB services: org_kde_powerdevil,upowerd
    Init: systemd v: 256 default: graphical tool: systemctl
  Packages: 1908 pm: pacman pkgs: 1900 libs: 516 tools: pamac,yay pm: flatpak
    pkgs: 8 Compilers: clang: 18.1.8 gcc: 14.2.1 Shell: Zsh v: 5.9 default: Bash
    v: 5.2.37 running-in: yakuake inxi: 3.3.36

apart from that, the network widget looks weird:
Screenshot_networkwidget_20241012
but the network in system settings looks normal to me

any clues? I’m a litte desperate…

Check the explanation in that file right above these options.
The connection will still be closed … it is not kept alive, it is just a check whether it still is.

Perhaps your bridge address conflicts with your LAN interface address?

Or try a NAT connection type instead of the bridge?

I tried with NAT and the result is the same.
I think the problem lies more in the area of qemu://system sockets and spice, because after the window with the viewer closes, i have to reconnect virt-manager to qemu:///system.
I have also tried changing the video from virtio to qxl to eliminate virtio from the equation.

My output from
systemctl status libvirtd
looks different than yours - that’s all I can say

what does:
systemctl status dnsmasq.service
give you?

It should not be active, not specially configured and not enabled.

this is what I get - with everything working:

systemctl status dnsmasq.service 
○ dnsmasq.service - dnsmasq - A lightweight DHCP and caching DNS server
     Loaded: loaded (/lib/systemd/system/dnsmasq.service; disabled; vendor preset: enabled)
     Active: inactive (dead)

cave:
this system is not Arch/Manjaro, this is a Mint host
running Manjaro, Arch and a Debian Linux variant.

ip a
ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: enp3s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether 54:53:ed:b3:0e:45 brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 84:a6:c8:e1:0d:fc brd ff:ff:ff:ff:ff:ff
    inet 192.168.178.24/24 brd 192.168.178.255 scope global dynamic noprefixroute wlan0
       valid_lft 831126sec preferred_lft 831126sec
4: virbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 52:54:00:63:9f:62 brd ff:ff:ff:ff:ff:ff
    inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
       valid_lft forever preferred_lft forever
    inet6 fe80::5054:ff:fe63:9f62/64 scope link 
       valid_lft forever preferred_lft forever
9: vnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master virbr0 state UNKNOWN group default qlen 1000
    link/ether fe:54:00:ed:bd:3c brd ff:ff:ff:ff:ff:ff
    inet6 fe80::fc54:ff:feed:bd3c/64 scope link 
       valid_lft forever preferred_lft forever
I like the format of ifconfig better
ifconfig 
enp3s0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 54:53:ed:b3:0e:45  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Lokale Schleife)
        RX packets 23631  bytes 2568643 (2.5 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 23631  bytes 2568643 (2.5 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

virbr0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.122.1  netmask 255.255.255.0  broadcast 192.168.122.255
        inet6 fe80::5054:ff:fe63:9f62  prefixlen 64  scopeid 0x20<link>
        ether 52:54:00:63:9f:62  txqueuelen 1000  (Ethernet)
        RX packets 86  bytes 6348 (6.3 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 86  bytes 10736 (10.7 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

vnet0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::fc54:ff:feed:bd3c  prefixlen 64  scopeid 0x20<link>
        ether fe:54:00:ed:bd:3c  txqueuelen 1000  (Ethernet)
        RX packets 86  bytes 7552 (7.5 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 549  bytes 37830 (37.8 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.178.24  netmask 255.255.255.0  broadcast 192.168.178.255
        ether 84:a6:c8:e1:0d:fc  txqueuelen 1000  (Ethernet)
        RX packets 10007258  bytes 10950573094 (10.9 GB)
        RX errors 0  dropped 98062  overruns 0  frame 0
        TX packets 2137983  bytes 402043014 (402.0 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

hmm, from within the guest (if not doing something complex with routing) you should not see the vibr0 interface. At least that is what I guess from the screenshot and in my guests I do not see this interface, it is visible on the hosts tho since it is the virtual bridge to the ‘real’ network. This might be the reason there are connection issues.

No .pacnew files somewhere that need integrating/merging?

if posting terminal output (as the inxi output) use

```
text here
```
so it wraps at the intended place now it is a wall of characters.

Are you trying to access the host network from within the guest?

Are you trying to isolate the guest from the host network?

I have to ask - because this feels like an xy problem

  • what are you trying to do?
  • what is the purpose?
  • what is the end goal?
  • what are you trying to accomplish?
1 Like

Mine output for dnsmasq and ifconfig looks the same

systemctl status dnsmasq.service                                                                                                                                                                
○ dnsmasq.service - dnsmasq - A lightweight DHCP and caching DNS server
     Loaded: loaded (/usr/lib/systemd/system/dnsmasq.service; disabled; preset: disabled)
     Active: inactive (dead)
       Docs: man:dnsmasq(8)

enp3s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        ether 40:61:86:4b:e5:49  txqueuelen 1000  (Ethernet)
        RX packets 402699  bytes 562935297 (536.8 MiB)
        RX errors 0  dropped 4828  overruns 0  frame 0
        TX packets 202409  bytes 18256404 (17.4 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 1369  bytes 499249 (487.5 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 1369  bytes 499249 (487.5 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

virbr1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.100.1  netmask 255.255.255.0  broadcast 192.168.100.255
        ether 52:54:00:5d:d2:b5  txqueuelen 1000  (Ethernet)
        RX packets 2152  bytes 130488 (127.4 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 3857  bytes 5090175 (4.8 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

vnet0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::fc54:ff:fe75:1666  prefixlen 64  scopeid 0x20<link>
        ether fe:54:00:75:16:66  txqueuelen 1000  (Ethernet)
        RX packets 2152  bytes 160616 (156.8 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 5216  bytes 5163031 (4.9 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

I’m sorry, but I don’t know enough to be able to help you with this.

I simply followed instructions on how to configure stuff - and it all works.

I wouldn’t know where to begin to diagnose your issue (except for the dnsmasq thing that came to mind).

Addendum:
As far as I have understood, it is not a network problem, but the access to qemu:///system.
In addition, it seems to play a role whether the system was temporarily locked or in sleep or hibernate mode, and how much load is on the system.
After a clean reboot, without other running applications, I have a 75% chance that the VM will start and run without problems.
Unfortunately, a start with debug log did not provide any further information.

Perhaps my system with i7-860 and 8GB RAM is slowly reaching its limits after 15 years :wink:

that is definitely NOT the issue here

1 Like

Even back when your PC was new, 8G isn’t a lot for VMs. But now you got a whole Plasma DE and a lot of smaller things taking a little more RAM than they used to.

In all my use cases for compressing my swap, it just slowed things down. But you are pretty scarce on memory, especially for virtualizing. Does it make a big difference for you?

Just thinking if when you’re running out of memory, that is a ton of tacked on extra CPU you need just use your VMs to do their thing. Do all/some cores gets pinned during your issues? (in htop or whatever)

It’s even using a swapfile, and not a partition, to further degrade performance.

But there’s a few things you can do, to try and find which one is the bigger bottleneck. zram does complicate this for troubleshooting, as you can’t entirely separate CPU and RAM.

Well, i changed the swap to a swap partition and removed zswap, but it made no difference.
So far the 8GB memory was sufficient (the vm has 3 cores and 3gb ram assigned). Since I installed Manjaro over 2 years ago, everything has been stable. The problems only started about half a year ago. It also irritates me that it only loses the connection when I log in and start the desktop environment. whereby it makes no difference whether manjaro/kde or mxlinux/xfce.