- Users - libvirt List Archives

libivrt client using python on windows
by Talha Jawaid 14 Oct '20

14 Oct '20

Hello, I want to run a python script on Windows to remotely control libvirt running on a (Linux) server. This was all working fine while prototyping stuff on the server but now I am having some trouble installing the python module on windows ("pip install" fails). I struggled through getting it to COMPILE but then ran into linking issues. Seems like the actual libvirt library is needed to run (and even compile) on Windows? Is there a prebuilt package somewhere that I could get? Do I really need the whole libvirt library or is there a client only package? How could I go about accomplishing my goal here? Thanks, -Talha

2 1

unable to find any master var store for loader error
by daggs 14 Oct '20

14 Oct '20

Greetings, I have the following machine: https://dpaste.com/5BPA3F77F which I'm trying to boot in uefi. /etc/libvirt/qemu.conf looks like this: https://dpaste.com/B3SFHUY6R and the ovmf files exists in the path, see: # ll /usr/share/edk2-ovmf/OVMF_CODE.fd /usr/share/edk2-ovmf/OVMF_VARS.fd /usr/share/edk2-ovmf/OVMF_CODE.secboot.fd /usr/share/edk2-ovmf/OVMF_VARS.secboot.fd -rw-r--r-- 1 root root 1966080 Aug 21 14:32 /usr/share/edk2-ovmf/OVMF_CODE.fd -rw-r--r-- 1 root root 1966080 Aug 21 14:32 /usr/share/edk2-ovmf/OVMF_CODE.secboot.fd -rw-r--r-- 1 root root 131072 Aug 21 14:32 /usr/share/edk2-ovmf/OVMF_VARS.fd -rw-r--r-- 1 root root 131072 Aug 21 14:32 /usr/share/edk2-ovmf/OVMF_VARS.secboot.fd when I try to start the machine, I get this error: error: Failed to start domain vm1 error: operation failed: unable to find any master var store for loader: /usr/share/edk2-ovmf/OVMF_CODE.fd libvirt version is 6.7.0 and qemu version is 5.1.0 any idea how to fix this issue? Thanks. Dagg.

3 6

Re: Encrypting boot partition Libvirt not showing the OS booting up
by john doe 13 Oct '20

13 Oct '20

On 10/12/2020 11:53 AM, john doe wrote: > On 10/12/2020 11:37 AM, Peter Krempa wrote: >> On Mon, Oct 12, 2020 at 11:27:20 +0200, john doe wrote: >>> Hi, thank you for your answer, I'm sending this privatly as you asked >>> for private information. >>> Can I ask you to keep those information private? >>> >>> On 10/12/2020 10:29 AM, Peter Krempa wrote: >>>> On Mon, Oct 12, 2020 at 10:03:15 +0200, john doe wrote: >>>>> Hi, >>>>> >>>>> I have installed Debian Buster with encrypted LVM so apon installation >>>>> my root partition is encrypted. >>>>> So far so good but as soon as I encrypt the boot partition, after >>>>> reboot >>>>> the OS won't start. >>>>> If I start the drive directly with qemu, it works but it looks like >>>>> Libvirt is somehow not able to deel with it. >>>> >>>> This is not enough information to diagnose the problem. >>>> >>>> We'll need the following: >>>> >>>> 1) Did you encrypt the partition using the debian installer >>>> >>> >>> No, I did it after installation following the instructions at (1). >>> >>>> 2) what vm XML you used: >>>> a) during installation >>> >>> The domain xml file was created by virt-install with the following >>> command: >>> $ virsh destroy try01; virsh undefine try01; time virt-install >>> --name=try01 --ram=1024 --noreboot --cpuset=auto --cpu host >>> --vcpus=1,maxvcpus=4 --disk=path=/mnt/usbkey01/machines/try/try01,size=6 >>> --graphic none --pxe --os-variant=debian10 --network >>> bridge=br0,mac=0e:35:32:84:c3:f3 --filesystem >>> type=mount,mode=mapped,source=/mnt/usbkey01/public,target=public_dir >>> >>>> b) when trying to finally boot the vm >>>> >>> >>> Attached as 'try01.xml' obtained by doing 'virsh dumpxml try01 > >>> try01.xml'. >>> >>>> 3) what qemu command line you've used at the point you claim it worked >>>> >>> >>> qemu-system-x86_64 -drive file=/mnt/usbkey01/machines/try/try01 -m 1024 >>> -boot c -accel kvm -machine q35 -nographic >>> >>>> 4) what is the error/final state when the VM fails to boot with libvirt >>>> >>> >>> After having encrypted the boot partition: >>> >>> $virsh console try01 >>> root@0e-35-32-84-c3-f3:# [ 208.513259] watchdog: watchdog0: watchdog >>> did not stop! >>> [ 208.855971] reboot: Restarting system >>> >>> >>> $ qemu-system-x86_64 -drive file=/mnt/usbkey01/machines/try/try01 -m >>> 1024 -boot c -accel kvm -machine q35 -nographic >>> SeaBIOS (version 1.12.0-1) >>> >>> >>> iPXE (http://ipxe.org) 00:02.0 C980 PCI2.10 PnP PMM+3FF8FE80+3FECFE80 >>> C980 >>> >>> >>> >>> Booting from Hard Disk... >>> Attempting to decrypt master key... >>> Enter passphrase for hd0,msdos1 (43a322dfc8ba4628b80afc66d49642a7): >>> >>> >>> As you can see above, if I invoked qemu directly, I get prompted for the >>> boot passthrase but I'm not getting it when using libvirt. >> >> Okay, so the root cause ... or "problem" here is that you don't see the >> console via 'virsh console' after the guest OS rebooted. >> >> My suspicion according to the VM XML is that the VM restart triggered a >> restart of the qemu process and thus our internal handler of the console >> passthrough disconnected. >> >> Please try a "virsh destroy $VM" if the VM is running/stuck waiting for >> the password without actually showing it and then start it using >> >> virsh start --console $VM >> >> This will start it and connect to the console immediately. >> >> Please report your findings, we might want to discuss what happens when >> a console is connected and the guest uses a setting of: >> >> <on_reboot>restart</on_reboot> >> >> when the VM is rebooted. >> > > Still no luck: > > $ virsh destroy try01; virsh start --console try01 > error: Failed to destroy domain try01 > error: Requested operation is not valid: domain is not running > > Domain try01 started > Connected to domain try01 > Escape character is ^] > > > > > > I did not modify anything during the time I sent my answer and seeing > yours. > I sent privately the requested xml file to 'Peter Krempa <pkrempa(a)redhat.com>'. Peter Krempa 's privately answered me back suggesting to add the following in the domain xml file: <bios useserial='yes'/> under <os> such as ... <os> <type arch='x86_64' machine='pc-q35-3.1'>hvm</type> <boot dev='hd'/> <bios useserial='yes'/> </os> This does not help at all and still give the output sent previously. -- John Doe

5 12

Re: Attached disk blockpull
by Peter Krempa 13 Oct '20

13 Oct '20

This is a libvirt question, so asking it on the qemu-block might not get you an answer that quick, ... or ever if I didn't notice your other question also addressed incorrectly. [adding libvirt-users(a)redhat.com to cc] On Tue, Sep 01, 2020 at 10:57:34 -0400, Yoonho Park wrote: > I am trying to perform a blockpull on an attached disk, but I cannot do > this using "virsh attach-disk" specifying a new, empty overlay file created > with "qemu-img create". The VM does not pick up the backing_file path from Could you please elaborate on the exact steps? specifically the arguments for qemu-img create. My feeling is that you didn't specify the backing image format (-F) when creating the overlay, but it's hard to tell from this very sparse question. > the qcow2 overlay file, and there seems to be no way to specify the backing > path through the attach-disk command itself. Instead the backing path has virsh attach-disk is a syntax-sugar wrapper which generates the XML document which is in fact used to attach disk. You can use virsh attach-disk --print-xml to see what would be used. > to be specified in the xml file used to create the VM, which precludes > attaching a new disk to a running VM. Is this a bug? Is it possible to using virsh attach-device allows you to pass in a whole <devices> subelement such as <disk> with any configuration you are able to specify when defining the XML. The virsh attach-disk is limited to just "basic" config options. > attach a disk to a running VM, and specify its backing path, using qemu > directly? This is with qemu 4.2.0 and libvirt 6.0.0.

1 0

Failed to get udev device for syspath '/sys/devices/virtual/dmi/id'
by Mathieu Tarral 12 Oct '20

12 Oct '20

Hi, I'm facing an issue with libvirt and the LIBXL driver, failing when searching for DMI data in /sys. info : libvirt version: 5.0.0, package: 4+deb10u1 (Guido Günther <agx(a)sigxcpu.org> Thu, 05 Dec 2019 00:22:14 +0100) error : udevGetDMIData:1719 : internal error: Failed to get udev device for syspath '/sys/devices/virtual/dmi/id' or '/sys/class/dmi/id' error : libxlDriverConfigNew:1803 : Unable to configure libxl's memory management parameters error : virStateInitialize:662 : Initialization of LIBXL state driver failed: internal error: Failed to get udev device for syspath '/sys/devices/virtual/dmi/id' or '/sys/class/dmi/id' error : daemonRunStateInit:799 : Driver state initialization failed The relevant function udevGetDMIData in libvirt: https://github.com/libvirt/libvirt/blob/cb09344a2cccc0cc9bcefa3cb53d7af45ba… I don't understand what's happening, as this initialization failure only happens when I boot on the Xen kernel. Also, the /sys/class/dmi* paths are not exposed on Xen. Note: Running on Xen 4.12.1 Any ideas ? Thanks !

4 5

Encrypting boot partition Libvirt not showing the OS booting up
by john doe 12 Oct '20

12 Oct '20

Hi, I have installed Debian Buster with encrypted LVM so apon installation my root partition is encrypted. So far so good but as soon as I encrypt the boot partition, after reboot the OS won't start. If I start the drive directly with qemu, it works but it looks like Libvirt is somehow not able to deel with it. What am I missing? -- John Doe

2 1

Building libvirt library without libvirtd or virsh
by Román González 09 Oct '20

09 Oct '20

Hello there, I'm trying to play with musl and libvirt to see if I'm able to build a libvirt client binary without dynamic lib dependencies. I have two questions: 1) to your knowledge, is this exercise futile? 2) Do you know if there is a way to *only* compile the library bits? I want to reduce the number of dependencies in the build, and only construct the libvirt libraries, not libvirtd nor virsh. Thanks in advance for any help you can provide. Roman.-

3 4

Is it possible that "virsh destroy" does not stop a domain ?
by Lentes, Bernd 08 Oct '20

08 Oct '20

Hi, Is it possible that "virsh destroy" does not stop a domain ? I'm asking because i have some domains running in a two-node HA-Cluster (pacemaker). And sometimes one node get fenced (killed) because it couldn't stop a domain. That's very ugly. This is also the reason why i asked before what "virsh destroy" really does ? IIRC a kill -9 can't terminate a process which is in "D" state (uninterruptible sleep). So if the process of the domain is in "D" state, it can't be finished. Right ? Pacemaker tries to shutdown or destroy a domain with a resource agent, which is a shell script, similar to an init script. Here is an excerp from the resource agent for virtual domains: force_stop() { local out ex translate local status=0 ocf_log info "Issuing forced shutdown (destroy) request for domain ${DOMAIN_NAME}." out=$(LANG=C virsh $VIRSH_OPTIONS destroy ${DOMAIN_NAME} 2>&1) # hier wird die domain destroyed ex=$? translate=$(echo $out|tr 'A-Z' 'a-z') echo >&2 "$translate" case $ex$translate in *"error:"*"domain is not running"*|*"error:"*"domain not found"*|\ *"error:"*"failed to get domain"*) : ;; # unexpected path to the intended outcome, all is well sucess [!0]*) ocf_exit_reason "forced stop failed" # <============ fail of destroy seems to be possible return $OCF_ERR_GENERIC ;; 0*) while [ $status != $OCF_NOT_RUNNING ]; do VirtualDomain_status status=$? done ;; esac return $OCF_SUCCESS } The function force_stop is responsible for stop/destroy the domain. And it cares about a non-working "virsh destroy". Is there a developer who can explain what "virsh destroy" really does ? Or is there another ML for the developers ? Bernd -- Bernd Lentes Systemadministration Institute for Metabolism and Cell Death (MCD) Building 25 - office 122 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/mcd stay healthy Helmholtz Zentrum MÃ¼nchen Helmholtz Zentrum MÃ¼nchen

3 3

PCI Passthrough and Surprise Hotplug
by Marc Smith 08 Oct '20

08 Oct '20

Hi, I'm using QEMU/KVM on RHEL (CentOS) 7.8.2003: # cat /etc/redhat-release CentOS Linux release 7.8.2003 I'm passing an NVMe drive into a Linux KVM virtual machine (<type arch='x86_64' machine='pc-i440fx-rhel7.0.0'>hvm</type>) which has the following 'hostdev' entry: <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x42' slot='0x00' function='0x0'/> </source> <alias name='hostdev5'/> <rom bar='off'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x0f' function='0x0'/> </hostdev> This all works fine during normal operation, but I noticed when we remove the NVMe drive (surprise hotplug event), the PCIe EP then seems "stuck"... here we see the link-down event on the host (when the drive is removed): [67720.177959] pciehp 0000:40:01.2:pcie004: Slot(238-1): Link Down [67720.178027] vfio-pci 0000:42:00.0: Relaying device request to user (#0) And naturally, inside of the Linux VM, we see the NVMe controller drop: [ 1203.491536] nvme nvme1: controller is down; will reset: CSTS=0xffffffff, PCI_STATUS=0xffff [ 1203.522759] blk_update_request: I/O error, dev nvme1n2, sector 33554304 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 [ 1203.560505] nvme 0000:01:0f.0: Refused to change power state, currently in D3 [ 1203.561104] nvme nvme1: Removing after probe failure status: -19 [ 1203.583506] Buffer I/O error on dev nvme1n2, logical block 4194288, async page read [ 1203.583514] blk_update_request: I/O error, dev nvme1n1, sector 33554304 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 We see this EP is found at IOMMU group '76': # readlink /sys/bus/pci/devices/0000\:42\:00.0/iommu_group ../../../../kernel/iommu_groups/76 And it is no longer bound to the 'vfio-pci' driver (expected) on the host. I was expecting to see all of the FD's to the /dev/vfio/NN character devices closed, but it seems they are still open: # lsof | grep "vfio/76" qemu-kvm 242364 qemu 70u CHR 235,4 0t0 3925324 /dev/vfio/76 qemu-kvm 242364 242502 qemu 70u CHR 235,4 0t0 3925324 /dev/vfio/76 qemu-kvm 242364 242511 qemu 70u CHR 235,4 0t0 3925324 /dev/vfio/76 qemu-kvm 242364 242518 qemu 70u CHR 235,4 0t0 3925324 /dev/vfio/76 qemu-kvm 242364 242531 qemu 70u CHR 235,4 0t0 3925324 /dev/vfio/76 qemu-kvm 242364 242533 qemu 70u CHR 235,4 0t0 3925324 /dev/vfio/76 qemu-kvm 242364 242542 qemu 70u CHR 235,4 0t0 3925324 /dev/vfio/76 qemu-kvm 242364 242550 qemu 70u CHR 235,4 0t0 3925324 /dev/vfio/76 qemu-kvm 242364 242554 qemu 70u CHR 235,4 0t0 3925324 /dev/vfio/76 SPICE 242364 242559 qemu 70u CHR 235,4 0t0 3925324 /dev/vfio/76 After the NVMe drive was removed for 100 seconds, we see the following kernel messages on the host: [67820.179749] vfio-pci 0000:42:00.0: Relaying device request to user (#10) [67900.272468] vfio_bar_restore: 0000:42:00.0 reset recovery - restoring bars [67900.272652] vfio_bar_restore: 0000:42:00.0 reset recovery - restoring bars [67900.319284] vfio_bar_restore: 0000:42:00.0 reset recovery - restoring bars I also noticed these messages related to the EP that is down currently that seem to continue indefinitely on the host (every 100 seconds): [67920.181882] vfio-pci 0000:42:00.0: Relaying device request to user (#20) [68020.184945] vfio-pci 0000:42:00.0: Relaying device request to user (#30) [68120.188209] vfio-pci 0000:42:00.0: Relaying device request to user (#40) [68220.190397] vfio-pci 0000:42:00.0: Relaying device request to user (#50) [68320.192575] vfio-pci 0000:42:00.0: Relaying device request to user (#60) But perhaps that is expected behavior. In any case, the problem comes when I re-insert the NVMe drive into the system... on the host, we see the link-up event: [68418.595101] pciehp 0000:40:01.2:pcie004: Slot(238-1): Link Up But the device is not bound to the 'vfio-pci' driver: # ls -ltr /sys/bus/pci/devices/0000\:42\:00.0/driver ls: cannot access /sys/bus/pci/devices/0000:42:00.0/driver: No such file or directory And appears to fail when attempting to bind to it manually: # echo "0000:42:00.0" > /sys/bus/pci/drivers/vfio-pci/bind -bash: echo: write error: No such device Device is enabled: # cat /sys/bus/pci/devices/0000\:42\:00.0/enable 1 So, wondering if this is expected behavior? Stopping the VM and starting it (virsh destroy/start) allows the device to work in the VM again, but for my particular use case, this is not an option. Need the surprise hotplug functionality to work with the PCIe EP passed into the VM. And perhaps this is an issue elsewhere (eg, vfio-pci). Any tips/suggestions on where to dig more would be appreciated. Thanks for your time. --Marc

2 2

[libvirt-users] Live migrate + change interface name
by Marc Roos 07 Oct '20

07 Oct '20

Is it possible to do a live migrate of a guest, having on the from host a source_device=eth2 and to host a source_dev=eth1?

2 4

time in domain very unstable
by Lentes, Bernd 07 Oct '20

07 Oct '20

Hi, i have a domain (SLES 10 SP4) running with KVM. Time is very wrong when booting unless ntp synchronizes. What can i do ? Bernd -- Bernd Lentes Systemadministration Institute for Metabolism and Cell Death (MCD) Building 25 - office 122 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/mcd stay healthy Helmholtz Zentrum MÃ¼nchen Helmholtz Zentrum MÃ¼nchen

2 3

Unable to start or create any vm's on the qemu/kvm network
by muke101 06 Oct '20

06 Oct '20

Hi, for some reason my libvirt install has suddenly stopped working with any vm's on the qemu/kvm network, and I can't seem to figure out how to fix it or even anything that indicates what's causing the problem. I've posted my problem to discord servers, subreddits, irc's and the server fault stackexchange to no avail, so I'm hoping that if I share my stackexchnage post here someone might be able to take a look and figure out the problem? Here's the post with more details: https://serverfault.com/questions/1036370/error-when-starting-vm-on-the-qem… Any help would be appreciated, thanks.

2 1

what does "virsh destroy" really ?
by Lentes, Bernd 06 Oct '20

06 Oct '20

Hi, what does "virsh destroy" with the domain ? Send a kill -9 to the process ? Bernd -- Bernd Lentes Systemadministration Institute for Metabolism and Cell Death (MCD) Building 25 - office 122 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/mcd stay healthy Helmholtz Zentrum MÃ¼nchen Helmholtz Zentrum MÃ¼nchen

5 6

Any way to persistently edit a single VM's AppArmor profile?
by Brian Turek 06 Oct '20

06 Oct '20

In order to test a patch I submitted I've been experimenting with "qemu:commandline" to use some newer features for a QEMU host/guest file share. I quickly ran into issues with AppArmor as virt-aa-helper understandably doesn't parse "qemu:commandline" for directories to add to the dynamically generated AppArmor profile. After reading a bunch of documentation, I cannot find a way to persistently edit a single VM's AppArmor profile. virt-aa-helper will respect a pre-existing "/etc/apparmor.d/libvirt/libvirt-<uuid>" file but then delete it when the VM shuts down. virt-aa-helper does not respect pre-existing "/etc/apparmor.d/libvirt/libvirt-<uuid>.files" and will just overwrite it. The best I came up with was to edit "/etc/apparmor.d/abstractions/libvirt-qemu" but that affects ALL QEMU-based VMs whereas I really only need to tweak one profile. I'm an AppArmor novice so I'm hoping there might be some other way to do what I need. Anyone have any ideas? Thank you

1 0

Determining when a guest booted / how long it's been running
by Digimer 01 Oct '20

01 Oct '20

4 6

cant create network with virt-manager
by Marko Horn 28 Sep '20

28 Sep '20

hello list, i cant create an isolated network with the virt-manager. installed version virt-manager 3.0.0 installed version libvirt 6.2.0 output in error-message: Error creating virtual network: internal error: Failed to apply firewall rules /sbin/iptables -w --table filter --insert LIBVIRT_INP --in-interface virbr3 --protocol tcp --destination-port 67 --jump ACCEPT: iptables: No chain/target/match by that name. Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 66, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/createnet.py", line 428, in _async_net_create netobj.create() File "/usr/lib/python3.7/site-packages/libvirt.py", line 3174, in create if ret == -1: raise libvirtError ('virNetworkCreate() failed', net=self) libvirt.libvirtError: internal error: Failed to apply firewall rules /sbin/iptables -w --table filter --insert LIBVIRT_INP --in-interface virbr3 --protocol tcp --destination-port 67 --jump ACCEPT: iptables: No chain/target/match by that name any ideas? thank you marko -- Mitten drin statt nur Datei!

2 2

Help on Meson build Error
by Wei Wang 25 Sep '20

25 Sep '20

Seems it didn't appear on the mailing list, resent it. Hi folks, I'm trying to build libvirt using meson with the latest upstream libvirt, but the compilation fails: (followed on https://libvirt.org/compiling.html, not sure if any dependencies are missed. I checked, src/util/libvirt_util.a.p does not exist.) FAILED: src/util/libvirt_util.a.p/glibcompat.c.o .... In file included from ../src/util/glibcompat.c:19: ./config.h:1026:10: fatal error: config-post.h: No such file or directory FAILED: src/util/libvirt_util.a.p/virfirmware.c.o In file included from ../src/util/virarch.c:22: ./config.h:1026:10: fatal error: config-post.h: No such file or directory FAILED: src/util/libvirt_util.a.p/viraudit.c.o In file included from ../src/util/viraudit.c:22: ./config.h:1026:10: fatal error: config-post.h: No such file or directory Any help is appreciated. Thanks, Wei

4 20

[libvirt] SRIOV configuration
by Edward Haas 25 Sep '20

25 Sep '20

Hello, We encountered a problem while testing SRIOV on kubevirt [1]: We are currently using the Device "hostdev" generic options to pass-through the VF to the guest. It is not done through the "interface" (with type hostdev) because that option requires access to the PF which is not available in our case (the VF is moved to the container namespace where libvirt runs, but not the PF, however libvirt attempts to access the PF and fails). The PCI addresses appearing on the domxml are not the same as the ones mappend/detected in the VM itself. I compared the domxml on the host and the lspci in the VM while the VM runs. This occurs only when SRIOV is defined, messing up also the other "regular" vnics. Somehow, everything comes up and runs (with the SRIOV interface as well) on the first boot (even though the PCI addresses are not in sync), but additional boots cause the VM to mess up the interfaces (not all are detected). This is how the domxml hostdev section looks like: ``` <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x3b' slot='0x0a' function='0x4'/> </source> <alias name='hostdev0'/> <address type='pci' domain='0x0000' bus='0x06' slot='0x01' function='0x0'/> </hostdev> ``` Is there something we are missing or we misconfigured? Tested with 6.0.0-16.fc31 My second question is: Can libvirt avoid accessing the PF (as we do not need mac and other options). 1. https://github.com/kubevirt/kubevirt Thanks, Edy.

3 2

consuming pre-created tap - with multiqueue
by Miguel Duarte de Mora Barroso 24 Sep '20

24 Sep '20

Hello, On KubeVirt, we are trying to pre-create a tap device, then instruct libvirt to consume it (via the type=ethernet , managed='no' attributes). It works as expected, **unless** when we create a multi-queue tap device. The difference when creating the tap device is that we set the multi-queue flag; libvirt throws the following error when consuming it: ``` LibvirtError(Code=38, Domain=0, Message='Unable to create tap device tap0: Invalid argument') ``` After digging a bit on the libvirt code (we're using libvirt 6.0.0), I see this on the logs (immediately before the error): {"component":"virt-launcher","level":"info","msg":"Enabling IFF_VNET_HDR","pos":"virNetDevProbeVnetHdr:190","subcomponent":"libvirt","thread":"33" ,"timestamp":"2020-09-22T10:34:29.335000Z"} I do not understand how it can try to set the VNET_HDR flag, since I have not set it when I created it, which, as per [0] should only happen when requested. Here's the tap device I'm creating: (output of `ip tuntap show`) - tap0: tap persist0x100 user 107 group 107 I'm confused by this, since on [1] it says that only one flag can be used (persist *or* vnet_hdr). Also, from my limited understanding, in order to open a pre-created tap device, it must be set to persistent. Am I right (in the sense that these flags cannot co-exist) ? If so, why would libvirt be setting the VNET_HDR flag on the tap device ? [0] - https://github.com/libvirt/libvirt/blob/v6.0.0/src/util/virnetdevtap.c#L261 [1] - https://github.com/libvirt/libvirt/blob/v6.0.0/src/util/virnetdevtap.c#L209

2 3

Help on meson build
by Wei Wang 24 Sep '20

24 Sep '20

Hi folks, I'm trying to build libvirt using meson with the latest upstream libvirt, but the compilation fails: (followed on https://libvirt.org/compiling.html, not sure if any dependencies are missed) FAILED: src/util/libvirt_util.a.p/glibcompat.c.o .... In file included from ../src/util/glibcompat.c:19: ./config.h:1026:10: fatal error: config-post.h: No such file or directory FAILED: src/util/libvirt_util.a.p/virfirmware.c.o In file included from ../src/util/virarch.c:22: ./config.h:1026:10: fatal error: config-post.h: No such file or directory FAILED: src/util/libvirt_util.a.p/viraudit.c.o In file included from ../src/util/viraudit.c:22: ./config.h:1026:10: fatal error: config-post.h: No such file or directory Any help is appreciated. Thanks, Wei

1 0

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

23 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

Fwd: can't define domain - error: cannot open /dev/null: Operation not permitted
by Lentes, Bernd 21 Sep '20

21 Sep '20

> Von: "Lentes, Bernd" <bernd.lentes(a)helmholtz-muenchen.de> > Datum: 21. September 2020 um 18:38:48 MESZ > An: Martin Kletzander <mkletzan(a)redhat.com> > Betreff: Aw: can't define domain - error: cannot open /dev/null: Operation not permitted > > Hi Martin, > > after configuring the logging and a restart of the service the problem dissapeared !?! > > Bernd > > Bernd Lentes > > > Am 21.09.2020 um 10:02 schrieb Martin Kletzander <mkletzan(a)redhat.com>: > > > > On Sun, Sep 20, 2020 at 01:09:51PM +0200, Lentes, Bernd wrote: > >> Hi, > >> > > > > Hi, I'll start with the usual... > > > >> i have a two-node cluster running on SLES 12 with pacemaker. > >> The cluster refused to start the domains on one node. > >> So i took some of the domains out of the cluster and tried to start it manually. > >> This is what happened: > >> > >> virsh # define /mnt/share/vm_documents-oo.xml > >> error: Failed to define domain from /mnt/share/vm_documents-oo.xml > >> error: cannot open /dev/null: Operation not permitted > >> > >> Same with another domain. > >> > > > > What does the XML look like? What do the logs[0] say? > > > >> On the other node domains are defined and started without problems. > > > > Are the configs (libvirtd.conf and qemu.conf) the same on both nodes? > > > > Have a nice day, > > Martin > > > > [0] https://libvirt.org/kbase/debuglogs.html > > > >> Permissions on /dev and /dev/null are the same: > >> > >> ha-idg-1:/mnt/share # ll -d /dev > >> drwxr-xr-x 25 root root 5420 Sep 17 20:47 /dev > >> ha-idg-1:/mnt/share # ll /dev/null > >> crw-rw-rw- 1 root root 1, 3 Aug 24 14:39 /dev/null > >> > >> ha-idg-2:/mnt/share # ll -d /dev > >> drwxr-xr-x 25 root root 5340 Sep 9 10:31 /dev > >> ha-idg-2:/mnt/share # ll /dev/null > >> crw-rw-rw- 1 root root 1, 3 Aug 24 15:48 /dev/null > >> > >> ha-idg-1 is the one causing trouble. > >> Both systems SLES 12 SP4, same patchlevel. > >> livirt is: > >> ha-idg-1:/mnt/share # rpm -qa|grep -i libvirt > >> libvirt-daemon-driver-storage-iscsi-4.0.0-8.15.2.x86_64 > >> libvirt-libs-4.0.0-8.15.2.x86_64 > >> python-libvirt-python-4.0.0-2.34.x86_64 > >> libvirt-daemon-driver-nwfilter-4.0.0-8.15.2.x86_64 > >> libvirt-glib-1_0-0-0.2.1-1.2.x86_64 > >> typelib-1_0-LibvirtGLib-1_0-0.2.1-1.2.x86_64 > >> libvirt-admin-4.0.0-8.15.2.x86_64 > >> libvirt-daemon-driver-storage-4.0.0-8.15.2.x86_64 > >> libvirt-daemon-driver-storage-core-4.0.0-8.15.2.x86_64 > >> libvirt-daemon-driver-storage-scsi-4.0.0-8.15.2.x86_64 > >> libvirt-client-4.0.0-8.15.2.x86_64 > >> libvirt-daemon-driver-nodedev-4.0.0-8.15.2.x86_64 > >> libvirt-daemon-driver-storage-logical-4.0.0-8.15.2.x86_64 > >> libvirt-daemon-driver-qemu-4.0.0-8.15.2.x86_64 > >> libvirt-daemon-driver-secret-4.0.0-8.15.2.x86_64 > >> libvirt-daemon-driver-storage-rbd-4.0.0-8.15.2.x86_64 > >> libvirt-daemon-driver-interface-4.0.0-8.15.2.x86_64 > >> libvirt-daemon-4.0.0-8.15.2.x86_64 > >> libvirt-daemon-driver-network-4.0.0-8.15.2.x86_64 > >> libvirt-daemon-driver-storage-mpath-4.0.0-8.15.2.x86_64 > >> libvirt-daemon-qemu-4.0.0-8.15.2.x86_64 > >> libvirt-daemon-config-network-4.0.0-8.15.2.x86_64 > >> libvirt-daemon-driver-storage-disk-4.0.0-8.15.2.x86_64 > >> > >> Any ideas ? > >> Maybe a restart would help, but it's Linux, not Windows ... > >> I'd like to understand what's going wrong. > >> > >> Thanks. > >> > >> > >> Bernd > >> -- > >> > >> Bernd Lentes > >> Systemadministration > >> Institute for Metabolism and Cell Death (MCD) > >> Building 25 - office 122 > >> 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/mcd > >> > >> stay healthy > >> Helmholtz Zentrum MÃ¼nchen > >> > >> Helmholtz Zentrum MÃ¼nchen > >> > >> Helmholtz Zentrum Münche Helmholtz Zentrum Münche

1 0

Fwd: can't define domain - error: cannot open /dev/null: Operation not permitted
by Lentes, Bernd 21 Sep '20

21 Sep '20

> Von: "Lentes, Bernd" <bernd.lentes(a)helmholtz-muenchen.de> > Datum: 21. September 2020 um 18:38:48 MESZ > An: Martin Kletzander <mkletzan(a)redhat.com> > Betreff: Aw: can't define domain - error: cannot open /dev/null: Operation not permitted > Helmholtz Zentrum M��nchen Helmholtz Zentrum M��nchen

1 0

can't define domain - error: cannot open /dev/null: Operation not permitted
by Lentes, Bernd 21 Sep '20

21 Sep '20

Hi, i have a two-node cluster running on SLES 12 with pacemaker. The cluster refused to start the domains on one node. So i took some of the domains out of the cluster and tried to start it manually. This is what happened: virsh # define /mnt/share/vm_documents-oo.xml error: Failed to define domain from /mnt/share/vm_documents-oo.xml error: cannot open /dev/null: Operation not permitted Same with another domain. On the other node domains are defined and started without problems. Permissions on /dev and /dev/null are the same: ha-idg-1:/mnt/share # ll -d /dev drwxr-xr-x 25 root root 5420 Sep 17 20:47 /dev ha-idg-1:/mnt/share # ll /dev/null crw-rw-rw- 1 root root 1, 3 Aug 24 14:39 /dev/null ha-idg-2:/mnt/share # ll -d /dev drwxr-xr-x 25 root root 5340 Sep 9 10:31 /dev ha-idg-2:/mnt/share # ll /dev/null crw-rw-rw- 1 root root 1, 3 Aug 24 15:48 /dev/null ha-idg-1 is the one causing trouble. Both systems SLES 12 SP4, same patchlevel. livirt is: ha-idg-1:/mnt/share # rpm -qa|grep -i libvirt libvirt-daemon-driver-storage-iscsi-4.0.0-8.15.2.x86_64 libvirt-libs-4.0.0-8.15.2.x86_64 python-libvirt-python-4.0.0-2.34.x86_64 libvirt-daemon-driver-nwfilter-4.0.0-8.15.2.x86_64 libvirt-glib-1_0-0-0.2.1-1.2.x86_64 typelib-1_0-LibvirtGLib-1_0-0.2.1-1.2.x86_64 libvirt-admin-4.0.0-8.15.2.x86_64 libvirt-daemon-driver-storage-4.0.0-8.15.2.x86_64 libvirt-daemon-driver-storage-core-4.0.0-8.15.2.x86_64 libvirt-daemon-driver-storage-scsi-4.0.0-8.15.2.x86_64 libvirt-client-4.0.0-8.15.2.x86_64 libvirt-daemon-driver-nodedev-4.0.0-8.15.2.x86_64 libvirt-daemon-driver-storage-logical-4.0.0-8.15.2.x86_64 libvirt-daemon-driver-qemu-4.0.0-8.15.2.x86_64 libvirt-daemon-driver-secret-4.0.0-8.15.2.x86_64 libvirt-daemon-driver-storage-rbd-4.0.0-8.15.2.x86_64 libvirt-daemon-driver-interface-4.0.0-8.15.2.x86_64 libvirt-daemon-4.0.0-8.15.2.x86_64 libvirt-daemon-driver-network-4.0.0-8.15.2.x86_64 libvirt-daemon-driver-storage-mpath-4.0.0-8.15.2.x86_64 libvirt-daemon-qemu-4.0.0-8.15.2.x86_64 libvirt-daemon-config-network-4.0.0-8.15.2.x86_64 libvirt-daemon-driver-storage-disk-4.0.0-8.15.2.x86_64 Any ideas ? Maybe a restart would help, but it's Linux, not Windows ... I'd like to understand what's going wrong. Thanks. Bernd -- Bernd Lentes Systemadministration Institute for Metabolism and Cell Death (MCD) Building 25 - office 122 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/mcd stay healthy Helmholtz Zentrum MÃ¼nchen Helmholtz Zentrum MÃ¼nchen

2 1

redirecting guest serial to file on the host
by daggs 21 Sep '20

21 Sep '20

Greetings, I have a vm to which I can access using virsh console vm1/ I'd like in addition to be able to dump the serial of the vm in to a file on the host. I've found this https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/ht… but it seems that the first second example which might be suited to what I need doesn't work as I get an empty file: here are my serial config for the vm: <serial type='pty'> <source path='/dev/pts/2'/> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> <alias name='serial0'/> </serial> <serial type='file'> <source path='/var/log/router-serial.log'/> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> <alias name='serial1'/> </serial> <console type='pty' tty='/dev/pts/2'> <source path='/dev/pts/2'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> what might be wrong in the above? Dagg.

2 1