- Users - libvirt List Archives

virsh create fails with "Unable to find any firmware to satisfy 'efi'" for aarch64 guest on macOS
by Nathan Vander Wilt 30 Nov '21

30 Nov '21

I am having trouble when I `virsh create test.xml` with an aarch64 guest on a macOS (Apple Silicon) host. I've wrestled with a variety of issues but the one I simply haven't been able to get past is this regarding the UEFI firmware: error: Failed to create domain from test.xml error: operation failed: Unable to find any firmware to satisfy 'efi' This is with `virsh --version` of 7.9.0 and `qemu-system-aarch64 --version` of 6.1.0, both installed via the common `brew` tool from its main 'homebrew/core' tap. I have confirmed that the loader/nvram files referenced do exist. Running `qemu-system-aarch64 -L help` outputs two lines: /opt/homebrew/Cellar/qemu/6.1.0_1/bin/../share/qemu-firmware /opt/homebrew/Cellar/qemu/6.1.0_1/bin/../share/qemu The …/share/qemu-firmware folder does NOT exist, but symlinking it to a …/share/qemu/firmware folder which does exist does not improve the situation. I have also tried renaming the …/share/qemu/firmware folder (e.g. `mv firmware zzz-firmware`) as some notes I found led me to believe that libvirst might ignore my loader/nvram settings entirely if QEMU had the "new" firmware JSON configuration stuff there? But again no improvement…. How can I debug this further? What should I try next? thanks, -natevw --- the test.xml domain configuration I am trying --- <domain type="qemu" xmlns:qemu="http://libvirt.org/schemas/domain/qemu/1.0"> <name>test1</name> <uuid>D45FCA3E-B873-4608-A0B8-3D8529E7CFB7</uuid> <memory unit="MiB">2048</memory> <cpu mode="host-model" check="partial" /> <vcpu>2</vcpu> <clock offset="utc"/> <qemu:commandline> <qemu:arg value='-accel'/> <qemu:arg value='hvf'/> </qemu:commandline> <os firmware="efi"> <type arch="aarch64" machine="virt">hvm</type> <loader readonly="yes" secure="no" type="pflash">/opt/homebrew/share/qemu/edk2-aarch64-code.fd</loader> <nvram template="/opt/homebrew/share/qemu/edk2-arm-vars.fd">/Users/me/vm_testing/vm-test1.efi.fd</nvram> <bootmenu enable="no"/> <boot dev="hd"/> </os> <features> <acpi/> <gic version="3"/> <pae/> </features> <devices> <emulator>/opt/homebrew/bin/qemu-system-aarch64</emulator> <disk type="file" device="disk"> <driver name="qemu" type="qcow2"/> <source file="/Users/me/vm_testing/vm-test1.qcow2"/> <target dev="vda" bus="virtio"/> </disk> <interface type="network"> <source network="default"/> <model type="virtio"/> </interface> <console type="pty"> <target type="serial" port="0"/> </console> <rng model="virtio"> <backend model="random">/dev/urandom</backend> </rng> </devices> </domain>

5 10

Fwd: Installing virtiofs drivers on Windows 11....
by Mario Marietto 30 Nov '21

30 Nov '21

Hello to everyone. I'm testing Windows 11 with bhyve and I've found an annoying problem that prevents me from completing some tasks that I'm working on. It seems that the virtio-9p driver does not work inside the Windows 11 os emulated with bhyve and maybe also with qemu-kvm. When Windows 11 is launched,I don't see the folder "mnt" mounted on the root folder of Windows 11. Below you can see which bhyve parameters I've used : bhyve -S -c 4 -m 8G -w -H \ -s 0,hostbridge \ -s 1,ahci-cd,/home/marietto/Downloads/virtio/virtio-win-0.1.208.iso \ -s 2,ahci-hd,/mnt/da0p1/Backups/OS/bhyve/Windows/win11.img \ -s 3,fbuf,tcp=0.0.0.0:5900,w=1440,h=900,wait \ -s 8,virtio-net,tap0 \ ----> -s 9,virtio-9p,sharename=/mnt \ -s 30,xhci,tablet \ -s 31,lpc \ -l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd \ vm0 Investigating a little bit more and reading from this tutorial : https://virtio-fs.gitlab.io/howto-windows.html I've realized that there should be some problem with the WinFsp <http://www.secfs.net/winfsp> - Windows File System Proxy and or with the virtiofs PCI device driver because I'm not able to enable the virtiofs service with the command used on the tutorial : C:\> sc start VirtioFsSvc it gives the error : "the dependency service does not exist or it has been marked for the elimination. I've attached some screenshots to help you to understand what's happening. Please help me,thanks. Attached screenshots : https://ibb.co/m5vm1hd https://ibb.co/Qd6TS5d https://ibb.co/3018SGd -- Mario.

2 7

virsh blockjob $domain --abort
by Jeff Brown 30 Nov '21

30 Nov '21

Please advise: After a scheduled crontab snapshot backup of a VM it failed to do a blockcommit, and is currently writing to both the snapshot and the original QCOW2 images. (I don't think it's a bug, and suspect that I caused it by running the backup script manually while the snapshot was already running.) $ virsh blockcommit VM sda --active --pivot --shallow --verbose error: block copy still active: disk 'sda' already in active block job $ virsh blockjob VM sda --info Active Block Commit: [100 %] $ virsh domblkerror VM No errors found Running on Debian 9 (Stretch). $ virsh version Compiled against library: libvirt 3.0.0 Using library: libvirt 3.0.0 Using API: QEMU 3.0.0 Running hypervisor: QEMU 2.8.1 Now, I've read up on the probable solution, somewhat, but running $ virsh blockjob $domain --abort on this production server scares me; and I'm just asking whether it would be advisable to stop services and make a full data backup prior to doing so? It would entail taking the services offline for at least an hour. The snapshot is currently at 12GB, and according to blockjob --info the VM image is 100% in synch. Will appreciate any advice. Thank you. Best regards, Jeff

2 1

Libvirt + Debian Live = Heart Attack
by Elias Mobery 25 Nov '21

25 Nov '21

Hi everyone! I've built a Debian Live ISO with packages qemu and libvirt to run a VM in the live environment. The guest images are placed in /var/lib/libvirt/images and 2GB each. Everything works great, except for one issue. When starting a VM, libvirt automatically issues a chown command to the images, changing ownership. This results in a copy of the images being created in /run/live/overlay/rw/var/lib/libvirt/images I don't want these copies to be made but can't stop it. I've tried editing qemu.conf user/group, dynamic ownership etc. without any luck. Is there a way to STOP libvirt from changing the ownership of these images?

3 8

Questions on device-added and device-removed events
by Han Han 23 Nov '21

23 Nov '21

Hi developers, When the guest OS is booting, the event for live attachment could be caught by libvirt, while the event for live detachment could not. Version: libvirt-7.9 qemu-kvm-6.1 Steps: Terminal 1: ➜ ~ virsh event --loop --all Terminal 2: ➜ ~ virsh start avocado-vt-vm1; qemu-img create /tmp/vdb 10M; virsh attach-disk avocado-vt-vm1 /tmp/vdb vdb; virsh detach-disk avocado-vt-vm1 vdb The outputs from terminal 1: event 'agent-lifecycle' for domain 'avocado-vt-vm1': state: 'disconnected' reason: 'domain started' event 'lifecycle' for domain 'avocado-vt-vm1': Resumed Unpaused event 'lifecycle' for domain 'avocado-vt-vm1': Started Booted event 'device-added' for domain 'avocado-vt-vm1': virtio-disk1 event 'agent-lifecycle' for domain 'avocado-vt-vm1': state: 'connected' reason: 'channel event' As you can see, the device live attachment and the device detachment are both executed when the guest OS is booting, but there is only the event 'device-added' is recorded. So my questions are: 1. Is it the expected results for the results above? 2. If so, what is the internal difference between 'device-added' and 'device-removed'? 3. I notice there is the DEVICE_DELETED event in qmp? Any relation between the 'device-removed' of libvirt and the DEVICE_DELETED of qmp?

2 1

how to use vhost-user-vsock
by Jiatong Shen 23 Nov '21

23 Nov '21

Hello community, I am looking for a way to configure vhost-user-vsock using libvirt, but looks like it is not written in doc. How can I use vhost-user-vsock using libvirt? Thank you. -- Best Regards, Jiatong Shen

2 1

configure path name of ebtables executable
by Michael Ströder 18 Nov '21

18 Nov '21

HI! Is it possible to configure the full path name of the ebtables executable used somewhere in libvirt's config? Background: I'd like to avoid automatic alternatives implementation to mess up libvirt installation. See also: https://bugzilla.opensuse.org/show_bug.cgi?id=1192799 Ciao, Michael.

2 3

Cannot access KVM using virsh console after KVM rebooted or shut off
by Yifei Liu 16 Nov '21

16 Nov '21

Dear all, I used ssh with -X option to connect to an Ubuntu remote server where I applied virsh (libvirt) to manage my KVM virtual machines, and my local machine is MacOS. Then, I used virt-install to install a Tiny Core Linux VM, and I got a pop-up Virt Viewer window (via XQuartz) which is the console for my Tiny Core VM. However, if I rebooted my VM, then I checked the VM state by virsh list --all which was running. Then, I tried `virsh console my_vm_domain` but this command got stuck on: > Connected to domain my_vm_domain > Escape character is ^] The `virsh console` command hung without any response. This issue also happened when I used virsh console after I shut down and later started the VM. Even the VM was already started, I cannot return to the VM console by `virsh console`. I can get the VM console in Virt Viewer at the first boot (using virt-install). But, if I shutdown the VM once, I can never access the VM console by virsh console even the VM state is running. Any idea about how to use virsh console? Thanks, Yifei

3 2

can't connect to virtlogd: Unable to open system token /run/libvirt/common/system.token: Permission denied
by 梁朝军 16 Nov '21

16 Nov '21

Hi all, I have encountered a new issue when start a VM with new builded libvirt. I failed to start VM from defined xml and hit the error like "can't connect to virtlogd: Unable to open system token /run/libvirt/common/system.token: Permission denied” Any inputs are appreciated. The libvit version: libvirtd -V setlocale: No such file or directory libvirtd (libvirt) 7.6.0 Os : cat /etc/redhat-release Red Hat Enterprise Linux release 8.4 (Ootpa) Linux kernel: uname -a Linux localhost.localdomain 4.18.0-305.el8.x86_64 #1 SMP Thu Apr 29 08:54:30 EDT 2021 x86_64 x86_64 x86_64 GNU/Linux QEMU version: usr/libexec/qemu-kvm --help QEMU emulator version 5.1.0 (qemu-kvm-5.1.0-1.el8) Copyright (c) 2003-2020 Fabrice Bellard and the QEMU Project developers Thanks!

2 1

CPU vendor_id handling
by Toolybird 16 Nov '21

16 Nov '21

Hello, There are times when spoofing the CPU vendor_id is convenient. For example, some x86 guest OS's only run on Intel and refuse to run on an AMD host. Libvirt does support this in the "host-model" case, but it doesn't work for CPU "host-passthrough". On the QEMU command line it's as easy as: $ qemu-system-x86_64 -cpu host,vendor=GenuineIntel This works fine in libvirt XML: <cpu mode='host-model'> <model vendor_id='GenuineIntel'/> </cpu> This doesn't: <cpu mode='host-passthrough'> <model vendor_id='GenuineIntel'/> </cpu> Libvirt silently strips out the model line after saving "virsh edit ..." Is there any reason why libvirt cannot support this in the host-passthrough case? The status quo means that some folks end up resorting to <qemu:arg value='-cpu'/> hacks which of course causes all sorts of confusion with multiple -cpu lines getting passed to QEMU. Thanks

2 1