- Users - libvirt List Archives

Re: [libvirt-users] disable libvirt-nwfilter
by Michal Privoznik 07 May '19

07 May '19

[Please keep the list CC-ed as it may help somebody from future when searching for solution to the same problem] On 5/6/19 6:08 PM, nakata(a)geekpit.org wrote: > Am 2019-05-06 16:26, schrieb Michal Privoznik: >> On 5/6/19 3:44 PM, nakata(a)geekpit.org wrote: >>> Hi, >>> >>> i want to disable the nwfilter functionality of libvirt. >>> It's surely nice for some people, nevertheless i don't want libvirt >>> to alter any netfilter rules, neither i want the according >>> functionality even available. >> >> It's not only NWFilter that will inject firewall rules. Depending on >> configuration it might also be the default network. >> >>> I know about nwfilter-undefine, but what i'm looking for is an option >>> to globally disable this functionality at all. Some config flag or >>> similar. >>> How can i achieve that? >> >> Unless you have a domain <interface/> defined so that it uses a >> nwfilter then no firwall rules are added by nwfilter code. >> >> If you still want to remove nwfilter module then just uninstall it, >> e.g. via: >> >> dnf remove libvirt-daemon-driver-nwfilter libvirt-daemon-config-nwfilter >> >> Michal > > Hi, > > me again. > Another question libvirt is adding chains. Where do i disable these: > > chains are LIBVIRT-{FWO,FWX,FWI, INP, OUT} > > These are absolutely and explicit unwanted. > Adding new rich features for folks is a fine thing, but i need an opt out. > Please, how do i get rid of it? As I've said, there are two sources which cause libvirt to insert FW rules. By uninstalling nwfilter module you've eliminated one. But since you're still able to run the domain this step was useless because your domain doesn't have nwfilter configured for any of its <interface/>-s and thus nwfilter module did nothing but sit there. The other module that is inserting FW rules is network module. Currently, when libvirtd is starting it reads all the configs of defined networks. If a NATed network is found then it creates those LIBVIRT-* chains and when the network is started then all the rules will be placed into those chains to not contaminate config set by sysadmin. There is patch to postpone creating the chains unitl network actually is starting: https://www.redhat.com/archives/libvir-list/2019-April/msg01547.html So your options here are: a) undefine all NATed networks (typically there's 'default' network) b) uninstall network module (but this will render all domains using <interface type='network'/> unable to start). As an extension to a) you can have a network with <forward mode='open'/> which preserves all the advantages of having a libvirt network but does not install any FW rules. Of course, any comments to aforementioned patch are welcome too. Michal

1 0

[libvirt-users] Autodetecting backing file properties when using vol-create-as
by Gionatan Danti 06 May '19

06 May '19

Hi all, experimenting with vol-create-as, I think it should autodetect some data - filesize and backing file format, specifically. However, the current implementation require us to specify both filesize and backing file format. Considering that qemu-img already autodetects these data, there are any reason for the lack of autodetect by libvirt? Should I open a bugzilla issue? Below you can find a practical example of what I mean. System is CentOS Linux release 7.6.1810 (Core) with libvirt-4.5.0-10.el7_6.4.x86_64 Please let me know if I am missing something. Thanks. # create base file [root@singularity images]# qemu-img create base.qcow2 8G -f qcow2 Formatting 'base.qcow2', fmt=qcow2 size=8589934592 cluster_size=65536 lazy_refcounts=off refcount_bits=16 [root@singularity images]# qemu-img info base.qcow2 image: base.qcow2 file format: qcow2 virtual size: 8.0G (8589934592 bytes) disk size: 17K cluster_size: 65536 Format specific information: compat: 1.1 lazy refcounts: false refcount bits: 16 corrupt: false # create overlay1.qcow2 via qemu-img; note how backing file format is autodetected ("-f qcow2" regards the overlay file itself) [root@singularity images]# qemu-img create -b /var/lib/libvirt/images/base.qcow2 overlay1.qcow2 -f qcow2 Formatting 'overlay1.qcow2', fmt=qcow2 size=8589934592 backing_file=/var/lib/libvirt/images/base.qcow2 cluster_size=65536 lazy_refcounts=off refcount_bits=16 [root@singularity images]# qemu-img info overlay1.qcow2 image: overlay1.qcow2 file format: qcow2 virtual size: 8.0G (8589934592 bytes) disk size: 17K cluster_size: 65536 backing file: /var/lib/libvirt/images/base.qcow2 Format specific information: compat: 1.1 lazy refcounts: false refcount bits: 16 corrupt: false # try the same with virsh vol-create-as; note how you must specify filesize and the backing file format is *wrong* (leading to an unusable overlay disk) [root@singularity images]# virsh vol-create-as default overlay2.qcow2 8G --format qcow2 --backing-vol /var/lib/libvirt/images/base.qcow2 Vol overlay2.qcow2 created [root@singularity images]# qemu-img info overlay2.qcow2 image: overlay2.qcow2 file format: qcow2 virtual size: 8.0G (8589934592 bytes) disk size: 17K cluster_size: 65536 backing file: /var/lib/libvirt/images/base.qcow2 backing file format: raw Format specific information: compat: 0.10 refcount bits: 16 -- 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

1 1

[libvirt-users] disable libvirt-nwfilter
by nakata＠geekpit.org 06 May '19

06 May '19

Hi, i want to disable the nwfilter functionality of libvirt. It's surely nice for some people, nevertheless i don't want libvirt to alter any netfilter rules, neither i want the according functionality even available. I know about nwfilter-undefine, but what i'm looking for is an option to globally disable this functionality at all. Some config flag or similar. How can i achieve that? greetings

2 1

[libvirt-users] VM: Unable to enable scatter-gather / tx-checksumming / tcp-segmentation offload
by Harsh Gondaliya 06 May '19

06 May '19

In my Linux VM, I am unable to change scatter-gather / tx-checksumming / TCP-segmentation offload features by ethtool command. I am using virtio nic with vhostuser port backend. It shows me an error: Cannot change tx-checksumming Cannot change scatter-gather Cannot change tcp-segmentation offload Could not change any device features Ony running command ethtool -k ens3, I get the following: [image: image.png] If there is something that needs to be changed in the domain XML itself then please guide me what changes to do?

2 2

[libvirt-users] Running all my virtual machines with a low priority
by R. Diez 02 May '19

02 May '19

Hi all: I have an Ubuntu 18.04 system. What is the easiest way to run all of my virtual machines with a low priority? Say a "nice" level of 15. I just do not want my virtual machines to have too much of an impact in any other processes on the system. Thanks in advance, rdiez

3 8

[libvirt-users] NUMA revisited
by Patrick Meyer 02 May '19

02 May '19

Moin libvirters, I'm looking into the current numa settings for a large-ish libvirt/qemu based setup and I ended up having a couple of questions: 1) Has kernel.numa_balancing completely replaced numad or is there still a time and place for numad when we have a modern kernel? 2) Should I pin vCPUs to numa nodes and/or use numatune at all, when using kernel.numa_balancing? 3) The libvirt domain xml elements for vcpu and numatune.memory have placement options. According to the docs setting them to auto will query numad for a good placements. Should I keep numad running just for this? 4) Should I still expose the numa topology via cpu.numa.cell if I use the auto placement for vcpu and numatune? 5) Does the cpus attribute in the cpu.numa.cell elements reference vCPU cores or the real physical CPU cores? Most examples reference them as ranges, which confuses me as on my numa hosts node0 has cores 0,2,4.. and node1 the others. I'd like to benchmark a couple of different options using our production workloads once I actually have grasp what combinations could make any sense. Maybe somebody would like to share the cpu/memory/numa settings they ended up with and why? Thanks a lot, Patrick Meyer

1 0

[libvirt-users] Unable to have TSO GSO feature in VM
by Harsh Gondaliya 02 May '19

02 May '19

I am trying to turn ON TSO in my Ubuntu Virtual machine but it gives me the following error: [image: image.png] Also on doing *ethtool -k ens3* all the features are marked as [fixed]. How to use libvirt to configure VM to have TSO?

1 0

[libvirt-users] Cloning a volume via storage XML
by Weller, Lennart 30 Apr '19

30 Apr '19

Hello everyone, After the Bug with libvirt was found and fixed by Michal I am now looking for a way to actually do the task I intended to do. I cannot find any information if it is possible to clone a base-volume a la vol- clone for ceph rbd. As I posted in my addendum to the first post here I thought something like this volume xml would do the job: <volume> <name>coreos00.disk</name> <capacity unit="bytes">9116319744</capacity> <target> <format type="raw"></format> <permissions> <mode>644</mode> </permissions> </target> <backingStore> <path>vmdisks/coreos_2023</path> <format type="raw"></format> </backingStore> </volume> But even with the fix applied this simply creates an empty volume of the given size. Granted this has no information about the snapshot so I was sceptical that this would be enough in the first place. If the vol-clone is not an option right now via volume xml it's not that wild as I could just patch the terraform-libvirt-provider to do the task beforehand but I wanted to know if it there exists an option for libvirt to do it automatically when provided with an xml. I can't find any options in the storage xml documentation so my guess would be no. Kind regards, Lennart Weller

1 1

[libvirt-users] libvirtd via unix socket using system uri
by lameventanas＠gmail.com 30 Apr '19

30 Apr '19

I want to run libvirtd as a special user, and allowing users that belong to a special group to connect via qemu+unix:///system (eg: unix socket). I did everything necessary to do so: created a libvirt user and group, added the libvirt user to the kvm group, added my normal user to the libvirt group, and made sure the socket is owned by libvirt:libvirt with permissions set to 770. libvirtd starts successfully, but when I try to connect as the normal user I get this error: bash$ virsh --connect qemu+unix://system error: failed to connect to the hypervisor error: invalid argument: using unix socket and remote server 'system' is not supported. A trace shows virsh is not even trying to open the socket. I want to use the socket because I just need local connectivity and don't want to run sasl and set up certificates for this, but at the same time want to run libvirtd as a dedicated user. Is there any reason to prevent libvirt from being used like this?

4 10

[libvirt-users] Error connecting to hypervisor
by Sukrit Bhatnagar 29 Apr '19

29 Apr '19

Hi, I have compiled and installed libvirt from git checkout and started libvirtd service. The version is 5.3.0 and I have done system-wide installation. When I do a `virsh list`, I get the following error: error: failed to connect to the hypervisor error: Unable to encode message header Similarly, the libvirtd instance shows the following error: 2019-04-23 21:36:57.777+0000: 1807: info : libvirt version: 5.3.0 2019-04-23 21:36:57.777+0000: 1807: info : hostname: dell 2019-04-23 21:36:57.777+0000: 1807: error : virNetSocketReadWire:1803 : End of file while reading data: Input/output error Furthermore, virnetmessagetest show the following error: $ VIR_TEST_DEBUG=1 ./virnetmessagetest TEST: virnetmessagetest 1) Message Header Encode ... libvirt: XML-RPC error : Unable to encode message header FAILED 2) Message Header Decode ... libvirt: XML-RPC error : Unable to decode message length FAILED 3) Message Payload Encode ... libvirt: XML-RPC error : Unable to encode message header FAILED 4) Message Payload Decode ... libvirt: XML-RPC error : Unable to decode message length FAILED 5) Message Payload Stream Encode ... libvirt: XML-RPC error : Unable to encode message header FAILED I am also compiling qemu from source and the virsh commands ran fine when I was using libvirt 4.7.0 from Fedora repository. Any ideas how I can solve this issue? Thanks, Sukrit

3 3

[libvirt-users] Libvirt pool cannot see or create rbd clones
by Weller, Lennart 29 Apr '19

29 Apr '19

Hello everyone, To increase my odds of finding an answer I also wanted to ask here. This is my post from serverfault[1] in verbatim: While trying to get a cloned disk running from my OS snapshot I run into the problem that Libvirt cannot see existing images cloned from a snapshot. Created via: # rbd -p vmdisks clone vmdisks/coreos_2023@base vmdisks/coreos00.disk The base image has the one snapshot 'base' and is protected. The cloned disk is created just fine: # rbd -p vmdisks info coreos00.disk rbd image 'coreos00.disk': size 8.49GiB in 2174 objects order 22 (4MiB objects) block_name_prefix: rbd_data.48a99c6b8b4567 format: 2 features: layering flags: create_timestamp: Thu Apr 25 14:46:52 2019 parent: vmdisks/coreos_2023@base overlap: 8.49GiB I temporarily have Libvirt configured with a rbd pool that uses the ceph admin user. But I cannot see the cloned disk. Just the parent: virsh # vol-list --pool rbd_image_root Name Path --------------------------------------------------------------------- --------- coreos_2023 vmdisks/coreos_2023 If I try to create the cloned image from within virsh I run into the following issue: virsh # vol-clone --pool rbd_image_root coreos_2023 coreos00.disk error: Failed to clone vol from coreos_2023 error: failed to iterate RBD snapshot coreos_2023@base: Operation not permitted Note that this pool uses the Ceph admin user which makes the Operation not permitted a tad odd. Am I missing a configuration option here that would allow for the pool to use clones? I can't find any information on this in the documentation so far. And the source code of libvirt looks like it should support both features. Versions: Libvirt Machine: Ubuntu 18.04 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 Ceph Machine: openSUSE Leap 42.3 Ceph 12.2.5 [1] https://serverfault.com/questions/964586/libvirt-pool-cannot-see-or-create-…

2 2

[libvirt-users] 5.2.0 xen and maxGrantFrames
by Christoph 26 Apr '19

26 Apr '19

Hi libvirt 5.2.0 should support maxGrantFrames setting for xen (changelog). I get ever an error if I use it in the config: <domain type='xen'> <name>satan.chao5.int</name> <uuid>f1f96b1c-fb75-4707-afb7-604d696d29cc</uuid> <memory unit='KiB'>3145728</memory> <currentMemory unit='KiB'>3145728</currentMemory> <vcpu placement='static'>4</vcpu> <bootloader>pygrub</bootloader> <os> <type arch='x86_64' machine='xenpvh'>xenpvh</type> </os> <clock offset='utc' adjustment='reset'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <disk type='block' device='disk'> <driver name='phy' type='raw'/> <source dev='/dev/vg_lilith/lv_satan_root'/> <target dev='xvda' bus='xen'/> </disk> <disk type='block' device='disk'> <driver name='phy' type='raw'/> <source dev='/dev/vg_lilith/lv_satan_home'/> <target dev='xvdb' bus='xen'/> </disk> <disk type='block' device='disk'> <driver name='phy' type='raw'/> <source dev='/dev/vg_lilith/lv_satan_swap'/> <target dev='xvdc' bus='xen'/> </disk> <disk type='block' device='disk'> <driver name='phy' type='raw'/> <source dev='/dev/md10'/> <target dev='xvdd' bus='xen'/> </disk> <disk type='block' device='disk'> <driver name='phy' type='raw'/> <source dev='/dev/disk/by-uuid/6beff9f2-a88c-4d21-86c6-ff90439b4ca3'/> <target dev='xvde' bus='xen'/> </disk> <disk type='block' device='disk'> <driver name='phy' type='raw'/> <source dev='/dev/disk/by-uuid/e19e6e23-b35c-4fae-b34a-0e2835bde74d'/> <target dev='xvdf' bus='xen'/> </disk> <disk type='block' device='disk'> <driver name='phy' type='raw'/> <source dev='/dev/disk/by-uuid/3d50dfab-5ffe-4558-9ab3-36fd504607be'/> <target dev='xvdg' bus='xen'/> </disk> <disk type='block' device='disk'> <driver name='phy' type='raw'/> <source dev='/dev/disk/by-uuid/c4593072-0161-4bdc-b8b6-317fdd23f8ed'/> <target dev='xvdh' bus='xen'/> </disk> <disk type='block' device='disk'> <driver name='phy' type='raw'/> <source dev='/dev/disk/by-uuid/372167e4-c1ea-4ce6-813b-9c57dd4e67a6'/> <target dev='xvdi' bus='xen'/> </disk> <disk type='block' device='disk'> <driver name='phy' type='raw'/> <source dev='/dev/mapper/keys'/> <target dev='xvdz' bus='xen'/> <readonly/> </disk> <controller type='xenbus' index='0' maxGrantFrames='128'/> <interface type='bridge'> <mac address='00:16:3e:05:31:50'/> <source bridge='xenbr5'/> <script path='vif-bridge'/> </interface> <interface type='bridge'> <mac address='00:16:3e:15:31:50'/> <source bridge='xenbr15'/> <script path='vif-bridge'/> </interface> <console type='pty'> <target type='xen' port='0'/> </console> <input type='mouse' bus='xen'/> <input type='keyboard' bus='xen'/> <memballoon model='xen'/> </devices> </domain> What Im doing wrong? -- ------ Greetz

3 3

[libvirt-users] PCI passthrough and abstraction
by Mauricio Tavares 25 Apr '19

25 Apr '19

When you pass a device in the pci chain (after virsh nodedev-dettach'ing it from host) to the guest, how much is passed without being emulated/abstracted?

2 2

[libvirt-users] Live Disk Backup with Active Blockcommit
by Wolf 25 Apr '19

25 Apr '19

Hi! I was reading the Wiki about 'Live Disk Backup with Active Blockcommit, https://wiki.libvirt.org/page/Live-disk-backup-with-active-blockcommit and see that example shown seems to be using two different names for the same file. First showing the current block device in use: $ virsh domblklist vm1 Target Source ------------------------------------------------ vda /export/images/base.qcow2 Then copying the same file for backup: $ cp /export/images/base.img /export/images/copy.img => Is there are reason why the block device first is called 'base.qcow2' and then 'base.img'? I also saw another name that seems to be wrong based on the context. It doesn't have the same implication as my earlier example, as the name of the overlay file is not written in the command itself, but still: ------ $ virsh snapshot-create-as --domain vm1 guest-state1 \ --diskspec vda,file=/export/images/overlay1.qcow2 \ --disk-only --atomic Then: $ virsh domblklist vm1 Target Source ------------------------------------------------ vda /export/images/overlay.qcow2 Now that the backup is finished, perform active blockcommit by live mergning contents of 'overlay1' into base . . . ." ------ => Here it seems like the overlay file first is called ''overlay1.qcow2" and the ' virsh domblklist vm1' command shows that it is actually called: 'overlay.qcow2' And then back to ''overlay1 in the following text: 'mergning contents of 'overlay1' into base' (Where 'mergning' is spelled wrong, but that doesn't affect the logic). => Do I understand all this correctly? I came to this article based on this answer on Serverfault: https://serverfault.com/a/921966 Since I didn't understand the logic of the file changing names, I visited the file linked to in the answer on wiki.libvirt.org and saw that the same was written there. So maybe change these errors in the Wiki if I understand all this correctly? Thanks for input! Best regards, Wolf

2 1

[libvirt-users] JVM crashes during GC
by Sachin Soman 24 Apr '19

24 Apr '19

Hi, Could you tell me if the following is some known issue? While performing the following simple test, I see my JVM crashing (consistently): 1. Open a connection to an ESXi driver/host (passing ConnectAuthDefault instance). 2. Close the connection. 3. Invoke GC When GC is triggered, at some point, some unallocated native memory is being tried to release. That's failing. The error thrown is: java(78745,0x70000241e000) malloc: *** error for object 0x7fd5df561390: pointer being freed was not allocated *** set a breakpoint in malloc_error_break to debug Frames from core dump: frame #0: 0x00007fff5b274b66 libsystem_kernel.dylib`__pthread_kill + 10 frame #1: 0x00007fff5b43f080 libsystem_pthread.dylib`pthread_kill + 333 frame #2: 0x00007fff5b1d01ae libsystem_c.dylib`abort + 127 frame #3: 0x00007fff5b2ce8a6 libsystem_malloc.dylib`free + 521 frame #4: 0x00000001127f43a7 frame #5: 0x00000001127e3ffd frame #6: 0x00000001127e3ffd frame #7: 0x00000001127e3ffd frame #8: 0x00000001127e3ffd frame #9: 0x00000001127e4042 frame #10: 0x00000001127e3ffd frame #11: 0x00000001127e3ffd frame #12: 0x00000001127dc4e7 frame #13: 0x000000010c0e235e libjvm.dylib`JavaCalls::call_helper(JavaValue*, methodHandle*, JavaCallArguments*, Thread*) + 1710 frame #14: 0x000000010c0e2b02 libjvm.dylib`JavaCalls::call_virtual(JavaValue*, KlassHandle, Symbol*, Symbol*, JavaCallArguments*, Thread*) + 356 frame #15: 0x000000010c0e2cae libjvm.dylib`JavaCalls::call_virtual(JavaValue*, Handle, KlassHandle, Symbol*, Symbol*, Thread*) + 74 frame #16: 0x000000010c1208ee libjvm.dylib`thread_entry(JavaThread*, Thread*) + 124 frame #17: 0x000000010c33e84d libjvm.dylib`JavaThread::thread_main_inner() + 155 frame #18: 0x000000010c33ff12 libjvm.dylib`JavaThread::run() + 448 frame #19: 0x000000010c26058a libjvm.dylib`java_start(Thread*) + 246 frame #20: 0x00007fff5b43c661 libsystem_pthread.dylib`_pthread_body + 340 frame #21: 0x00007fff5b43c50d libsystem_pthread.dylib`_pthread_start + 377 frame #22: 0x00007fff5b43bbf9 libsystem_pthread.dylib`thread_start + 13 I have installed Libvirt 5.2.0. Java bindings libvirt-java 0.5.1 JNA 4.0.0 Tested Java environments: Oracle Java 8 and OpenJDK 8 on MAC, OpenJDK 11 on Ubuntu 16 Thanks & Regards Sachin Soman

3 11

[libvirt-users] how to use Libvirt create bridge for vm on Mac OS
by llilulu 23 Apr '19

23 Apr '19

Hi Recently, I install Libvirt and Qemu in my Mac book, I find I can't create a bridge like linux bridge use for my vm, I want to know how to create a bridge on Mac for vm. Thanks.

2 1

Re: [libvirt-users] [libvirt] Why virsh domxml-to-native qemu-argv changes PCI slot number
by Andrea Bolognani 18 Apr '19

18 Apr '19

Moving to libvirt-users where it belongs. On Thu, 2019-04-18 at 06:47 +0000, Tal Attaly wrote: > Hi, > I have bridge type interface defined with slot 3 - > <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> > but after running virsh domxml-to-native qemu-argv I get slot 2- > -netdev tap,fd=21,id=hostnet0 -device e1000,netdev=hostnet0,id=net0,mac=f2:ff:ff:ff:ff:07,bus=pci.0,addr=0x2 > Any idea why it's happen and how to keep the slot number? Libvirt version is 4.5.0 I can reproduce this, and also confirm that it shouldn't happen :) qemuDomainAssignAddresses() is supposed to make sure that any address configured explicitly by the user (or previously by libvirt) is preserved, and it's doing that correctly when it's called from inside qemuDomainDefAssignAddresses(); however, for some reason, by the time we call it again in qemuProcessPrepareDomain() the PCI address for the network interface is no longer set, and so a fresh one gets assigned instead. I'll investigate further and get back to you. > here is the full domain XML - > > <domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> > <name>vm1</name> > <uuid>dbad303e-fc1b-454e-8861-712bf1766a64</uuid> > <memory unit='KiB'>4194304</memory> > <currentMemory unit='KiB'>4194304</currentMemory> > <vcpu placement='static'>1</vcpu> > <os> > <type arch='x86_64' machine='pc-i440fx-2.12'>hvm</type> > <boot dev='hd'/> > </os> > <features> > <acpi/> > <apic/> > </features> > <cpu mode='custom' match='exact' check='partial'> > <model fallback='allow'>SandyBridge-IBRS</model> > </cpu> > <clock offset='utc'> > <timer name='rtc' tickpolicy='catchup'/> > <timer name='pit' tickpolicy='delay'/> > <timer name='hpet' present='no'/> > </clock> > <on_poweroff>destroy</on_poweroff> > <on_reboot>restart</on_reboot> > <on_crash>destroy</on_crash> > <pm> > <suspend-to-mem enabled='no'/> > <suspend-to-disk enabled='no'/> > </pm> > <devices> > <emulator>/qemu/x86_64-softmmu/qemu-system-x86_64</emulator> > <disk type='file' device='disk'> > <driver name='qemu' type='qcow2'/> > <source file='/var/lib/libvirt/images/vm.img'/> > <target dev='hda' bus='ide'/> > <address type='drive' controller='0' bus='0' target='0' unit='0'/> > </disk> > <controller type='usb' index='0' model='ich9-ehci1'> > <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x7'/> > </controller> > <controller type='usb' index='0' model='ich9-uhci1'> > <master startport='0'/> > <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0' multifunction='on'/> > </controller> > <controller type='usb' index='0' model='ich9-uhci2'> > <master startport='2'/> > <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x1'/> > </controller> > <controller type='usb' index='0' model='ich9-uhci3'> > <master startport='4'/> > <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x2'/> > </controller> > <controller type='ide' index='0'> > <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> > </controller> > <controller type='pci' index='0' model='pci-root'/> > <interface type='bridge'> > <mac address='f2:ff:ff:ff:ff:07'/> > <source bridge='br0:'/> > <model type='e1000'/> > <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> > </interface> > <serial type='tcp'> > <source mode='bind' host='10.210.27.119' service='9999'/> > <protocol type='telnet'/> > <target type='isa-serial' port='0'> > <model name='isa-serial'/> > </target> > </serial> > <console type='tcp'> > <source mode='bind' host='10.210.27.119' service='9999'/> > <protocol type='telnet'/> > <target type='serial' port='0'/> > </console> > <input type='mouse' bus='ps2'/> > <input type='keyboard' bus='ps2'/> > <memballoon model='virtio'> > <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> > </memballoon> > </devices> > <qemu:commandline> > <qemu:env name='CONFIG_FILE' value='/opt/cfg/qemu.cfg'/> > </qemu:commandline> > </domain> -- Andrea Bolognani / Red Hat / Virtualization

2 3

[libvirt-users] Failed to probe capabilities on libvirt v5.1.0
by Vladik Romanovsky 12 Apr '19

12 Apr '19

Hi everyone, Unfortunately, I'm facing an issue with libvirt 5.1.0 when probing capabilities. Failed to probe capabilities for /usr/bin/qemu-system-x86_64: internal error: Failed to start QEMU binary /usr/bin/qemu-system-x86_64 for probing: qemu-system-x86_64: cannot create PID file: Cannot open pid file: Permission denied I see that the qmp directory is being created, however, it belongs to root instead of qemu: /var/lib/libvirt/qemu/qmp-U1w6o6: 0 drwx------. 2 root root 6 Apr 11 14:46 qmp-U1w6o6 The user and group are set to "qemu" in /etc/libvirt/qemu.conf I would appreciate any pointers. Thank you! Vladik

2 1

[libvirt-users] Network hooks for ethernet interfaces
by Ruben Kerkhof 12 Apr '19

12 Apr '19

Hi all, I have a hook script, /etc/libvirt/hooks/network, that doesn't seem to be called when I attach an interface with type 'ethernet' with this xml snippet: <interface type='ethernet'> <model type="virtio"/> <source> <ip address="10.100.0.1" prefix="24" peer="10.100.0.10"/> </source> </interface> https://www.libvirt.org/hooks.html#intro says "A network is started or stopped or an interface is plugged/unplugged to/from the network (since 1.2.2)". While I don't have a network defined in xml, I'd expect this to work just as well for 'ethernet' type interfaces. Am I wrong? Kind regards, Ruben Kerkhof

4 7

[libvirt-users] CGroup V2 Support
by ITeng A 10 Apr '19

10 Apr '19

Dear all Does the current version of libvirt support the new cgroup v2 ? I am running KVM qemu VMs on Ubuntu with linux Kernel 4.18 with cgroup v1 and I would like to use Cgroup v2 but we I mount cgroup v2 the libvirt virtualization daemon fail to start with error message that it cant create cgroup /system.slice/libvirtd.service no such file or directory. kind regards, Asraa Ali

2 1

[libvirt-users] Guest interface names not same as configured name
by PR PR 07 Apr '19

07 Apr '19

Hi, I am creating a guest with following description for interfaces in the xml using virsh create xml command. For some reason, the guest interface names in the VM dont match the names specified in the xml. Is there a way to make guest interface names predictable? Following is the qemu version on host dpkg --list | grep -i qemu ii qemu-kvm 1:2.11+dfsg-1ubuntu7.10 amd64 QEMU Full virtualization on x86 hardware <interface type='user'> <mac address='52:54:00:17:0b:e7'/> <guest dev='eth0'/> <model type='e1000'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> <interface type='ethernet'> <mac address='52:54:00:ee:70:34'/> <target dev='net0'/> <guest dev='Ethernet0'/> <model type='rtl8139'/> <alias name='net1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </interface> Thanks

2 2

[libvirt-users] Cannot create PID file
by Nicolás Iglesias 06 Apr '19

06 Apr '19

Hi Fellow users I've just compiled latest libvirt and qemu, both from their respective official repositories. Libvirtd starts perfect, but when I try to start a domain using the virsh console, I get the following: virsh # start --domain win8.1 error: Failed to start domain win8.1 error: internal error: Failed to start QEMU binary /usr/bin/qemu-system-x86_64 for probing: qemu-system-x86_64: cannot create PID file: Cannot open pid file: Permission denied I'm not sure where to look at. Any hint would be much appreciated. Regards, Nicolas Iglesias

2 2

[libvirt-users] Schema
by Maximilian Schieder 06 Apr '19

06 Apr '19

Hey, Is there a Schema of creating a VM (Domain)? Something like: Create Storagepool Init Storagepool Maxi

2 1

[libvirt-users] is it possible to create a snapshot from a guest residing in a plain partition ?
by Lentes, Bernd 04 Apr '19

04 Apr '19

Hi, i can store the disk of a guest in a plain partition which isn't formatted. That's no problem, i did it already several times, although the promised speed increase didn't appear. But is it possible to create from such a guest a snapshot in a .sn file using virsh ? Regards, Bernd -- Bernd Lentes Systemadministration Institut für Entwicklungsgenetik Gebäude 35.34 - Raum 208 HelmholtzZentrum münchen bernd.lentes(a)helmholtz-muenchen.de phone: +49 89 3187 1241 phone: +49 89 3187 3827 fax: +49 89 3187 2294 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 Geschaeftsfuehrung: Prof. Dr. med. Dr. h.c. Matthias Tschoep, Heinrich Bassler, Kerstin Guenther Registergericht: Amtsgericht Muenchen HRB 6466 USt-IdNr: DE 129521671

2 3

[libvirt-users] SEV machines and memory pinning
by Boris Bobrov 04 Apr '19

04 Apr '19

Hello, I am working on implementing SEV support in OpenStack. There are some questions that came up in the discussion of the spec [0] [0] https://review.openstack.org/#/c/641994/ As far as i understand, the memory for SEV machines need to be pinned so that it doesn't migrate to swap and page migration. ROMS, UEFI pflash and video RAM should be pinned too. Initially we planned to use hard_limit of <memtune> element to pin the memory. However, from the discussion in the spec it seems that there is no way to determine a good enough value and that hard_limit should not be used at all. What should be used then? There is a suggestion to use something like this: <memoryBacking> <hugepages> <page size="2" unit="M" nodeset="1"/> </hugepages> <nosharepages/> <locked/> <source type="file"/> <access mode="shared"/> <allocation mode="immediate"/> </memoryBacking> Will it work? Are there any caveats we should remember about with this config? If we can use it, is there anything that would be redundant or not necessary for our case?

2 1