- 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