- Users - libvirt List Archives

[libvirt-users] Question about disabling UFO on guest
by Bao Nguyen 05 Aug '20

05 Aug '20

Hello everyone, I would like to ask a question regarding to disable UFO of virtio vNIC in my guest. I have read the document at https://libvirt.org/formatdomain.html *host* The csum, gso, tso4, tso6, ecn and ufo attributes with possible values on and off can be used to turn off host offloading options. By default, the supported offloads are enabled by QEMU. *Since 1.2.9 (QEMU only)* The mrg_rxbuf attribute can be used to control mergeable rx buffers on the host side. Possible values are on (default) and off. *Since 1.2.13 (QEMU only)* *guest* The csum, tso4, tso6, ecn and ufo attributes with possible values on and off can be used to turn off guest offloading options. By default, the supported offloads are enabl ed by QEMU. *Since 1.2.9 (QEMU only)* Then I disabled UFO on my vNIC on guest as the following configuration <devices> <interface type='network'> <source network='default'/> <target dev='vnet1'/> <model type='virtio'/> <driver name='vhost' txmode='iothread' ioeventfd='on' event_idx='off' queues='5' rx_queue_size='256' tx_queue_size='256'> *<host gso='off' ufo='off' />* *<guest ufo='off'/>* </driver> </interface> </devices> Then I reboot my node to get the change effect and it works. However, can I disable the UFO without touching the host OS? or it always has to disable on both host and guest like that? Thanks, Brs, Natsu

2 1

Libvirt qemu-system-x86_64 on ppc64le no multi threading
by Kim-Norman Sahm 03 Aug '20

03 Aug '20

hi, i’m running Debian 10 on POWER9 and would like to spawn x86_64 emulated VMs. The virtual machine is configured to run with 8 vpus but it’s very slow. On the host you can see that the qemu-system-x86_64 process is using just one core! Ppc64le guests are using multi cores, so its looks like an config problem or software bug with the x86 emulator. <domain type='qemu'> <name>ubuntu</name> <uuid>a38148e3-6a85-4793-8d58-8725e8bef25a</uuid> <metadata> <libosinfo:libosinfo xmlns:libosinfo="http://libosinfo.org/xmlns/libvirt/domain/1.0"> <libosinfo:os id="http://debian.org/debian/10"/> </libosinfo:libosinfo> </metadata> <memory unit='KiB'>33554432</memory> <currentMemory unit='KiB'>33554432</currentMemory> <vcpu placement='static'>8</vcpu> <os> <type arch='x86_64' machine='pc-q35-5.0'>hvm</type> <boot dev='hd'/> </os> <features> <acpi/> <apic/> </features> <cpu mode='custom' match='exact' check='none'> <model fallback='forbid'>qemu64</model> </cpu> <clock offset='utc'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>destroy</on_crash> <pm> <suspend-to-mem enabled='no'/> <suspend-to-disk enabled='no'/> </pm> <devices> <emulator>/usr/bin/qemu-system-x86_64</emulator> <disk type='file' device='disk'> <driver name='qemu' type='qcow2'/> <source file='/var/lib/libvirt/images/ubuntu-x86_64.qcow2'/> <target dev='vda' bus='virtio'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <target dev='sda' bus='sata'/> <readonly/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <controller type='usb' index='0' model='qemu-xhci' ports='15'> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='pci' index='0' model='pcie-root'/> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </controller> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x10'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x11'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0x12'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0x13'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/> </controller> <controller type='pci' index='5' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='5' port='0x14'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x4'/> </controller> <controller type='pci' index='6' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='6' port='0x15'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x5'/> </controller> <controller type='pci' index='7' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='7' port='0x16'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x6'/> </controller> <interface type='bridge'> <mac address='52:54:00:cc:08:18'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </interface> <serial type='pty'> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='vnc' port='-1' autoport='yes'> <listen type='address'/> </graphics> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/> </video> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/> </memballoon> <rng model='virtio'> <backend model='random'>/dev/urandom</backend> <address type='pci' domain='0x0000' bus='0x06' slot='0x00' function='0x0'/> </rng> </devices> </domain> # ps ax|grep qemu 31546 ? Sl 2:38 /usr/bin/qemu-system-x86_64 -name guest=ubuntu,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-59-ubuntu/master-key.aes -machine pc-q35-5.0,accel=tcg,usb=off,dump-guest-core=off -cpu qemu64 -m 32768 -overcommit mem-lock=off -smp 8,sockets=8,cores=1,threads=1 -uuid a38148e3-6a85-4793-8d58-8725e8bef25a -no-user-config -nodefaults -chardev socket,id=charmonitor,fd=32,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -no-hpet -no-reboot -global ICH9-LPC.disable_s3=1 -global ICH9-LPC.disable_s4=1 -boot strict=on -device pcie-root-port,port=0x10,chassis=1,id=pci.1,bus=pcie.0,multifunction=on,addr=0x2 -device pcie-root-port,port=0x11,chassis=2,id=pci.2,bus=pcie.0,addr=0x2.0x1 -device pcie-root-port,port=0x12,chassis=3,id=pci.3,bus=pcie.0,addr=0x2.0x2 -device pcie-root-port,port=0x13,chassis=4,id=pci.4,bus=pcie.0,addr=0x2.0x3 -device pcie-root-port,port=0x14,chassis=5,id=pci.5,bus=pcie.0,addr=0x2.0x4 -device pcie-root-port,port=0x15,chassis=6,id=pci.6,bus=pcie.0,addr=0x2.0x5 -device pcie-root-port,port=0x16,chassis=7,id=pci.7,bus=pcie.0,addr=0x2.0x6 -device qemu-xhci,p2=15,p3=15,id=usb,bus=pci.2,addr=0x0 -device virtio-serial-pci,id=virtio-serial0,bus=pci.3,addr=0x0 -blockdev {"driver":"file","filename":"/var/lib/libvirt/images/ubuntu-x86_64.qcow2","node-name":"libvirt-2-storage","auto-read-only":true,"discard":"unmap"} -blockdev {"node-name":"libvirt-2-format","read-only":false,"driver":"qcow2","file":"libvirt-2-storage","backing":null} -device virtio-blk-pci,bus=pci.4,addr=0x0,drive=libvirt-2-format,id=virtio-disk0,bootindex=2 -blockdev {"driver":"file","filename":"/var/lib/libvirt/images/ubuntu-20.04-live-server-amd64.iso","node-name":"libvirt-1-storage","auto-read-only":true,"discard":"unmap"} -blockdev {"node-name":"libvirt-1-format","read-only":true,"driver":"raw","file":"libvirt-1-storage"} -device ide-cd,bus=ide.0,drive=libvirt-1-format,id=sata0-0-0,bootindex=1 -netdev tap,fd=34,id=hostnet0 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:cc:08:18,bus=pci.1,addr=0x0 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev socket,id=charchannel0,fd=35,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 -device usb-tablet,id=input0,bus=usb.0,port=1 -vnc 127.0.0.1:1 -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pcie.0,addr=0x1 -device virtio-balloon-pci,id=balloon0,bus=pci.5,addr=0x0 -object rng-random,id=objrng0,filename=/dev/urandom -device virtio-rng-pci,rng=objrng0,id=rng0,bus=pci.6,addr=0x0 -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny -msg timestamp=on Does anybody knows this problem? Best regards Kim

3 3

Xend and libvirt
by David K. Kahurani 03 Aug '20

03 Aug '20

Hello On a probably a few days old build of libvirt, it is not possible to connect to my local system. The command used is: $virsh -c xen:///system The errors can be seen from libvirtd logs[1] an interesting part being: " Aug 01 16:30:13 metal libvirtd[1680]: Failed to connect socket to '/var/run/libvirt/virtxend-sock':> Aug 01 16:30:13 metal libvirtd[1680]: End of file while reading data: Input/output error " >From the log, libxl driver is trying to connect to a socket which is tagged xend. My host is running Xen 5.1+ release from which Xend has been removed. Xend was removed from Xen in 4.5+ release, at least according to the docs[2] "xl was introduced in the Xen 4.1 release, however xend remained the default. At the time of the Xen 4.2 release, xend was declared deprecated and xl became the default toolstack. xend has finally been removed from the Xen 4.5 release" Any ideas would be much appreciated! Sincerely, David 1. https://termbin.com/l1br 2. https://wiki.xen.org/wiki/XL

3 4

Cannot pass secret id for backing file after taking external snapshot on encrypted qcow2 file
by yaohua.wu＠zstack.io 03 Aug '20

03 Aug '20

Hi， I used 'virsh snapshot-create' create an encrypted external snapshot, when I try to use 'qemu-img check' top file, found no entrance to pass backing-file's secret-id 1、Version centos-release-8.2-2.2004.0.1.el8.x86_64 libvirt.x86_64 6.0.0-17.el8 qemu-kvm.x86_64 15:4.2.0-19.el82、Reproduce Steps 1)Create an encrypted qcow2 qemu-img create --object secret,id=sec0,data=123456 -f qcow2 -o encrypt.format=luks,encrypt.key-secret=sec0 first.qcow2 1G 2)Create external snapshot with 'encrypted' xml # cat snap.xml <domainsnapshot> <disks> <disk name='hdc' snapshot='no'/> <disk name='vdb' snapshot='external'> <source file='/root/first-snapshot.qcow2'> <encryption format='luks'> <secret type='passphrase' uuid='f52a81b2-424e-490c-823d-6bd4235bc572'/> </encryption> </source> </disk> </disks> </domainsnapshot> # virsh dumpxml test-vm | awk '/<disk/,/<\/disk/' <disk type='file' device='disk'> <driver name='qemu' type='qcow2'/> <source file='/root/first-snapshot.qcow2' index='5'/> <backingStore type='file' index='2'> <format type='qcow2'/> <source file='/root/first.qcow2'> <encryption format='luks'> <secret type='passphrase' uuid='f981dd17-143f-45bc-88e6-222222222222'/> </encryption> </source> <backingStore/> </backingStore> <target dev='vdb' bus='virtio'/> <encryption format='luks'> <secret type='passphrase' uuid='f52a81b2-424e-490c-823d-6bd4235bc572'/> </encryption> <alias name='virtio-disk1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x0a' function='0x0'/> </disk> 3)try to qemu-img check top qcow2 file Note: The secid of the backing file is not recorded, so when I use qemu-img check/etc.. how to pass the secret to qemu of backing files # qemu-img info -U first-snapshot.qcow2 image: first-snapshot.qcow2 file format: qcow2 virtual size: 1 GiB (1073741824 bytes) disk size: 544 KiB encrypted: yes cluster_size: 65536 backing file: /root/first.qcow2 ### backing file: json:{"encrypt.format": "luks", "encrypt.key-secret": "secrete-id"} backing file format: luks Format specific information: compat: 1.1 lazy refcounts: false refcount bits: 16 encrypt: ivgen alg: plain64 hash alg: sha256 cipher alg: aes-256 uuid: e4158089-26e4-433f-990e-1d1d0723feee format: luks cipher mode: xts slots: [0]: active: true iters: 1257888 key offset: 4096 stripes: 4000 [1]: active: false key offset: 262144 [2]: active: false key offset: 520192 [3]: active: false key offset: 778240 [4]: active: false key offset: 1036288 [5]: active: false key offset: 1294336 [6]: active: false key offset: 1552384 [7]: active: false key offset: 1810432 payload offset: 2068480 master key iters: 300073 corrupt: false # qemu-img check -U --object secret,id=sec_1,file=/etc/libvirt/secrets/f52a81b2-424e-490c-823d-6bd4235bc572.base64,format=base64 --image-opts encrypt.format=luks,encrypt.key-secret=sec_1,file.filename=first-snapshot.qcow2 --object secret,id=sec_2,file=/etc/libvirt/secrets/f981dd17-143f-45bc-88e6-222222222222.base64,format=base64 qemu-img: Could not open 'encrypt.format=luks,encrypt.key-secret=sec_1,file.filename=first-snapshot.qcow2': Could not open backing file: Parameter 'key-secret' is required for cipher yaohua.wu(a)zstack.io

2 1

libvirt segfaults with "internal,error: Missing monitor reply object", during block live-migration
by Alex Walender 31 Jul '20

31 Jul '20

Dear libvirt community, Using recent Ubuntu Stein Cloud Packages, we are observing random libvirtd live-migration crashes on the target host. Libvirt is having a SEGFAULT with the qemu driver. Transferring block devices usually works without issues. However, the following memory transfer is causing the target libvirtd randomly to close down its socket, resulting in a roll-backed migration process.I can reproduce this with large VMs, which have a large memory pool. The last error message we see in libvirt logs is: error : qemuMonitorJSONCommandWithFd:315 : internal error: Missing monitor reply object With this, libvirt segfaults and restarts. Before we encountered this issue, we used an older nova-compute package (19.0.3). Not sure if this made a difference with usage of libvirtd-api. After upgrade, we also see a lot of recurring errors during migration: warning : qemuDomainObjBeginJobInternal:7044 : Cannot start job (query, none, none) for domain instance-00008f56; current job is (none, none, migration in) owned by (0 <null>, 0 <null>, 0 remoteDispatchDomainMigratePrepare3Params (flags=0x809b)) for (0s, 0s, 14834s) error : qemuDomainObjBeginJobInternal:7066 : Timed out during operation: cannot acquire state change lock (held by monitor=remoteDispatchDomainMigratePrepare3Params) They don't abort the running migration process, but spam every minute to the systemd journal. Source and destination run the same packages: Ubuntu 18.04.4 LTS (GNU/Linux 4.15.0-99-generic x86_64) OpenStack Stein (Ubuntu Cloud Archive) Libvirt+QEMU_x86 keystone-common 2:15.0.1-0ubuntu1~cloud0 libvirt-daemon 5.0.0-1ubuntu2.6~cloud0 qemu-system-x86 1:3.1+dfsg-2ubuntu3.7~cloud0 neutron-linuxbridge-agent 2:14.2.0-0ubuntu1~cloud0 neutron-plugin-ml2 2:14.2.0-0ubuntu1~cloud0 nova-compute 2:19.2.0-0ubuntu1~cloud0 nova-compute-libvirt 2:19.2.0-0ubuntu1~cloud0 I have attached source/destination debug logs from libvirtd and nova-compute here: https://denzelx.ddns.net/index.php/s/KPJ7vv4aTcb69XD Any help would be nice! Best Regards -- M.Sc Alex Walender de.NBI Cloud Bielefeld Administrator Center for Biotechnology (CeBiTec) University of Bielefeld 33594 Bielefeld Germany room: M3-118 phone: +49 (521) 106 2907

3 3

Routed network can't reach outside network
by Rui Correia 29 Jul '20

29 Jul '20

Greetings folks. I've setup libvirtd on my manjaro linux laptop. Got a couple of VM's running (Win10 and Debian10) through NAT without any issues. This is what the current network diagram looks like and it works fine: +-----------------------------------+ | +---------------------+ | | | +----------+ | | | | |Win 10 VM | | | | | |10.1.1.10 | | | | | +----------+ | | | Laptop | | | | Manjaro | +-------------+ | | | 10.0.0.10 | |Debian 10 VM | | | +-------->+ | |10.1.1.11 | | | | | | +-------------+ | | | | |NAT | | | | |10.1.1.0/24 | | | | +---------------------+ | +------------+ | +-----------------------------------+ |router | | |switch +---+ |10.0.0.0/24 | | +---------+ +------------+ | |Desktop | +-------->+Manjaro | |10.0.0.11| +---------+ But now I need the debian machine to be accessible from another host on the lan 10.0.0.0/24 which of course is outside the host. That network diagram would look like this: +-----------------------------------------+ | +------------------+ | | | +----------+ | | | | |Win 10 VM | | | | | |10.1.1.10 | | | | | NAT +----------+ | | | | 10.1.1.0/24 | | | +------------------+ | | Laptop | +-------->+ Manjaro +------------------------+ | | | 10.0.0.10 | +-------------+ | | | | | |Debian 10 VM | | | | | | |10.2.2.10 | | | | | | Routed +-------------+ | | +------------+ | | | 10.2.2.0/24 | | |router | | | +------------------------+ | |switch +---+ +-----------------------------------------+ |10.0.0.0/24 | | +------------+ | | | +---------+ | |Desktop | +-------->+Manjaro | |10.0.0.11| +---------+ So, I've setup a 'routed network' for the Debian 10 VM but it's not working as I would expect. The host can ping the Debian VM and the Debian VM can ping the host but the Debian VM cannot ping the router 10.0.0.1 or any ip address on the internet. I've been using Virtual Machine Manager to set everything up. And this is how the routed network is configured <network connections="1"> <name>routed</name> <uuid>970a25f7-29b6-4a6b-b890-f593eae4fc15</uuid> <forward dev="wlo1" mode="route"> <interface dev="wlo1"/> </forward> <bridge name="virbr2" stp="on" delay="0"/> <mac address="52:54:00:bf:35:42"/> <domain name="routed"/> <ip address="10.2.2.1" netmask="255.255.255.0"> <dhcp> <range start="10.2.2.2" end="10.2.2.254"/> </dhcp> </ip> </network> Any idea on what i might be doing wrong? Thanks in advance. Cheers Rui Correia

6 9

machinectl does not show libvirtd vms
by Ismael Bouya 28 Jul '20

28 Jul '20

(this is a follow-up of a discussion on IRC with mprivozn) Hello, I’m facing an issue where systemd-machined is not aware of new VMs happening in libvirt (with QEMU). I attached debug logs for a VM starting. To repeat the discussion that happened on IRC: - libvirt config does not specify anything related to cgroup_controllers - cgroups are mounted (mount | grep cgroup is not empty) - in libvirtd.service I see no mention of cgroups (apart from comments related to TasksMax and LimitMEMLOCK) I’m suspecting a packaging issue in my distribution (NixOS) but I’m not really sure where I should look at to solve it. NB: the reason I wanted machinectl was to make use of nsswitch mymachines facilities, which I learnt wouldn’t work anyway. So I’m only reporting it in case something needs to be fixed (probably in my distribution packaging). -- Ismael

1 0

Re: Routed network can't reach outside network
by Rui Correia 23 Jul '20

23 Jul '20

Hi Ken, Of course I did it all by hand. :-D No, I didn't. I'm a fraud. I used http://asciiflow.com/ which asks you to register in order to save your drawings in their cloud. If you don't register, you can still draw and export your drawings, but you can't save them for reusing those later. I see I've missed a couple of posts in this small thread. I was under the impression that I had subscribed to the list but apparently I'm only receiving the messages directly addressed to me. Hence why I took so much time to reply. I'll try to subscribe again. Thank you all in advance. Cheers, Rui Correia On Thu, Jul 23, 2020 at 3:31 PM Marc Roos <M.Roos(a)f1-outsourcing.eu> wrote: > > > > > you must be an ASCII charting demigod. Did you use software to make > those, or do > > them yourselves? Either way, I'm impressed... > > Search for AsciiArtStudio.exe > > > > >

1 0

virt-install missing parameters
by David 22 Jul '20

22 Jul '20

Hello, Hopefully this is the right place to send a question like this... I'm attempting to automate creation of VMs using virt-install and a cloud-init disk image. To get this to work, I need to specify the location of the cloud-init configs by passing smbios key/value pairs. Normally, -smbios is provided to qemu to do this. With virt-install, the Internet says I should use --sysinfo. However, --sysinfo (as well as --qemu-comandline) is reported as an invalid command flag, and it is not present when I look at man virt-install and virt-install --help. I am hoping someone on the list knows why this isn't working or can explain how I might provide the arguments to qemu. The host is Debian 9. It is up-to-date as far as package versions are concerned, as much as Debian 9 can be. I can't find any indication about why the arguments would have been taken away. Thanks!

1 0

host and vm on isolated network, there is ip (via dhcp) but not ping
by daggs 22 Jul '20

22 Jul '20

Greetings, I've setup an vm with openwrt in it, defined a isolated lan between the vm and the host and booted the vm up. I see the vm is up, made sure the vnic is visible in both the host and guest and added it to the br in the guest. I've issued an dhcpd call on the vnic (labeled vnic0) in the host and got an ip, see: dagg@NCC-5001D ~ $ dhcpcd vnet0 DUID 00:01:00:01:23:dd:d8:5b:e0:d5:5e:d9:f2:e2 vnet0: IAID 00:10:20:bf vnet0: rebinding lease of 192.168.1.130 vnet0: probing address 192.168.1.130/24 vnet0: soliciting an IPv6 router vnet0: leased 192.168.1.130 for 43200 seconds vnet0: adding route to 192.168.1.0/24 vnet0: adding default route via 192.168.1.1 forked to background, child pid 26279 dagg@NCC-5001D ~ $ ifconfig virtsw0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether 52:54:00:3e:3f:88 txqueuelen 1000 (Ethernet) RX packets 123098 bytes 16327962 (15.5 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 6 bytes 252 (252.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 vnet0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.1.130 netmask 255.255.255.0 broadcast 192.168.1.255 inet6 fe80::fc54:ff:fe10:20bf prefixlen 64 scopeid 0x20<link> ether fe:54:00:10:20:bf txqueuelen 1000 (Ethernet) RX packets 45 bytes 8002 (7.8 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 39 bytes 2676 (2.6 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 dagg@NCC-5001D ~ $ ping 192.168.1.1 PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data. ^C --- 192.168.1.1 ping statistics --- 2 packets transmitted, 0 received, 100% packet loss, time 1018ms the vm's xml can be found at https://pastebin.com/1gXBGcPb virtsw0 is defined as follows: <network connections='1'> <name>virtsw0</name> <uuid>c8eb15a3-cc5c-4bd6-8f3b-5790792ddccc</uuid> <bridge name='virtsw0' stp='on' delay='0'/> <mac address='52:54:00:3e:3f:88'/> </network> the os is gentoo, the versions are libvirt-6.2.0 qemu-5.0.0. I have another server running debian 10 with the same virtsw0 definition, there the connection is working. /var/lib/libvirt/dnsmasq/virtsw0.macs has only [] in it, can that be the issue? Thanks, Dagg.

2 2