- Users - libvirt List Archives

ERROR Could not find an installable distribution at ....
by Kaushal Shriyan 14 Feb '20

14 Feb '20

Hi, I am trying to set up alpine Linux Guest OS using the below command #virt-install --name=mfecdrupalalphine --file=/linuxkvmguestosdisk/var/lib/libvirt/images/mfecdrupalalphine.img --file-size=100 --nonsparse --vcpus=2 --ram=6096 --network=bridge:br0 --os-type=linux --os-variant=alpinelinux3.8 --graphics none --location=/linuxkvmguestosdisk/var/lib/libvirt/isos/alpine-standard-3.11.3-x86_64.iso --extra-args="console=ttyS0" Starting install... Retrieving file .treeinfo... | 0 B 00:00:00 Retrieving file content... | 0 B 00:00:00 ERROR Could not find an installable distribution at '/linuxkvmguestosdisk/var/lib/libvirt/isos/alpine-standard-3.11.3-x86_64.iso': The URL could not be accessed, maybe you mistyped? The location must be the root directory of an install tree. See virt-install man page for various distro examples. Domain installation does not appear to have been successful. If it was, you can restart your domain by running: virsh --connect qemu:///system start mfecdrupalalphine otherwise, please restart your installation. The iso file do exist as per the below details ls -l /linuxkvmguestosdisk/var/lib/libvirt/isos/alpine-standard-3.11.3-x86_64.iso -rw-r--r-- 1 root root 127926272 Feb 12 17:49 /linuxkvmguestosdisk/var/lib/libvirt/isos/alpine-standard-3.11.3-x86_64.iso # Any clue? I look forward to hearing from you and thanks in advance. Best Regards, Kaushal

2 1

problems with understanding of the memory parameters in the xml file
by Lentes, Bernd 13 Feb '20

13 Feb '20

Hi guys, despite reading hours and hours in the internet i'm still struggling with "memory", "currentmemory" and "maxMemory". Maybe you can help me to sort it out. My idea is that a guest has an initial value of memory (which "memory" seems to be) when booting. We have some Windows 10 guests which calculate some stuff and i would like to increase memory during runtime until it reaches a fixed maximum value. My hope was that a higher "maxMemory" could solve this, that the guest claims more memory and gets it. I didn't get it. Is my idea wrong ? Do i need a balloon driver for that ? What i find concerning ballooning is that it doesn't work automatically but has to be adjusted manually. Is that right ? Balloon drivers for windows are available. Is my idea right, does that work basically ? If yes how do i have to set the parameters ? Is the memory released after the guest has e.g. finished his calculation ? Does that work automatically or do i have to adjust that manually ? Thanks. Bernd -- Bernd Lentes Systemadministration Institute for Metabolism and Cell Death (MCD) Building 35.34 - Raum 208 HelmholtzZentrum münchen bernd.lentes(a)helmholtz-muenchen.de phone: +49 89 3187 1241 phone: +49 89 3187 3827 fax: +49 89 3187 2294 http://www.helmholtz-muenchen.de/mcd Perfekt ist wer keine Fehler macht Also sind Tote perfekt Helmholtz Zentrum MÃ¼nchen Helmholtz Zentrum Muenchen Deutsches Forschungszentrum fuer Gesundheit und Umwelt (GmbH) Ingolstaedter Landstr. 1 85764 Neuherberg www.helmholtz-muenchen.de Aufsichtsratsvorsitzende: MinDir.in Prof. Dr. Veronika von Messling Geschaeftsfuehrung: Prof. Dr. med. Dr. h.c. Matthias Tschoep, Kerstin Guenther Registergericht: Amtsgericht Muenchen HRB 6466 USt-IdNr: DE 129521671

2 2

does the guest have a snapshot ?
by Lentes, Bernd 11 Feb '20

11 Feb '20

Hi, i'm cuurently a bit confused if a guest does have a valid snapshot or not. This is the xml: ... <disk type='file' device='disk'> <driver name='qemu' type='qcow2'/> <source file='/var/lib/libvirt/images/crispor_1604/crispor_1604.sn'/> <backingStore type='file' index='1'> <format type='raw'/> <source file='/var/lib/libvirt/images/crispor_1604/crispor_1604.img'/> <backingStore/> </backingStore> <target dev='vda' bus='virtio'/> <alias name='virtio-disk0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </disk> ... both files are currently in access by the respective qemu process. lsof: qemu-kvm 19533 root 13u REG 253,0 29761732608 12091393 /var/lib/libvirt/images/crispor_1604/crispor_1604.sn qemu-kvm 19533 root 14r REG 253,0 111561775513 44793857 /var/lib/libvirt/images/crispor_1604/crispor_1604.img Here are both files: pc60181:/var/lib/libvirt/images/crispor_1604 # ll ... -rw------- 1 root root 111561775513 Oct 22 15:23 crispor_1604.img -rw-r--r-- 1 root root 29761732608 Feb 7 15:13 crispor_1604.sn crispor_1604.sn has a recent timestamp. The snapshot is currently in use: virsh # domblklist crispor_1604 Target Source ------------------------------------------------ vda /var/lib/libvirt/images/crispor_1604/crispor_1604.sn But virsh does not show any snapshot: virsh # snapshot-list crispor_1604 Name Creation Time State ------------------------------------------------------------ So i'm a bit confused. Does it have a valid snapshot or not. How can i find out and how can i get rid of it ? Thanks. Bernd -- Bernd Lentes Systemadministration Institute for Metabolism and Cell Death (MCD) Building 35.34 - Raum 208 HelmholtzZentrum münchen bernd.lentes(a)helmholtz-muenchen.de phone: +49 89 3187 1241 phone: +49 89 3187 3827 fax: +49 89 3187 2294 http://www.helmholtz-muenchen.de/mcd Perfekt ist wer keine Fehler macht Also sind Tote perfekt Helmholtz Zentrum MÃ¼nchen Helmholtz Zentrum Muenchen Deutsches Forschungszentrum fuer Gesundheit und Umwelt (GmbH) Ingolstaedter Landstr. 1 85764 Neuherberg www.helmholtz-muenchen.de Aufsichtsratsvorsitzende: MinDir.in Prof. Dr. Veronika von Messling Geschaeftsfuehrung: Prof. Dr. med. Dr. h.c. Matthias Tschoep, Kerstin Guenther Registergericht: Amtsgericht Muenchen HRB 6466 USt-IdNr: DE 129521671

2 4

No DHCP on default network when guest has multiple interfaces
by Patrick O'Neill 08 Feb '20

08 Feb '20

Hello, I am trying to boot a VM in libvirt that has 2 interfaces. The first interface is connected to the default network and the second connects to a bridge interface on the host. When the VM boots the first interface doesn't receive an IP address from DHCP. It works when the VM only has one interface though. If I login to the VM using virsh console I noticed that in NetworkManager the connection name and device are mixed [root@localhost ~]# nmcli con show NAME UUID TYPE DEVICE eth0 cc31f368-0a43-4c85-bd15-6aaa3ca23b3d ethernet eth1 If I run 'dhclient eth0' the interface gets an IP address from the default network as expected. [root@localhost ~]# dhclient eth0 [root@localhost ~]# 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: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 52:54:00:00:01:00 brd ff:ff:ff:ff:ff:ff inet 192.168.122.10/24 brd 192.168.122.255 scope global dynamic eth0 valid_lft 3599sec preferred_lft 3599sec 3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 52:54:00:48:e3:b8 brd ff:ff:ff:ff:ff:ff inet6 fe80::5054:ff:fe48:e3b8/64 scope link noprefixroute valid_lft forever preferred_lft forever The VM is created using the following command virt-install --import --name ${VM_HOST_NAME} \ --memory 2048 --vcpus 2 --cpu host \ --disk path=/var/lib/libvirt/images/${VM_HOST_NAME}.qcow2,format=qcow2,bus=virtio \ --network network=default \ --network bridge=bridge0,model=virtio \ --os-type=linux \ --os-variant=rhel7.6 \ --graphics none Any ideas what could cause this problem? The guest OS is CentOS 7.7 and the host is CentOS 8, but I have the same problem with a CentOS 7 hypervisor.

2 1

Does Libvirt's json parser support single quoted string in qmp json string?
by Peter Luo 05 Feb '20

05 Feb '20

Hi All, I’m using qmp command via “virsh qemu-monitor-command” to perform block related jobs. And in my case, I execute block-commit to commit the changes in the top image to the base image which is encrypted. So in the base parameter, I need a json string which is single quoted to support the encryption parameters. However, the virsh is failed to parse the whole json qmp command. Attempt 1: Single quote without backflash, failed root@host:~# virsh qemu-monitor-command i-9wdfw2x8 "{\"execute\": \"block-commit\", \"arguments\": { \"device\": \"drive-virtio-disk2\", \"job-id\": \"job100\", \"base\":'json:{\"encrypt.key-secret\":\"vol-38973xjl.secret\",\"driver\":\"qcow2\",\"file\":{\"driver\":\"file\",\"filename\":\"/pitrix/data/container/vol-38973xjl.img\"}}', \"top\": \"/pitrix/data/container/vol-38973xjl_ss-2tw7v0mm.img\"}}" error: internal error: cannot parse json {"execute": "block-commit", "arguments": { "device": "drive-virtio-disk2", "job-id": "job100", "base":'json:{"encrypt.key-secret":"vol-38973xjl.secret","driver":"qcow2","file":{"driver":"file","filename":"/pitrix/data/container/vol-38973xjl.img"}}', "top": "/pitrix/data/container/vol-38973xjl_ss-2tw7v0mm.img"}}: lexical error: invalid char in json text. , "job-id": "job100", "base":'json:{"encrypt.key-secret":"vo (right here) ------^ Attempt 2: Single quote with backflash, failed root@host:~# virsh qemu-monitor-command i-9wdfw2x8 "{\"execute\": \"block-commit\", \"arguments\": { \"device\": \"drive-virtio-disk2\", \"job-id\": \"job100\", \"base\":\'json:{\"encrypt.key-secret\":\"vol-38973xjl.secret\",\"driver\":\"qcow2\",\"file\":{\"driver\":\"file\",\"filename\":\"/pitrix/data/container/vol-38973xjl.img\"}}\', \"top\": \"/pitrix/data/container/vol-38973xjl_ss-2tw7v0mm.img\"}}" error: internal error: cannot parse json {"execute": "block-commit", "arguments": { "device": "drive-virtio-disk2", "job-id": "job100", "base":\'json:{"encrypt.key-secret":"vol-38973xjl.secret","driver":"qcow2","file":{"driver":"file","filename":"/pitrix/data/container/vol-38973xjl.img"}}\', "top": "/pitrix/data/container/vol-38973xjl_ss-2tw7v0mm.img"}}: lexical error: invalid char in json text. , "job-id": "job100", "base":\'json:{"encrypt.key-secret":"v (right here) ------^ My libvirt version is 5.7.0, libyajl is 2.1.0. Thanks, Peter Luo

6 9

USB devices with same vendor:product id
by Maxime Accadia 04 Feb '20

04 Feb '20

Hi, We have a VM with several USB devices attached. Everything works well, but sometimes, after a reboot of the host, some usb device get a different bus/device number and that prevent the reboot of the VM : ------- error: Failed to start domain xxx error: internal error: Did not find USB device 04b9:0300 bus:1 device:5 ------- I guess this is because we have multiple usb devices with the same vendor/product ID : ------- <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x04b9'/> <product id='0x0300'/> <address bus='2' device='4'/> </source> <alias name='hostdev0'/> <address type='usb' bus='0' port='2'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x0529'/> <product id='0x0001'/> <address bus='1' device='7'/> </source> <alias name='hostdev1'/> <address type='usb' bus='0' port='1.2'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x0529'/> <product id='0x0001'/> <address bus='2' device='3'/> </source> <alias name='hostdev2'/> <address type='usb' bus='0' port='1.4'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x04b9'/> <product id='0x0300'/> <address bus='1' device='6'/> </source> <alias name='hostdev3'/> <address type='usb' bus='0' port='1.1'/> </hostdev> ------- Any idea on how to handle this case ? We were thinking about using udev, but it seems that libvirt only supports vendor/id (not unique in our case) and bus/device (not predictable) to identify usb devices. Thanks, Maxime Accadia P.S. We use libvirt 4.0.0 on Ubuntu 18.04

3 4

Re: Does Libvirt's json parser support single quoted string in qmp json string?
by Peter Luo 31 Jan '20

31 Jan '20

Hi Peter Krempa, Thanks for your quick response, yes, I know since libvirt 5.8, the -blockdev is used for disk by default. However we have to maintain the old releases for the production environment for a while, so I still need use the old way to create the disk. >"base" argument must be a string. this means you need double quotes in >JSON ("). You also must properly escape any further JSON. > Do you mean the base argument need be formatted like below? \"base\":\"json:{\"encrypt.key-secret\":\"vol-38973xjl.secret\",\"driver\":\"qcow2\",\"file\":{\"driver\":\"file\",\"filename\":\"/pitrix/data/container/vol-38973xjl.img\"}}\" Please help me to point out where the examples are located? I did take a quick look at those test files, but no one seems to be matched with my case. Thanks, Peter Luo On 31/1/20, 6:52 PM, "Peter Krempa" <pkrempa(a)redhat.com> wrote: On Fri, Jan 31, 2020 at 18:38:33 +0800, Peter Luo wrote: > Hi All, > > > > I’m using qmp command via “virsh qemu-monitor-command” to perform block related jobs. > > And in my case, I execute block-commit to commit the changes in the top image to the base image which is encrypted. > > So in the base parameter, I need a json string which is single quoted to support the encryption parameters. > > However, the virsh is failed to parse the whole json qmp command. None of the above should be required with libvirt-5.10 and later when using qemu-4.2. Those two versions start using blockdev way of specifying images and encrypted images are supported. Please consider using libvirt-6.0 though as there are few fixes for blockdev. > > > > Attempt 1: Single quote without backflash, failed > > root@host:~# virsh qemu-monitor-command i-9wdfw2x8 "{\"execute\": \"block-commit\", \"arguments\": { \"device\": \"drive-virtio-disk2\", \"job-id\": \"job100\", \"base\":'json:{\"encrypt.key-secret\":\"vol-38973xjl.secret\",\"driver\":\"qcow2\",\"file\":{\"driver\":\"file\",\"filename\":\"/pitrix/data/container/vol-38973xjl.img\"}}', \"top\": \"/pitrix/data/container/vol-38973xjl_ss-2tw7v0mm.img\"}}" > > error: internal error: cannot parse json {"execute": "block-commit", "arguments": { "device": "drive-virtio-disk2", "job-id": "job100", "base":'json:{"encrypt.key-secret":"vol-38973xjl.secret","driver":"qcow2","file":{"driver":"file","filename":"/pitrix/data/container/vol-38973xjl.img"}}', "top": "/pitrix/data/container/vol-38973xjl_ss-2tw7v0mm.img"}}: lexical error: invalid char in json text. > > , "job-id": "job100", "base":'json:{"encrypt.key-secret":"vo "base" argument must be a string. this means you need double quotes in JSON ("). You also must properly escape any further JSON. Given that libvirt now supports the operation natively I'll refrain from elaborating on how to properly escape JSON to contain JSON strings, but there are few examples in the test suite. But please use the upstream supported way instead.

2 1

Detecting of features of VMs
by Peter Krempa 29 Jan '20

29 Jan '20

Hi, I was asked by Nir and Eyal of the oVirt project on how to detect whether a certain feature is supported by libvirt. As I thought it might be better to document this publically rather than being lost in a private thread I'm posting this to libvirt-users. The specific question will be answered below. --- There are currently two interfaces which allow discovery of libvirts and in turn qemu's capabilities. Both return an XML which describes various aspects of the hosts or VMs capabilities. virConnectGetCapabilities(conn) https://libvirt.org/formatcaps.html The XML returned by this API describes mostly the host itself, the CPU, NUMA topology, security driver support, migration features but also describes guests architectures supported by the guest. In case of the qemu driver the guest section describes some of the aspects and configurations supported by the default qemu binary, the machine types and virtualization types it supports. Additionally the <features> section describes support for some long-existing features such as ACPI, APIC and disk snapshots. As these features are supported for a long time, it can be assumed that they are present (at least in case of the qemu driver) when the second API is present. Now while the virConnectGetCapabilities API provides mostly useful information about the host, the limitation of not being able to report information about specific qemu binaries or machine types lead to introduction. virConnectGetDomainCapabilities(conn, emulator_binary_path, architecture, machine_type, virt_type, flags) https://libvirt.org/formatdomaincaps.html The XML returned by this API describes the capabilities of an VM which would be started using the parameters given to the API (note that if the parameters are NULL a default is provided). The <os> subelement describes supported OS loader types and firmware binaries. <cpu> describes which CPU models are supported by the emulator and also the CPU which would be used if 'host-model' is selected as the CPU model. The <devices> section describes models and some properties of devices supported by the VM. The 'enum's reported in this XML map to supported values of some of the fields we report the possible configurations for. Note that these values are reported individually and all combinations aren't necessarily supported. The last section 'features' describes whether some high-level features supported by such a VM. The features themselves are described in the documentation above. Note that the entries into 'features' are added arbitrarily depending on whether a feature is deemed important enough to be exposed. So please feel free to report if anything is missing or it would be helpful if we reported any feature. --- Now specifically to the question: I was asked on when it's safe to pass VIR_DOMAIN_UNDEFINE_CHECKPOINTS_METADATA to virDomainUndefine. In this case it's safe to pass it if <features> contains the <backup> element regardless of the value of 'supported' attribute. I'll also mention this in the documentation of the domain caps XML.

2 1

Host CPU usage high on guest network load (macvtap).
by André Malm 29 Jan '20

29 Jan '20

Hello, Is it reasonable for one CPU on the host to be loaded 20-30% on 100 mbps download in a guest? There is barely any (1-2%) load in the guest. The host is running ubuntu 18.04 on an Intel i7-7700K, virtualization etc is enabled. Everything except host load on guest network activity is fine. This is how i setup the network with virt-install: --network type=direct,source=enp1s0,source_mode=bridge,model=virtio,mac=00:11:22:33:44:55 In the guest (ubuntu18.04 cloud minimal) i run a simple wget, setting mode to vepa still works but the cpu load is the same.

1 0

Emulation packages for Centos8
by Mauricio Tavares 28 Jan '20

28 Jan '20

So I was looking for the qemu-system-ppc so I could emulate that cpu in my Intel I7 centos8 box. So far I found that available for fedora (and ubuntu) but not centos. Does anyone have a suggestion for where (repo) I can get said package?

1 0