December 2020 - 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

Get Host Capabilities failed: Internal JSON-RPC error: {'reason': 'internal error: Duplicate key'}
by tommy 13 Jan '21

13 Jan '21

Hi,everyone: I got this error in my ovirt env: VDSM ooengh1.tltd.com command Get Host Capabilities failed: Internal JSON-RPC error: {'reason': 'internal error: Duplicate key'} Systemctl message is: Dec 23 20:48:48 ooengh1.tltd.com vdsm[2431]: ERROR Internal server error Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/yajsonrpc/__init__.py", line 345, in _handle_request res = method(**params) File "/usr/lib/python2.7/site-packages/vdsm/rpc/Bridge.py", line 198, in _dynamicMethod result = fn(*methodArgs) File "<string>", line 2, in getCapabilities File "/usr/lib/python2.7/site-packages/vdsm/common/api.py", line 50, in method ret = func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/API.py", line 1371, in getCapabilities c = caps.get() File "/usr/lib/python2.7/site-packages/vdsm/host/caps.py", line 93, in get machinetype.compatible_cpu_models()) File "/usr/lib/python2.7/site-packages/vdsm/common/cache.py", line 43, in __call__ value = self.func(*args) File "/usr/lib/python2.7/site-packages/vdsm/machinetype.py", line 142, in compatible_cpu_models all_models = domain_cpu_models(c, arch, cpu_mode) File "/usr/lib/python2.7/site-packages/vdsm/machinetype.py", line 97, in domain_cpu_models domcaps = conn.getDomainCapabilities(None, arch, None, virt_type, 0) File "/usr/lib/python2.7/site-packages/vdsm/common/libvirtconnection.py", line 131, in wrapper ret = f(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/common/function.py", line 94, in wrapper return func(inst, *args, **kwargs) File "/usr/lib64/python2.7/site-packages/libvirt.py", line 3844, in getDomainCapabilities if ret is None: raise libvirtError ('virConnectGetDomainCapabilities() failed', conn=self) libvirtError: internal error: Duplicate key AnyOne can help me ? Thanks!

2 4

[resent] virt-manager connection fails with 'qemu unexpectedly closed the monitor'
by John Paul Adrian Glaubitz 12 Jan '21

12 Jan '21

Hi! I recently ran into a problem when connecting to libvirtd 6.9.0 on Debian unstable and trying to import an existing image with Windows 7. Upon finishing the wizard and starting the instance, the import process fails with the following error message: Unable to complete install: 'internal error: qemu unexpectedly closed the monitor' Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 65, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/createvm.py", line 2081, in _do_async_install installer.start_install(guest, meter=meter) File "/usr/share/virt-manager/virtinst/install/installer.py", line 731, in start_install domain = self._create_guest( File "/usr/share/virt-manager/virtinst/install/installer.py", line 679, in _create_guest domain = self.conn.createXML(install_xml or final_xml, 0) File "/usr/lib64/python3.8/site-packages/libvirt.py", line 4366, in createXML raise libvirtError('virDomainCreateXML() failed') libvirt.libvirtError: internal error: qemu unexpectedly closed the monitor Since this error message is rather generic, I don't know where to start debugging. Does anyone know how to increase verbosity here to get an error message that might be more helpful? Thanks, Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaubitz(a)debian.org `. `' Freie Universitaet Berlin - glaubitz(a)physik.fu-berlin.de `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913

2 4

Problem with xen hvm DomU
by Christoph 08 Jan '21

08 Jan '21

Hi can someone say me whats wrong in this config: <domain type='xen'> <name>fenrir.chao5.int</name> <uuid>7aedcd03-54e8-4055-8d1b-37dd34194859</uuid> <memory unit='KiB'>2097152</memory> <currentMemory unit='KiB'>2097152</currentMemory> <vcpu placement='static'>2</vcpu> <os> <type arch='x86_64' machine='xenfv'>hvm</type> <loader type='rom'>/usr/lib/xen/boot/hvmloader</loader> <kernel>/usr/lib64/xen/boot/hvmloader</kernel> <boot dev='hd'/> </os> <features> <acpi/> <apic/> <pae/> </features> <clock offset='variable' adjustment='0' basis='localtime'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <disk type='file' device='disk'> <driver name='qemu' type='raw'/> <source file='/dev/vg_astarte/lv_fenrir_root'/> <target dev='hda' bus='ide'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='raw'/> <source file='/dev/vg_astarte/lv_fenrir_swap'/> <target dev='hdb' bus='ide'/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='xenbus' index='0'/> <controller type='ide' index='0'/> <interface type='bridge'> <mac address='00:16:3e:05:30:04'/> <source bridge='xenbr5'/> <script path='vif-bridge'/> <model type='netfront'/> </interface> <interface type='bridge'> <mac address='00:16:3e:04:30:04'/> <source bridge='xenbr4'/> <script path='vif-bridge'/> <model type='netfront'/> </interface> <interface type='bridge'> <mac address='00:16:3e:15:30:04'/> <source bridge='xenbr15'/> <script path='vif-bridge'/> <model type='netfront'/> </interface> <interface type='bridge'> <mac address='00:16:3e:14:30:04'/> <source bridge='xenbr14'/> <script path='vif-bridge'/> <model type='netfront'/> </interface> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='vnc' port='6000' autoport='no' listen='0.0.0.0'> <listen type='address' address='0.0.0.0'/> </graphics> <video> <model type='cirrus' vram='8192' heads='1' primary='yes'/> </video> <memballoon model='xen'/> </devices> </domain> If I try to start it with virsh create... then I see only: error: Failed to create domain from /etc/libvirt/libxl/fenrir.chao5.int.xml error: internal error: libxenlight failed to create new domain 'fenrir.chao5.int' ------ Greetz

2 6

about the script /etc/qemu-ifup with nmcli command
by Yalan Zhang 05 Jan '21

05 Jan '21

Hi, I have tried the qemu-ifup script as below with nmcli command as brctl is deprecated on rhel8, but the guest network can not work. I think the script needs update. Could you please help to have a look? Thank you in advance. 1. prepare a linux bridge on the host named br0; 2. prepare the qemu-ifup script as below: # cat /etc/qemu-ifup #!/bin/bash # A br0 bridge should be already set up. # Compare with: # http://en.wikibooks.org/wiki/QEMU/Networking#qemu-ifup # # For the bridge setup, see: # http://wiki.libvirt.org/page/Networking#Fedora.2FRHEL_Bridging # http://gist.github.com/393525 ip link set "$1" up nmcli c add type bridge-slave ifname $1 con-name $1 master br0 autoconnect yes 3. start vm with below interface setting: # virsh dumpxml rh | grep /interface -B5 <interface type='ethernet'> <mac address='52:54:00:79:ba:dd'/> <script path='/etc/qemu-ifup'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </interface> # virsh start rh Domain rh started 4.check on guest, the interface can not get dhcp ip address; 5. check on host, # nmcli con NAME UUID TYPE DEVICE br0 f68f73c7-10ee-40c1-bb09-3366d11ac896 bridge br0 ... vnet0 90a48d77-dccc-4b59-98f5-09f8cbd62458 ethernet -- # nmcli dev DEVICE TYPE STATE CONNECTION br0 bridge connected br0 ... vnet0 tun unmanaged -- 6. hotplug a bridge type interface and compare the tap devices: # virsh attach-interface rh bridge br0 --model virtio Interface attached successfully # nmcli con NAME UUID TYPE DEVICE br0 f68f73c7-10ee-40c1-bb09-3366d11ac896 bridge br0 vnet1 07c2a1f8-396f-4d5f-b61f-ef2ddb42ed93 tun vnet1 --->the hot-plugged one ... vnet0 90a48d77-dccc-4b59-98f5-09f8cbd62458 ethernet -- ----> the ethernet one # nmcli dev DEVICE TYPE STATE CONNECTION vnet1 tun connected (externally) vnet1 --->the hot-plugged one vnet0 tun unmanaged -- ----> the ethernet one ... 7. from the outputs above, the back-end tun device for ethernet type interface is unmanaged. I don't know how to update the script to fix it. Could you please help? ------- Best Regards, Yalan Zhang IRC: yalzhang

2 2

virt-manager connection fails with 'qemu unexpectedly closed the monitor'
by John Paul Adrian Glaubitz 04 Jan '21

04 Jan '21

Hi! I recently ran into a problem when connecting to libvirtd 6.9.0 on Debian unstable and trying to import an existing image with Windows 7. Upon finishing the wizard and starting the instance, the import process fails with the following error message: Unable to complete install: 'internal error: qemu unexpectedly closed the monitor' Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 65, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/createvm.py", line 2081, in _do_async_install installer.start_install(guest, meter=meter) File "/usr/share/virt-manager/virtinst/install/installer.py", line 731, in start_install domain = self._create_guest( File "/usr/share/virt-manager/virtinst/install/installer.py", line 679, in _create_guest domain = self.conn.createXML(install_xml or final_xml, 0) File "/usr/lib64/python3.8/site-packages/libvirt.py", line 4366, in createXML raise libvirtError('virDomainCreateXML() failed') libvirt.libvirtError: internal error: qemu unexpectedly closed the monitor Since this error message is rather generic, I don't know where to start debugging. Does anyone know how to increase verbosity here to get an error message that might be more helpful? Thanks, Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaubitz(a)debian.org `. `' Freie Universitaet Berlin - glaubitz(a)physik.fu-berlin.de `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913

2 1

Unexplicable permission error when trying to read a qemu firmware file
by Emmanuel Kasper 04 Jan '21

04 Jan '21

Hi I want to create a CoreOS VM following the steps mentioned at https://docs.fedoraproject.org/en-US/fedora-coreos/getting-started, using a Debian 11 (bullseye) system. I am thus creating a VM with the following virt-install command: virt-install --connect="qemu:///system" --name=coreos \ --vcpus=2 --memory=2048 \ --os-variant=fedora29 --import --graphics=none \ --disk="size=10,backing_store=$PWD/fedora-coreos-33.20201201.3.0-qemu.x86_64.qcow2" \ --qemu-commandline="-fw_cfg name=opt/com.coreos/config,file=/tmp/example.ign" which spits some warnings and this mysterious error 2020-12-29T16:52:03.858938Z qemu-system-x86_64: warning: host doesn't support requested feature: MSR(48FH).vmx-exit-load-perf-global-ctrl [bit 12] 2020-12-29T16:52:03.858941Z qemu-system-x86_64: warning: host doesn't support requested feature: MSR(490H).vmx-entry-load-perf-global-ctrl [bit 13] 2020-12-29T16:52:03.864778Z qemu-system-x86_64: -fw_cfg name=opt/com.coreos/config,file=/tmp/example.ign: can't load /tmp/example.ign: Failed to open file “/tmp/example.ign”: Permission denied the file /tmp/example.ign is perfectly world readable, -rw-rw-rw- 1 manu manu 1130 Dec 29 17:23 /tmp/example.ign so I am puzzled at what could cause this permission error. on a RHEL8 system, I had the same error, and was able to fix by setting a security context on the firmware file: sudo semanage fcontext --add --type virt_content_t /tmp/example.ign restorecon /tmp/example.ign now this Debian system does not selinux installed at all. ls -dZ / ? / I could also read the qemu firmware file when using the qemu:///session connection any pointers where to look for ? Emmanuel

2 1

Isolated bridge does not bridge
by Paul van der Vlis 04 Jan '21

04 Jan '21

Hello, I want to do some testing and I have removed two VM's from the bridge what connects them to internet, and added them to another isolated bridge what's not connected to internet. Problem is that I cannot reach the other host in the isolated network. Something like this: virsh shutdown kvm66 virsh shutdown kvm68 brctl delif br0 vnet10 vnet6 # the interfaces of kvm66 and kvm68 brctl addbr br1 brctl addif br1 vnet10 vnet6 Then I've replaced br0 to br1 in the XML of both VM's with "virsh edit". Then I did start the VM's using the serial console (no network): virsh start --console kvm66 virsh start --console kvm68 I cannot ping from one machine to the other. Why?? With regards, Paul -- Paul van der Vlis Linux systeembeheer Groningen https://www.vandervlis.nl/

4 5

How to open listener of Libvirt ?
by tommy 04 Jan '21

04 Jan '21

Hi,every one: My Ubuntu is : 20.04 LTS, and I using libvirtd on it to manage KVM vm, but now I can not open listener function of the libvirtd. SYSTEM SOCKET ACTIVATION The libvirtd daemon is capable of starting in two modes. In the traditional mode, it will create and listen on UNIX sockets itself. If the --listen parameter is given, it will also listen on TCP/IP socket(s), according to the listen_tcp and listen_tls options in /etc/libvirt/libvirtd.conf In socket activation mode, it will rely on systemd to create and listen on the UNIX, and optionally TCP/IP, sockets and pass them as pre-opened file de� scriptors. In this mode, it is not permitted to pass the --listen parameter, and most of the socket related config options in /etc/libvirt/libvirtd.conf will no longer have any effect. To enable TCP or TLS sockets use either $ systemctl start libvirtd-tls.socket Or $ systemctl start libvirtd-tcp.socket But, on my system, there are no such service like libvirtd-tls.socket or libvirtd-tcp.socket. root@ubts1:~# systemctl | grep libvirt libvirt-guests.service loaded active exited Suspend/Resume Running libvirt Guests libvirtd.service loaded active running Virtualization daemon libvirtd-admin.socket loaded active running Libvirt admin socket libvirtd-ro.socket loaded active running Libvirt local read-only socket libvirtd.socket loaded active running Libvirt local socket How can I open the listener ? Thanks！

2 3

cannot get Libvirt/qemu to use secure boot
by Felix Rubio Dalmau 29 Dec '20

29 Dec '20

Hi everybody, I am having serious trouble enabling secure boot via virt-install... and I do not see clearly even where to look for help :-/. Maybe somebody can point me on the right direction? I am running: arch linux edk2-ovmf 202011-1 libvirt 6.5 virt-install 3.2 qemu 5.2 I am creating the domain with virt-install, and the parameters --features smm.state=on --boot loader=/usr/share/ovmf/x64/OVMF_CODE.secboot.fd,nvram.template=/usr/share/ovmf/x64/OVMF_VARS.fd,loader.readonly=yes,loader.type=pflash,loader_secure=yes If I boot into the UEFI I can see there is the menu for the OVMF and Secure Boot available, but when I get into the Secure Boot entry, I only see it is "disabled" and I cannot tick the "Attempt secure boot" box. As far as I understand, by using OVMF_CODE.secboot.f I should already get the default keys working, so I should be good to go to test this setup, but... to no success. Does anybody have any idea on what might be wrong/where can I get help (should this not be the place?) Thank you! Felix

1 1

Manage libvirt actions through netgroups and PolKit
by Gi Actor 26 Dec '20

26 Dec '20

1 0

libvirt-lxc: Permission issue of /proc/net
by John Hurnett 24 Dec '20

24 Dec '20

Hi, I've encountered a problem that some of /proc/net/ files can't be accessed in unprivileged containers, because it is owned by nobody:nogroup (-1:-1) and have 440 permissions. This exact issue was solved in LXC project by unsharing netns: https://github.com/lxc/lxc/commit/5b1e83cbc498cd3edeaf13afa987d530299a35a7 . Maybe it could be similarly fixed on libvirt-lxc? BR, John H.

2 2

AppArmor issue when using gluster storage pool
by Max Schettler 16 Dec '20

16 Dec '20

Hi, I'm trying to run a VM image that's stored on a gluster storage pool which I added to libvirt (5.0.0) on a Debian 10 installation. Whenever I try to boot a gluster-based VM, I get an error message about a missing AppArmor profile. In fact, the corresponding files (/etc/apparmor.d/libvirt/libvirt-{,.files}) are missing. After some tinkering I noticed that the profile for the VM are in fact missing iff there is a gluster-based disk attached to the VM in question. Whenever I remove the disk, the profile files reappear, and when I add it again, they are not present. I am wondering what might cause this, and how I could fix, or work around it, other than outright disabling AppArmor altogether. Thanks and best regards, Max Schettler -- Max Schettler, M.Sc. TKN, TU Berlin, Germany http://www.ccs-labs.org/team/schettler/

1 0

SASL(-1): generic failure: All-whitespace username - from HA/pacemaker
by lejeczek 15 Dec '20

15 Dec '20

Hi guys, I have a HA/pacemaker cluster with VirtualDomain and it all seems to work fine, VMs start & stop, except for live migration. So I thought I'd start here with errors I see, from 'pacemaker': ... All-whitespace username. notice: vpn1_migrate_to_0[977276] error output [ error: authentication failed: Failed to start SASL negotiation: -1 (SASL(-1): generic failure: All-whitespace username.) ] notice: vpn1_migrate_to_0[977276] error output [ ocf-exit-reason:vpn1: live migration to dzien failed: 1 ] notice: Result of migrate_to operation for vpn1 on swir: error notice: swir-vpn1_migrate_to_0:189 [ error: authentication failed: Failed to start SASL negotiation: -1 (SASL(-1): generic failure: All-whitespace username.)\nocf-exit-reason:vpn1: live migration to dzien failed: 1\n ] notice: Result of stop operation for vpn1 on swir: ok Can you shed more light on what virsh/libvirt says there? many thanks, L.

1 0

live migration with authentication - how?
by lejeczek 15 Dec '20

15 Dec '20

Hi guys. I'm trying I assumed something very crude, logic suggested I should try it first: $ virsh migrate reactos qemu+ssh://dzien/system?authfile=/etc/ovirt-hosted-engine/virsh_auth.conf Please enter your authentication name: vdsm@ovirt Please enter your password: As you can see I still get asked for credentials. Is it possible to live migrate that(or some) way, without being asked for those? many thanks, L.

2 2

Libvirt-lxc: iptables not working in containers
by John Hurnett 15 Dec '20

15 Dec '20

Hi, I can't get iptables to work in libvirt-lxc containers. "iptables -L" command shows empty chains. However I tested the same scenario with pure lxc and iptables works as it should. Has anyone experienced that? It seems like a bug, but maybe there is some libvirt xml parameter I am missing? BR

2 1

Installing Kali Linux as Guest OS in KVM Hypervisor
by Kaushal Shriyan 11 Dec '20

11 Dec '20

Hi, I have run the below command to install Kali Linux using linux-2020.4-installer-amd64.iso from https://www.kali.org/downloads/ #virt-install --name kalilinux --memory 4096 --vcpus=2 --location=/linuxkvmaddgbdisk/kali-linux-2020.4-installer-amd64.iso,kernel=install.amd/gtk/vmlinuz,initrd=install.amd/gtk/initrd.gz --network=bridge:br0 --os-type=linux --os-variant=debian9 --graphics=none --extra-args "console=ttyS0" -v --disk path=/linuxkvmaddgbdisk/kalilinux.img,size=50 I am not able to get the root login prompt when I run the below command to set IP and hostname for the guest OS. Am I missing any parameters from the above virt-install command to install Kali Linux as Guest OS in KVM Hypervisor? #virsh console kalilinux Connected to domain kalilinux Escape character is ^] Any help will be highly appreciated. I look forward to hearing from you. Thanks in Advance. Best Regards, Kaushal

4 6

[CFP] Virtualization & IaaS Devroom
by Piotr Kliczewski 11 Dec '20

11 Dec '20

We are excited to announce that the call for proposals is now open for the Virtualization & IaaS devroom at the upcoming FOSDEM 2021, to be hosted virtually on February 6th 2021. This year will mark FOSDEM’s 21th anniversary as one of the longest-running free and open source software developer events, attracting thousands of developers and users from all over the world. Due to Covid-19, FOSDEM will be held virtually this year on February 6th & 7th, 2021. About the Devroom The Virtualization & IaaS devroom will feature session topics such as open source hypervisors and virtual machine managers such as Xen Project, KVM, bhyve, and VirtualBox, and Infrastructure-as-a-Service projects such as KubeVirt, Apache CloudStack, Foreman, OpenStack, oVirt, QEMU and OpenNebula. This devroom will host presentations that focus on topics of shared interest, such as KVM; libvirt; shared storage; virtualized networking; cloud security; clustering and high availability; interfacing with multiple hypervisors; hyperconverged deployments; and scaling across hundreds or thousands of servers. Presentations in this devroom will be aimed at users or developers working on these platforms who are looking to collaborate and improve shared infrastructure or solve common problems. We seek topics that encourage dialog between projects and continued work post-FOSDEM. Important Dates Submission deadline: 20th of December Acceptance notifications: 25th of December Final schedule announcement: 31st of December Recorded presentations upload deadline: 15th of January Devroom: 6th February 2021 Submit Your Proposal All submissions must be made via the Pentabarf event planning site[1]. If you have not used Pentabarf before, you will need to create an account. If you submitted proposals for FOSDEM in previous years, you can use your existing account. After creating the account, select Create Event to start the submission process. Make sure to select Virtualization and IaaS devroom from the Track list. Please fill out all the required fields, and provide a meaningful abstract and description of your proposed session. Submission Guidelines We expect more proposals than we can possibly accept, so it is vitally important that you submit your proposal on or before the deadline. Late submissions are unlikely to be considered. All presentation slots are 30 minutes, with 20 minutes planned for presentations, and 10 minutes for Q&A. All presentations will need to be pre-recorded and put into our system at least a couple of weeks before the event. The presentations should be uploaded by 15th of January and made available under Creative Commons licenses. In the Submission notes field, please indicate that you agree that your presentation will be licensed under the CC-By-SA-4.0 or CC-By-4.0 license and that you agree to have your presentation recorded. For example: "If my presentation is accepted for FOSDEM, I hereby agree to license all recordings, slides, and other associated materials under the Creative Commons Attribution Share-Alike 4.0 International License. Sincerely, <NAME>." In the Submission notes field, please also confirm that if your talk is accepted, you will be able to attend the virtual FOSDEM event for the Q&A. We will not consider proposals from prospective speakers who are unsure whether they will be able to attend the FOSDEM virtual event. If you are experiencing problems with Pentabarf, the proposal submission interface, or have other questions, you can email our devroom mailing list[2] and we will try to help you. Code of Conduct Following the release of the updated code of conduct for FOSDEM, we'd like to remind all speakers and attendees that all of the presentations and discussions in our devroom are held under the guidelines set in the CoC and we expect attendees, speakers, and volunteers to follow the CoC at all times. If you submit a proposal and it is accepted, you will be required to confirm that you accept the FOSDEM CoC. If you have any questions about the CoC or wish to have one of the devroom organizers review your presentation slides or any other content for CoC compliance, please email us and we will do our best to assist you. Call for Volunteers We are also looking for volunteers to help run the devroom. We need assistance with helping speakers to record the presentation as well as helping with streaming and chat moderation for the devroom. Please contact devroom mailing list [2] for more information. Questions? If you have any questions about this devroom, please send your questions to our devroom mailing list. You can also subscribe to the list to receive updates about important dates, session announcements, and to connect with other attendees. See you all at FOSDEM! [1] <https://penta.fosdem.org/submission/FOSDEM17>https://penta.fosdem .org/submission/FOSDEM21 [2] iaas-virt-devroom at lists.fosdem.org

1 1

Cannot passthrough usb with bus number and device number
by YaoHua Wu 08 Dec '20

08 Dec '20

Sometimes, qemu cannot find correct usb device number Reproduce steps: 1、lsusb Bus 001 Device 011: ID 090c:1000 1、prepare usb device attach xml <hostdev managed="yes" mode="subsystem" type="usb"> <source> <vendor id="0x090c" /> <product id="0x1000" /> <address bus='001' device='011'/> </source><address bus="1" port="1" type="usb" /> </hostdev> 2、virsh attach-device vm usb.xml error: internal error: Did not find USB device 090c:1000 bus:1 device 9 Question: why the device number returned in qemu's error report is not what I wrote in xml， what I mean is that if my dev number is really wrong, the returned error should also be the number I wrote， commonly when using dongle Look forward to your reply yaohua.wu

2 3

unable to migrate when TLS is used
by Vjaceslavs Klimovs 07 Dec '20

07 Dec '20

With libvirt 6.9.0, qemu 5.1.0, and following configurations: libvirt: key_file = "/etc/ssl/libvirt/server.lan.key" cert_file = "/etc/ssl/libvirt/server.lan.crt" ca_file = "/etc/ssl/libvirt/ca.crt" log_filters="3:remote 4:event 3:util.json 3:rpc 1:*" log_outputs="1:file:/var/log/libvirt/libvirtd.log" qemu: default_tls_x509_cert_dir = "/etc/ssl/qemu" default_tls_x509_verify = 1 migration with tls: virsh # migrate vm1 qemu+tls://server2.lan/system --persistent --undefinesource --copy-storage-all --verbose --tls never succeeds. Progress stops typically at high progress amounts (95%-98%), and network traffic drastically drops as well (from 1 gbps+ to nothing). domjobinfo progress also stops. Without --tls migrations succeed without issues without any other changes to hosts or configurations. Logs of failed migration: Source: https://drive.google.com/file/d/1d0dJumicW0TUdG1osNxNnWWiYpfAaIb_/view?usp=… Destination: https://drive.google.com/file/d/1d0dJumicW0TUdG1osNxNnWWiYpfAaIb_/view?usp=… Same exact hosts, successful migration logs (without --tls): Source: https://drive.google.com/file/d/1d0dJumicW0TUdG1osNxNnWWiYpfAaIb_/view?usp=… Destination: https://drive.google.com/file/d/1EWkCkSBhj76T05k86QjdL-6icJyruK5-/view?usp=… Should I report this as a bug or is there an issue with my configuration?

2 3

Nfs mount 'gone' after vm's start
by Marc Roos 05 Dec '20

05 Dec '20

I have had a nfs-ganesha mount provision install images for vm's, and recently I have the mount stall after starting a vm. (even when it does not access an iso image on the nfs mount) I have the host ip on a macvtap of the connected interface. The vm is also having an macvtap on the same interface to allow host-guest communication. I am mounting the nfs with these options. nfs4 ro,vers=4,proto=tcp,soft,nodev,_netdev,noatime,timeo=30,x-systemd.device -timeout=30,x-systemd.mount-timeout=30,x-systemd.automount,x-systemd.idl e-timeout=30 0 0 The problem is fixed by doing a simple 'umount -l' Anyone seen something similar? I suspect this could be related by the macvtap being created, but I cannot remember seeing this mount fail before.

1 0

apparmor DENIED on domain shutdown
by Francesc Guasch 05 Dec '20

05 Dec '20

Hi. I upgraded one of my servers to Ubuntu 20.04. Since then domains won't shutdown. They are in the "in shutdown" state. I googled around and I found it is probably because of apparmor. I see this message in the logs: kernel: [740222.848210] audit: type=1400 audit(1606983397.013:338): apparmor="DENIED" operation="signal" profile="libvirt-a2c1456f-3371-49eb-9fa4-f8576ca4e878" pid=2375 comm="libvirtd" requested_mask="receive" denied_mask="receive" signal=term peer="libvirtd" I tried to run this but it does nothing: aa-complain /usr/sbin/libvirtd The only solution I found was to run aa-disable to the machine id so it can be shut down. I found some similar issues but I can't figure out what I have to tweak in the apparmor files. If you can point me to some doc may be I skipped I will or any solution I would appreciate it. This is - Ubuntu 20.04 - libvirt 6.0.0-0 - qemu-kvm 1:4.2-3 Thank you very much.

2 3

qemu guest agent(QGA) in guest OS
by Henry lol 01 Dec '20

01 Dec '20

Hello, AFAIK, QGA is automatically installed and run in guest OS after installing OS from iso file whereas it's not installed in case of installing OS on the host even with same iso and configuration. So, I am wondering how it works differently depending on the guest or host. Does the OS installer selectively install packages? thanks.

1 0

How to exit console in L2 vm?
by Yalan Zhang 30 Nov '20

30 Nov '20

Hi, I have a question about nested virtualization. The scenario is as below: 1. Prepare the nested environment, start L2 guest. 2. On the host, connect the L1 vm console, then on L1 guest, connect the L2 guest console: (host)# virsh console L1_vm Connected to domain L1_vm Escape character is ^] (Ctrl + ]) ... (L1 vm)# virsh console L2_vm Connected to domain L2_vm Escape character is ^] (Ctrl + ]) ... (L2 vm)# <=== press " ^] " to exit the console, it return to the **host** (host)# Is it expected that "^]" in L2 guest will exit thoroughly to the host, not the L1 guest? Thank you! ------- Best Regards, Yalan Zhang IRC: yalzhang

4 4