1) What happens if you run systemd-detect-virt by itself, from the command line? Does it work, or does it encounter permission denials as well? 2) When the permission denied errors appear, does AppArmor generate any denial logs? If so, could you please attach them to this bug?
** Tags added: sec-7660 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2127111 Title: within qemu-RISCV64: systemd-detect-virt results in "Failed to check for virtualization: Permission denied" Status in apparmor package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: ubuntu@ubuntu:~$ systemd-detect-virt Failed to check for virtualization: Permission denied ubuntu@ubuntu:~$ sudo systemd-detect-virt Failed to check for virtualization: Permission denied From: systemd 257 (257.9-0ubuntu2) ubuntu@ubuntu:~$ uname -a Linux ubuntu 6.17.0-5-generic #5.1-Ubuntu SMP PREEMPT_DYNAMIC Tue Sep 23 20:28:40 UTC 2025 riscv64 riscv64 riscv64 GNU/Linux This is Ubuntu 25.10 riscv64 running within qemu-system-riscv64 on Ubuntu 25.10 x86_64 See https://github.com/systemd/systemd/issues/39192 for full analysis. Solved with systemd-detect-virt from github: systemd 259 (259~devel) https://github.com/systemd/systemd/issues/39192#issuecomment-3373625656 ProblemType: Bug DistroRelease: Ubuntu 25.10 Package: systemd 257.9-0ubuntu2 ProcVersionSignature: User Name 6.17.0-5.5.1-generic 6.17.0-rc7 Uname: Linux 6.17.0-5-generic riscv64 ApportVersion: 2.33.1-0ubuntu3 Architecture: riscv64 CasperMD5CheckResult: unknown CloudArchitecture: riscv64 CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: 20250624 CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net) CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Wed Oct 8 17:10:26 2025 Lspci-vt: -[0000:00]-+-00.0 Red Hat, Inc. QEMU PCIe Host bridge +-01.0 Red Hat, Inc. Virtio RNG \-02.0 Red Hat, Inc. Virtio block device Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: riscv-virtio qemu ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=vt220 XDG_RUNTIME_DIR=<set> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-5-generic root=UUID=423824f9-91ff-4e47-a13e-549b3604b64e ro efi=debug earlycon=sbi SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) acpidump: dmi.bios.date: 01/01/2025 dmi.bios.release: 25.1 dmi.bios.vendor: U-Boot dmi.bios.version: 2025.01-3ubuntu4 dmi.board.name: qemu dmi.board.vendor: riscv-virtio dmi.chassis.type: 3 dmi.modalias: dmi:bvnU-Boot:bvr2025.01-3ubuntu4:bd01/01/2025:br25.1:svnriscv-virtio:pnqemu:pvr:rvnriscv-virtio:rnqemu:rvr:cvn:ct3:cvr:sku: dmi.product.name: qemu dmi.sys.vendor: riscv-virtio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2127111/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
