June 2018 - Users - libvirt List Archives

[libvirt-users] [virtual interface] detach interface during boot succeed with no changes
by Yalan Zhang 08 Sep '22

08 Sep '22

Hi guys, when I detach an interface from vm during boot (vm boot not finished), it always fail. I'm not sure if there is an existing bug. I have confirmed with someone that for disk, there is similar behavior, if this is also acceptable? # virsh destroy rhel7.2; virsh start rhel7.2 ;sleep 2; virsh detach-interface rhel7.2 network 52:54:00:98:c4:a0; sleep 2; virsh dumpxml rhel7.2 |grep /interface -B9 Domain rhel7.2 destroyed Domain rhel7.2 started Interface detached successfully <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </controller> <interface type='network'> <mac address='52:54:00:98:c4:a0'/> <source network='default' bridge='virbr0'/> <target dev='vnet0'/> <model type='rtl8139'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> When I detach after the vm boot, expand the sleep time to 10, it will succeed. # virsh destroy rhel7.2; virsh start rhel7.2 ;sleep 10; virsh detach-interface rhel7.2 network 52:54:00:98:c4:a0; sleep 2; virsh dumpxml rhel7.2 |grep /interface -B9 Domain rhel7.2 destroyed Domain rhel7.2 started Interface detached successfully ------- Best Regards, Yalan Zhang IRC: yalzhang Internal phone: 8389413

3 4

[libvirt-users] Add Virtlyst to the list of libvirt users
by Daniel Nicoletti 24 Sep '20

24 Sep '20

Hi, I've just released v1.0.0 of Virtlyst[1] a web tool to manage VMs using Qt/C++/Cutelyst https://dantti.wordpress.com/2018/04/19/announcing-virtlyst-a-web-interface… Thanks. 1 - https://github.com/cutelyst/Virtlyst -- Daniel Nicoletti KDE Developer - http://dantti.wordpress.com

4 5

[libvirt-users] Question about disabling UFO on guest
by Bao Nguyen 05 Aug '20

05 Aug '20

Hello everyone, I would like to ask a question regarding to disable UFO of virtio vNIC in my guest. I have read the document at https://libvirt.org/formatdomain.html *host* The csum, gso, tso4, tso6, ecn and ufo attributes with possible values on and off can be used to turn off host offloading options. By default, the supported offloads are enabled by QEMU. *Since 1.2.9 (QEMU only)* The mrg_rxbuf attribute can be used to control mergeable rx buffers on the host side. Possible values are on (default) and off. *Since 1.2.13 (QEMU only)* *guest* The csum, tso4, tso6, ecn and ufo attributes with possible values on and off can be used to turn off guest offloading options. By default, the supported offloads are enabl ed by QEMU. *Since 1.2.9 (QEMU only)* Then I disabled UFO on my vNIC on guest as the following configuration <devices> <interface type='network'> <source network='default'/> <target dev='vnet1'/> <model type='virtio'/> <driver name='vhost' txmode='iothread' ioeventfd='on' event_idx='off' queues='5' rx_queue_size='256' tx_queue_size='256'> *<host gso='off' ufo='off' />* *<guest ufo='off'/>* </driver> </interface> </devices> Then I reboot my node to get the change effect and it works. However, can I disable the UFO without touching the host OS? or it always has to disable on both host and guest like that? Thanks, Brs, Natsu

2 1

[libvirt-users] Libvirt access control drivers
by Anastasiya Ruzhanskaya 22 Nov '18

22 Nov '18

Hello! According to the documentation access control drivers are not in really "good condition". There is a polkit, but it can distinguish users only according the pid. However, I have met some articles about more fine-grained control and about selinux drivers for libvirt? So, what is the status now? Should I implement something by myself if I want access based on login, are their instructions how to write these drivers or there is smth already?

3 18

[libvirt-users] ceph rbd pool and libvirt manageability (virt-install)
by Jelle de Jong 29 Aug '18

29 Aug '18

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello everybody, I created a rbd pool and activated it, but I can't seem to create volumes in it with virsh or virt-install? # virsh pool-dumpxml myrbdpool <pool type='rbd'> <name>myrbdpool</name> <uuid>2d786f7a-2df3-4d79-ae60-1535bcf1c6b5</uuid> <capacity unit='bytes'>6997998301184</capacity> <allocation unit='bytes'>10309227031</allocation> <available unit='bytes'>6977204658176</available> <source> <host name='ceph01.powercraft.nl' port='6789'/> <host name='ceph02.powercraft.nl' port='6789'/> <host name='ceph03.powercraft.nl' port='6789'/> <name>libvirt-pool</name> <auth type='ceph' username='libvirt'> <secret uuid='029a334e-ed57-4293-bb99-ffafa8867122'/> </auth> </source> </pool> # virt-install --version 1.0.1 # virsh --version 1.2.9 I ended using virsh edit ceph-test.powercraft.nl and making creating the disk manually. <disk type='network' device='disk'> <auth username='libvirt'> <secret type='ceph' uuid='029a334e-ed57-4293-bb99-ffafa8867122'/> </auth> <source protocol='rbd' name='libvirt-pool/kvm01-storage'> <host name='ceph01.powercraft.nl' port='6789'/> <host name='ceph02.powercraft.nl' port='6789'/> <host name='ceph03.powercraft.nl' port='6789'/> </source> <target dev='vdc' bus='virtio'/> </disk> I use virt-install a lot to define, import and undefine domains, how can I use virt-install to manage my rdb disks? Kind regards, Jelle de Jong -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iJwEAQECAAYFAlV1xlQACgkQ1WclBW9j5HkbPQP+PjNrzvlqysslOp2Yk7wH4Mxy 2sh2dn96G0KOAHEeEn3BN6IWlnD1TADZbHdpTtMwkdv48Xwn0sP1s+3QDM4pb3gP n+z+dVxS8FouDIy/eiso3IBCj3g4TWbEX8ZHqs3jKqe0lZgAXBzB9xYSUowcEBrZ ddkPbr8p8ozWyOG+9V8= =lkK7 -----END PGP SIGNATURE-----

2 3

[libvirt-users] East-west traffic network filter
by Ales Musil 03 Jul '18

03 Jul '18

Hello, I would like to make filter that allows communication only between specified VMs. Those VMs should be specified by their MAC address. The filter should extend clean-traffic but I was not able to get it working with that reference. I have came up with modified clean-traffic which works fine [1]. Is there a way to achieve the same behavior with reference to clean-traffic? Thank you. Best wishes, Ales Musil [1] <filter name='clean-traffic-gateway'>  <filterref filter='no-mac-spoofing'/>  <filterref filter='no-ip-spoofing'/>  <filterref filter='no-arp-spoofing'/>  <rule action='accept' direction='inout' priority='-500'> <mac protocolid='arp'/> </rule>  <rule action='accept' direction='in'> <mac match='yes' srcmacaddr='$GATEWAY_MAC' srcmacmask='$GATEWAY_MAC_MASK' /> </rule>  <rule action='accept' direction='out'> <mac match='yes' dstmacaddr='$GATEWAY_MAC' dstmacmask='$GATEWAY_MAC_MASK' /> </rule>  <filterref filter='no-other-l2-traffic'/>  <filterref filter='qemu-announce-self'/> </filter> -- ALES MUSIL INTERN - rhv network Red Hat EMEA <https://www.redhat.com/> amusil(a)redhat.com IM: amusil <https://red.ht/sig>

3 5

[libvirt-users] Reintroduce "allocate entire disk" checkbox on virt-manager
by Gionatan Danti 28 Jun '18

28 Jun '18

Hi list, on older virt-manager versions (ie: what shipped with RHEL 6), a checkbox called "allocate entire disk" was selectable when configuring a new virtual machine. When checked, it means that the RAW disk image file was entirely allocated, generally issuing a fallocate() call. When unchecked, the disk image was a sparse file, with on-demand space allocation. On new virt-manager versions (ie: what ships with RHEL 7), the checkbox is gone. This means that for creating a sparse allocated file from within the "new vm" wizard, one is forced to use a Qcow2 file (selectable in the global preferences). No sparse RAM images can be created within such wizard. As a heavy consumer of RAW disk files, I would really like to have the checkbox back, especially in RHEL/CentOS 7.x Do you plan to reintroduce it? For RHEL/CentOS, should I open a Bugzilla ticket? Thanks. -- Danti Gionatan Supporto Tecnico Assyoma S.r.l. - www.assyoma.it email: g.danti(a)assyoma.it - info(a)assyoma.it GPG public key ID: FF5F32A8

3 9

[libvirt-users] Virtio-net drivers immune to Nethammer?
by procmem 27 Jun '18

27 Jun '18

Hi I'm a privacy distro maintainer investigating the implications of the newly published nethammer attack [0] on KVM guests particularly the virtio-net drivers. The summary of the paper is that rowhammer can be remotely triggered by feeding susceptible* network driver crafted traffic. This attack can do all kinds of nasty things such as modifying SSL certs on the victim system. * Susceptible drivers are those relying on Intel CAT, uncached memory or the clflush instruction. My question is, do virtio-net drivers do any of these things? *** [0] https://arxiv.org/abs/1805.04956

4 7

[libvirt-users] virsh error: domain is already quiesced
by Jérôme 26 Jun '18

26 Jun '18

Hi all. I'm having issues while creating snapshots. I posted on Stack Exchange [1], but figured I might get more success here. My VM backup script fails while creating the snapshot. virsh snapshot-create-as --domain machine_1 snap --diskspec vda,file=/srv/test/test-snap.qcow2 --disk-only --atomic --no-metadata --quiesce error: Requested operation is not valid: domain is already quiesced Even after a VM reboot, the system is still quiesced and I get the same error. I thought quiesce means FS freeze, but this makes no sense since I can still write to the FS when logged in the faulty VMs. And this would not survive a reboot, right? Could it be a communication issue that makes the host think the GA says the machine is quiesced while it is not? In any case, is there a command to enquire the quiesce state (apart from attempting a snapshot and see if I get an error)? Assuming the faulty VMs went quiesced after a unreproducible error, I could fix that by exiting quiesced state, whatever that means. Is there a virsh command to unquiesce the VM? The whole backup procedure used to work and now it fails on 2 VMs but still works on 2 others and I can't think of any relevant difference between them. Software versions: - Host is Debian Jessie with qemu-kvm 2.8+dfsg-3~bop8+1 from backports. - Guests are Debian Stretch with qemu-guest-agent 2.8+dfsg-6+deb9u4. (For the record, the backup script is on GitHub [2]. Basically, what it does is 1/ create snapshot, 2/ copy, 3/ commit snapshot.) If I remove the `quiesce` option from the snapshot command line, things work smooth. But obviously, this is not ideal. Thanks for any hint. [1] https://serverfault.com/questions/917247/virsh-error-domain-is-already-quie… [2] https://github.com/Nobatek/vmbackup/blob/master/vmbackup -- Jérôme

2 2

[libvirt-users] How libvirt interacts with dhcpd?
by Daniel. 21 Jun '18

21 Jun '18

Hi everybody, I'm using libvirt together with xCAT, on the same host, for testing purposes. xCAT install and manages dhcpd. How libvirt interacts with dhcpd? And if doens't how does the dhcp server of libvirt works, plus where I can find information on how to troubleshot it? Regards, -- “If you're going to try, go all the way. Otherwise, don't even start. ..." Charles Bukowski

2 6

[libvirt-users] Network problem when rebooting Fedora qemu/kvm guest on Gentoo host
by Dan Johansson 18 Jun '18

18 Jun '18

Hello, I have some problem with some of my qemu/kvm guests running Fedora on a Gentoo host where my Gentoo guests works without problem. The problem that I have is that when I reboot (shutdown -r now) the Fedora guest "loses" (ifconfig does not show a IP-address) their network connections. The Gentoo guests reboots without problem. All the guests have same HW-configuration, only Name/DiskImage/MAC- addresses differ. Here some technical details: Host: Distribution Gentoo Kernel 4.9.95-gentoo Qemu app-emulation/qemu-2.11.1-r2 USE="aio bzip2 caps curl fdt filecaps gnutls jpeg lzo ncurses nls pin-upstream-blobs png sdl seccomp vhost-net vnc xattr" QEMU_SOFTMMU_TARGETS="x86_64" QEMU_USER_TARGETS="x86_64" libvirt app-emulation/libvirt-4.3.0 USE="caps dbus libvirtd nls qemu udev" Guest Distribution Fedora 28 Kernel 4.16.15-300.fc28.x86_64 Networkmanager NetworkManager.x86_64 1:1.10.8-1.fc28 Any suggestions? -- Dan Johansson *************************************************** This message is printed on 100% recycled electrons! ***************************************************

1 0

[libvirt-users] Feedback for a new application NIMO using the libvirt API
by Jay Mehta 14 Jun '18

14 Jun '18

Hello folks, A while back I developed VM instance monitoring tool "NIMO", Nova (Openstack's project Nova) Instance Monitor. The need to develop Nimo arise with requirement to monitor VM's boot stages. A VM boot undergoes multiple stages, like creating block device, mounting root filesystem, mounting local filesystem, DHCP lease acquiring, post-install activities, etc., and it could fail or stuck at any of these stages. It would be good to have a monitor in place to identify which stage a VM is in while booting and how much time it takes at each stage. A special need for such tool arise on the cloud space, where end-user do not have access to log on to the hypervisor. It also helps to people who build custom VM images and add a lot of tasks in post install script and would like to know performance of each step. The below is the github link and it has an architecture diagram. https://github.com/jay-g-mehta/nimo I would love to hear all of your response and feel free to use it, extend it. Thanks, Jay

1 0

[libvirt-users] "virsh" list
by Bo YU 13 Jun '18

13 Jun '18

Hello, I installed libvirt from package manager(debian apt) and want to modify feture in it, so i git clone from https://libvirt.org/git/?p=libvirt.git;a=summary But now i have trouble to start virsh. I have traced the email: https://www.redhat.com/archives/libvirt-users/2017-February/msg00074.html Here is output of command below: strace -o libvirt.log -f -s 1000 /usr/sbin/libvirtd https://github.com/yuzibo/linux-programming/blob/master/tmp/libvirt.log Here: sudo gdb -p $(pgrep libvirtd) (gdb) t a a bt [New LWP 14781] [New LWP 14782] [New LWP 14783] [New LWP 14784] [New LWP 14785] [New LWP 14786] [New LWP 14787] [New LWP 14788] [New LWP 14789] [New LWP 14790] [New LWP 14791] [New LWP 14792] [New LWP 14793] [New LWP 14794] [New LWP 14795] [New LWP 14796] [New LWP 14799] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x00007fcf4c75f67d in poll () at ../sysdeps/unix/syscall-template.S:84 84../sysdeps/unix/syscall-template.S: (no such file or directory)没有那个文件或目录. "" Thread 18 (Thread 0x7fcf3a4e8700 (LWP 14799)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x00007fcf4e17ee36 in virCondWait (c=c@entry=0x7fcf3400cc90, m=m@entry=0x7fcf3400cc50) at util/virthread.c:154 #2 0x00007fcf405498a0 in udevEventHandleThread (opaque=<optimized out>) at node_device/node_device_udev.c:1606 #3 0x00007fcf4e17ec02 in virThreadHelper (data=<optimized out>) at util/virthread.c:206 #4 0x00007fcf4ca26494 in start_thread (arg=0x7fcf3a4e8700) at pthread_create.c:333 #5 0x00007fcf4c768acf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 Thread 17 (Thread 0x7fcf3b315700 (LWP 14796)): #0 0x00007fcf4c75f67d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x00007fcf4c77917e in __poll_chk (fds=<optimized out>, nfds=<optimized out>, timeout=<optimized out>, fdslen=<optimized out>) at poll_chk.c:27 #2 0x00007fcf4e10f281 in poll (__timeout=-1, __nfds=<optimized out>, __fds=0x7fcf3b3143b0) at /usr/include/x86_64-linux-gnu/bits/poll2.h:41 #3 virCommandProcessIO (cmd=cmd@entry=0x7fcf34015d30) --Type <return> to continue, or q <return> to quit--- at util/vircommand.c:2085 #4 0x00007fcf4e1134ea in virCommandRun (cmd=0x7fcf34015d30, exitstatus=exitstatus@entry=0x7fcf3b314924) at util/vircommand.c:2316 #5 0x00007fcf3e239fca in virQEMUCapsInitQMPCommandRun ( cmd=cmd@entry=0x7fcf34015b10, forceTCG=forceTCG@entry=false) at qemu/qemu_capabilities.c:4262 #6 0x00007fcf3e23f4b9 in virQEMUCapsInitQMP (qmperr=0x7fcf3b314970, runGid=<optimized out>, runUid=<optimized out>, libDir=<optimized out>, qemuCaps=0x7fcf340159d0) at qemu/qemu_capabilities.c:4318 #7 virQEMUCapsNewForBinaryInternal (hostArch=VIR_ARCH_X86_64, binary=0x7fcf3403e160 "/usr/local/bin/qemu-system-x86_64", libDir=<optimized out>, runUid=<optimized out>, runGid=<optimized out>, microcodeVersion=166, kernelVersion=0x7fcf3404e120 "4.14.0+ #1 SMP Sun Nov 26 15:17:48 HKT 2017") at qemu/qemu_capabilities.c:4405 #8 0x00007fcf3e23f793 in virQEMUCapsNewData (binary=<optimized out>, privData=<optimized out>) at qemu/qemu_capabilities.c:4447 #9 0x00007fcf4e18ca1e in virFileCacheNewData ( name=0x7fcf3403e160 "/usr/local/bin/qemu-system-x86_64", cache=0x7fcf3404ddf0) at util/virfilecache.c:219 #10 virFileCacheValidate (cache=cache@entry=0x7fcf3404ddf0, name=name@entry=0x7fcf3403e160 "/usr/local/bin/qemu-system-x86_64", data=data@entry=0x7fcf3b314ae0) at util/virfilecache.c:290 ---Type <return> to continue, or q <return> to quit--- #11 0x00007fcf4e18cd77 in virFileCacheLookup ( cache=cache@entry=0x7fcf3404ddf0, name=name@entry=0x7fcf3403e160 "/usr/local/bin/qemu-system-x86_64") at util/virfilecache.c:323 #12 0x00007fcf3e23f9ee in virQEMUCapsCacheLookup ( cache=cache@entry=0x7fcf3404ddf0, binary=0x7fcf3403e160 "/usr/local/bin/qemu-system-x86_64") at qemu/qemu_capabilities.c:4583 #13 0x00007fcf3e23fc94 in virQEMUCapsInitGuest (guestarch=VIR_ARCH_X86_64, hostarch=VIR_ARCH_X86_64, cache=0x7fcf3404ddf0, caps=0x7fcf3404ded0) at qemu/qemu_capabilities.c:736 #14 virQEMUCapsInit (cache=0x7fcf3404ddf0) at qemu/qemu_capabilities.c:971 #15 0x00007fcf3e28d3a0 in virQEMUDriverCreateCapabilities ( driver=driver@entry=0x7fcf3401cbd0) at qemu/qemu_conf.c:1101 #16 0x00007fcf3e2d0be2 in qemuStateInitialize (privileged=true, callback=<optimized out>, opaque=<optimized out>) at qemu/qemu_driver.c:851 #17 0x00007fcf4e2b0bff in virStateInitialize (privileged=<optimized out>, callback=0x564b91ad18a0 <daemonInhibitCallback>, opaque=0x564b933e4540) at libvirt.c:662 #18 0x0000564b91ad18fb in daemonRunStateInit (opaque=0x564b933e4540) at remote/remote_daemon.c:802 #19 0x00007fcf4e17ec02 in virThreadHelper (data=<optimized out>) at util/virthread.c:206 ---Type <return> to continue, or q <return> to quit--- #20 0x00007fcf4ca26494 in start_thread (arg=0x7fcf3b315700) at pthread_create.c:333 #21 0x00007fcf4c768acf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 Thread 16 (Thread 0x7fcf3bb16700 (LWP 14795)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x00007fcf4e17ee36 in virCondWait (c=c@entry=0x564b933f1bc8, m=m@entry=0x564b933f1ba0) at util/virthread.c:154 #2 0x00007fcf4e17f983 in virThreadPoolWorker ( opaque=opaque@entry=0x564b933d6d80) at util/virthreadpool.c:124 #3 0x00007fcf4e17ebd8 in virThreadHelper (data=<optimized out>) at util/virthread.c:206 #4 0x00007fcf4ca26494 in start_thread (arg=0x7fcf3bb16700) at pthread_create.c:333 #5 0x00007fcf4c768acf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 Thread 15 (Thread 0x7fcf3c317700 (LWP 14794)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x00007fcf4e17ee36 in virCondWait (c=c@entry=0x564b933f1bc8, ---Type <return> to continue, or q <return> to quit--- m=m@entry=0x564b933f1ba0) at util/virthread.c:154 #2 0x00007fcf4e17f983 in virThreadPoolWorker ( opaque=opaque@entry=0x564b933d6cc0) at util/virthreadpool.c:124 #3 0x00007fcf4e17ebd8 in virThreadHelper (data=<optimized out>) at util/virthread.c:206 #4 0x00007fcf4ca26494 in start_thread (arg=0x7fcf3c317700) at pthread_create.c:333 #5 0x00007fcf4c768acf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 Thread 14 (Thread 0x7fcf3cb18700 (LWP 14793)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x00007fcf4e17ee36 in virCondWait (c=c@entry=0x564b933f1bc8, m=m@entry=0x564b933f1ba0) at util/virthread.c:154 #2 0x00007fcf4e17f983 in virThreadPoolWorker ( opaque=opaque@entry=0x564b933d6c00) at util/virthreadpool.c:124 #3 0x00007fcf4e17ebd8 in virThreadHelper (data=<optimized out>) at util/virthread.c:206 #4 0x00007fcf4ca26494 in start_thread (arg=0x7fcf3cb18700) at pthread_create.c:333 #5 0x00007fcf4c768acf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 ---Type <return> to continue, or q <return> to quit--- Thread 13 (Thread 0x7fcf3d319700 (LWP 14792)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x00007fcf4e17ee36 in virCondWait (c=c@entry=0x564b933f1bc8, m=m@entry=0x564b933f1ba0) at util/virthread.c:154 #2 0x00007fcf4e17f983 in virThreadPoolWorker ( opaque=opaque@entry=0x564b933d6b20) at util/virthreadpool.c:124 #3 0x00007fcf4e17ebd8 in virThreadHelper (data=<optimized out>) at util/virthread.c:206 #4 0x00007fcf4ca26494 in start_thread (arg=0x7fcf3d319700) at pthread_create.c:333 #5 0x00007fcf4c768acf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 Thread 12 (Thread 0x7fcf3db1a700 (LWP 14791)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x00007fcf4e17ee36 in virCondWait (c=c@entry=0x564b933f1bc8, m=m@entry=0x564b933f1ba0) at util/virthread.c:154 #2 0x00007fcf4e17f983 in virThreadPoolWorker ( opaque=opaque@entry=0x564b933d6a60) at util/virthreadpool.c:124 #3 0x00007fcf4e17ebd8 in virThreadHelper (data=<optimized out>) ---Type <return> to continue, or q <return> to quit--- at util/virthread.c:206 #4 0x00007fcf4ca26494 in start_thread (arg=0x7fcf3db1a700) at pthread_create.c:333 #5 0x00007fcf4c768acf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 Thread 11 (Thread 0x7fcf41df5700 (LWP 14790)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x00007fcf4e17ee36 in virCondWait (c=c@entry=0x564b933e49b8, m=m@entry=0x564b933e48f0) at util/virthread.c:154 #2 0x00007fcf4e17f944 in virThreadPoolWorker ( opaque=opaque@entry=0x564b933d5ca0) at util/virthreadpool.c:124 #3 0x00007fcf4e17ebd8 in virThreadHelper (data=<optimized out>) at util/virthread.c:206 #4 0x00007fcf4ca26494 in start_thread (arg=0x7fcf41df5700) at pthread_create.c:333 #5 0x00007fcf4c768acf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 Thread 10 (Thread 0x7fcf425f6700 (LWP 14789)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 ---Type <return> to continue, or q <return> to quit--- #1 0x00007fcf4e17ee36 in virCondWait (c=c@entry=0x564b933e49b8, m=m@entry=0x564b933e48f0) at util/virthread.c:154 #2 0x00007fcf4e17f944 in virThreadPoolWorker ( opaque=opaque@entry=0x564b933d5b00) at util/virthreadpool.c:124 #3 0x00007fcf4e17ebd8 in virThreadHelper (data=<optimized out>) at util/virthread.c:206 #4 0x00007fcf4ca26494 in start_thread (arg=0x7fcf425f6700) at pthread_create.c:333 #5 0x00007fcf4c768acf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 Thread 9 (Thread 0x7fcf42df7700 (LWP 14788)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x00007fcf4e17ee36 in virCondWait (c=c@entry=0x564b933e49b8, m=m@entry=0x564b933e48f0) at util/virthread.c:154 #2 0x00007fcf4e17f944 in virThreadPoolWorker ( opaque=opaque@entry=0x564b933d5bc0) at util/virthreadpool.c:124 #3 0x00007fcf4e17ebd8 in virThreadHelper (data=<optimized out>) at util/virthread.c:206 #4 0x00007fcf4ca26494 in start_thread (arg=0x7fcf42df7700) at pthread_create.c:333 #5 0x00007fcf4c768acf in clone () ---Type <return> to continue, or q <return> to quit--- at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 Thread 8 (Thread 0x7fcf435f8700 (LWP 14787)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x00007fcf4e17ee36 in virCondWait (c=c@entry=0x564b933e49b8, m=m@entry=0x564b933e48f0) at util/virthread.c:154 #2 0x00007fcf4e17f944 in virThreadPoolWorker ( opaque=opaque@entry=0x564b933d5b00) at util/virthreadpool.c:124 #3 0x00007fcf4e17ebd8 in virThreadHelper (data=<optimized out>) at util/virthread.c:206 #4 0x00007fcf4ca26494 in start_thread (arg=0x7fcf435f8700) at pthread_create.c:333 #5 0x00007fcf4c768acf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 Thread 7 (Thread 0x7fcf43df9700 (LWP 14786)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x00007fcf4e17ee36 in virCondWait (c=c@entry=0x564b933e49b8, m=m@entry=0x564b933e48f0) at util/virthread.c:154 #2 0x00007fcf4e17f944 in virThreadPoolWorker ( opaque=opaque@entry=0x564b933d5d60) at util/virthreadpool.c:124 ---Type <return> to continue, or q <return> to quit--- #3 0x00007fcf4e17ebd8 in virThreadHelper (data=<optimized out>) at util/virthread.c:206 #4 0x00007fcf4ca26494 in start_thread (arg=0x7fcf43df9700) at pthread_create.c:333 #5 0x00007fcf4c768acf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 Thread 6 (Thread 0x7fcf445fa700 (LWP 14785)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x00007fcf4e17ee36 in virCondWait (c=c@entry=0x564b933e4918, m=m@entry=0x564b933e48f0) at util/virthread.c:154 #2 0x00007fcf4e17f983 in virThreadPoolWorker ( opaque=opaque@entry=0x564b933d5b00) at util/virthreadpool.c:124 #3 0x00007fcf4e17ebd8 in virThreadHelper (data=<optimized out>) at util/virthread.c:206 #4 0x00007fcf4ca26494 in start_thread (arg=0x7fcf445fa700) at pthread_create.c:333 #5 0x00007fcf4c768acf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 Thread 5 (Thread 0x7fcf44dfb700 (LWP 14784)): #0 pthread_cond_wait@@GLIBC_2.3.2 () ---Type <return> to continue, or q <return> to quit--- at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x00007fcf4e17ee36 in virCondWait (c=c@entry=0x564b933e4918, m=m@entry=0x564b933e48f0) at util/virthread.c:154 #2 0x00007fcf4e17f983 in virThreadPoolWorker ( opaque=opaque@entry=0x564b933d5bc0) at util/virthreadpool.c:124 #3 0x00007fcf4e17ebd8 in virThreadHelper (data=<optimized out>) at util/virthread.c:206 #4 0x00007fcf4ca26494 in start_thread (arg=0x7fcf44dfb700) at pthread_create.c:333 #5 0x00007fcf4c768acf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 Thread 4 (Thread 0x7fcf455fc700 (LWP 14783)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x00007fcf4e17ee36 in virCondWait (c=c@entry=0x564b933e4918, m=m@entry=0x564b933e48f0) at util/virthread.c:154 #2 0x00007fcf4e17f983 in virThreadPoolWorker ( opaque=opaque@entry=0x564b933d5ca0) at util/virthreadpool.c:124 #3 0x00007fcf4e17ebd8 in virThreadHelper (data=<optimized out>) at util/virthread.c:206 #4 0x00007fcf4ca26494 in start_thread (arg=0x7fcf455fc700) at pthread_create.c:333 ---Type <return> to continue, or q <return> to quit--- #5 0x00007fcf4c768acf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 Thread 3 (Thread 0x7fcf45dfd700 (LWP 14782)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x00007fcf4e17ee36 in virCondWait (c=c@entry=0x564b933e4918, m=m@entry=0x564b933e48f0) at util/virthread.c:154 #2 0x00007fcf4e17f983 in virThreadPoolWorker ( opaque=opaque@entry=0x564b933d5d60) at util/virthreadpool.c:124 #3 0x00007fcf4e17ebd8 in virThreadHelper (data=<optimized out>) at util/virthread.c:206 #4 0x00007fcf4ca26494 in start_thread (arg=0x7fcf45dfd700) at pthread_create.c:333 #5 0x00007fcf4c768acf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 Thread 2 (Thread 0x7fcf465fe700 (LWP 14781)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x00007fcf4e17ee36 in virCondWait (c=c@entry=0x564b933e4918, m=m@entry=0x564b933e48f0) at util/virthread.c:154 #2 0x00007fcf4e17f983 in virThreadPoolWorker ( ---Type <return> to continue, or q <return> to quit--- opaque=opaque@entry=0x564b933d5e20) at util/virthreadpool.c:124 #3 0x00007fcf4e17ebd8 in virThreadHelper (data=<optimized out>) at util/virthread.c:206 #4 0x00007fcf4ca26494 in start_thread (arg=0x7fcf465fe700) at pthread_create.c:333 #5 0x00007fcf4c768acf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 Thread 1 (Thread 0x7fcf4eb4dd40 (LWP 14780)): #0 0x00007fcf4c75f67d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x00007fcf4e122684 in poll (__timeout=-1, __nfds=6, __fds=<optimized out>) at /usr/include/x86_64-linux-gnu/bits/poll2.h:46 #2 virEventPollRunOnce () at util/vireventpoll.c:641 #3 0x00007fcf4e121371 in virEventRunDefaultImpl () at util/virevent.c:327 #4 0x00007fcf4e243e4d in virNetDaemonRun (dmn=0x564b933e4540) at rpc/virnetdaemon.c:850 #5 0x0000564b91ad0d5e in main (argc=<optimized out>, argv=<optimized out>) at remote/remote_daemon.c:1460 Thank you in advance!

1 0

[libvirt-users] Amazon s3 as libvirt storage pool
by Shashwat shagun 11 Jun '18

11 Jun '18

Namaste, i want to use Minio (open source amazon S3 compatible object storage) as libvirt storage pool. is such thing possible? i apologize if this is a stupid question. if not then can i write some driver for it? -- Regards, Shashwat Shagun

2 1

[libvirt-users] Are more then one overlay possible without recieving a "Permission denied"?
by Xen Mann 07 Jun '18

07 Jun '18

I've created a backing chain like this. FirstFollr.ovl is an overlay to Base.img and so on. Base.img (ok - Win 10 Installation starting) FirstFloor.ovl (ok - Win 10 Installation starting) SecondFloor.ovl (permission denied -> Base.img) => assumed Bug Roof.ovl (permission denied -> Base.img) => assumed Bug Using virsh / virt-manager, I can only start Base and FirstFloor. Starting Second and Roof are failing. What's wrong? Details are described in: https://bugzilla.redhat.com/show_bug.cgi?id=1588373 System infos: Compiled against library: libvirt 4.0.0 Using library: libvirt 4.0.0 Using API: QEMU 4.0.0 Running hypervisor: QEMU 2.11.1 Ubuntu 18.04 LTS (Dell Precission Tower 3620)

1 0

[libvirt-users] List-Archives ...
by thg 07 Jun '18

07 Jun '18

Hi everybody, actually I wanted to search the list archive, before asking, but unfortunately I don't "get" it: $ gunzip 2018-May.txt.gz gunzip: 2018-May.txt.gz: not in gzip format It seems, that in every archive-file there is always one message in plaintext and then a big binary block. Any hint? Thanks a lot, -- kind regards, thg

3 2

[libvirt-users] Vlan on vhostuser interfaces
by Pradeep K.S 06 Jun '18

06 Jun '18

I am planning to configure vlan on vhostuser interfaces in the libvirt xml, it throws out error. Does this configuration is supported ? I can install higher version if required. *Error:* unsupported configuration: an interface of type 'vhostuser' is requesting a vlan tag, but that is not supported for this type of connection *Libvirt version:* [redhathost@qemu]# libvirtd --version libvirtd (libvirt) 3.2.0 *Qemu version:* QEMU emulator version 2.9.0(qemu-kvm-ev-2.9.0-16.el7_4.11.1) *Domain XML* <interface type='vhostuser'> <mac address='02:3a:c1:4b:a1:0a'/> <source type='unix' path='/tmp/vhost-test' mode='server'/> <vlan trunk='yes'> <tag id='3' nativeMode='tagged'/> <tag id='4'/> </vlan> <model type='virtio'/> <driver rx_queue_size='1024'> <host mrg_rxbuf='on'/> </driver> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> -- Thanks and Regards, Pradeep.K.S.

2 1

[libvirt-users] Make discard='unmap' the default?
by Ian Pilcher 01 Jun '18

01 Jun '18

Is it possible to make discard='unmap' the default for virtio-scsi disks? (Related, is it possible to make virtio-scsi the default disk type, rather than virtio-blk?) Thanks! -- ======================================================================== Ian Pilcher arequipeno(a)gmail.com -------- "I grew up before Mark Zuckerberg invented friendship" -------- ========================================================================

3 6

[libvirt-users] virRandomBits - not very random
by Brian Rak 01 Jun '18

01 Jun '18

I just ran into an issue where I had about 30 guests get duplicate mac addresses assigned. These were scattered across 30 different machines. Some debugging revealed that: 1) All the host machines were restarted within a couple seconds of each other 2) All the host machines had fairly similar libvirtd pids (within ~100 PIDs of each other) 3) Libvirt seeds the RNG using 'time(NULL) ^ getpid()' This perfectly explains why I saw so many duplicate mac addresses. Why is the RNG seed such a predictable value? Surely there has to be a better source of a random seed then the timestamp and the pid? The PID seems to me to be a very bad source of any randomness. I just ran a test across 60 of our hosts. 43 of them shared their PID with at least one other machine.

7 13

[libvirt-users] Two Node Cluster
by Cobin Bluth 01 Jun '18

01 Jun '18

Hello Libvirt Users, I would like to setup a two node bare-metal cluster. I need to guidance on the network configuration. I have attached a small diagram, the same diagram can be seen here: https://i.imgur.com/SOk6a6G.png I would like to configure the following details: - Each node has a DHCP enabled guest network where VMs will run. (eg, *192.168.1.0/24 <http://192.168.1.0/24>* for Host1, and *192.168.2.0/24 <http://192.168.2.0/24>* for Host2) - Any guest in Host1 should be able to ping guests in Host2, and vice versa. - All guests have routes to reach the open internet (so that '*yum update*' will work "out-of-the-box") - Each node will be able to operate fully if the other physical node fails. (no central DHCP server, etc) - I would like to *add more physical nodes later* when I need the resources. This is what I have done so far: - Installed latest Ubuntu 18.04, with latest version of libvirt and supporting software from ubuntu's apt repo. - Each node can reach the other via its own eth0. - Each node has a working vxlan0, which can ping the other via its vxlan0, so it looks like the vxlan config is working. (I used *ip link add vxlan0 type vxlan...*) - Configured route on Host1 like so: *ip route add 192.168.2.0/24 <http://192.168.2.0/24> via 172.20.0.1* - Configured route on Host2 also: *ip route add 192.168.1.0/24 <http://192.168.1.0/24> via 172.20.0.2* - All guests on Host1 (and Host1) can ping eth0 and vxlan0 on Host2, and vice versa, yay. - Guests on Host1 *cannot* ping guests on Host2, I suspect because the the default NAT config of the libvirt network. So, at this point I started to search for tutorials or more information/documentation, but I am a little overwhelmed by the sheer amount of information, as well as a lot of "stale" information on blogs etc. I have learned that I can *virsh net-edit default*, and then change it to an "open" network:* <forward mode='open'/>* After doing this, the guests cannot reach outside their own network, nor reach the internet, so I assume that I would need to add some routes, or something else to get the network functioning like I want it. There is also *<forward mode="route"/>*, but I dont fully understand the scenarios where one would need an *open* or a *route* forward mode. I have also shied away from using openvswitch, and have opted for ifupdown2. (I have taken most of my inspiration from this blog post: https://joejulian.name/post/how-to-configure-linux-vxlans-with-multiple-uni… ) Some questions that I have for the mailing list, any help would be greatly appreciated: - Is my target configuration of a KVM cluster uncommon? Do you see drawbacks of this setup, or does it go against "typical convention"? - Would my scenario be better suited for an "*open*" network or a "*route*" network? - What would be the approach to complete this setup?

3 4