** Description changed: [ Impact ] Apport does not allow libvirt to use EDK II provided by package qemu- efi-riscv64 installed in the default path. Upstream has accepted a patch for the virt-aa-helper: https://gitlab.com/libvirt/libvirt/-/commit/c63bdd17b9f5c31a2511f173d60455b83d22c561 [ Test Plan ] Install libvirt-clients libvirt-daemon libvirt-daemon-system. Create a libvirt instance with 'virsh define my.xml' where my.xml has the following content: <?xml version="1.0"?> <domain type="qemu"> - <uuid>1a35d812-d84c-42c3-a21d-6c67a6c5db06</uuid> - <name>ubuntu24.04-riscv64</name> - <os> - <type arch='riscv64' machine='virt'>hvm</type> - <loader readonly='yes' type='pflash'>/usr/share/qemu-efi-riscv64/RISCV_VIRT_CODE.fd</loader> - <nvram type='file' template='/usr/share/qemu-efi-riscv64/RISCV_VIRT_VARS.fd'> - <source file='/home/ubuntu/RISCV_VIRT_VARS.fd'/> - </nvram> - <boot dev='hd'/> - </os> - <memory unit="MiB">512</memory> - <vcpu placement="static">2</vcpu> - <cpu match='exact'> - <model>rv64</model> - <topology sockets='1' cores='2' threads='1' /> - </cpu> - <devices> - <emulator>usr/bin/qemu-system-riscv64</emulator> - <rng model='virtio'> - <backend model='builtin'/> - </rng> - <console type="pty"> - <target type="serial" port="0"/> - </console> - </devices> + <uuid>1a35d812-d84c-42c3-a21d-6c67a6c5db06</uuid> + <name>ubuntu24.04-riscv64</name> + <os> + <type arch='riscv64' machine='virt'>hvm</type> + <loader readonly='yes' type='pflash'>/usr/share/qemu-efi-riscv64/RISCV_VIRT_CODE.fd</loader> + <nvram type='file' template='/usr/share/qemu-efi-riscv64/RISCV_VIRT_VARS.fd'> + <source file='/home/ubuntu/RISCV_VIRT_VARS.fd'/> + </nvram> + <boot dev='hd'/> + </os> + <memory unit="MiB">512</memory> + <vcpu placement="static">2</vcpu> + <cpu match='exact'> + <model>rv64</model> + <topology sockets='1' cores='2' threads='1' /> + </cpu> + <devices> + <emulator>usr/bin/qemu-system-riscv64</emulator> + <rng model='virtio'> + <backend model='builtin'/> + </rng> + <console type="pty"> + <target type="serial" port="0"/> + </console> + </devices> </domain> It should be possible to launch the VM but the following is observed $ virsh start ubuntu24.04-riscv64 && virsh console ubuntu24.04-riscv64 --safe error: Failed to start domain 'ubuntu24.04-riscv64' error: internal error: cannot load AppArmor profile 'libvirt-1a35d812-d84c-42c3-a21d-6c67a6c5db06' + User libvirt-qemu needs access (R+X) to the directory with the copy of + /usr/share/qemu-efi-riscv64/RISCV_VIRT_CODE.fd. [ Where problems could occur ] Launching the RISC-V virtual machine with EDK II might still fail. [ Other Info ] Merge request in Debian: https://salsa.debian.org/libvirt-team/libvirt/-/merge_requests/246
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2091357 Title: [SRU] virt-aa-helper: allow riscv64 EDK II To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/2091357/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
