- Users - libvirt List Archives

[libvirt-users] libvirtd (4.9) version takes a long time to start
by Sharath Kurudi 11 Feb '19

11 Feb '19

Hi, I have installed libvirt 4.9. libvirtd 4.9 takes a long time to come up. I enabled debug prints and also put my own prints Logs are below 2019-02-06 05:55:49.082+0000: 377: info : libvirt version: 4.9.0 2019-02-06 05:55:49.082+0000: 377: info : hostname: draco 2019-02-06 05:55:49.082+0000: 377: info : virObjectNew:248 : OBJECT_NEW: obj=0x558e782d8bb0 classname=virAccessManager 2019-02-06 05:55:49.082+0000: 377: debug : virAccessManagerNewDriver:105 : Initialized with stack 2019-02-06 05:55:49.082+0000: 377: info : virObjectNew:248 : OBJECT_NEW: obj=0x558e782cd870 classname=virAccessManager 2019-02-06 05:55:49.082+0000: 377: debug : virAccessManagerNewDriver:105 : Initialized with none 2019-02-06 05:55:49.082+0000: 377: info : virObjectRef:382 : OBJECT_REF: obj=0x558e782d8bb0 2019-02-06 05:55:49.082+0000: 377: info : virObjectUnref:344 : OBJECT_UNREF: obj=0x558e782d8bb0 2019-02-06 05:55:49.082+0000: 377: debug : main:1200 : Decided on pid file path '/var/run/libvirtd.pid' 2019-02-06 05:55:49.082+0000: 377: debug : main:1213 : Decided on socket paths '/var/run/libvirt/libvirt-sock', '/var/run/libvirt/libvirt-sock-ro' and '/var/run/libvirt/libvirt-admin-sock' 2019-02-06 05:55:49.082+0000: 377: debug : virFileClose:109 : Closed fd 5 2019-02-06 05:55:49.082+0000: 378: debug : virFileClose:109 : Closed fd 4 2019-02-06 05:55:49.082+0000: 378: debug : virFileClose:109 : Closed fd 4 2019-02-06 05:55:49.082+0000: 378: debug : virFileClose:109 : Closed fd 6 2019-02-06 05:55:49.083+0000: 379: debug : main:1255 : Ensuring run dir '/var/run/libvirt' exists 2019-02-06 05:55:49.083+0000: 379: debug : virFileMakePathHelper:3034 : path=/var/run/libvirt mode=0777 2019-02-06 05:55:49.083+0000: 379: debug : virNetlinkStartup:137 : Running global netlink initialization 2019-02-06 05:55:49.083+0000: 379: debug : virNetlinkStartup:144 : Sharath Returning from global netlink initialization 2019-02-06 05:55:49.083+0000: 379: debug : main:1270 : Sharath virNetlinkStartup done 2019-02-06 05:55:49.083+0000: 379: debug : virNetDaemonNew:127 : Sharath Running virNetDaemonNew 2019-02-06 05:55:49.083+0000: 379: debug : virNetDaemonNew:131 : Sharath virNetDaemonInitalize done 2019-02-06 05:55:49.083+0000: 379: info : virObjectNew:248 : OBJECT_NEW: obj=0x558e782ce1b0 classname=virNetDaemon 2019-02-06 05:55:49.083+0000: 379: debug : virNetDaemonNew:136 : Sharath virNetDaemonInitalize done The above logs loop till libvirtd comes up. It is also seen that more than one instance of libvirtd runs simultaneously during delay. Any ideas on how to resolve? Thanks

2 1

[libvirt-users] libvirtd (4.9) version takes a long time to start
by Sharath Kurudi 07 Feb '19

07 Feb '19

Hi, I have installed libvirt 4.9. libvirtd 4.9 takes a long time to come up. I enabled debug prints and also put my own prints Logs are below 2019-02-06 05:55:49.082+0000: 377: info : libvirt version: 4.9.0 2019-02-06 05:55:49.082+0000: 377: info : hostname: draco 2019-02-06 05:55:49.082+0000: 377: info : virObjectNew:248 : OBJECT_NEW: obj=0x558e782d8bb0 classname=virAccessManager 2019-02-06 05:55:49.082+0000: 377: debug : virAccessManagerNewDriver:105 : Initialized with stack 2019-02-06 05:55:49.082+0000: 377: info : virObjectNew:248 : OBJECT_NEW: obj=0x558e782cd870 classname=virAccessManager 2019-02-06 05:55:49.082+0000: 377: debug : virAccessManagerNewDriver:105 : Initialized with none 2019-02-06 05:55:49.082+0000: 377: info : virObjectRef:382 : OBJECT_REF: obj=0x558e782d8bb0 2019-02-06 05:55:49.082+0000: 377: info : virObjectUnref:344 : OBJECT_UNREF: obj=0x558e782d8bb0 2019-02-06 05:55:49.082+0000: 377: debug : main:1200 : Decided on pid file path '/var/run/libvirtd.pid' 2019-02-06 05:55:49.082+0000: 377: debug : main:1213 : Decided on socket paths '/var/run/libvirt/libvirt-sock', '/var/run/libvirt/libvirt-sock-ro' and '/var/run/libvirt/libvirt-admin-sock' 2019-02-06 05:55:49.082+0000: 377: debug : virFileClose:109 : Closed fd 5 2019-02-06 05:55:49.082+0000: 378: debug : virFileClose:109 : Closed fd 4 2019-02-06 05:55:49.082+0000: 378: debug : virFileClose:109 : Closed fd 4 2019-02-06 05:55:49.082+0000: 378: debug : virFileClose:109 : Closed fd 6 2019-02-06 05:55:49.083+0000: 379: debug : main:1255 : Ensuring run dir '/var/run/libvirt' exists 2019-02-06 05:55:49.083+0000: 379: debug : virFileMakePathHelper:3034 : path=/var/run/libvirt mode=0777 2019-02-06 05:55:49.083+0000: 379: debug : virNetlinkStartup:137 : Running global netlink initialization 2019-02-06 05:55:49.083+0000: 379: debug : virNetlinkStartup:144 : Sharath Returning from global netlink initialization 2019-02-06 05:55:49.083+0000: 379: debug : main:1270 : Sharath virNetlinkStartup done 2019-02-06 05:55:49.083+0000: 379: debug : virNetDaemonNew:127 : Sharath Running virNetDaemonNew 2019-02-06 05:55:49.083+0000: 379: debug : virNetDaemonNew:131 : Sharath virNetDaemonInitalize done 2019-02-06 05:55:49.083+0000: 379: info : virObjectNew:248 : OBJECT_NEW: obj=0x558e782ce1b0 classname=virNetDaemon 2019-02-06 05:55:49.083+0000: 379: debug : virNetDaemonNew:136 : Sharath virNetDaemonInitalize done The above logs loop till libvirtd comes up. It is also seen that more than one instance of libvirtd runs simultaneously during delay. Any ideas on how to resolve? Thanks Sharath

1 0

[libvirt-users] concurrent migration of several domains rarely fails
by Lentes, Bernd 06 Feb '19

06 Feb '19

Hi, i have a two-node cluster with several domains as resources. During testing i tried several times to migrate some domains concurrently. Usually it suceeded, but rarely it failed. I found one clue in the log: Dec 03 16:03:02 ha-idg-1 libvirtd[3252]: 2018-12-03 15:03:02.758+0000: 3252: error : virKeepAliveTimerInternal:143 : internal error: connection closed due to keepalive timeout The domains are configured similar: primitive vm_geneious VirtualDomain \ params config="/mnt/san/share/config.xml" \ params hypervisor="qemu:///system" \ params migration_transport=ssh \ op start interval=0 timeout=120 trace_ra=1 \ op stop interval=0 timeout=130 trace_ra=1 \ op monitor interval=30 timeout=25 trace_ra=1 \ op migrate_from interval=0 timeout=300 trace_ra=1 \ op migrate_to interval=0 timeout=300 trace_ra=1 \ meta allow-migrate=true target-role=Started is-managed=true \ utilization cpu=2 hv_memory=8000 What is the algorithm to discover the port used for live migration ? I have the impression that "params migration_transport=ssh" is worthless, port 22 isn't involved for live migration. My experience is that for the migration tcp ports > 49151 are used. But the exact procedure isn't clear for me. Does live migration uses first tcp port 49152 and for each following domain one port higher ? E.g. for the concurrent live migration of three domains 49152, 49153 and 49154. Why does live migration for three domains usually succeed, although on both hosts just 49152 and 49153 is open ? Is the migration not really concurrent, but sometimes sequential ? Bernd -- Bernd Lentes Systemadministration Institut für Entwicklungsgenetik Gebäude 35.34 - Raum 208 HelmholtzZentrum münchen [ mailto:bernd.lentes@helmholtz-muenchen.de | bernd.lentes(a)helmholtz-muenchen.de ] phone: +49 89 3187 1241 fax: +49 89 3187 2294 [ http://www.helmholtz-muenchen.de/idg | http://www.helmholtz-muenchen.de/idg ] wer Fehler macht kann etwas lernen wer nichts macht kann auch nichts lernen Helmholtz Zentrum Muenchen Deutsches Forschungszentrum fuer Gesundheit und Umwelt (GmbH) Ingolstaedter Landstr. 1 85764 Neuherberg www.helmholtz-muenchen.de Aufsichtsratsvorsitzende: MinDirig.in Petra Steiner-Hoffmann Stellv.Aufsichtsratsvorsitzender: MinDirig. Dr. Manfred Wolter Geschaeftsfuehrer: Prof. Dr. med. Dr. h.c. Matthias Tschoep, Heinrich Bassler, Dr. rer. nat. Alfons Enhsen Registergericht: Amtsgericht Muenchen HRB 6466 USt-IdNr: DE 129521671

3 6

[libvirt-users] Installing libvirt and Xen on Red Hat 7.5
by Lianjie Cao 06 Feb '19

06 Feb '19

Hi, I am installing OpenStack on Red Hat 7.5. For Nova compute component, I choose libvirt and Xen. However, I am running into some problems. It seems libvirt is unable to communicate with Xen. Xen installation: I installed Xen410 using "Xen make easy" https://xen.crc.id.au/support/guides/install/. Here is a list of packages installed and verification that Xen is running. # lsb_release -a LSB Version: :core-4.1-amd64:core-4.1-noarch Distributor ID: RedHatEnterpriseServer Description: Red Hat Enterprise Linux Server release 7.5 (Maipo) Release: 7.5 Codename: Maipo # yum list | grep xen * kernel-xen: us3.mirror.crc.id.au * kernel-xen-extra: us3.mirror.crc.id.au kernel-xen.x86_64 4.14.94-6.el7xen @kernel-xen kernel-xen.x86_64 4.14.97-6.el7xen @kernel-xen kernel-xen-devel.x86_64 4.14.97-6.el7xen @kernel-xen kernel-xen-firmware.x86_64 4.14.97-6.el7xen @kernel-xen kernel-xen-headers.x86_64 4.14.97-6.el7xen @kernel-xen kernel-xen-release.noarch 1:7-13 @kernel-xen xen410.x86_64 4.10.2-7.el7 @kernel-xen xen410-devel.x86_64 4.10.2-7.el7 @kernel-xen xen410-hypervisor.x86_64 4.10.2-7.el7 @kernel-xen xen410-libs.x86_64 4.10.2-7.el7 @kernel-xen xen410-licenses.x86_64 4.10.2-7.el7 @kernel-xen xen410-ocaml.x86_64 4.10.2-7.el7 @kernel-xen xen410-runtime.x86_64 4.10.2-7.el7 @kernel-xen xen46-licenses.x86_64 4.6.6-16.el7 @kernel-xen # xl info host : nfv-sec-cn01-pa.labs.hpecorp.net release : 4.14.97-6.el7xen.x86_64 version : #2 SMP Fri Feb 1 00:33:52 AEDT 2019 machine : x86_64 nr_cpus : 32 max_cpu_id : 63 nr_nodes : 2 cores_per_socket : 8 threads_per_core : 2 cpu_mhz : 1995 hw_caps : bfebfbff:17bee3ff:2c100800:00000001:00000001:00000000:00000000:00000100 virt_caps : hvm hvm_directio total_memory : 131034 free_memory : 96587 sharing_freed_memory : 0 sharing_used_memory : 0 outstanding_claims : 0 free_cpus : 0 xen_major : 4 xen_minor : 10 xen_extra : .3-pre xen_version : 4.10.3-pre xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler : credit xen_pagesize : 4096 platform_params : virt_start=0xffff800000000000 xen_changeset : Tue Nov 20 15:45:04 2018 +0100 git:b6e203b-dirty xen_commandline : placeholder dom0_mem=32768M cpufreq=xen dom0_max_vcpus=8 dom0_vcpus_pin console=tty0 console=com1 com1=115200,8n1 cc_compiler : gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-28) cc_compile_by : mockbuild cc_compile_domain : cc_compile_date : Wed Nov 21 02:09:26 AEDT 2018 build_id : 2d53c8b15aaf737b0351e78ad863eb5a530e7df0 xend_config_format : 4 libvirt was installed as dependencies of openstack-nova-compute from yum. ================================================================================================================================================================================================== Package Arch Version Repository Size ================================================================================================================================================================================================== Installing: openstack-nova-compute noarch 1:17.0.9-1.el7 openstack-queens 7.9 k Installing for dependencies: OpenIPMI-modalias x86_64 2.0.23-2.el7 RedHat-7Server-x86_64-errata 16 k attr x86_64 2.4.46-13.el7 RedHat-7Server-x86_64-errata 66 k dosfstools x86_64 3.0.20-9.el7 RedHat-7.1Server-x86_64 101 k fuse x86_64 2.9.2-10.el7 RedHat-7Server-x86_64-errata 86 k gdisk x86_64 0.8.6-5.el7 RedHat-7.1Server-x86_64 187 k glusterfs-cli x86_64 3.8.4-53.el7 RedHat-7Server-x86_64-errata 176 k hivex x86_64 1.3.10-6.9.el7 RedHat-7Server-x86_64-errata 101 k ipmitool x86_64 1.8.18-7.el7 RedHat-7Server-x86_64-errata 441 k libguestfs x86_64 1:1.36.10-6.el7_5.2 RedHat-7Server-x86_64-errata 1.9 M libreport-filesystem x86_64 2.1.11-40.el7 RedHat-7Server-x86_64-errata 39 k libvirt-daemon x86_64 3.9.0-14.el7_5.6 RedHat-7Server-x86_64-errata 852 k libvirt-daemon-driver-interface x86_64 3.9.0-14.el7_5.6 RedHat-7Server-x86_64-errata 220 k libvirt-daemon-driver-network x86_64 3.9.0-14.el7_5.6 RedHat-7Server-x86_64-errata 389 k libvirt-daemon-driver-nodedev x86_64 3.9.0-14.el7_5.6 RedHat-7Server-x86_64-errata 221 k libvirt-daemon-driver-nwfilter x86_64 3.9.0-14.el7_5.6 RedHat-7Server-x86_64-errata 243 k libvirt-daemon-driver-qemu x86_64 3.9.0-14.el7_5.6 RedHat-7Server-x86_64-errata 714 k libvirt-daemon-driver-secret x86_64 3.9.0-14.el7_5.6 RedHat-7Server-x86_64-errata 210 k libvirt-daemon-driver-storage x86_64 3.9.0-14.el7_5.6 RedHat-7Server-x86_64-errata 173 k libvirt-daemon-driver-storage-core x86_64 3.9.0-14.el7_5.6 RedHat-7Server-x86_64-errata 405 k libvirt-daemon-driver-storage-disk x86_64 3.9.0-14.el7_5.6 RedHat-7Server-x86_64-errata 182 k libvirt-daemon-driver-storage-gluster x86_64 3.9.0-14.el7_5.6 RedHat-7Server-x86_64-errata 183 k libvirt-daemon-driver-storage-iscsi x86_64 3.9.0-14.el7_5.6 RedHat-7Server-x86_64-errata 179 k libvirt-daemon-driver-storage-logical x86_64 3.9.0-14.el7_5.6 RedHat-7Server-x86_64-errata 183 k libvirt-daemon-driver-storage-mpath x86_64 3.9.0-14.el7_5.6 RedHat-7Server-x86_64-errata 178 k libvirt-daemon-driver-storage-rbd x86_64 3.9.0-14.el7_5.6 RedHat-7Server-x86_64-errata 185 k libvirt-daemon-driver-storage-scsi x86_64 3.9.0-14.el7_5.6 RedHat-7Server-x86_64-errata 179 k libvirt-daemon-kvm x86_64 3.9.0-14.el7_5.6 RedHat-7Server-x86_64-errata 173 k libvirt-python x86_64 3.9.0-1.el7 RedHat-7Server-x86_64-errata 335 k mdadm x86_64 4.0-13.el7 RedHat-7Server-x86_64-errata 431 k mtools x86_64 4.0.18-5.el7 RedHat-7.1Server-x86_64 203 k perl-hivex x86_64 1.3.10-6.9.el7 RedHat-7Server-x86_64-errata 41 k python-libguestfs x86_64 1:1.36.10-6.el7_5.2 RedHat-7Server-x86_64-errata 203 k scrub x86_64 2.5.2-7.el7 RedHat-7Server-x86_64-errata 41 k squashfs-tools x86_64 4.3-0.21.gitaae0aff4.el7 RedHat-7.1Server-x86_64 101 k supermin5 x86_64 5.1.19-1.el7 RedHat-7Server-x86_64-errata 631 k syslinux x86_64 4.05-13.el7 RedHat-7Server-x86_64-errata 990 k syslinux-extlinux x86_64 4.05-13.el7 RedHat-7Server-x86_64-errata 363 k However, after installation, Nova complains "no connection driver available for xen:///". Also, virsh cannot connect Xen. /var/log/nova/nova-compute.log 2019-02-01 15:13:29.965 5091 INFO nova.service [-] Starting compute node (version 18.1.0-1.el7) 2019-02-01 15:13:30.023 5091 ERROR nova.virt.libvirt.host [-] Connection to libvirt failed: no connection driver available for xen:///: libvirtError: no connection driver available for xen:/// 2019-02-01 15:13:30.023 5091 ERROR nova.virt.libvirt.host Traceback (most recent call last): 2019-02-01 15:13:30.023 5091 ERROR nova.virt.libvirt.host File "/usr/lib/python2.7/site-packages/nova/virt/libvirt/host.py", line 460, in get_connection 2019-02-01 15:13:30.023 5091 ERROR nova.virt.libvirt.host conn = self._get_connection() 2019-02-01 15:13:30.023 5091 ERROR nova.virt.libvirt.host File "/usr/lib/python2.7/site-packages/nova/virt/libvirt/host.py", line 443, in _get_connection 2019-02-01 15:13:30.023 5091 ERROR nova.virt.libvirt.host {'msg': ex}) 2019-02-01 15:13:30.023 5091 ERROR nova.virt.libvirt.host File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 220, in __exit__ 2019-02-01 15:13:30.023 5091 ERROR nova.virt.libvirt.host self.force_reraise() 2019-02-01 15:13:30.023 5091 ERROR nova.virt.libvirt.host File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 196, in force_reraise 2019-02-01 15:13:30.023 5091 ERROR nova.virt.libvirt.host six.reraise(self.type_, self.value, self.tb) 2019-02-01 15:13:30.023 5091 ERROR nova.virt.libvirt.host File "/usr/lib/python2.7/site-packages/nova/virt/libvirt/host.py", line 432, in _get_connection 2019-02-01 15:13:30.023 5091 ERROR nova.virt.libvirt.host self._wrapped_conn = self._get_new_connection() 2019-02-01 15:13:30.023 5091 ERROR nova.virt.libvirt.host File "/usr/lib/python2.7/site-packages/nova/virt/libvirt/host.py", line 386, in _get_new_connection 2019-02-01 15:13:30.023 5091 ERROR nova.virt.libvirt.host wrapped_conn = self._connect(self._uri, self._read_only) 2019-02-01 15:13:30.023 5091 ERROR nova.virt.libvirt.host File "/usr/lib/python2.7/site-packages/nova/virt/libvirt/host.py", line 242, in _connect 2019-02-01 15:13:30.023 5091 ERROR nova.virt.libvirt.host libvirt.openAuth, uri, auth, flags) 2019-02-01 15:13:30.023 5091 ERROR nova.virt.libvirt.host File "/usr/lib/python2.7/site-packages/eventlet/tpool.py", line 148, in proxy_call 2019-02-01 15:13:30.023 5091 ERROR nova.virt.libvirt.host rv = execute(f, *args, **kwargs) 2019-02-01 15:13:30.023 5091 ERROR nova.virt.libvirt.host File "/usr/lib/python2.7/site-packages/eventlet/tpool.py", line 129, in execute 2019-02-01 15:13:30.023 5091 ERROR nova.virt.libvirt.host six.reraise(c, e, tb) 2019-02-01 15:13:30.023 5091 ERROR nova.virt.libvirt.host File "/usr/lib/python2.7/site-packages/eventlet/tpool.py", line 83, in tworker 2019-02-01 15:13:30.023 5091 ERROR nova.virt.libvirt.host rv = meth(*args, **kwargs) 2019-02-01 15:13:30.023 5091 ERROR nova.virt.libvirt.host File "/usr/lib64/python2.7/site-packages/libvirt.py", line 105, in openAuth 2019-02-01 15:13:30.023 5091 ERROR nova.virt.libvirt.host if ret is None:raise libvirtError('virConnectOpenAuth() failed') 2019-02-01 15:13:30.023 5091 ERROR nova.virt.libvirt.host libvirtError: no connection driver available for xen:/// # virsh -c xen:/// list error: failed to connect to the hypervisor error: no connection driver available for xen:/// Then I check the connection drivers of libvirt. It seems the daemon driver for xen is missing. # ls -l /usr/lib64/libvirt/connection-driver/ total 2664 -rwxr-xr-x 1 root root 115976 Jun 5 2018 libvirt_driver_interface.so -rwxr-xr-x 1 root root 292008 Jun 5 2018 libvirt_driver_lxc.so -rwxr-xr-x 1 root root 169424 Jun 5 2018 libvirt_driver_network.so -rwxr-xr-x 1 root root 119720 Jun 5 2018 libvirt_driver_nodedev.so -rwxr-xr-x 1 root root 174216 Jun 5 2018 libvirt_driver_nwfilter.so -rwxr-xr-x 1 root root 1545344 Jun 5 2018 libvirt_driver_qemu.so -rwxr-xr-x 1 root root 86616 Jun 5 2018 libvirt_driver_secret.so -rwxr-xr-x 1 root root 202568 Jun 5 2018 libvirt_driver_storage.so But I couldn't find the xen driver (libvirt-daemon-driver-xen) from yum. I do find it driver on some websites ( http://rpmfind.net/linux/rpm2html/search.php?query=libvirt-daemon-driver-xen) but I am not sure which is the right version to choose. I also found this email https://www.spinics.net/lists/centos-virt/msg05163.html. Then I decided to compile libvirt from source code. So I checked out the source code from github and tried to configure and compile it. However, from the output of ./autogen.sh --system, I don't find driver for xen is enabled. Actually, xen is not listed as driver in the output. configure: configure: Configuration summary configure: ===================== configure: configure: Drivers configure: configure: QEMU: yes configure: OpenVZ: yes configure: VMware: yes configure: VBox: yes configure: XenAPI: no configure: libxl: yes configure: LXC: yes configure: PHYP: no configure: ESX: no configure: Hyper-V: no configure: vz: no configure: Bhyve: no configure: Test: yes configure: Remote: yes configure: Network: yes configure: Libvirtd: yes configure: Interface: yes configure: configure: Storage Drivers configure: configure: Dir: yes configure: FS: yes configure: NetFS: yes configure: LVM: yes configure: iSCSI: yes configure: iscsi-direct: no configure: SCSI: yes configure: mpath: yes configure: Disk: no configure: RBD: no configure: Sheepdog: no configure: Gluster: no configure: ZFS: no configure: Virtuozzo storage: no configure: configure: Security Drivers configure: configure: SELinux: yes configure: AppArmor: no configure: configure: Driver Loadable Modules configure: configure: driver_modules: yes (CFLAGS='' LIBS='-ldl') configure: configure: Libraries configure: configure: acl: no configure: apparmor: no configure: attr: no configure: audit: no configure: avahi: no configure: bash_completion: no configure: blkid: no configure: capng: no configure: curl: no configure: dbus: no configure: dlopen: yes (CFLAGS='' LIBS='-ldl') configure: firewalld: no configure: firewalld-zone: no configure: fuse: no configure: glusterfs: no configure: gnutls: yes (CFLAGS='-I/usr/include/p11-kit-1 ' LIBS='-lgnutls ') configure: hal: no configure: libiscsi: no configure: libnl: yes (CFLAGS=' ' LIBS='-lnl ') configure: libpcap: no configure: libssh: no configure: libxl: yes (CFLAGS=' -DLIBXL_API_VERSION=0x040500' LIBS='-lxenlight -lxlutil -lxenstore -lxentoollog') configure: libxml: yes (CFLAGS='-I/usr/include/libxml2 ' LIBS='-lxml2 ') configure: macvtap: yes (CFLAGS='' LIBS='') configure: netcf: no configure: NLS: yes configure: nss: yes configure: numactl: no configure: openwsman: no configure: pciaccess: yes (CFLAGS=' ' LIBS='-lpciaccess ') configure: pm_utils: yes (CFLAGS='' LIBS='') configure: polkit: no configure: rbd: no configure: readline: no configure: sanlock: no configure: sasl: yes (CFLAGS='' LIBS='-lsasl2') configure: selinux: yes (CFLAGS='' LIBS='-lselinux') configure: ssh2: no configure: udev: yes (CFLAGS=' ' LIBS='-ludev ') configure: virtualport: yes (CFLAGS='' LIBS='') configure: xdr: yes (CFLAGS='' LIBS='') configure: xenapi: no configure: yajl: yes (CFLAGS='' LIBS='-lyajl') configure: configure: Windows configure: configure: Cygwin: no configure: MinGW: no configure: MSVC: no configure: windres: no configure: configure: Test suite configure: configure: Coverage: no configure: Alloc OOM: no configure: configure: Miscellaneous configure: configure: Debug: yes configure: Use -Werror: yes configure: Warning Flags: -fno-common -W -Waddress -Waggressive-loop-optimizations -Wall -Wattributes -Wbad-function-cast -Wbuiltin-macro-redefined -Wcast-align -Wchar-subscripts -Wclobbered -Wcomment -Wcomments -Wcoverage-mismatch -Wcpp -Wdeprecated-declarations -Wdiv-by-zero -Wdouble-promotion -Wempty-body -Wendif-labels -Wextra -Wformat-contains-nul -Wformat-extra-args -Wformat-security -Wformat-y2k -Wformat-zero-length -Wfree-nonheap-object -Wignored-qualifiers -Wimplicit -Wimplicit-function-declaration -Wimplicit-int -Winit-self -Winline -Wint-to-pointer-cast -Winvalid-memory-model -Winvalid-pch -Wlogical-op -Wmain -Wmaybe-uninitialized -Wmissing-braces -Wmissing-declarations -Wmissing-field-initializers -Wmissing-include-dirs -Wmissing-parameter-type -Wmissing-prototypes -Wmultichar -Wnarrowing -Wnested-externs -Wnonnull -Wold-style-declaration -Wold-style-definition -Woverflow -Woverride-init -Wpacked-bitfield-compat -Wparentheses -Wpointer-arith -Wpointer-sign -Wpointer-to-int-cast -Wpragmas -Wpsabi -Wreturn-local-addr -Wreturn-type -Wsequence-point -Wshadow -Wsizeof-pointer-memaccess -Wstrict-aliasing -Wstrict-prototypes -Wsuggest-attribute=const -Wsuggest-attribute=format -Wsuggest-attribute=noreturn -Wsuggest-attribute=pure -Wswitch -Wsync-nand -Wtrampolines -Wtrigraphs -Wtype-limits -Wuninitialized -Wunknown-pragmas -Wunused -Wunused-but-set-parameter -Wunused-but-set-variable -Wunused-function -Wunused-label -Wunused-local-typedefs -Wunused-parameter -Wunused-result -Wunused-value -Wunused-variable -Wvarargs -Wvariadic-macros -Wvector-operation-performance -Wvolatile-register-var -Wwrite-strings -Wnormalized=nfc -Wno-sign-compare -Wjump-misses-init -Wswitch-enum -Wno-format-nonliteral -fstack-protector-strong -fexceptions -fasynchronous-unwind-tables -fipa-pure-const -Wno-suggest-attribute=pure -Wno-suggest-attribute=const -Werror configure: DTrace: no configure: numad: no configure: Init script: systemd configure: Char device locks: /var/lock configure: Default Editor: vi configure: Loader/NVRAM: configure: virt-login-shell: yes configure: virt-host-validate: yes configure: TLS priority: NORMAL configure: configure: Developer Tools configure: configure: wireshark_dissector: no configure: configure: Privileges configure: configure: QEMU: root:root configure: My question is how should I install the libvirt-daemon-driver-xen driver and make Nova work with Xen? Thanks a lot in advance! Best regards, Lianjie Cao

3 2

[libvirt-users] Unable to start libvirt systemd service
by Sharath Kurudi 04 Feb '19

04 Feb '19

Hi all, I am using the libvirt 4.9 version. I get the following error when I try to run the command virsh list after the system comes up virsh list error: failed to connect to the hypervisor error: Failed to connect socket to '/var/run/libvirt/libvirt-sock': No such file or directory When I run the command ps -ef | grep libvirtd, to find whether the libvirtd process is running. I get the following message. ps -ef | grep libvirtd root 418 1 0 06:33 ? 00:00:00 /usr/sbin/libvirtd --daemon --config /etc/libvirt/libvirtd.conf root 420 1 0 06:33 ? 00:00:00 /usr/sbin/libvirtd --daemon --config /etc/libvirt/libvirtd.conf After sometime, I see that the virsh list command goes through and the command ps -ef | grep libvirtd, gives the following putput ps -ef | grep libvirtd root 420 1 0 06:33 ? 00:00:00 /usr/sbin/libvirtd --daemon --config /etc/libvirt/libvirtd.conf root 610 227 0 06:34 ttyS0 00:00:00 grep libvirtd root@draco:~# virsh list Id Name State -------------------- Following are the logs of journalctl -xe | grep libvirtd -- Unit libvirtd.service has begun starting up. Feb 04 06:32:01 draco libvirtd[388]: 2019-02-04 06:32:01.298+0000: 388: info : libvirt version: 4.9.0 Feb 04 06:32:01 draco libvirtd[388]: 2019-02-04 06:32:01.298+0000: 388: info : hostname: draco Feb 04 06:32:01 draco libvirtd[388]: 2019-02-04 06:32:01.298+0000: 388: warning : virGetHostnameImpl:714 : getaddrinfo failed for 'draco': Temporary failure in name resolution Feb 04 06:33:31 draco systemd[1]: libvirtd.service: Start operation timed out. Terminating. Feb 04 06:33:31 draco systemd[1]: libvirtd.service: Failed with result 'timeout'. -- Subject: Unit libvirtd.service has failed -- Unit libvirtd.service has failed. Feb 04 06:33:31 draco systemd[1]: libvirtd.service: Service hold-off time over, scheduling restart. Feb 04 06:33:31 draco systemd[1]: libvirtd.service: Scheduled restart job, restart counter is at 4. -- Automatic restarting of the unit libvirtd.service has been scheduled, as the result for -- Subject: Unit libvirtd.service has finished shutting down -- Unit libvirtd.service has finished shutting down. -- Subject: Unit libvirtd.service has begun start-up -- Unit libvirtd.service has begun starting up. Feb 04 06:33:31 draco libvirtd[418]: 2019-02-04 06:33:31.799+0000: 418: info : libvirt version: 4.9.0 Feb 04 06:33:31 draco libvirtd[418]: 2019-02-04 06:33:31.799+0000: 418: info : hostname: draco [4 draco libvirtd[418]: 2019-02-04 06:33:31.799+0000: 418: warning : virGetHostnameImpl:714 : getaddrn Feb 04 06:33:31 draco libvirtd[418]: 2019-02-04 06:33:31.799+0000: 418: warning : virGetHostnameImpl:714 : getaddrinfo failed for 'draco': Temporary failure in name resolution -- Subject: Unit libvirtd.service has finished start-up -- Unit libvirtd.service has finished starting up. Feb 04 06:34:41 draco libvirtd[420]: 482: info : libvirt version: 4.9.0 Feb 04 06:34:41 draco libvirtd[420]: 482: info : hostname: draco Feb 04 06:34:41 draco libvirtd[420]: 482: error : virGetUserID:1041 : invalid argument: Failed to parse user 'tss' Feb 04 06:34:41 draco libvirtd[420]: 482: error : virGetGroupID:1124 : invalid argument: Failed to parse group 'tss' - msg 68/68 100% It is found that the libvirt systemd service times out, and for some unkonwn reason the previous libvitrd process is not killed. I dont see any errors in /var/log/messages or /var/log/syslog. Could anyone please help? Thanks Sharath

1 0

[libvirt-users] Hook problem
by David Gilmour 30 Jan '19

30 Jan '19

I am trying to use /etc/libvirt/hooks/qemu to control the startup of several guests with interdependencies. The goal is to delay the start of guest B until the DNS server on guest A is running. To accomplish this, I wrote a qemu hook script that detects the normal startup of guest B and start a second script in the background to wait until the preconditions to start B are fulfilled, then start B using a call to the virsh command. For this strategy to work, it must handle the case where libvirt has chosen guest B as the first guest to attempt to start. (Although renaming the symlinks in /etc/libvirt/qemu/autostart to force starting the guests in a particular order might work, I do not want to rely on this undocumented behavior). In the case where libvirt happens to attempt to start guest B before it starts guest A, the hook script needs to somehow tell libvirt to skip guest B and go on to starting the next guest. Otherwise a deadlock would result as libvirt waited for B to start, but B was waiting for A to start. I have tried to handle this by returning failure from the hook script for the initial attempt to start B once the background script has been started to implement the DNS check and eventually the delayed start of B. Unfortunately, I cannot find a way to force libvirt to continue until the background script exits. No combination of background execution, nohup, disown, setsid -f, or at seems to detach the process sufficiently to "fool" libvirt into acting on the "exit 1" line in the qemu script and proceed on to start other guests. As a result, the dependency of B on A deadlocks, and neither guest ever starts. Can someone please either find an error in my approach or propose a different strategy to implement this customized dependency of the startup of one guest on another? Thanks - ====== Here is my qemu script: #!/bin/bash if [[ "$2" == 'start' ]]; then echo "$0: Starting $1..." |& logger if [[ "$1" == 'B' ]]; then # The next line is where the background script is invoked /bin/bash /usr/local/bin/startB & # These also don't work: # (/bin/bash /usr/local/bin/startB) & ; disown # setsid -f (/bin/bash /usr/local/bin/startB) & ; disown # Unfortunately, the exit in the following line doesn't force libvirt to move on to the next guest to start until the background command has itself exited exit 1; fi fi Here is the startB script, including a call to a program named in the $dnssuccess variable that does the testing of DNS availability on guest A: #!/bin/bash until $dnssuccess do echo "$0: Delaying start of guest B 10 seconds" |& logger sleep 10; done # It's now OK to start guest echo "$0: Now starting guest B" |& logger virsh start B; =====

2 1

[libvirt-users] Keyboard problems with VNC access
by Nick Howitt 30 Jan '19

30 Jan '19

Hi, I am pretty new to libvirt, but have succeeded in setting up two VM's, Windows 10 and ClearOS (a Centos derivative) and they both have the same issue. I have installed both of them with a UK English keyboard, but the host machine is remote and in the US with a US locale. When I access either through VNC (I've tried TightVNC and VNC-Viewer), a number of my keys don't map correctly. As an example the \ key comes up with a #, and the # key comes up with a 3 (as does the 3 key). Other keys are the standard US type of mapping, but the £ (above 3) comes up blank and the $ (above 4) comes up with $ which, I think is the UK setting and not the US setting. At this point I am thoroughly confused. Does anyone have any ideas? Thanks, Nick

2 2

[libvirt-users] Workaround for "internal snapshots of a VM with pflash based firmware are not supported" problem?
by Andreas Tscharner 29 Jan '19

29 Jan '19

Hello World, We were hit by the "internal snapshots of a VM with pflash based firmware are not supported" problem. Is there a workaround for it (for which revert works)? Another format perhaps? Our use case: We have an image (Win10, UEFI) with some software installed. This image is used by Jenkins to execute some tests. After the tests, the image should be reverted to the original state. Jenkins uses the libvirt plugin to connect to and start/stop and revert the virtual machines. The images are in qcow2 format. We've usually created a snapshot of the base state using "virsh snapshot-create-as" on the host system, but this is no longer possible. What is the recommended workaround? TIA and best regards Andreas -- Andreas Tscharner sternenfeuer(a)gmail.com Gordon's Law: If you think you have the solution, the question was poorly phrased.

1 0

[libvirt-users] unable to list virtualbox domain remotely
by François Marsy 25 Jan '19

25 Jan '19

Hi dear all, I have the following issue : I have a libvirtd intstalled on an ubuntu desktop. The libvirtd is listening on port 16509 (options listen_tls = 0 and listen_tcp = 1) On the desktop I have a virtualbox installed with a running VM : "styx32-dry-run3" I want to control my VM remotely by using libvirt. I performed following tests : 1)Local virsh running fine : virsh -c vbox:///session list Id Name State ---------------------------------------------------- 2 styx32-dry-run3 running 2)Using the tcp port is showing an empty list: virsh -c vbox+tcp://127.0.0.1:16509/session list Id Name State ---------------------------------------------------- 3)net-list command works virsh -c vbox+tcp://127.0.0.1:16509/session net-list Name State Autostart Persistent ---------------------------------------------------------- vboxnet0 active no autostart yes Can any of you help me please, I really don't understand why my VM is not showing up in the 2 ) list .. and I really don't know where to look at :-( Kind regards Francois

1 0

[libvirt-users] stuck in pxe loop from uefi + tianocore/ovmf
by jsl6uy js16uy 24 Jan '19

24 Jan '19

Hello all, hope all is well Was wondering if I'm doing something wrong/missing something. I have pxe+tftp+uefi working between 2 vms. However after the build is done and I reboot, I still come up to pxe b/c tianocore always starts, from what I've seen, with trying PXE first. Great for initial builds :) but I would like to it stop after. In the xml I am pointing to the disk to boot first. if I virsh destory and run qemu directly on the qcow image, the vm comes up as expected and boots into the OS I have tried removing the nvram under /var/lib/libvirt/qemu/nvram/virtmachine. But the vm boots up and starts looking for pxe again. If I let that timeout, then type exit and select continue in the tianocore boot firmware, I just loop back into trying pxe over ipv4 etc I tried <rom bar='off'/> on the e1000 and that does work to stop pxe. Then I get to the uefi shell quickly, but all I see at that point is 2 BLK maps pointing to floppy 1 and 2. I see nothing when I try to manually add a new boot option. any help/wisdom would be appreciated. libvirtd (libvirt) 4.9.0 qemu command: sudo qemu-system-x86_64 -m 2048 -L /usr/share/ovmf/x64/ -bios OVMF_CODE.fd -drive file=/images/rdhcli02,format=qcow2,cache=writeback,if=virtio -device virtio-net,netdev=net10,mac=52:54:00:11:22:33 -netdev tap,id=net10,ifname=rdhcli02,script=no,downscript=no Is there a way to address this?

1 1

[libvirt-users] Problems with incoming multicasts
by David Gra 24 Jan '19

24 Jan '19

Hello I have realized a problem with incomming multicast packages to a VM. My Setup is: 1 Host with 1 VM. On the external Network (Host: eth0), there ist a Multicast Stream. The packages are visible at the hosts eth0. The Guest is connected via macvtap to the eth0 from the Host. Host and Guest ist CentOS 7.6 in Future it should be RedHat 7.6. The guest is connected via macvtap0 to eth0. If i performe tcpdump on eth0 of the host, i can see teh packages. If i performe tcpdump on macvtap0 on the host, i can see the packages anyway. If i performe tcpdump on the guests eth0, i can't see the multicast packages. Normal unicast communications to the external systems are still working. All my network is only IPv4. Is there a limitation to multicast on libvirt? Best regards and thank's a lot for your help!

1 0

[libvirt-users] LXC guest to have/make a device node (FUSE)
by lejeczek 22 Jan '19

22 Jan '19

hi guys With lxc container under libvirt control - how can guest create device nodes? I'm specifically looking for FUSE device. Is it possible somehow to get it to the guest(passthrough?) or allow the guest to create dev node? many thanks, L.

3 2

[libvirt-users] Slow ssh
by Pascal Legrand 22 Jan '19

22 Jan '19

Hello, i'm using libvirt/kvm/qemu on a stable Debian Linux KVM 4.9.0-6-amd64 . qemu-kvm : 1:2.8+dfsg-6+deb9u5 libvirt-daemon : 3.0.0-4+deb9u3 libvirt-clients : 3.0.0-4+deb9u3 virt-manager : 1:1.4.0-5 virt-viewer : 5.0-1 virtinst : 1:1.4.0-5 My guests are made with this kind of command line : virt-install --connect=qemu:///system --name=debian --ram=2048 --disk /home/vm/debian.qcow2,size=10,format=qcow2 --network=bridge:bridge-0-1,model=virtio --network=bridge:bridge-0-2,model=virtio --network=bridge:bridge-0-3,model=virtio --accelerate --noautoconsole --vnc --vnclisten=0.0.0.0 --keymap=fr --cdrom=/home/iso/debian-6.0.1a-i386-netinst.iso --os-type=linux --os-variant=debiansqueeze --hvm Since a long time ago now (may be a Debian upgrade) i noticed that ssh session from my personal PC to guests are very slow (connection and behaviour) My ssh configuration is the same on all my real/vm servers. The problem occure only on my guest. Have you got a solution or an idea to solve this problem ? Thanks for your help -- Pascal

2 1

[libvirt-users] *-sock created as part of normal daemon startup?
by Keith Bierman 18 Jan '19

18 Jan '19

As noted in another thread, I've not had success with homebrew/Mac OSX's libvirt install. On Ubuntu and CentOS virtual machines, installing "libvirt-daemon" and friends, I end up with various "-sock" files in /var/run/libvirt. This seems sensible. After installing on MacOS X with homebrew ls /usr/local/var/run/libvirt hostdevmgr lockd qemu storage so perhaps it isn't surprising that virsh -c vbox:/// fails. Am I right in believing that the lack of -sock files means that the "brew services start libvirt" is either misconfigured or otherwise failing?

1 0

[libvirt-users] virt-install and IOThreads
by Igor Gnatenko 18 Jan '19

18 Jan '19

Hello, is there any way of specifying iothreads via virt-install command? I've tried appending ",iothread='1'" but that didn't work. Thanks in advance! -- -Igor Gnatenko

3 3

[libvirt-users] VM running with storage image file deleted
by Roosen, Nicolas 17 Jan '19

17 Jan '19

Hello, I have a strange issue I'd like to have some insights on. We have 2 running VM, the storage pool is over NFS. Unfortunately, the backend storage folder has been deleted (so the image file in it as well, obviously) ... Yet, the 2 VM are still up and running, with their root filesystem being mounted "rw". - how does that work? I was expecting that with the file image being deleted, the VM would not work at all. - since the VM is still running, is there a way to create a snapshot of it in order to re-create the image file on another storage pool ? I'm currently exploring "virsh snapshot-create-as ...", but if access to the image file is needed, it will fail. Thanks. -- Nicolas

4 5

[libvirt-users] cpu0 unhandled rdmsr:
by Christophe Dumont 16 Jan '19

16 Jan '19

Hello, Do you know what this means : kvm: 2918: cpu0 unhandled rdmsr: 0x345 kvm: 2918: cpu0 unhandled rdmsr: 0x1c9 kvm: 2918: cpu0 unhandled rdmsr: 0x1a6 kvm: 2918: cpu0 unhandled rdmsr: 0x1a7 kvm: 2918: cpu0 unhandled rdmsr: 0x3f6 tap110i0: no IPv6 routers present kvm: 2952: cpu0 unhandled rdmsr: 0x345 kvm: 2952: cpu0 unhandled rdmsr: 0x1c9 kvm: 2952: cpu0 unhandled rdmsr: 0x1a6 kvm: 2952: cpu0 unhandled rdmsr: 0x1a7 kvm: 2952: cpu0 unhandled rdmsr: 0x3f6 I think it causes instability, we had to reboot the server twice and a backup script still fails. Thx -- Christophe Dumont 4, Passage du Lycée 38000 Grenoble 0633475733

2 2

[libvirt-users] forcing order of vnet creation
by daggs 13 Jan '19

13 Jan '19

dummy0 Link encap:Ethernet HWaddr C6:C8:2A:04:FD:23 BROADCAST NOARP MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:22048 errors:0 dropped:0 overruns:0 frame:0 TX packets:22048 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1068960 (1.0 MiB) TX bytes:1068960 (1.0 MiB) Greetings, I have a host that has two vms, one is a router that all the machines on the network connect to it and that other a test virtual machine. the router vm is connected to the host using a virt net, the test virtual machine is connected to the router via a virtual switch. my /etc/network/interfaces defines vnet1 as dhcp by assuming that it is the vnet for the host (it was seen multiple times). yesterday I came back from a vacation, booted the system and didn't got any ip to the host, the rest of the machines on the network got ip. at the end, the issue was that vnet1 was the virtual switch rather than the host's virtual nic. is there a way for "lock" the vnics config so they won't change? the host is Debian 9.6, the output of ifconfig -a is below (the "faulty" scenario) virtsw0 Link encap:Ethernet HWaddr 52:54:00:6B:1B:92 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:92908 errors:0 dropped:0 overruns:0 frame:0 TX packets:18 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:13257095 (12.6 MiB) TX bytes:756 (756.0 B) virtsw0-nic Link encap:Ethernet HWaddr 52:54:00:6B:1B:92 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) vnet0 Link encap:Ethernet HWaddr FE:54:00:8B:66:C1 inet addr:10.0.0.3 Bcast:10.0.0.255 Mask:255.255.255.0 inet6 addr: fe80::fc54:ff:fe8b:66c1/64 Scope:Link inet6 addr: fdab:9802:eb52:0:fc54:ff:fe8b:66c1/64 Scope:Global UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:528665 errors:0 dropped:0 overruns:0 frame:0 TX packets:752585 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:44311555 (42.2 MiB) TX bytes:2165654771 (2.0 GiB) vnet1 Link encap:Ethernet HWaddr FE:54:00:A7:79:6B inet6 addr: fe80::fc54:ff:fea7:796b/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:92983 errors:0 dropped:0 overruns:0 frame:0 TX packets:81658 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:14566221 (13.8 MiB) TX bytes:4249914 (4.0 MiB) vnet2 Link encap:Ethernet HWaddr FE:54:00:54:78:BE inet6 addr: fe80::fc54:ff:fe54:78be/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:15 errors:0 dropped:0 overruns:0 frame:0 TX packets:257 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1962 (1.9 KiB) TX bytes:42261 (41.2 KiB) thanks, Dagg.

1 1

[libvirt-users] openVswitch
by lejeczek 09 Jan '19

09 Jan '19

hi guys I'm trying a typical, I'd presume, setup: two libvirt hosts with one lxc guest each. boxA: $ ovs-vsctl show 1a6a2e4f-11f3-48df-becd-03b59d00a1fb Bridge "ovsbr0" Port nm-team trunks: [55] Interface nm-team Port "vnet12" trunks: [55] Interface "vnet12" Port "ovsbr0" Interface "ovsbr0" type: internal ovs_version: "2.0.0" boxB: $ ovs-vsctl show 05ffa96c-a961-41e7-9f8a-74dbe214153a Bridge "ovsbr0" Port "vnet41" trunks: [55] Interface "vnet41" Port nm-team trunks: [55] Interface nm-team Port "ovsbr0" Interface "ovsbr0" type: internal ovs_version: "2.0.0" In libvirt openvswitch network defines & starts okey, both guests start okey, yet guests cannot ping one another. Ifaces in guests seem to instantiate okey cause each guest can ping its own IP (on libvirt openvswitch net) You can see that on each host openvswitch port is nm-team, which I presume must be pretty "regular" situation. Only thing I'm not sure is that the same nm-team (on each host) is also a port to NM's bridge. (which works fine, these bridge ifaces on both hosts ping each other no problems). Which bits I get wrong or am missing? many thanks, L.

1 0

[libvirt-users] Golang libvirt bindings problem
by Branimir Pejakovic 09 Jan '19

09 Jan '19

Hello everybody! First, allow me to wish you all a Happy New year! I have a problem with a small app that I wrote in Go and which uses libvirt go bindings. Actually, the problem exists only when I want to compile the code statically. Basically, when CGO_ENABLED=0 is exported, go (running go test, go run, go build) complains: undefined: libvirt.NewConnect When I try to compile the source dynamically (running the same go <command> commands) the app works/checks out as expected and works without any problem. I tried this on: - CentOS 7.6 (go version 1.11.2) - Ubuntu 18.04 LTS (go version 1.10.4) Both systems - as advised on project's github pages/godoc.org - have libvirt-dev package installed. Also, the libvirt module is imported as advised: libvirt "github.com/libvirt/libvirt-go" GOPATH is set to /home/$USER/go I downloaded the package via go get; go get -v -u github.com/libvirt/libvirt-go. Please if somebody encountered this before, could you give me a hint if possible in order to solve this? Thank you very much in advance! Regards, Branimir

2 1

[libvirt-users] virsh on mac os X
by Keith Bierman 08 Jan '19

08 Jan '19

Mac OS X 10.14.2 VirtualBox 5.2.22 and 6.0.0 libvirt installed via homebrew virsh -V Virsh command line tool of libvirt 4.10.0 See web site at https://libvirt.org/ Compiled with support for: Hypervisors: QEMU/KVM VMware VirtualBox ESX Test Networking: Remote Bridging Storage: Dir Miscellaneous: Daemon Secrets Debug brew services start libvirt virsh -c vbox:///session list error: failed to connect to the hypervisor error: internal error: unable to initialize VirtualBox driver API Unless there's a known issue with Mojave that's escaped me, surely I've done something clueless .. pointers to the FM or otherwise greatly appreciated. Keith Bierman khbkhb(a)gmail.com

1 4

[libvirt-users] xen and libvirt
by Christoph 07 Jan '19

07 Jan '19

Hi Does someone know how it is possible these parameters: e820_host max_grant_frames to set with libvirt xml config? I use them with xl config but I want to change to libvirt config/tools. (with libvirt 4.10 it is possible to start pvh domains) -- ------ Greetz

2 3

[libvirt-users] script called from qemu hook freezes.
by daggs 07 Jan '19

07 Jan '19

Greetings, I'm executing an external script when the qemu hook is called with start or release, the script is rather simple, upon start it iterates over the output of lsusb -t and for each device, it looks if it should be added to the vm we started, if so, it attaches it to the vm as follows: virsh --connect qemu:///system "${cmd}" "${domain}" /dev/stdin << END <hostdev mode='subsystem' type='usb'> <source> <address bus='${busnum}' device='${devnum}' /> </source> </hostdev> END where cmd is attach-device, domain is the vm's name, busnum and devnum come from the output of the lsusb -t. my issue is that upon the first attach attempt, the cmd hangs, I need to kill it and after than I cannot preform any virsh cmd, I must restart the host. if I try to execute the same cmd after the vm is up, it works great. why the attach process gets stuck? do I need to execute it under different stage? thanks, Dagg.

3 6

[libvirt-users] macvtap and tagged VLANs to the VM
by Marc Haber 04 Jan '19

04 Jan '19

Hi, I would like to run a network firewall as a VM on a KVM host. There are ~ 25 VLANs delivered to the KVM host on three dedicated links, no LACP or other things. I have the VLANs 100-180 on the host's enp1s0, the VLANs 200-280 on the host's enp2s0 and the VLANs 300-380 on the host's enp3s0. To save myself from configuring all VLANs on the KVM host, I'd like to hand the entire ethernet link to the VM and to have the VLAN interfaces there. Using classical Linux bridges (brctl), things work fine. They don't when I try macvlan: On the host: 4: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000 link/ether 00:0d:b9:34:2a:fe brd ff:ff:ff:ff:ff:ff promiscuity 1 addrgenmode eui64 numtxqueues 1 numrxqueues 1 gso_max_size 65536 gso_max_segs 65535 5: unt382@enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 00:0d:b9:34:2a:fe brd ff:ff:ff:ff:ff:ff promiscuity 0 vlan protocol 802.1Q id 382 <REORDER_HDR> addrgenmode eui64 numtxqueues 1 numrxqueues 1 gso_max_size 65536 gso_max_segs 65535 15: macvtap3@enp3s0: <BROADCAST,MULTICAST,ALLMULTI,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 500 link/ether 52:54:00:bf:bb:ab brd ff:ff:ff:ff:ff:ff promiscuity 0 macvtap mode bridge addrgenmode eui64 numtxqueues 1 numrxqueues 1 gso_max_size 65536 gso_max_segs 65535 4: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 00:0d:b9:34:2a:fe brd ff:ff:ff:ff:ff:ff inet6 fe80::20d:b9ff:fe34:2afe/64 scope link valid_lft forever preferred_lft forever 5: unt382@enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 00:0d:b9:34:2a:fe brd ff:ff:ff:ff:ff:ff inet6 fe80::20d:b9ff:fe34:2afe/64 scope link valid_lft forever preferred_lft forever 15: macvtap3@enp3s0: <BROADCAST,MULTICAST,ALLMULTI,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 500 link/ether 52:54:00:bf:bb:ab brd ff:ff:ff:ff:ff:ff inet6 fe80::5054:ff:febf:bbab/64 scope link valid_lft forever preferred_lft forever In the XML: <interface type='direct'> <mac address='52:54:00:bf:bb:ab'/> <source dev='enp3s0' mode='bridge'/> <target dev='macvtap3'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> And in the VM: root@grml ~ # ip -d link show 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 promiscuity 0 addrgenmode eui64 numtxqueues 1 numrxqueues 1 gso_max_size 65536 gso_max_segs 65535 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000 link/ether 52:54:00:bf:bb:ab brd ff:ff:ff:ff:ff:ff promiscuity 0 addrgenmode eui64 numtxqueues 1 numrxqueues 1 gso_max_size 65536 gso_max_segs 65535 3: vlan0@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 52:54:00:bf:bb:ab brd ff:ff:ff:ff:ff:ff promiscuity 0 vlan protocol 802.1Q id 382 <REORDER_HDR> addrgenmode eui64 numtxqueues 1 numrxqueues 1 gso_max_size 65536 gso_max_segs 65535 root@grml ~ # ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1 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:bf:bb:ab brd ff:ff:ff:ff:ff:ff inet6 fe80::5054:ff:febf:bbab/64 scope link valid_lft forever preferred_lft forever 3: vlan0@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 52:54:00:bf:bb:ab brd ff:ff:ff:ff:ff:ff inet 192.168.252.220/24 brd 192.168.252.255 scope global vlan0 valid_lft forever preferred_lft forever inet6 fe80::5054:ff:febf:bbab/64 scope link valid_lft forever preferred_lft forever root@grml ~ # I then ping from the VM to 192.168.252.241, which is a differnt host on the network, neither the VM host the VM is running on nor another VM on the same host. That should rule out the connectivity issues that a macvtap interface has, right? On the VM, I see ARP requests going out, but no answers come in. On the pinged host, I see: 22:50:23.881163 52:54:00:bf:bb:ab > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 60: Request who-has 192.168.252.241 tell 192.168.252.220, length 46 22:50:23.881242 52:54:00:95:df:a6 > 52:54:00:bf:bb:ab, ethertype ARP (0x0806), length 42: Reply 192.168.252.241 is-at 52:54:00:95:df:a6, length 28 So, the packets going out from my VM are correctly delivered to the target, the target replies, but the replies never make it back to the VM. Do I see correctly that tcpdump on the VM host won't give accurate readings since macvtap will divert the frame before tcpdump will see it? On the other hand, a VM directly configured to the host's unt382 interface works fine: <interface type='direct'> <mac address='52:54:00:cb:ed:34'/> <source dev='unt382' mode='bridge'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> I would however like to avoid having 25 interface stanzas in my XML. I would appeciate any ideas to solve this issue. I know this is most probably not a libvirt issue, but this list is about the only place that comes to my mind where people knowledgeable about those complex network stuff might hang around. If there is a better place to ask, I am open for suggestion. Please pardon my intrusion. Greetings Marc -- ----------------------------------------------------------------------------- Marc Haber | "I don't trust Computers. They | Mailadresse im Header Leimen, Germany | lose things." Winona Ryder | Fon: *49 6224 1600402 Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421

2 5

[libvirt-users] assigning PCI addresses with bus > 0x09
by Riccardo Ravaioli 04 Jan '19

04 Jan '19

Hi, My goal is to assign PCI addresses to a number of devices (network interfaces, disks and PCI devices in PCI-passthrough) without delegating to libvirt the generation of those values. This should give me more control and for sure more predictability over the hardware configuration of a virtual machine and consequently the name of the interfaces in it. I'm using libvirt 4.3.0 to create qemu/KVM virtual machines running Linux (Debian Stretch). So, for every device of the type mentioned above, I add this line: <address type='pci' domain='0x0000' bus='0x__' slot='0x__' function='0x0'/>, ... with values from 00 to ff in the bus field, and from 00 to 1f in the slot field, as described in the documentation. Long story short, I noticed that as soon as I assign values > 0x09 to the bus field, the serial console hangs indefinitely, in both Debian and Ubuntu. The VM seems to be started correctly and its state is "running"; in the XML file created by libvirt, I see all controllers from 0 the largest bus value I assigned, so everything from that side seems ok. What am I missing here? Thanks! Riccardo

3 6