- Users - libvirt List Archives

About Libvirt Setmem&dommemstat Function
by 🍭 19 May '20

19 May '20

I am using 'virsh setmem' to adjust the vm memory. But I don't know what is the lowerlimit memory that can be adjusted to, so I try to update the version of libvirt&qemu to get caches of the vm memory so that I can calculate the lowerlimit. And when I upgrade libvirt to 4.10.0, qemu upgrade to 4.1.0, still, I cannot get 'stat-disk-caches'.  How can I solve it ? Thx.

1 0

Firmware auto-select limitation
by GUOQING LI 15 May '20

15 May '20

Hi everyone and Martin I would like to confirm the conversation we had in regard the possible limitation of firmware auto-select feature that’s been released since v5.20. I recall you saying that there were a lot of issues with auto select and later they shipped it into a Json file , it still didn’t solve all the problems, did it? Is it better to explicitly specify the loader and nvram path than using auto-select ? Just today, I encountered the issue of using firmware=“efi” on libvirt 5.4.0 I am running Ubuntu eoan 19.10, I am wondering how did it happen. Detailed error Error starting domain: internal error: process exited while connecting to monitor: 2020-05-15T14:19:06.033267Z qemu-system-x86_64: -drive file=/usr/share/OVMF/OVMF_CODE.fd,if=pflash,format=raw,unit=0,readonly=on: Failed to lock byte 100 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: internal error: process exited while connecting to monitor: 2020-05-15T14:19:06.033267Z qemu-system-x86_64: -drive file=/usr/share/OVMF/OVMF_CODE.fd,if=pflash,format=raw,unit=0,readonly=on: Failed to lock byte 100

3 2

DNSMASQ Libvirt
by Santhosh Kumar Gunturu 15 May '20

15 May '20

Hi, Net-dump xml File. root@NFV-FRU:~# virsh net-dumpxml data-2 <network> <name>data-2</name> <uuid>ace4935f-0367-4632-be7c-61bab2da7d4a</uuid> <bridge name='data-2br1' stp='on' delay='0'/> <mac address='52:54:00:46:43:7d'/> <ip address='10.12.12.1' netmask='255.255.255.240'> <dhcp> <range start='10.12.12.4' end='10.12.12.4'/> </dhcp> </ip> </network> The DHCP response is going with Subnet Mask 255.255.255.0 10.12.12.1.bootps > 10.12.12.4.bootpc: [udp sum ok] BOOTP/DHCP, Reply, length 300, xid 0x7331d77a, Flags [none] (0x0000) Your-IP 10.12.12.4 Server-IP 10.12.12.1 Client-Ethernet-Address 52:54:00:5f:ab:94 (oui Unknown) Vendor-rfc1048 Extensions Magic Cookie 0x63825363 DHCP-Message Option 53, length 1: Offer Server-ID Option 54, length 4: 10.12.12.1 Lease-Time Option 51, length 4: 3600 RN Option 58, length 4: 1800 RB Option 59, length 4: 3150 Subnet-Mask Option 1, length 4: 255.255.255.0 BR Option 28, length 4: 10.12.12.255 Domain-Name-Server Option 6, length 4: 10.12.12.1 Can I know the reason ? Thanks & Regards Santhosh Kumar Gunturu

2 1

What is expiry time represents in this format
by Santhosh Kumar Gunturu 15 May '20

15 May '20

I see the output. root@X10SDV-8C-TLN4F:/mnt/config# cat /var/lib/libvirt/dnsmasq/mgmt-1br1.status [ { "ip-address": "192.168.27.8", "mac-address": "52:54:00:42:21:14", "hostname": "vyatta", "expiry-time": 1589500228 } ] Can you please explain what does the expiry-time mean ? What are its units ? Please let me know. Thanks & Regards Santhosh Kumar Gunturu

3 2

Re: Storage cleaning
by Lothar Schilling 14 May '20

14 May '20

Thank you, that's it! virsh vol-list storage VM1 /dev/storage/VM1.img VM2 /dev/storage/VM2.img VM3 /dev/storage/VM3.img [dead] VM4 /dev/storage/VM4.img [dead] A last stupid question (I don't want to make a big mistake ...): Is virsh vol-delete VM3 virsh vol-delete VM4 the right command to get rid of the offending ones? Am 14.05.2020 um 19:10 schrieb Alvin Starr: > > virsh pool-list > you will get something like: > Name State Autostart > ----------------------------------------------- > default active yes > gnome-boxes active no > windows-openstack-image active yes > > then run virsh vol-list <your volume name> > > and you should be able to see the volumes that are still defined. > > > On 5/14/20 1:01 PM, Lothar Schilling wrote: >> virsh list --all >> >> 15 VM1 running >> 16 VM2 running >> >> ps ax | grep virt >> >> 14281 ? Sl 1170:30 /usr/libexec/qemu-kvm -name VM1 [...] >> 14384 ? Sl 376:45 /usr/libexec/qemu-kvm -name VM2 [...] >> >> Am 14.05.2020 um 17:45 schrieb Alvin Starr: >> >>> List your storage pool to insure that they have been deleted from >>> the pool. >>> If they are not there anymore then check to make sure nothing is >>> running that would have the VM images open. >>> >>> On 5/14/20 11:01 AM, Lothar Schilling wrote: >>>> Hi everybody, >>>> >>>> we have a Centos 6 host with libvirtd 0.10.2. It's holding a >>>> storage pool of about 3.5 TB with 4 VMs. I decided to rearrange >>>> them, so I destroyed and undefined two of them. But now I am not >>>> able to install a new one because virsh gives me an "not enough >>>> space left". Those two undefined VMs still linger around somehow >>>> occupying a lot of that storage. How can I get rid of them? >>>> >>>> Name: storage >>>> UUID: 8b25e085-38d8-5a09-f80f-a29150f25d42 >>>> Status: laufend >>>> Persistent: yes >>>> Automatischer Start: yes >>>> Kapazität: 3,54 TiB >>>> Zuordnung: 3,39 TiB >>>> Verfügbar: 155,27 GiB >>>> >>>> Thank you very much >>>> >>>> Lothar Schilling >> >> >

1 0

Re: Storage cleaning
by Lothar Schilling 14 May '20

14 May '20

virsh list --all 15 VM1 running 16 VM2 running ps ax | grep virt 14281 ? Sl 1170:30 /usr/libexec/qemu-kvm -name VM1 [...] 14384 ? Sl 376:45 /usr/libexec/qemu-kvm -name VM2 [...] Am 14.05.2020 um 17:45 schrieb Alvin Starr: > List your storage pool to insure that they have been deleted from the > pool. > If they are not there anymore then check to make sure nothing is > running that would have the VM images open. > > On 5/14/20 11:01 AM, Lothar Schilling wrote: >> Hi everybody, >> >> we have a Centos 6 host with libvirtd 0.10.2. It's holding a storage >> pool of about 3.5 TB with 4 VMs. I decided to rearrange them, so I >> destroyed and undefined two of them. But now I am not able to install >> a new one because virsh gives me an "not enough space left". Those >> two undefined VMs still linger around somehow occupying a lot of that >> storage. How can I get rid of them? >> >> Name: storage >> UUID: 8b25e085-38d8-5a09-f80f-a29150f25d42 >> Status: laufend >> Persistent: yes >> Automatischer Start: yes >> Kapazität: 3,54 TiB >> Zuordnung: 3,39 TiB >> Verfügbar: 155,27 GiB >> >> Thank you very much >> >> Lothar Schilling

1 0

Storage cleaning
by Lothar Schilling 14 May '20

14 May '20

Hi everybody, we have a Centos 6 host with libvirtd 0.10.2. It's holding a storage pool of about 3.5 TB with 4 VMs. I decided to rearrange them, so I destroyed and undefined two of them. But now I am not able to install a new one because virsh gives me an "not enough space left". Those two undefined VMs still linger around somehow occupying a lot of that storage. How can I get rid of them? Name: storage UUID: 8b25e085-38d8-5a09-f80f-a29150f25d42 Status: laufend Persistent: yes Automatischer Start: yes Kapazität: 3,54 TiB Zuordnung: 3,39 TiB Verfügbar: 155,27 GiB Thank you very much Lothar Schilling

1 0

Unit libvirtd.service could not be found. on VM
by Dana Elfassy 13 May '20

13 May '20

Hi all, Some background: I recently has some issues with libvirt on my laptop when I got the error 'operation failed: pool 'default' already exists with uuid dd48b6ad-9a00-46eb-a3a4-c122d8a294a5' when I connected virt-manager. I was finally able to resolve it yesterday, when I removed libvirt and all its related content in /etc/libvirt, removed the pool by its UUID, deleted virbr0 & virbro-nic, removed the default network, reinstalled and created the network & default pool again Now I got libvirtd on my laptop up & running. However, when I install vms on my laptop, they don't have libvirtd.service This is the network configuration XML: <interface type="network"> <mac address="52:54:00:d0:40:69"/> <source network="default" portid="171a745c-f96d-412a-baa7-ee1feeaed6ac" bridge="virbr0"/> <target dev="vnet1"/> <model type="virtio"/> <alias name="net0"/> <address type="pci" domain="0x0000" bus="0x00" slot="0x03" function="0x0"/> </interface> I installed the vms with virt-manager. The Network source is Virtual network 'default': NAT I'm using CentOS8.1 on both my laptop & vms. Is there anything else I need to reconfigure or any thoughts why libvirtd.service doesn't exist on my VMS? Thanks, Dana

3 10

Re: USB-hotplugging fails with "failed to load cgroup BPF prog: Operation not permitted" on cgroups v2
by Pavel Hrdina 13 May '20

13 May '20

On Mon, Jan 20, 2020 at 09:00:15PM +0100, Pol Van Aubel wrote: > Hi, > > Quoting Pavel Hrdina (2020-01-20 14:29:36) > > On Sat, Jan 18, 2020 at 11:17:11PM +0100, Pol Van Aubel wrote: > > > Hi all, > > > > > > I've disabled cgroups v1 on my system with the kernel boot option > > > "systemd.unified_cgroup_hierarchy=1". Since doing so, USB hotplugging > > > fails to work, seemingly due to a permissions problem with BPF. Please > > > note that the technique I'm going to describe worked just fine for > > > hotplugging USB devices to running domains until this change. > > > Attaching / detaching USB devices when the domain is down still works as > > > expected. > > > > > > I get the same error when attaching a device in virt-manager, as I do > > > when running the following command: > > > > > > sudo virsh attach-device wenger /dev/stdin --persistent <<END > > > <hostdev mode='subsystem' type='usb' managed='yes'> > > > <source startupPolicy='optional'> > > > <vendor id='0x046d' /> > > > <product id='0xc215' /> > > > </source> > > > </hostdev> > > > END > > > > > > This returns > > > error: Failed to attach device from /dev/stdin > > > error: failed to load cgroup BPF prog: Operation not permitted > > > > > > > > > virt-manager returns basically the same error, but for completeness' > > > sake, here it is: > > > > > > failed to load cgroup BPF prog: Operation not permitted > > > > > > Traceback (most recent call last): > > > File "/usr/share/virt-manager/virtManager/addhardware.py", line 1327, in _add_device > > > self.vm.attach_device(dev) > > > File "/usr/share/virt-manager/virtManager/object/domain.py", line 920, in attach_device > > > self._backend.attachDevice(devxml) > > > File "/usr/lib/python3.8/site-packages/libvirt.py", line 590, in attachDevice > > > if ret == -1: raise libvirtError ('virDomainAttachDevice() failed', dom=self) > > > libvirt.libvirtError: failed to load cgroup BPF prog: Operation not permitted > > > > > > > > > Now, libvirtd is running as root, so I don't understand why any > > > operation on BPF programs is not permitted. I've dug into libvirt's code > > > a bit to see what is throwing this error and it boils down to > > > <https://github.com/libvirt/libvirt/blob/7d608469621a3fda72dff2a89308e68cc9f…> > > > and > > > <https://github.com/libvirt/libvirt/blob/02bf7cc68bfc76242f02d23e73cad36618f…> > > > but I have no clue what that syscall is doing, so that's where my > > > debugging capability basically ends. > > > > > > Maybe this is something as simple as setting the right ACL somewhere. I > > > haven't touched /etc/libvirt/qemu.conf except for setting nvram. There > > > *is* something about cgroup_device_acl there but afaict that's for > > > cgroups v1, when there was still a device cgroup controller. Any help > > > would be greatly appreciated. > > > > > > > > > Domain log files: > > > Upon execution of the above commands, nothing gets added to the domain > > > log in /var/log/qemu/wenger.log, so I've decided they're likely > > > irrelevant to the issue. Please ask for any additional info required. > > > > > > > > > System information: > > > Arch Linux, (normal) kernel 5.4.11 > > > libvirt 5.10.0 > > > qemu 4.2.0, using KVM. > > > Host system is x86_64 on an intel 5820k. > > > Guest system is probably irrelevant, but is Windows 10 on the same. > > > > > > > > > Possibly relevant kernel build options: > > > $ zgrep BPF /proc/config.gz > > > [22:55:52]: zgrep BPF /proc/config.gz > > > > > > CONFIG_CGROUP_BPF=y > > > CONFIG_BPF=y > > > CONFIG_BPF_SYSCALL=y > > > CONFIG_BPF_JIT_ALWAYS_ON=y > > > CONFIG_IPV6_SEG6_BPF=y > > > CONFIG_NETFILTER_XT_MATCH_BPF=m > > > # CONFIG_BPFILTER is not set > > > CONFIG_NET_CLS_BPF=m > > > CONFIG_NET_ACT_BPF=m > > > CONFIG_BPF_JIT=y > > > CONFIG_BPF_STREAM_PARSER=y > > > CONFIG_LWTUNNEL_BPF=y > > > CONFIG_HAVE_EBPF_JIT=y > > > CONFIG_BPF_EVENTS=y > > > # CONFIG_BPF_KPROBE_OVERRIDE is not set > > > # CONFIG_TEST_BPF is not set > > > > Hi > > > > I've installed clean archlinux to try this out and it works as expected, > > I'm able to attach USB device into a VM. > > > > My system env is mostly the same as yours except for kernel version: > > > > kernel 5.4.13 > > libvirt 5.10.0 > > qemu 4.2.0, using KVM. > > > > Please enable libvirt debug logs [1] and share the output with us. > > I've updated to 5.4.13 and created a barebones VM without storage to > reproduce the behaviour. libvirtd debug logs are attached. There appear > to be two BPF failures of the same BPF program (?). The first is on line > 23209, which appears to be part of machine startup, and which I don't > actually notice. The second one is where I manually add the USB device, > on line 30599. > > Thanks, Thanks for the logs, but it did not help to figure out where the issue is. I was hoping to see some error output from the syscall but the line that should contain it is empty: 2020-01-20 19:47:15.589+0000: 8579: debug : virBPFLoadProg:78 : Can you please check system logs and output of dmesg? I've managed to run into this article [1] that explains that even if you have all permissions and no SELinux you can still be blocked by something called kernel_lockdown and it should appear in dmesg. Pavel [1] <https://gehrcke.de/2019/09/running-an-ebpf-program-may-require-lifting-the-…>

2 3

libvirt object IVirtualBox is null
by claudia freitas 13 May '20

13 May '20

Hi, I'm using libvirt to manage virtual machines created with VirtualBox-6.0, however when I try to start, to shut down virsh vm I get the message of object IVirtualBox is null. However, if I leave the VirtualBox graphical interface open it works normally. Can anyone help or is experiencing the same problem? Thanks, Kilida2020

2 1

Another DKIM test message
by dberrange＠yahoo.com 13 May '20

13 May '20

Testing

1 0

Testing new email settings to fix DKIM
by dberrange＠yahoo.com 13 May '20

13 May '20

Testing

1 0

Running libvirtd inside chroot (mock to be precise)
by Marcin Sobczyk 13 May '20

13 May '20

Hi, I was wondering whether it's possible to run libvirtd inside a chroot environment. The assumption is that only one instance of libvirtd would be running on the machine at a time, but still, inside chroot. Currently in my chroot env I have: - /dev/kvm added with mknod - /dev/vhost-net added with mknod - mounted: - /dev/net - /dev/shm - /run/dbus When I run libvirtd in non-daemon mode I get one error: 2020-05-13 10:06:27.480+0000: 28555: error : virNetDevBridgeCreate:484 : error creating bridge interface virbr0: File exists but it seems to me that libvirtd can live with that. When I try to run a VM however I get a qemu error reported: 2020-05-13 08:56:51.643+0000: starting up libvirt version: 4.5.0, package: 35.3.module_el8.1.0+297+df420408 (CentOS Buildsys <bugs(a)centos.org>, 2020-04-10-11:06:38, ), qemu version: 2.12.0qemu-kvm-2.12.0-88.module_el8.1.0+297+df420408.3, kernel: 4.18.0-80.el8.x86_64, hostname: ..... LC_ALL=C PATH=/var/lib/ci_toolbox:/usr/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin HOME=/root/ovirt-system-tests USER=root LOGNAME=root QEMU_AUDIO_DRV=none /usr/libexec/qemu-kvm -name guest=992415aa-lago-basic-suite-master-engine,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-1-992415aa-lago-basic-/master-key.aes -machine pc-i440fx-rhel7.6.0,accel=kvm,usb=off,vmport=off,dump-guest-core=off -cpu host -m 4096 -realtime mlock=off -smp 2,sockets=2,cores=1,threads=1 -object iothread,id=iothread1 -numa node,nodeid=0,cpus=0,mem=2048 -numa node,nodeid=1,cpus=1,mem=2048 -uuid 10ed4b42-bb14-4b03-a411-c62fb1181c2d -display none -no-user-config -nodefaults -chardev socket,id=charmonitor,fd=31,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 -boot menu=off,strict=on -device virtio-scsi-pci,iothread=iothread1,id=scsi0,num_queues=2,bus=pci.0,addr=0x5 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x6 -drive file=/root/ovirt-system-tests/deployment-basic-suite-master/default/images/lago-basic-suite-master-engine_root.qcow2,format=qcow2,if=none,id=drive-virtio-disk0,serial=1,cache=writeback,discard=unmap -device virtio-blk-pci,iothread=iothread1,scsi=off,num-queues=1,bus=pci.0,addr=0x7,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1,write-cache=on -drive file=/root/ovirt-system-tests/deployment-basic-suite-master/default/images/lago-basic-suite-master-engine_nfs.raw,format=raw,if=none,id=drive-scsi0-0-0-0,serial=2,cache=writeback,discard=unmap -device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,write-cache=on -drive file=/root/ovirt-system-tests/deployment-basic-suite-master/default/images/lago-basic-suite-master-engine_iscsi.raw,format=raw,if=none,id=drive-scsi0-0-0-2,serial=3,cache=writeback,discard=unmap -device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=2,drive=drive-scsi0-0-0-2,id=scsi0-0-0-2,write-cache=on -netdev tap,fds=33:34,id=hostnet0,vhost=on,vhostfds=35:36 -device virtio-net-pci,mq=on,vectors=6,netdev=hostnet0,id=net0,mac=54:52:c0:a8:c8:02,bus=pci.0,addr=0x3 -netdev tap,fds=37:38,id=hostnet1,vhost=on,vhostfds=39:40 -device virtio-net-pci,mq=on,vectors=6,netdev=hostnet1,id=net1,mac=54:52:c0:a8:ca:02,bus=pci.0,addr=0x4 -chardev socket,id=charchannel0,fd=41,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 -chardev pty,id=charconsole0 -device virtconsole,chardev=charconsole0,id=console0 -device cirrus-vga,id=video0,bus=pci.0,addr=0x2 -object rng-random,id=objrng0,filename=/dev/urandom -device virtio-rng-pci,rng=objrng0,id=rng0,bus=pci.0,addr=0x9 -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny -msg timestamp=on 2020-05-13 08:56:51.643+0000: Domain id=1 is tainted: high-privileges 2020-05-13 08:56:51.643+0000: Domain id=1 is tainted: host-cpu libvirt: QEMU Driver error : internal error: Unable to find any /dev mount 2020-05-13 08:56:51.654+0000: shutting down, reason=failed And this one currently is blocking me. Did anyone try such a setup? Any help would be appreciated. Regards, Marcin

1 0

blockcommit --pivot does not succeed in conjunction with qemu 5.0.0
by Thomas Stein 11 May '20

11 May '20

Hello one and all. Got a problem with libvirt 6.2.0 and qemu 5.0.0. virsh blockcommit mymachine vda --active --verbose --pivot works until it shows [100%] but it never actually pivots. It just sits there. Is this a known issue with 6.2.0 and i should try 6.3.0? For now i switched back to qemu 4.2.0 and this seems to solve the issue too. Any hints? Ahoi! t.

2 3

Nested Virtualization on Google Cloud.
by Tanmoy Sinha 10 May '20

10 May '20

I am using nested virtualization on a Google Cloud Compute instance. Things are generally working fine with libvirt using qemu+kvm, however I observed that <cpu mode='host-model'> is not exposing avx and avx2 instruction set to the guest Linux instance. Google Cloud platform claims the CPU model of the host compute instance is Broadwell, however libvirt capabilities maps it to Westmere-IBRS and it has avx and avx2 features, yet host-model is not exposing those. As a workaround, I am using <cpu mode='host-passthrough'>, but I would like to know what is going wrong here? I can also share the output of cpuid of the host system, if that helps. I am not sure whether it's a libvirt issue or something to do with KVM. Any help would be appreciated. Following is the host information, along with the qemu process details for the linux guest. root@dev-vm:~# kvm --version QEMU emulator version 2.8.1(Debian 1:2.8+dfsg-6+deb9u9) Copyright (c) 2003-2016 Fabrice Bellard and the QEMU Project developers root@dev-vm:~# virsh --version setlocale: No such file or directory 3.0.0 root@dev-vm:~# virsh capabilities <capabilities> <host> <uuid>a2b6c5d9-dfea-7efb-defb-3cce3aadb067</uuid> <cpu> <arch>x86_64</arch> <model>*Westmere-IBRS*</model> <vendor>Intel</vendor> <topology sockets='1' cores='4' threads='2'/> <feature name='vme'/> <feature name='ss'/> <feature name='ht'/> <feature name='pclmuldq'/> <feature name='vmx'/> <feature name='fma'/> <feature name='pcid'/> <feature name='x2apic'/> <feature name='movbe'/> <feature name='xsave'/> <feature name='osxsave'/> <feature name='avx'/> <feature name='f16c'/> <feature name='rdrand'/> <feature name='hypervisor'/> <feature name='arat'/> <feature name='fsgsbase'/> <feature name='tsc_adjust'/> <feature name='bmi1'/> <feature name='hle'/> <feature name='avx2'/> <feature name='smep'/> <feature name='bmi2'/> <feature name='erms'/> <feature name='invpcid'/> <feature name='rtm'/> <feature name='rdseed'/> <feature name='adx'/> <feature name='smap'/> <feature name='md-clear'/> <feature name='ssbd'/> <feature name='xsaveopt'/> <feature name='pdpe1gb'/> <feature name='rdtscp'/> <feature name='abm'/> <feature name='3dnowprefetch'/> <feature name='invtsc'/> <pages unit='KiB' size='4'/> <pages unit='KiB' size='2048'/> <pages unit='KiB' size='1048576'/> </cpu> <power_management> <suspend_mem/> <suspend_disk/> <suspend_hybrid/> </power_management> <migration_features> <live/> <uri_transports> <uri_transport>tcp</uri_transport> 15771 ? Sl 0:03 qemu-system-x86_64 -enable-kvm -name guest=Util-LIN-1,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-11-Util-LIN-1/master-key.aes -machine pc-i440fx-2.1,accel=kvm,usb=off,dump-guest-core=off -cpu *Westmere-IBRS* ,+vme,+ss,+ht,+pclmuldq,+vmx,+fma,+pcid,+x2apic,+movbe,+xsave,+osxsave, *+avx,*+f16c,+rdrand,+hypervisor,+arat,+fsgsbase,+tsc_adjust,+bmi1,+hle, *+avx2*,+smep,+bmi2,+erms,+invpcid,+rtm,+rdseed,+adx,+smap,+md-clear,+ssbd,+xsaveopt,+pdpe1gb,+rdtscp,+abm,+3dnowprefetch -m 4096 -realtime mlock=off -smp 4,sockets=4,cores=1,threads=1 -uuid caa60e3c-f946-40a4-80ac-1fb86366c5f6 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-11-Util-LIN-1/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -boot strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device ahci,id=sata0,bus=pci.0,addr=0x4 -drive file=/var/lib/libvirt/images/Util-LIN-1/Util-LIN-1.qcow2,format=qcow2,if=none,id=drive-sata0-0-0 -device ide-hd,bus=sata0.0,drive=drive-sata0-0-0,id=sata0-0-0,bootindex=1 -drive file=/var/lib/libvirt/images/Util-LIN-1/Util-LIN-1-acdisk.qcow2,format=qcow2,if=none,id=drive-sata0-0-2 -device ide-hd,bus=sata0.2,drive=drive-sata0-0-2,id=sata0-0-2 -netdev tap,fd=34,id=hostnet0,vhost=on,vhostfd=36 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=1a:b2:ae:f7:69:c7,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -device usb-tablet,id=input0,bus=usb.0,port=1 -vnc 0.0.0.0:8 -device cirrus-vga,id=video0,bus=pci.0,addr=0x2 -incoming defer -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 -msg timestamp=on Regards Tanmoy Sinha

1 0

Libvirt APIs for creating virtual networks
by Santhosh Kumar Gunturu 08 May '20

08 May '20

I am using the Libvirt APIs to create the virtual networks to use the dnsmasq capabilities. I want to understand the APIs how to set the lease time in XML to control the dnsmasq lease time. Also, I need some DHCP statistics on the virtual network. Is there any API available to fetch the statistics ? Please let me know if any ? Thanks & Regards Santhosh Kumar Gunturu

3 6

Further DKIM testing validation
by dberrange＠yahoo.com 07 May '20

07 May '20

Please ignore this mail too.

1 0

Testing email DKIM handling
by dberrange＠yahoo.com 07 May '20

07 May '20

Please ignore this test message. Validating whether the mailing list is still breaking DKIM signed messages.

1 0

virsh connect to xen:///system fails: "error: internal error: Unexpected driver type 'Xen' opened" ?
by PGNet Dev 04 May '20

04 May '20

I'm setting up for libvirt remote access on a xend host. On the host, xl info | egrep "release|xen_version" release : 5.6.10-24.gde48f93-default xen_version : 4.13.0_12-lp151.700 systemctl --version systemd 234 I've installed rpm -qa libvirt-daemon-xen libvirt-daemon-xen-6.2.0-lp151.890.1.x86_64 libvirtd --version libvirtd (libvirt) 6.2.0 virsh --version 6.2.0 Per https://libvirt.org/daemons.html I've setup for use of modular daemons with systemd sockets, rather than monolithic libvirtd systemctl list-units | egrep " virt" virtxend.service loaded active running Virtualization xen daemon virtlockd.socket loaded active listening Virtual machine lock manager socket virtlogd.socket loaded active listening Virtual machine log manager socket virtnetworkd-admin.socket loaded active listening Libvirt network admin socket virtnetworkd-ro.socket loaded active listening Libvirt network local read-only socket virtnetworkd.socket loaded active listening Libvirt network local socket virtnodedevd-admin.socket loaded active listening Libvirt nodedev admin socket virtnodedevd-ro.socket loaded active listening Libvirt nodedev local read-only socket virtnodedevd.socket loaded active listening Libvirt nodedev local socket virtnwfilterd-admin.socket loaded active listening Libvirt nwfilter admin socket virtnwfilterd-ro.socket loaded active listening Libvirt nwfilter local read-only socket virtnwfilterd.socket loaded active listening Libvirt nwfilter local socket virtproxyd-admin.socket loaded active listening Libvirt proxy admin socket virtproxyd-ro.socket loaded active listening Libvirt proxy local read-only socket virtproxyd.socket loaded active listening Libvirt proxy local socket virtsecretd-admin.socket loaded active listening Libvirt secret admin socket virtsecretd-ro.socket loaded active listening Libvirt secret local read-only socket virtsecretd.socket loaded active listening Libvirt secret local socket virtstoraged-admin.socket loaded active listening Libvirt storage admin socket virtstoraged-ro.socket loaded active listening Libvirt storage local read-only socket virtstoraged.socket loaded active listening Libvirt storage local socket virtxend-admin.socket loaded active running Libvirt libxl admin socket virtxend-ro.socket loaded active running Libvirt libxl local read-only socket virtxend.socket loaded active running Libvirt libxl local socket /tree /run/libvirt/ /run/libvirt/ ├── hostdevmgr ├── libvirt-admin-sock ├── libvirt-sock ├── libvirt-sock-ro ├── libxl │ ├── autostarted │ ├── Domain-0.xml │ └── driver.pid ├── network │ ├── autostarted │ └── nwfilter.leases ├── nodedev ├── nwfilter ├── nwfilter-binding ├── qemu │ ├── autostarted │ └── slirp ├── secrets ├── storage │ └── autostarted ├── virtlockd-sock ├── virtlogd-sock ├── virtnetworkd-admin-sock ├── virtnetworkd-sock ├── virtnetworkd-sock-ro ├── virtnodedevd-admin-sock ├── virtnodedevd-sock ├── virtnodedevd-sock-ro ├── virtnwfilterd-admin-sock ├── virtnwfilterd-sock ├── virtnwfilterd-sock-ro ├── virtsecretd-admin-sock ├── virtsecretd-sock ├── virtsecretd-sock-ro ├── virtstoraged-admin-sock ├── virtstoraged-sock ├── virtstoraged-sock-ro ├── virtxend-admin-sock ├── virtxend-sock └── virtxend-sock-ro On the server, TLS certs are in place openssl version OpenSSL 1.1.1g 21 Apr 2020 cat /etc/libvirt/libvirt.conf ca_file = "/sec/ssl/CA/CA.CHAIN.crt.pem" cert_file = "/sec/ssl/libvirt/client.EC.crt.pem" key_file = "/sec/ssl/libvirt/client.EC.key.pem" cat /etc/libvirt/virtproxyd.conf ca_file = "/sec/ssl/CA/CA.CHAIN.crt.pem" cert_file = "/sec/ssl/libvirt/server.EC.crt.pem" key_file = "/sec/ssl/libvirt/server.EC.key.pem" On attempt to first _locally_ connect, virsh -c test:///default list sysinfo Id Name State ---------------------- 1 test running virsh -c test:///default sysinfo <sysinfo type='smbios'> <bios> <entry name='vendor'>LENOVO</entry> <entry name='version'>G4ETA1WW (2.61 )</entry> <entry name='date'>05/07/2014</entry> <entry name='release'>2.61</entry> </bios> </sysinfo> but virsh -c xen:///system?socket=/var/run/libvirt/libvirt-sock error: failed to connect to the hypervisor error: internal error: Unexpected driver type 'Xen' opened What's missing/incorrect in my config, causing the "Unexpected driver" error, and preventing the connect to local hypervisor?

2 2

sync guest time
by Miguel Duarte de Mora Barroso 30 Apr '20

30 Apr '20

Hi, I'm seeing the following issue when attempting to update the guest's clock on a running fc32 guest (using guest agent): ``` [root@virt-launcher-vmi-masquerade-mh2xm /]# virsh domtime 1 --pretty Time: 2020-04-30 23:27:29 [root@virt-launcher-vmi-masquerade-mh2xm /]# virsh domtime 1 --sync error: internal error: unable to execute QEMU agent command 'guest-set-time': hwclock failed to set hardware clock to system time # now, this one works. [root@virt-launcher-vmi-masquerade-mh2xm /]# virsh domtime 1 --now [root@virt-launcher-vmi-masquerade-44v2x /]# virsh domtime 1 --pretty Time: 2020-04-30 11:15:45 ``` This is the simplest reproducer I could come with; the original issue is this call to libvirt's `setTIme` in [0]. Is there any workaround I could try ? Am I doing something wrong here ? [0] - https://github.com/kubevirt/kubevirt/blob/6bb516148ce4c29825ae74f473e022075…

2 3

Re: [Query] Facing issue in build libvirt6.0 on ubuntu 1804
by Michal Privoznik 30 Apr '20

30 Apr '20

[Please keep the list CCed] On 4/30/20 12:02 PM, Ramesh B wrote: > Hi Michal, > > Thanks for quick response. > > Ubuntu: 18.04.3 LTS > QEMU emulator version 4.2.0 > libvirtd (libvirt) 4.0.0 > > I have lunched the guest os using QEMU. > I would like to use the virsh commands to get the status / control of > guest OS. > when i run any virsh commands not getting any response from QEMU. > When i tried to explore, found the solution saying use of QEMU monitor > will help. > added the below command while lunch, > -chardev > socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-freebsd11.0/monitor.sock,server,nowait > -mon chardev=charmonitor,id=monitor,mode=control > > but result in below mentioed error: > Failed to bind socket to > /var/lib/libvirt/qemu/domain-freebsd11.0/monitor.sock > > Then thought of building libvirt 6.0 version, will help to solve the > problem. Ah, so you wanted to use 'virsh qemu-attach' to attach libvirt to a running qemu. Yeah, it needs a monitor. However, the functionality was not maintained and probably not functional anyway so we've removed in the 5.5.0 release. > > Please guide me to solve this problem. > > Regards, > Babu B > But what's interesting is that you are unable to build. Which package is providing the rst2* binaries? Are their up to date? Michal

2 5

[Query] Facing issue in build libvirt6.0 on ubuntu 1804
by Ramesh B 30 Apr '20

30 Apr '20

Hi all, I am trying to build libvirt 6.0 on ubuntu OS 18.04. Facing one issue libvirt source compilation. ============================================ <stdin>:215: (ERROR/3) Error in "code-block" directive: 1 argument(s) required, 0 supplied. .. code-block:: help [command-or-group] <stdin>:229: (ERROR/3) Error in "code-block" directive: 1 argument(s) required, 0 supplied. .. code-block:: =========================================== *Source:* https://libvirt.org/sources/libvirt-6.0.0.tar.xz *Build Command*: $ mkdir build && cd build $ ../configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var $ make $ sudo make install Need help in solving the build error. is it possible to install libvirt package without build if yes please share the command/procedure/link. Thanks, Ramesh

3 6

why libvirtd can not list the running domain?
by 崔涛的个人邮箱 30 Apr '20

30 Apr '20

1. I run a user domain like this: [root@kvm1 ~]# qemu-system-x86_64 -enable-kvm -m 1G -smp 4 /images/test1.img WARNING: Image format was not specified for '/images/test1.img' and probing guessed raw. Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted. Specify the 'raw' format explicitly to remove the restrictions. VNC server running on ::1:5900 2. Then, I install and using my user domain. 3. Then, I login to libvirtd on my hosts,but can not get the user domain using list command. [root@kvm1 ~]# virsh -c qemu:///system Welcome to virsh, the virtualization interactive terminal. Type: 'help' for help with commands 'quit' to quit virsh # virsh # virsh # list Id Name State ---------------------------------------------------- virsh #

2 2

"failed to setup INTx fd: Operation not permitted" error when using PCI passthrough
by Riccardo Ravaioli 30 Apr '20

30 Apr '20

Hi, I'm on a Dell VEP 1405 running Debian 9.11 and I'm running a few tests with various interfaces given in PCI passthrough to a qemu/KVM Virtual Machine also running Debian 9.11. I noticed that only one of the four I350 network controllers can be used in PCI passthrough. The available interfaces are: *# dpdk-devbind.py --status Network devices using kernel driver ==============================* *===== 0000:02:00.0 'I350 Gigabit Network Connection 1521' if=eth2 drv=igb unused=igb_uio,vfio-pci,uio_* *pci_generic 0000:02:00.1 'I350 Gigabit Network Connection 1521' if=eth3 drv=igb unused=igb_uio,vfio-pci,uio_* *pci_generic 0000:02:00.2 'I350 Gigabit Network Connection 1521' if=eth0 drv=igb unused=igb_uio,vfio-pci,uio_* *pci_generic 0000:02:00.3 'I350 Gigabit Network Connection 1521' if=eth1 drv=igb unused=igb_uio,vfio-pci,uio_* *pci_generic 0000:04:00.0 'QCA986x/988x 802.11ac Wireless Network Adapter 003c' if= drv=ath10k_pci unused=igb_uio,vfio-pci,uio_* *pci_generic 0000:05:00.0 'Device 15c4' if=eth7 drv=ixgbe unused=igb_uio,vfio-pci,uio_* *pci_generic 0000:05:00.1 'Device 15c4' if=eth6 drv=ixgbe unused=igb_uio,vfio-pci,uio_* *pci_generic 0000:07:00.0 'Device 15e5' if=eth5 drv=ixgbe unused=igb_uio,vfio-pci,uio_* *pci_generic 0000:07:00.1 'Device 15e5' if=eth4 drv=ixgbe unused=igb_uio,vfio-pci,uio_**pci_generic* If I try PCI passthrough on 02:00.2 (eth0), it works fine. With any of the remaining three interfaces, libvirt fails with this error: *# virsh create vnf.xml error: Failed to create domain from vnf.xml error: internal error: process exited while connecting to monitor: 2020-04-06T16:08:47.048266Z qemu-system-x86_64: -device vfio-pci,host=02:00.1,id=**hostdev0,bus=pci.0,addr=0x5: vfio 0000:02:00.1: failed to setup INTx fd: Operation not permitted* The contents of vnf.xml are available here: https://pastebin.com/rT3RmAi5 This is what happened in *dmesg* when I tried to start the VM: *[ 7305.371730] igb 0000:02:00.1: removed PHC on eth3 [ 7307.085618] ACPI Warning: \_SB.PCI0.PEX2._PRT: Return Package has no elements (empty) (20160831/nsprepkg-130) [ 7307.085717] pcieport 0000:00:0b.0: can't derive routing for PCI INT B [ 7307.085719] vfio-pci 0000:02:00.1: PCI INT B: no GSI [ 7307.369611] igb 0000:02:00.1: enabling device (0400 -> 0402) [ 7307.369668] ACPI Warning: \_SB.PCI0.PEX2._PRT: Return Package has no elements (empty) (20160831/nsprepkg-130) [ 7307.369764] pcieport 0000:00:0b.0: can't derive routing for PCI INT B [ 7307.369766] igb 0000:02:00.1: PCI INT B: no GSI [ 7307.426266] igb 0000:02:00.1: added PHC on eth3 [ 7307.426269] igb 0000:02:00.1: Intel(R) Gigabit Ethernet Network Connection [ 7307.426271] igb 0000:02:00.1: eth3: (PCIe:5.0Gb/s:Width x2) 50:9a:4c:ee:9f:b1 [ 7307.426350] igb 0000:02:00.1: eth3: PBA No: 106300-000 [ 7307.426352] igb 0000:02:00.1: Using MSI-X interrupts. 4 rx queue(s), 4 tx queue(s)* These are all the messages related to that device in dmesg before I tried to start the VM: *# dmesg | grep 02:00.1 [ 0.185301] pci 0000:02:00.1: [8086:1521] type 00 class 0x020000 [ 0.185317] pci 0000:02:00.1: reg 0x10: [mem 0xdfd40000-0xdfd5ffff] [ 0.185334] pci 0000:02:00.1: reg 0x18: [io 0xd040-0xd05f] [ 0.185343] pci 0000:02:00.1: reg 0x1c: [mem 0xdfd88000-0xdfd8bfff] [ 0.185434] pci 0000:02:00.1: PME# supported from D0 D3hot D3cold [ 0.185464] pci 0000:02:00.1: reg 0x184: [mem 0xdeea0000-0xdeea3fff 64bit pref] [ 0.185467] pci 0000:02:00.1: VF(n) BAR0 space: [mem 0xdeea0000-0xdeebffff 64bit pref] (contains BAR0 for 8 VFs) [ 0.185486] pci 0000:02:00.1: reg 0x190: [mem 0xdee80000-0xdee83fff 64bit pref] [ 0.185488] pci 0000:02:00.1: VF(n) BAR3 space: [mem 0xdee80000-0xdee9ffff 64bit pref] (contains BAR3 for 8 VFs) [ 0.334021] DMAR: Hardware identity mapping for device 0000:02:00.1 [ 0.334463] iommu: Adding device 0000:02:00.1 to group 16 [ 0.398809] pci 0000:02:00.1: Signaling PME through PCIe PME interrupt [ 2.588049] igb 0000:02:00.1: PCI INT B: not connected [ 2.643900] igb 0000:02:00.1: added PHC on eth1 [ 2.643903] igb 0000:02:00.1: Intel(R) Gigabit Ethernet Network Connection [ 2.643905] igb 0000:02:00.1: eth1: (PCIe:5.0Gb/s:Width x2) 50:9a:4c:ee:9f:b1 [ 2.643984] igb 0000:02:00.1: eth1: PBA No: 106300-000 [ 2.643986] igb 0000:02:00.1: Using MSI-X interrupts. 4 rx queue(s), 4 tx queue(s) [ 2.873544] igb 0000:02:00.1 rename3: renamed from eth1 [ 2.939352] igb 0000:02:00.1 eth3: renamed from rename3* In particular this looks suspicious: *igb 0000:02:00.1: PCI INT B: not connected* The full dmesg is available here: https://pastebin.com/kPbUAKCi This is the PCI bus structure: *# lspci -tv -[0000:00]-+-00.0 Intel Corporation Device 1980 +-04.0 Intel Corporation Device 19a1 +-05.0 Intel Corporation Device 19a2 +-06.0-[01]----00.0 Intel Corporation Device 19e2 +-0b.0-[02-03]--+-00.0 Intel Corporation I350 Gigabit Network Connection | +-00.1 Intel Corporation I350 Gigabit Network Connection | +-00.2 Intel Corporation I350 Gigabit Network Connection | \-00.3 Intel Corporation I350 Gigabit Network Connection +-0f.0-[04]----00.0 Qualcomm Atheros QCA986x/988x 802.11ac Wireless Network Adapter +-12.0 Intel Corporation DNV SMBus Contoller - Host +-13.0 Intel Corporation DNV SATA Controller 0 +-15.0 Intel Corporation Device 19d0 +-16.0-[05-06]--+-00.0 Intel Corporation Device 15c4 | \-00.1 Intel Corporation Device 15c4 +-17.0-[07-08]--+-00.0 Intel Corporation Device 15e5 | \-00.1 Intel Corporation Device 15e5 +-18.0 Intel Corporation Device 19d3 +-1c.0 Intel Corporation Device 19db +-1f.0 Intel Corporation DNV LPC or eSPI +-1f.2 Intel Corporation Device 19de +-1f.4 Intel Corporation DNV SMBus controller \-1f.5 Intel Corporation DNV SPI Controller* By looking at lspci -v, there's something going on with the IRQ field exactly in three devices I can't use in PCI passthrough ("IRQ -2147483648"): *# lspci -v|grep -A1 I350 02:00.0 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01) Flags: bus master, fast devsel, latency 0, IRQ -2147483648 -- 02:00.1 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01) Flags: bus master, fast devsel, latency 0, IRQ -2147483648 -- 02:00.2 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01) Flags: bus master, fast devsel, latency 0, IRQ 18 -- 02:00.3 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01) Flags: bus master, fast devsel, latency 0, IRQ -2147483648* Finally, every i350 interface has its own IOMMU group in /sys/kernel/iommu_groups/. The kernel I'm using in the host machine is 4.9.189 and my libvirt version is 4.3.0. Any thoughts on this? Is there something I should enable in the BIOS or in the kernel to make this work? Thanks! Regards, Riccardo Ravaioli

1 1

Attaching DVD-writer
by Andreas Thörn 27 Apr '20

27 Apr '20

I want to add my dvd and be able to burn dvd’s. I’ve tried every solution I could find, but nothing works. In my xml i have: <disk type='block' device='cdrom'> <driver name='qemu' type='raw'/> <source dev='/dev/sr0'/> <target dev='sdb' bus='sata'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> In my guest (windows 10) it’s shown as "QEMU QEMU DVD-ROM” .. which of course means I can’t burn. If anyone has a solution it would be this mailing list Thanks Andreas

4 5