- Users - libvirt List Archives

[libvirt-users] virsh hangs when backup jobs run on the kvm host
by Zhan Adlun 07 Mar '19

07 Mar '19

Hi, Has anyone met the same problem that virsh hangs when there are some backup jobs running on the kvm host? I use dirty bitmap supported by qemu to do backups every 6 minitues. About a few hours later, I ran 'virsh list', It hung. Then I stopped the backup jobs ，nothing was getting better. I had checked the libvirt logs ，but found nothing useful . Maybe the high I/O caused the problem? or there are connection number limits when using virsh, because I use virsh to check the backup jobs are still running every 10 seconds? My os version is ' Ubuntu 12.04 LTS Release: 12.04 Codename: precise,Linux version 4.1.0-generic (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #1 SMP Wed Nov 9 02:04:23 CST 2016'. KVM version is 'QEMU emulator version 2.7.1(Debian 1:2.7+dfsg-3)'. Hoping for you reply. Thanks!

3 3

[libvirt-users] How do I close a console connection?
by Lars Kellogg-Stedman 05 Mar '19

05 Mar '19

I'm working on (re-) implementing serial console support in virtualbmc [1], and one of the issues I'm hitting right now is that after establishing a console connection via... self._stream = self._conn.newStream(libvirt.VIR_STREAM_NONBLOCK) self._domain.openConsole(None, self._stream, 0) ...I can't figure out how to close the console. Subsequent calls to openConsole fail because "a console connection is already open". I thought maybe I should close the stream, but that doesn't appear to be possible (there is a finish method, but it just tells me that "this function is not supported by the connection driver"). [1]: https://github.com/openstack/virtualbmc Cheers, -- Lars Kellogg-Stedman <lars(a)redhat.com> | larsks @ {irc,twitter,github} http://blog.oddbit.com/ |

2 1

[libvirt-users] libvirt 5.0.0 - LXC container still in "virsh list" output after shutdown
by mxs kolo 26 Feb '19

26 Feb '19

Hello. Centos 7.6 with libvirt build from base "virt" repository: libvirt-daemon-driver-lxc-5.0.0-1.el7.x86_64 libvirt-client-5.0.0-1.el7.x86_64 libvirt-daemon-5.0.0-1.el7.x86_64 libvirt-daemon-driver-network-5.0.0-1.el7.x86_64 libvirt-libs-5.0.0-1.el7.x86_64 + systemd-219-62.el7_6.2.x86_64 Now lxc containers with type='direct' can be started, but can't be stopped :) Before shutdown. # virsh list --all Id Name State ------------------------------------------ 16312 test.lxc running # machinectl | grep test lxc-16312-test.lxc container libvirt-lxc # pstree -apA 16312 libvirt_lxc,16312 --name test.lxc --console 42 --security=none --handshake 45 --veth macvlan0 |-systemd,16315 | |-agetty,16690 --noclear --keep-baud console 115200 38400 9600 vt220 | |-dbus-daemon,16659 --system --address=systemd: --nofork --nopidfile --systemd-activation | |-rsyslogd,17614 -n | | |-{rsyslogd},17616 | | `-{rsyslogd},17626 | |-sshd,17613 -D | |-systemd-journal,16613 | `-systemd-logind,16657 `-{libvirt_lxc},16319 Shutdown. # virsh shutdown 16312 Domain 16312 is being shutdown # echo $? 0 After. In list output still present: # virsh list --all Id Name State ------------------------------------------ 16312 test.lxc running # machinectl | grep test | wc -l 0 No main process: # ps axuwwf | grep libvirt_lxc | grep test | wc -l 0 LXC realy stopped, but only virsh still show it in list Cgroups "blkio, cpuacct, memory, cpu, cpu,cpuacct, devices, hugetlb, pids" deleted. But another cgroups still present in fs: drwxr-xr-x 2 root root 0 Jan 21 13:07 /sys/fs/cgroup/cpuset/machine.slice/machine-lxc\x2d16312\x2dtest.lxc.scope drwxr-xr-x 2 root root 0 Jan 21 13:07 /sys/fs/cgroup/freezer/machine.slice/machine-lxc\x2d16312\x2dtest.lxc.scope drwxr-xr-x 2 root root 0 Jan 21 13:07 /sys/fs/cgroup/net_cls/machine.slice/machine-lxc\x2d16312\x2dtest.lxc.scope drwxr-xr-x 2 root root 0 Jan 21 13:07 /sys/fs/cgroup/net_cls,net_prio/machine.slice/machine-lxc\x2d16312\x2dtest.lxc.scope drwxr-xr-x 2 root root 0 Jan 21 13:07 /sys/fs/cgroup/net_prio/machine.slice/machine-lxc\x2d16312\x2dtest.lxc.scope drwxr-xr-x 2 root root 0 Jan 21 13:07 /sys/fs/cgroup/perf_event/machine.slice/machine-lxc\x2d16312\x2dtest.lxc.scope Restarted libvirtd temporary place container in correct state: # systemctl restart libvirtd # virsh list --all | grep test - test.lxc shut off libvirt 4.5.0 and 4.10.0 perform correct LXC shutdown. b.r. Maxim Kozin

2 3

[libvirt-users] virsh confirmed edits do not persist
by Josh Mcneil 21 Feb '19

21 Feb '19

This may be user error, I am new to libvirt. I am using libvirt 5.0.0. I have created a VM (win10) in the system URI using virt-manager. I stopped the VM to edit it. I set my LIBVIRT_DEFAULT_URI="qemu:///system" and am able to read the domain configuration with `EDITOR=nano virsh edit win10`. When I save (ctrl+o) and exit (ctrl+x) I see the message "Domain win10 XML configuration edited." as expected. However, when I run the edit command again the changes do not appear to have persisted. I have tried starting and stopping the VM. I read that I may need to define the domain with virsh so I did that. None of these things seem to work. I would appreciate it if someone could help me solve this issue in order to be able to modify domains from virsh! Thanks in advance for any help! Josh

2 3

[libvirt-users] HELP!
by Shashwat shagun 16 Feb '19

16 Feb '19

I'm getting this error (below) [root@localhost test]# ./test virError(Code=6, Domain=20, Message='invalid connection pointer in virConnectListAllDomains') 0 running domains: when running this program :- (below) package main import ( "fmt" libvirt "github.com/libvirt/libvirt-go" ) type DomService struct { Conn *libvirt.Connect } func (d *DomService) Connect() error { var err error d.Conn, err = libvirt.NewConnect("qemu:///system") if err != nil { fmt.Println(err) } defer d.Conn.Close() return nil } func (d *DomService) ListDoms() error { doms, err := d.Conn.ListAllDomains(libvirt.CONNECT_LIST_DOMAINS_ACTIVE) if err != nil { fmt.Println(err) } //fmt.Println(doms) fmt.Printf("%d running domains:\n", len(doms)) for _, dom := range doms { name, err := dom.GetName() if err == nil { fmt.Printf(" %s\n", name) } dom.Free() } return nil } func main() { doms := DomService{} doms.Connect() doms.ListDoms() } -- Regards, Shashwat Shagun

3 2

[libvirt-users] virsh migrate --copy-storage-inc
by Paul van der Vlis 13 Feb '19

13 Feb '19

Hello, I use libvirt on machines without shared storage. My VM's have all one qcow2-disk, with the same name as the VM. When I want to migrate a VM, I check if there is an qcow2 image on the other host with that name. When that's not the case, I copy the image using rsync first. If the image excist, I don't do that, and I think that "--copy-storage-inc" will do it. But I don't know how intelligent "--copy-storage-inc" is. I use LVM inside the VM's, and it's possible that I have changed the size of a volume for example. My questions: Is "--copy-storage-inc" intelligent enough for such tasks? Is there documentation what is done during migration? Is it using rsync? Is it possible to make the migration process more verbose? Is what I do a good way? With regards, Paul van der Vlis BTW: this is what I do, sometimes the lines are broken wrong: ----------- # Rsync image when not on the other host: if test `ssh $other "if test -e /data/$vm.qcow2; then echo ja; else echo nee; fi"` = "nee"; then echo "rsync..." rsync /data/$vm.qcow2 $other://data/$vm.qcow2 if test $? = 0; then echo "gelukt"; else echo "niet gelukt"; exit; fi fi # migrate echo "migrate..." virsh migrate --live --p2p --tunnelled --copy-storage-inc --persistent --undefinesource --verbose $vm qemu+ssh://$other/system if test $? = 0; then echo "gelukt"; else echo "niet gelukt"; exit; fi ----------- -- Paul van der Vlis Linux systeembeheer Groningen https://www.vandervlis.nl/

2 2

[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 07 Feb '19

07 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