- Users - libvirt List Archives

[libvirt-users] Proxmox to libvirt conversion?
by Andre Goree 10 Jan '18

10 Jan '18

Hello all. I'm wondering if anyone on this list has come across the need to convert a Proxmox VM to a libvirt VM. Given that they use the same underlying technology (qemu/KVM), I'm pretty sure it's possible and just a matter of hashing out the differences in configuration (i.e. creating the necessary libvirt xml for the Proxmox disk), but figured I'd ask here first in case anyone has dealt with this (probably will find and ask on the Proxmox mailing list as well). Thanks in advance! -- Andre Goree -=-=-=-=-=- Email - andre at drenet.net Website - http://blog.drenet.net PGP key - http://www.drenet.net/pubkey.html -=-=-=-=-=-

1 0

[libvirt-users] VM migration upon shutdown in centos 7
by Raman Gupta 10 Jan '18

10 Jan '18

Hi, I have CentOS 7, two node system which allows live VM migration between them. Live migration triggered from virsh is happily happening. I am using GlusterFS for replicating VM disk files. Now I want to automatically do the live migration at the time of reboot/shutdown/halt of the host node and for this I have written a systemd service unit [vPreShutdownHook.service] and placed the live migration command in a migrate script which is invoked from this service unit. The migrate script is invoked but migration does not happen. If someone has some idea please help me to migrate VM upon shutdown. ######## vPreShutdownHook.service ############### [Unit] Description=vPreShutdownHook Requires=network.target Requires=libvirtd.service Requires=dbus.service Requires=glusterd.service Requires=glusterfsd.service DefaultDependencies=no Before=shutdown.target reboot.target [Service] Type=oneshot RemainAfterExit=true ExecStart=/bin/true ExecStop=/root/vm_migrate.sh [Install] WantedBy=multi-user.target ########## Command to migrate ############ /usr/bin/virsh migrate --verbose --p2p --tunneled --live --compressed --comp-methods "mt" --comp-mt-level 5 --comp-mt-threads 5 --comp-mt-dthreads 5 MY_VM qemu+ssh://root@$node2/system Thanks,

3 2

[libvirt-users] All VMs permanently 'paused'
by Mark Coolen 08 Jan '18

08 Jan '18

I set up Alpine Linux as a libvirt-based KVM hypervisor last week. Everything was working beautifully on Friday. I left two Windows VMs up and running and two 'Saved' on Friday afternoon. When I go in this morning the two running ones were 'Paused' and I can't unpause them with virt-manager or with virsh. The other two saved ones I can start, but they are immediately paused too. When I click to unpause in virt- manager nothing happens. When I 'resume' in virsh I get 'Domain ... resumed' but it's immediately paused again. I looked in /var/log/libvirt/libvirtd.log and qemu/<DOMAIN>.log and there doesn't seem to be anything happening. No errors or anything. As I say. Everything was working fine on Friday afternoon. Does anyone know what I should try next? I'll attach my logs and the XML of one of my machines. _ _ _ ___ _ )\/,) ___ __ )L, )) __ __ )) __ _ _ ((`(( ((_( (| ((\ ((__((_)((_)(( (('((\(

3 4

[libvirt-users] virsh and bash scripts
by Hetz Ben Hamo 08 Jan '18

08 Jan '18

Hi, I'm looking for a way to use virsh to connect to vCenter/VCSA and do some simple management of the VM's in case of power loss (I'm planning to run the script upon UPS/apcd event of power failure). Looking through the virsh documentation, I didn't find 2 things: 1. Login through a script (I don't see any user/password, specially since VCSA for example requires to use username(a)vsphere.local [or your AD domain insteadd of vsphere.local if you connected it to your AD domain]) 2. Get all the VMs running on the vCenter, not just specific hosts. Any suggestion? Thanks

2 2

[libvirt-users] Libvirt not terminating SSH processes
by Priyanka Gupta 08 Jan '18

08 Jan '18

Hi LibVirt team, I am facing an issue with libvert. I am closing a "qemu+ssh" connection but the initiated ssh process are going into sleep mode and not getting killed upon closing the connection. Can you please help me figure out the issue ? -- With Kind Regards Priyanka Gupta

2 1

[libvirt-users] Cannot Write xvga=yes in xml file
by Rogue S.T 05 Jan '18

05 Jan '18

Hello,my system info: virsh verison Compiled against library: libvirt 3.9.0 Using library: libvirt 3.9.0 Using API: QEMU 3.9.0 Running hypervisor: QEMU 2.10.90 And i want to pass through my gpu to my window 7 guest with <hostdev>, next line is comand i use: <hostdev mode='subsystem' type='pci' managed='yes' xvga='yes'> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </source> <rom bar='on' file='/root/gpu.dump'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </hostdev> But i get this error: XML document failed to validate against schema: Unable to validate doc against /ocl/share/libvirt/schemas/domain.rng Extra element devices in interleave Element domain failed to validate content If i delete xvga='yes',it's ok, but i get a other question, my display is not light.

2 3

[libvirt-users] libvirt net xml format
by Bhasker C V 04 Jan '18

04 Jan '18

Hi all, I went through the docs but could not find a way to pass the -h OR --no-hosts option to dnsmasq via libvirt xml Is there a way to do this via xml ? please can someone help. Thanks

3 3

[libvirt-users] Using Intel Quick-Sync with GPU capable Intel CPUs
by Benjammin2068 03 Jan '18

03 Jan '18

Rogue S.T asked about checking out graphics cards which brought the question to me... Is it possible to make Intel on-CPU GPU resources to Windows 10? (the box I'm working with has Xeon E5-2640v4 CPUs which should be QuickSync capable) What else do I have to do to take advantage of this? Just load the drivers? Thanks, -Ben

2 2

[libvirt-users] questions about disk auth element for Backing Chain
by Meina Li 03 Jan '18

03 Jan '18

Hi, I am a libvirt qe, I am testing the function about the new location of disk auth element (as sub-element of the source element) in Backing Chain Management. And I have a questions: When all the backing chain are iscsi network disk type(no matter if the authentication is exist), start the guest , it will only has the top level disk in xml and there are no other backingStore in it. The test step is below. So can this function support all backing chain with network disk type actually, or only use network authentication as the base image for backing chain of file disk type? Can you help reviewing it? Thanks very much in advance! Test step: 1. iSCSI server: o- iscsi ............................................................................................................ [Targets: 2] | o- iqn.2003-01.org.linux-iscsi.localhost.x8664:sn.9cba196611e6 ....................................................... [TPGs: 1] | | o- tpg1 ..................................................................................... [gen-acls, tpg-auth, 1-way auth] | | o- acls .......................................................................................................... [ACLs: 0] | | o- luns .......................................................................................................... [LUNs: 4] | | | o- lun0 ................................................................ [fileio/file1 (/tmp/lun1.img) (default_tg_pt_gp)] | | o- portals .................................................................................................... [Portals: 1] | | o- 0.0.0.0:3260 ..................................................................................................... [OK] | o- iqn.2003-01.org.linux-iscsi.localhost.x8664:sn.a8d92ebb4ece ....................................................... [TPGs: 1] | o- tpg1 .................................................................................................. [gen-acls, no-auth] | o- acls .......................................................................................................... [ACLs: 0] | o- luns .......................................................................................................... [LUNs: 3] | | o- lun0 ................................................................ [fileio/file3 (/tmp/lun3.img) (default_tg_pt_gp)] | o- portals .................................................................................................... [Portals: 1] | o- 0.0.0.0:3260 ..................................................................................................... [OK] 2. Set iscsi secret. # cat iscsi-secret.xml <secret ephemeral='no' private='yes'> <description>iSCSI secret</description> <usage type='iscsi'> <target>libvirtiscsi</target> </usage> </secret> # virsh secret-define iscsi-secret.xml Secret 47bd2f3e-023f-44ba-85a3-e8fa7f16ff23 created # MYSECRET=`printf %s "redhat" | base64` # virsh secret-set-value 47bd2f3e-023f-44ba-85a3-e8fa7f16ff23 $MYSECRET Secret value set 3. Create backing chain. # qemu-img create -f qcow2 -b iscsi:// redhat:redhat@10.66.7.27:3260/iqn.2003-01.org.linux-iscsi.localhost.x8664:sn.9cba196611e6/0 iscsi:// 10.66.7.27:3260/iqn.2003-01.org.linux-iscsi.localhost.x8664:sn.a8d92ebb4ece/0 -o backing_fmt=qcow2 4. Start guest. # qemu-img info iscsi:// 10.66.7.27:3260/iqn.2003-01.org.linux-iscsi.localhost.x8664:sn.a8d92ebb4ece/0 --backing-chainimage: json:{"driver": "qcow2", "file": {"lun": "0", "portal": "10.66.7.27:3260", "driver": "iscsi", "transport": "tcp", "target": "iqn.2003-01.org.linux-iscsi.localhost.x8664:sn.a8d92ebb4ece"}} file format: qcow2 virtual size: 5.0G (5368709120 bytes) disk size: unavailable cluster_size: 65536 backing file: iscsi:// redhat:redhat@10.66.7.27:3260/iqn.2003-01.org.linux-iscsi.localhost.x8664:sn.9cba196611e6/0 backing file format: qcow2 Format specific information: compat: 1.1 lazy refcounts: false refcount bits: 16 corrupt: false image: json:{"driver": "qcow2", "file": {"lun": "0", "portal": " 10.66.7.27:3260", "driver": "iscsi", "transport": "tcp", "user": "redhat", "password": "redhat", "target": "iqn.2003-01.org.linux-iscsi.localhost.x8664:sn.9cba196611e6"}} file format: qcow2 virtual size: 5.0G (5368709120 bytes) disk size: unavailable cluster_size: 65536 Format specific information: compat: 1.1 lazy refcounts: false refcount bits: 16 corrupt: false # virsh dumpxml rhel7 | grep disk -A 9 ... <disk type='network' device='disk'> <driver name='qemu' type='qcow2'/> <source protocol='iscsi' name='iqn.2003-01.org.linux-iscsi.localhost.x8664:sn.a8d92ebb4ece/0'> <host name='10.66.7.27' port='3260'/> </source> <target dev='vdb' bus='virtio'/> <alias name='virtio-disk1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/> </disk> ... Best Regards Meina Li

1 0

[libvirt-users] [BUG] Not exiting media forced a promptly close of libvirt 3.10
by Holger Schranz 28 Dec '17

28 Dec '17

Hello, In the .xml file I use a media which is no longer available. In the past, I got the information media not available and the creation of the VM was stopped - O.k. behavior. Since 3.10 the libvirtd stopped promptly and all open consoles windows and the virt-manager closed promptly. For diagnose: etcsvms1:/kvm/CS8200/M5 # coredumpctl TIME PID UID GID SIG PRESENT EXE Fri 2017-12-22 08:16:35 CET 7056 0 0 11 * /usr/local/sbin/libvirtd Fri 2017-12-22 08:19:46 CET 10611 0 0 11 * /usr/local/sbin/libvirtd Fri 2017-12-22 09:28:48 CET 10728 0 0 11 * /usr/local/sbin/libvirtd etcsvms1:/kvm/CS8200/M5 # coredumpctl info libvirtd . . . PID: 10728 (libvirtd) UID: 0 (root) GID: 0 (root) Signal: 11 (SEGV) Timestamp: Fri 2017-12-22 09:28:39 CET (15min ago) Command Line: /usr/local/sbin/libvirtd -d Executable: /usr/local/sbin/libvirtd Control Group: / Slice: -.slice Boot ID: 01603763bc784c7380e310d5eea124d6 Machine ID: 89c660865c00403a9bacef32b6828556 Hostname: etcsvms1 Coredump: /var/lib/systemd/coredump/core.libvirtd.0.01603763bc784c7380e310 Message: Process 10728 (libvirtd) of user 0 dumped core. etcsvms1:/kvm/CS8200/M5 # coredumpctl dump libvirtd PID: 10728 (libvirtd) UID: 0 (root) GID: 0 (root) Signal: 11 (SEGV) Timestamp: Fri 2017-12-22 09:28:39 CET (16min ago) Command Line: /usr/local/sbin/libvirtd -d Executable: /usr/local/sbin/libvirtd Control Group: / Slice: -.slice Boot ID: 01603763bc784c7380e310d5eea124d6 Machine ID: 89c660865c00403a9bacef32b6828556 Hostname: etcsvms1 Coredump: /var/lib/systemd/coredump/core.libvirtd.0.01603763bc784c7380e310d5eea124d6.10728.1513931319000000.xz Message: Process 10728 (libvirtd) of user 0 dumped core. Refusing to dump core to tty. etcsvms1:/kvm/CS8200/M5 # coredumpctl gdb libvirtd PID: 10728 (libvirtd) UID: 0 (root) GID: 0 (root) Signal: 11 (SEGV) Timestamp: Fri 2017-12-22 09:28:39 CET (18min ago) Command Line: /usr/local/sbin/libvirtd -d Executable: /usr/local/sbin/libvirtd Control Group: / Slice: -.slice Boot ID: 01603763bc784c7380e310d5eea124d6 Machine ID: 89c660865c00403a9bacef32b6828556 Hostname: etcsvms1 Coredump: /var/lib/systemd/coredump/core.libvirtd.0.01603763bc784c7380e310d5eea124d6.10728.1513931319000000.xz Message: Process 10728 (libvirtd) of user 0 dumped core. GNU gdb (GDB; openSUSE Leap 42.3) 8.0.1 Copyright (C) 2017 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-suse-linux". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://bugs.opensuse.org/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /usr/local/sbin/libvirtd...done. [New LWP 10729] [New LWP 10731] [New LWP 10733] [New LWP 10735] [New LWP 10732] [New LWP 10739] [New LWP 10730] [New LWP 10741] [New LWP 10743] [New LWP 10734] [New LWP 10736] [New LWP 11276] [New LWP 10737] [New LWP 10738] [New LWP 10728] [New LWP 10740] [New LWP 10751] [New LWP 10742] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Core was generated by `/usr/local/sbin/libvirtd -d'. Program terminated with signal SIGSEGV, Segmentation fault. #0 virStorageFileReportBrokenChain (errcode=2, src=src@entry=0x7f0d4004ac40, parent=0x7f0d4004ac40) at storage/storage_source.c:422 422 unsigned int access_user = src->drv->uid; [Current thread is 1 (Thread 0x7f0d525ab700 (LWP 10729))] Missing separate debuginfos, use: zypper install device-mapper-debuginfo-1.02.97-77.1.x86_64 glibc-debuginfo-2.22-8.4.x86_64 krb5-debuginfo-1.12.5-12.1.x86_64 libapparmor1-debuginfo-2.10.3-16.1.x86_64 libavahi-client3-debuginfo-0.6.32-3.5.x86_64 libavahi-common3-debuginfo-0.6.32-3.5.x86_64 libblkid1-debuginfo-2.29.2-5.1.x86_64 libcap2-debuginfo-2.22-18.16.x86_64 libcom_err2-debuginfo-1.42.11-15.1.x86_64 libcurl4-debuginfo-7.37.0-23.1.x86_64 libdbus-1-3-debuginfo-1.8.22-5.1.x86_64 libffi4-debuginfo-5.3.1+r233831-10.1.x86_64 libgmp10-debuginfo-5.1.3-7.15.x86_64 libgnutls28-debuginfo-3.3.27-1.5.x86_64 libhogweed2-debuginfo-2.7.1-12.1.x86_64 libidn11-debuginfo-1.28-8.3.x86_64 libkeyutils1-debuginfo-1.5.9-7.13.x86_64 libldap-2_4-2-debuginfo-2.4.44-18.1.x86_64 liblzma5-debuginfo-5.2.2-3.15.x86_64 libnettle4-debuginfo-2.7.1-12.1.x86_64 libnl1-debuginfo-1.1.4-6.13.x86_64 libopenssl1_0_0-debuginfo-1.0.2j-16.1.x86_64 libp11-kit0-debuginfo-0.20.7-1.2.x86_64 libpciaccess0-debuginfo-0.13.4-4.3.x86_64 libpcre1-debuginfo-8.39-11.1.x86_64 libsasl2-3-debuginfo-2.1.26-14.1.x86_64 libselinux1-debuginfo-2.5-4.17.x86_64 libssh2-1-debuginfo-1.4.3-18.3.x86_64 libtasn1-6-debuginfo-4.9-1.2.x86_64 libudev1-debuginfo-228-38.1.x86_64 libuuid1-debuginfo-2.29.2-5.1.x86_64 libxml2-2-debuginfo-2.9.4-12.1.x86_64 libyajl2-debuginfo-2.0.1-21.3.x86_64 libz1-debuginfo-1.2.8-13.15.x86_64 (gdb) Best regards Holger --- Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft. https://www.avast.com/antivirus

4 7