June 2021 - 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

Need more doc for libvirt-console-proxy
by Guy Godfroy 05 Oct '21

05 Oct '21

Hello, I'm making a web app for my company that will enable different teams to manage their own VMs. I wish to make possible to interact with each VM console, so I plan to use some xterm.js with websockets. So I discovered libvirt-console-proxy [1] when I looked for something to put a libvirt console into a websocket. That seems like the right tool for the job. The only doc I found is this article from 2017 [2]. After trying to understand from this article and from --help, I still have many questions. I am really bad at reading code so I can't even get answers from the sources. My main concern is: How a client is supposed to talk to the proxy? It is said that a security token must be provided. How? HTTP header? Which header? Am I missing something in websocket protocol? I think an example client implementation would help a lot. Also, I tried to use virtconsoleresolveradm to set up metadata on my domains like explained in the article [1] : ./virtconsoleresolveradm enable milou Enabled access to domain 'milou' But that doesn't seem to do anything (except defining the metadata namespace in the XML): virsh metadata milou http://libvirt.org/schemas/console-proxy/1.0 <consoles/> I precise that I have already this in my XML: <serial type='pty'> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> </serial> <console type='pty'> <target type='serial' port='0'/> </console> Should I remove that? Should I edit that? Thanks for your help. Guy Godfroy [1] https://gitlab.com/libvirt/libvirt-console-proxy [2] https://www.berrange.com/posts/2017/01/26/announce-new-libvirt-console-prox…

1 1

Fail to do blockcopy to network dest xml with --reuse-external
by Han Han 28 Jun '21

28 Jun '21

Hello, libvirt developers, Recently I find an issue of libvirt blockcopy: Versions: libvirt-7.4.0 qemu-kvm-6.0.0 Steps: 1. Create a nbd server # qemu-img create -f qcow2 /var/lib/libvirt/images/fedora-1.qcow2 10G -o preallocation=full # qemu-nbd -e 10 /var/lib/libvirt/images/fedora-1.qcow2 -p 10001 2. Prepare a running VM # virsh list Id Name State ------------------------ 3 fedora running # virsh dumpxml 3|xmllint --xpath //disk - <disk type="file" device="disk"> <driver name="qemu" type="qcow2"/> <source file="/var/lib/libvirt/images/fedora.qcow2" index="1"/> <backingStore/> <target dev="hda" bus="ide"/> <alias name="ide0-0-0"/> <address type="drive" controller="0" bus="0" target="0" unit="0"/> </disk> 3. Blockcopy to a nbd dest xml with --reuse-external # cat /tmp/copy.xml <disk type='network' device='disk'> <driver name='qemu' type='qcow2'/> <source protocol="nbd"> <host name="localhost" port="10001" /> </source> <backingStore/> <target dev='hda' bus='ide'/> </disk> # virsh blockcopy fedora hda --xml /tmp/copy.xml --transient-job --wait --verbose --finish --reuse-external error: unsupported configuration: reused mirror destination format must be specified But it works without --reuse-external # virsh blockcopy fedora hda --xml /tmp/copy.xml --transient-job --wait --verbose --finish Block Copy: [100 %] Successfully copied Since it is clear that the format of dest image is qcow2, the error message "reused mirror destination format must be specified" is wrong. The blockcopy with network disk + --reuse-external should either be supported or post a better error message. I am not sure if --reuse-external flag is only for file type disk. It seems the description of VIR_DOMAIN_BLOCK_COPY_REUSE_EXT( https://github.com/libvirt/libvirt/blob/7c08141f906e20e730c4b6407bc638e743d…) indicates this flag is for file only: * VIR_DOMAIN_BLOCK_COPY_REUSE_EXT flag is present stating that the file * was pre-created with the correct format and metadata and sufficient * size to hold the copy. In case the VIR_DOMAIN_BLOCK_COPY_SHALLOW flag * is used the pre-created file has to exhibit the same guest visible contents * as the backing file of the original image. This allows a management app to * pre-create files with relative backing file names, rather than the default * of absolute backing file names. Please help to confirm if it is a bug here.

1 0

issue when not using acpi indices in libvirt 7.4.0 and qemu 6.0.0
by Riccardo Ravaioli 25 Jun '21

25 Jun '21

Hi everyone, We have an issue with how network interfaces are presented in the VM with the latest libvirt 7.4.0 and qemu 6.0.0. Previously, we were on libvirt 7.0.0 and qemu 5.2.0, and we used increasing virtual PCI addresses for any type of network interface (virtio, PCI passthrough, SRIOV) in order to decide the interface order inside the VM. For instance the following snippet yields ens1, ens2 and ens3 in a Debian Buster VM: <interface type="ethernet"> <target dev="0.vSrv"/> <mac address="52:54:00:aa:cc:05"/> <address bus="0x01" domain="0x0000" function="0x0" slot="0x01" type="pci"/> <model type="virtio"/> <driver> <host csum="off"/> </driver> </interface> <interface type="ethernet"> <target dev="1.vSrv"/> <mac address="52:54:00:aa:bb:81"/> <address bus="0x01" domain="0x0000" function="0x0" slot="0x02" type="pci"/> <model type="virtio"/> <driver> <host csum="off"/> </driver> </interface> <hostdev managed="yes" mode="subsystem" type="pci"> <source> <address bus="0x0d" domain="0x0000" function="0x0" slot="0x00"/> </source> <address bus="0x01" domain="0x0000" function="0x0" slot="0x03" type="pci"/> </hostdev> After upgrading to libvirt 7.4.0 and qemu 6.0.0, the XML snippet above yielded: - ens1 for the first virtio interface => OK - rename4 for the second virtio interface => **KO** - ens3 for the PCI passthrough interface => OK Argh! What happened to ens2? By running udev inside the VM, I see that "rename4" is the result of a conflict between the ID_NET_NAME_SLOT of the second and the third interface, both appearing as ID_NET_NAME_SLOT=ens3. In theory rename4 should show ID_NET_NAME_SLOT=ens2. What happened? # udevadm info -q all /sys/class/net/rename4 P: /devices/pci0000:00/0000:00:03.0/0000:01:02.0/virtio4/net/rename4 L: 0 E: DEVPATH=/devices/pci0000:00/0000:00:03.0/0000:01:02.0/virtio4/net/rename4 E: INTERFACE=rename4 E: IFINDEX=4 E: SUBSYSTEM=net E: USEC_INITIALIZED=94191911 E: ID_NET_NAMING_SCHEME=v240 E: ID_NET_NAME_MAC=enx525400aabba1 E: ID_NET_NAME_PATH=enp1s2 E: ID_NET_NAME_SLOT=ens3 E: ID_BUS=pci E: ID_VENDOR_ID=0x1af4 E: ID_MODEL_ID=0x1000 E: ID_PCI_CLASS_FROM_DATABASE=Network controller E: ID_PCI_SUBCLASS_FROM_DATABASE=Ethernet controller E: ID_VENDOR_FROM_DATABASE=Red Hat, Inc. E: ID_MODEL_FROM_DATABASE=Virtio network device E: ID_PATH=pci-0000:01:02.0 E: ID_PATH_TAG=pci-0000_01_02_0 E: ID_NET_DRIVER=virtio_net E: ID_NET_LINK_FILE=/usr/lib/systemd/network/99-default.link E: SYSTEMD_ALIAS=/sys/subsystem/net/devices/rename4 E: TAGS=:systemd: # udevadm info -q all /sys/class/net/ens3 P: /devices/pci0000:00/0000:00:03.0/0000:01:03.0/net/ens3 L: 0 E: DEVPATH=/devices/pci0000:00/0000:00:03.0/0000:01:03.0/net/ens3 E: INTERFACE=ens3 E: IFINDEX=2 E: SUBSYSTEM=net E: USEC_INITIALIZED=3600940 E: ID_NET_NAMING_SCHEME=v240 E: ID_NET_NAME_MAC=enx00900b621235 E: ID_OUI_FROM_DATABASE=LANNER ELECTRONICS, INC. E: ID_NET_NAME_PATH=enp1s3 E: ID_NET_NAME_SLOT=ens3 E: ID_BUS=pci E: ID_VENDOR_ID=0x8086 E: ID_MODEL_ID=0x1533 E: ID_PCI_CLASS_FROM_DATABASE=Network controller E: ID_PCI_SUBCLASS_FROM_DATABASE=Ethernet controller E: ID_VENDOR_FROM_DATABASE=Intel Corporation E: ID_MODEL_FROM_DATABASE=I210 Gigabit Network Connection E: ID_PATH=pci-0000:01:03.0 E: ID_PATH_TAG=pci-0000_01_03_0 E: ID_NET_DRIVER=igb E: ID_NET_LINK_FILE=/usr/lib/systemd/network/99-default.link E: SYSTEMD_ALIAS=/sys/subsystem/net/devices/ens3 E: TAGS=:systemd: Is there anything we can do in the XML definition of the VM to fix this? The PCI tree from within the VM is the following, if it helps: (with libvirt 7.0.0 and qemu 5.2.0 it was the same) # lspci -tv -[0000:00]-+-00.0 Intel Corporation 440FX - 82441FX PMC [Natoma] +-01.0 Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II] +-01.1 Intel Corporation 82371SB PIIX3 IDE [Natoma/Triton II] +-01.2 Intel Corporation 82371SB PIIX3 USB [Natoma/Triton II] +-01.3 Intel Corporation 82371AB/EB/MB PIIX4 ACPI +-02.0 Cirrus Logic GD 5446 +-03.0-[01]--+-01.0 Red Hat, Inc. Virtio network device | +-02.0 Red Hat, Inc. Virtio network device | \-03.0 Intel Corporation I210 Gigabit Network Connection +-04.0-[02]-- +-05.0-[03]-- +-06.0-[04]-- +-07.0-[05]-- +-08.0-[06]----01.0 Red Hat, Inc. Virtio block device +-09.0 Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH) 6 port SATA Controller [AHCI mode] +-0a.0 Red Hat, Inc. Virtio console +-0b.0 Red Hat, Inc. Virtio memory balloon \-0c.0 Red Hat, Inc. Virtio RNG I see that a new feature in qemu and libvirt is to add ACPI indices in order to have network interfaces appear as *onboard* and sort them through this index as opposed to virtual PCI addresses. This is great. I see that in this case, interfaces appear as eno1, eno2, etc. However, for the sake of backward compatibility, is there a way to have the previous behaviour where interfaces were called by their PCI slot number (ens1, ens2, etc.)? If I move to the new naming yielded by ACPI indices, I am mostly worried about any possible change in interface names that might occur across VMs running different OS's, with respect to what we had before with libvirt 7.0.0 and qemu 5.2.0. Thanks! Best, Riccardo Ravaioli

3 4

Libvirt hit a issue when do VM migration
by 梁朝军 23 Jun '21

23 Jun '21

Hi All, Who can give me a help? I hit another issue when do vm migration? Libvirt throw out the error like below "libvirt: Domain Config error : unsupported configuration: vcpu enable order of vCPU '0' differs between source and destination definitions” The cup information is defined VM domain on source host is like: <vcpu placement='static'>2</vcpu> <vcpus> <vcpu id='0' enabled='yes' hotpluggable='no' order='1'/> <vcpu id='1' enabled='yes' hotpluggable='no' order='2'/> </vcpus> <cputune> <vcpupin vcpu='0' cpuset='42'/> <vcpupin vcpu='1' cpuset='43'/> </cputune> The distinction host previews generate xml for VM like: <vcpu placement='static'>2</vcpu> <vcpus> <vcpu id='0' enabled='yes' hotpluggable='no' order='1'/> <vcpu id='1' enabled='yes' hotpluggable='no' order='2'/> </vcpus> <cputune> <vcpupin vcpu='0' cpuset='42'/> <vcpupin vcpu='1' cpuset='43'/> </cputune> What’t wrong with it? Or I missing some actions in configurations regarding the migration Thanks a lot !

3 4

unaccessible directory in lxcContainerResolveSymlinks
by Priyanka Gupta 23 Jun '21

23 Jun '21

Hi, Could someone pls let me know when this condition could possibly arise? lxcContainerResolveSymlinks:621 : Skipped unaccessible '/flash/dir' The code seems to call access('/flash/dir', F_OK) which shall only check for existence of this directory '/flash/dir'. I have this directory created on my host. Is there anything that I am missing? Thanks Priyanka

2 5

Testing DKIM handling
by dberrange＠yahoo.com 22 Jun '21

22 Jun '21

Testing whether DKIM signatures still get mangled....

1 0

driver_remote option defaults to auto
by Jiatong Shen 21 Jun '21

21 Jun '21

Hello community, I am looking at building and packaging libvirt source code. I am seeing from commit https://github.com/libvirt/libvirt/commit/83ff55b5a2618d32f623d7ca0b6f9c28b… `driver_remote` is defaulting to auto which is different from enabled before. I am curious what does auto mean? does it mean that meson will take over and determine if driver_remote should be enabled or we have to write more logic in meson.build? currently it seems there is no effort to auto determine driver_remote. I think it is interesting because https://github.com/libvirt/libvirt/blob/54b602019d7dfa94a6c52ef7aa3abdfaa93… sasl seems required remote_driver to have a value of enabled... -- Best Regards, Jiatong Shen

3 2

KVM Virtual Machine Network - Guest-guest/VM-VM only network (no host/hypervisor access, no outbound connectivity)
by Eduardo Lúcio Amorim Costa 14 Jun '21

14 Jun '21

I know that with the *virsh* command I can create several types of networks (a "NAT network", for example) as we can see in these URLs... KVM network management <https://programmersought.com/article/52213715009/> KVM default NAT-based networking <https://www.ibm.com/downloads/cas/ZVJGQX8E> (page 33) *QUESTION:* How can I create a network (*lan_n*) where only guests/VMs have connectivity, with no outbound connectivity and no host/hypervisor connectivity? *NOTE:* The connectivity to other resources will be provided by a *pfSense* firewall server that will have access to another network (*wan_n*) with outbound connectivity and other resources. Network layout... [N]wan_n ↕ [I]wan_n [V]pfsense_vm [I]lan_n ↕ [N]lan_n ↕ ............................. ↕ ↕ ↕ [V]some_vm_0 [V]some_vm_1 [V]some_vm_4 [V]some_vm_2 [V]some_vm_5 [V]some_vm_3 _ [N] - Network; _ [I] - Network Interface; _ [V] - Virtual Machine. *Thanks! =D* *ORIGINAL QUESTION: *https://serverfault.com/q/1066478/276753 <https://programmersought.com/article/52213715009/> -- *Eduardo Lúcio* Tecnologia, Desenvolvimento e Software Livre LightBase Consultoria em Software Público eduardo.lucio(a)lightbase.com.br <eduardo.lucio(a)LightBase.com.br> *+55-61-3347-1949* - http://brlight.org <eduardo.lucio(a)LightBase.com.br> - *Brasil-DF* *Software livre! Abrace essa idéia!* *"Aqueles que negam liberdade aos outros não a merecem para si mesmos."* *Abraham Lincoln*

2 1

the SSL cert of libvirt.org is outdated
by 伍翀 14 Jun '21

14 Jun '21

hi, there, the SSL cert of libvirt.org is outdated, could anyone replace it as new one?

2 2

Re: interface qos conflicts with ovs
by Michal Prívozník 11 Jun '21

11 Jun '21

[please keep the list CC'ed] On 6/11/21 4:42 PM, Jiatong Shen wrote: > ah, OK. we are hitting this one when transfering to neutron ovs firewall > and would like to fix > it before moving to production.. does this bug still exist? If yes, can we > take it and try > submitting a fix? Thank you. Sure you can! I'm happy to review patches. Michal

1 0

interface qos conflicts with ovs
by Jiatong Shen 11 Jun '21

11 Jun '21

Hello community, We found a strange situation where interface qos is being cleared up. After some search, looks like ovs will clear tc setting at least on ingress. related code is https://github.com/openvswitch/ovs/blob/91cb55bc8aad7fe17060778482dc7ad18dc… so I would like to know if it is more ideal to set ovs port qos and replace current tc when ovs port is used? thank you -- Best Regards, Jiatong Shen

2 1

lxcContainerMountFSBind - Failed to bind mount directory
by Priyanka Gupta 10 Jun '21

10 Jun '21

Hi Everyone, I am looking to understand this piece of code and error. 2021-06-09 06:52:55.548+0000: 1: debug : lxcContainerMountAllFS:1612 : Mounting all non-root filesystems 2021-06-09 06:52:55.548+0000: 1: debug : lxcContainerMountAllFS:1619 : Mounting '/bootflash/SHARED-IOX' -> '/bootflash/SHARED-IOX' 2021-06-09 06:52:55.548+0000: 1: debug : lxcContainerResolveSymlinks:630 : Resolving '/bootflash/SHARED-IOX' 2021-06-09 06:52:55.548+0000: 1: debug : lxcContainerResolveSymlinks:646 : Resolved '/bootflash/SHARED-IOX' to /bootflash/SHARED-IOX 2021-06-09 06:52:55.548+0000: 1: debug : lxcContainerMountFSBind:1176 : src=/bootflash/SHARED-IOX dst=/bootflash/SHARED-IOX 2021-06-09 06:52:55.548+0000: 1: error : lxcContainerMountFSBind:1223 : Failed to bind mount directory /.oldroot/bootflash/SHARED-IOX to /bootflash/SHARED-IOX: No such file or directory I am on Libvirt 5.5.0 Any pointers? Thanks Priyanka

2 1

why cannot connect to libvirtd using virsh ???
by tommy 10 Jun '21

10 Jun '21

[root@test2 ~]# virsh -c quem+ssh://root@192.168.10.175/system root(a)192.168.10.175's <mailto:root@192.168.10.175's> password: error: failed to connect to the hypervisor error: no connection driver available for quem:///system But, on the same terminal using virt-manager to connect to 192.168.10.175 is successful. Why ?

3 3

virtiofs mounted filesystems & SELinux
by Link Dupont 07 Jun '21

07 Jun '21

I am mounting a filesystem into a domain using the virtiofs driver. <filesystem accessmode="passthrough" type="mount"> <source dir="/home"/> <target dir="/home"/> <driver type="virtiofs"/> </filesystem> Both my host (Fedora 34) and guest (CentOS 8.4) are running with SELinux enforcing. From my host, I can see that the SELinux context type is set to user_home_dir_t. $ ls -ldZ /home/link drwxr-xr-x. 61 link link system_u:object_r:user_home_dir_t:s0 8192 May 21 12:41 /home/link >From within the guest however, the volume is unlabeled_t $ ls -lZd /home/link drwxr-xr-x. 61 link link system_u:object_r:unlabeled_t:s0 8192 May 21 12:53 / home/link Is there a way to pass the SELinux context through to the guest? Or mount the volume with the correct options to map SELinux contexts?

6 12

Re: How to hot plugin a new vhost-user-blk-pci device to running VM?
by 梁朝军 05 Jun '21

05 Jun '21

Thanks all of you for your help. One more question regarding vhost-user-blk-pci type device, how to identify a vhost-blk disk in QEUM VM ? for example, disk name looks like vda,vdb,..., but that some application in VM want to detect that a certain entry is really the device it is waiting for. Specific for windows , they always show as disk 0, 1, 2….etc Is there any way to identify those disk with each other in VM? thanks > 在 2021年5月17日，下午3:13，Michal Prívozník <mprivozn(a)redhat.com> 写道： > > On 5/17/21 7:08 AM, Liang Chaojun wrote: >> >> Thanks Michal and Peter for your response. I‘ m running it on qemu 5.1 build by myself. BTW, follow Peter’s suggestion, where I can get the latest rpms if I want to upgrade to Libvirt 7.1? As I know it seems need more than twenty related rpms not include dependency. > > Well, since you're building qemu yourself you could also build libvirt. > Just be aware that the v7.3.0 release was the last one that supports > RHEL-7. Newer releases might still work, but upstream does not aim to > make everything work. > > https://libvirt.org/platforms.html > > Michal >

4 5

Re: error when building from git checkout
by Andrea Bolognani 04 Jun '21

04 Jun '21

[re-adding libvirt-users] On Fri, Jun 04, 2021 at 04:49:49PM +0800, Jiatong Shen wrote: > Thank you very much for the reply. after applying this ps, the error is > gone. Glad to hear that! I've sent the patch to the mailing list now :) > also curious to know if there is a way to skip building docs? thank you. Passing -Ddocs=disabled to Meson should do the trick. -- Andrea Bolognani / Red Hat / Virtualization

2 1

error when building from git checkout
by Jiatong Shen 04 Jun '21

04 Jun '21

Hello community, I am trying to compile libvirt from source but being trapped with following error message when running ninja -C build ninja -C build ninja: Entering directory `build' [1/12] Generating virkeyname-osx.html with a meson_exe.py custom command FAILED: docs/manpages/virkeyname-osx.html /home/sjt/.local/bin/meson --internal exe --capture docs/manpages/virkeyname-osx.html -- /usr/bin/xsltproc --stringparam pagesrc docs/manpages/virkeyname-osx.rst --stringparam builddir /home/sjt/src/c/libvirt/build --stringparam timestamp 'Thu Jun 3 23:11:25 2021 UTC' --nonet ../docs/subsite.xsl docs/manpages/virkeyname-osx.html.in docs/manpages/virkeyname-osx.html.in:17: parser error : Double hyphen within comment: <!-- This file is auto-generated from keymaps.csv Data keymap-gen --lang=rst --title=virkeyname-osx --subtitle=Key name values for os ^ docs/manpages/virkeyname-osx.html.in:17: parser error : Double hyphen within comment: <!-- This file is auto-generated from keymaps.csv Data keymap-gen --lang=rst --title=virkeyname-osx --subtitle=Key name values for os ^ docs/manpages/virkeyname-osx.html.in:17: parser error : Double hyphen within comment: <!-- This file is auto-generated from keymaps.csv Data keymap-gen --lang=rst --title=virkeyname-osx --subtitle=Key name values for os ^ unable to parse docs/manpages/virkeyname-osx.html.in [2/12] Generating virkeycode-usb.html with a meson_exe.py custom command FAILED: docs/manpages/virkeycode-usb.html /home/sjt/.local/bin/meson --internal exe --capture docs/manpages/virkeycode-usb.html -- /usr/bin/xsltproc --stringparam pagesrc docs/manpages/virkeycode-usb.rst --stringparam builddir /home/sjt/src/c/libvirt/build --stringparam timestamp 'Thu Jun 3 23:11:25 2021 UTC' --nonet ../docs/subsite.xsl docs/manpages/virkeycode-usb.html.in docs/manpages/virkeycode-usb.html.in:17: parser error : Double hyphen within comment: <!-- This file is auto-generated from keymaps.csv Data keymap-gen --lang=rst --title=virkeycode-usb --subtitle=Key code values for us ^ docs/manpages/virkeycode-usb.html.in:17: parser error : Double hyphen within comment: <!-- This file is auto-generated from keymaps.csv Data keymap-gen --lang=rst --title=virkeycode-usb --subtitle=Key code values for us ^ docs/manpages/virkeycode-usb.html.in:17: parser error : Double hyphen within comment: <!-- This file is auto-generated from keymaps.csv Data keymap-gen --lang=rst --title=virkeycode-usb --subtitle=Key code values for us ^ unable to parse docs/manpages/virkeycode-usb.html.in [3/12] Generating virkeycode-atset1.html with a meson_exe.py custom command FAILED: docs/manpages/virkeycode-atset1.html /home/sjt/.local/bin/meson --internal exe --capture docs/manpages/virkeycode-atset1.html -- /usr/bin/xsltproc --stringparam pagesrc docs/manpages/virkeycode-atset1.rst --stringparam builddir /home/sjt/src/c/libvirt/build --stringparam timestamp 'Thu Jun 3 23:11:25 2021 UTC' --nonet ../docs/subsite.xsl docs/manpages/ virkeycode-atset1.html.in docs/manpages/virkeycode-atset1.html.in:17: parser error : Double hyphen within comment: <!-- This file is auto-generated from keymaps.csv Data keymap-gen --lang=rst --title=virkeycode-atset1 --subtitle=Key code values for ^ docs/manpages/virkeycode-atset1.html.in:17: parser error : Double hyphen within comment: <!-- This file is auto-generated from keymaps.csv Data keymap-gen --lang=rst --title=virkeycode-atset1 --subtitle=Key code values for ^ docs/manpages/virkeycode-atset1.html.in:17: parser error : Double hyphen within comment: <!-- This file is auto-generated from keymaps.csv Data keymap-gen --lang=rst --title=virkeycode-atset1 --subtitle=Key code values for ^ unable to parse docs/manpages/virkeycode-atset1.html.in [4/12] Generating virkeycode-xtkbd.html with a meson_exe.py custom command FAILED: docs/manpages/virkeycode-xtkbd.html any advice on how to fix it? thank you very much -- Best Regards, Jiatong Shen

2 1

Error: --boot uefi=RPI_EFI.fd : Did not find any UEFI binary path for arch 'aarch64' emulating raspi3 on jetson nano with virt-install
by Mario Marietto 03 Jun '21

03 Jun '21

Hello. it's more of a challenge,to be able to emulate the raspberry pi 3 on my Jetson nano (aarch64) using virt-install. I'm learning how to do that by reading heavily here : https://github.com/dhruvvyas90/qemu-rpi-kernel I tried to do something like this : virt-install \ --name pi \ --machine raspi3 \ --cpu arm1176 \ --memory 1024 \ --import \ --disk /root/Desktop/zi/Work/Android/Raspy/Debian/2019-09-26-raspbian-buster-lite.img,format=raw,bus=virtio \ --network user,model=virtio \ --video vga \ --graphics spice \ --rng device=/dev/urandom,model=virtio \ --boot 'uefi=RPI_EFI.fd,dtb=bcm2710-rpi-3-b-plus.dtb,kernel=kernel8.img,kernel_args=root=/dev/vda2 rootwait panic=1 dwc_otg.fiq_fsm_enable=0' \ --events on_reboot=destroy But I get this error : ERROR Error: --boot uefi=RPI_EFI.fd,dtb=bcm2710-rpi-3-b-plus.dtb,kernel= kernel8.img,kernel_args=root=/dev/vda2 rootwait panic=1 dwc_otg.fiq_fsm_enable=0: Did not find any UEFI binary path for arch 'aarch64' I've got the UEFI BIOS file from here : https://github.com/andreiw/RaspberryPiPkg/blob/master/Binary/prebuilt/2019J… I'm not sure if it isn't the right efi file to use in this specific configuration or if it is,but I'm passing the parameter badly. What do you suggest me to do ? -- Mario.

1 1

virt viewer for Mac
by Francesc Guasch 03 Jun '21

03 Jun '21

Hi. Please excuse me if this is not the right place to ask. We are using virt viewer happily from Linux, and though the Windows release sometimes has issues it seems it is maintained. There is this Mac client here: https://people.freedesktop.org/~teuf/spice-gtk-osx/ We have been reported it is outdated and somehow buggy. Is there another alternative ? Are there plans to port virt-viewer for Macs ? Thank you.

2 2