- 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