diff options
Diffstat (limited to 'gitlab/issues/target_arm/host_arm')
11 files changed, 288 insertions, 0 deletions
diff --git a/gitlab/issues/target_arm/host_arm/accel_HVF/2072.toml b/gitlab/issues/target_arm/host_arm/accel_HVF/2072.toml new file mode 100644 index 000000000..0aff96b75 --- /dev/null +++ b/gitlab/issues/target_arm/host_arm/accel_HVF/2072.toml @@ -0,0 +1,15 @@ +id = 2072 +title = "Regression in 8.2: Synchronous Exception when running a VM on AArch64" +state = "closed" +created_at = "2024-01-04T19:57:56.783Z" +closed_at = "2024-01-05T22:21:36.990Z" +labels = ["accel: HVF", "host: arm", "target: arm"] +url = "https://gitlab.com/qemu-project/qemu/-/issues/2072" +host-os = "n/a" +host-arch = "n/a" +qemu-version = "n/a" +guest-os = "n/a" +guest-arch = "n/a" +description = "n/a" +reproduce = "n/a" +additional = "n/a" diff --git a/gitlab/issues/target_arm/host_arm/accel_HVF/2312.toml b/gitlab/issues/target_arm/host_arm/accel_HVF/2312.toml new file mode 100644 index 000000000..df260c315 --- /dev/null +++ b/gitlab/issues/target_arm/host_arm/accel_HVF/2312.toml @@ -0,0 +1,52 @@ +id = 2312 +title = "hvf_vcpu_exec isv assert with qemu-xhci device" +state = "closed" +created_at = "2024-04-25T19:52:40.633Z" +closed_at = "2024-09-16T16:13:34.496Z" +labels = ["accel: HVF", "host: arm", "hostos: macOS", "target: arm"] +url = "https://gitlab.com/qemu-project/qemu/-/issues/2312" +host-os = "macOS" +host-arch = "aarch64" +qemu-version = "9.0.0" +guest-os = "u-boot" +guest-arch = "aarch64" +description = """Using the qemu-xhci device with HVF on darwin-aarch64 causes [this assert](https://gitlab.com/qemu-project/qemu/-/blob/master/target/arm/hvf/hvf.c#L1920) to fire. + +``` +travis@gmachine vms % cat launch.sh +#!/usr/bin/env bash + +~/sources/nixpkgs/result-qemu/bin/qemu-system-aarch64 \\ + -nographic \\ + -machine virt \\ + -accel hvf \\ + -cpu host \\ + -m 16M \\ + -device qemu-xhci \\ + -bios ~/sources/nixpkgs/result-uboot-bin/u-boot.bin +travis@gmachine vms % ./launch.sh + + +U-Boot 2024.04 (Apr 02 2024 - 10:58:58 +0000) + +DRAM: 16 MiB (effective 16 EiB) +Assertion failed: (isv), function hvf_vcpu_exec, file ../target/arm/hvf/hvf.c, line 1920. +./launch.sh: line 10: 22295 Abort trap: 6 ~/sources/nixpkgs/result-qemu/bin/qemu-system-aarch64 -nographic -machine virt -accel hvf -cpu host -m 16M -device qemu-xhci -bios ~/sources/nixpkgs/result-uboot-bin/u-boot.bin +``` + +This is NixOS' build of u-boot 2024.04. This is also Nixpkgs' build of qemu-9.0.0; by default it contains some patches, but if I remove those and build with the unmodified release tarball there's no change in behavior. Naturally this doesn't happen with TCG and I haven't found any other (non-USB) device to cause this issue.""" +reproduce = """On a darwin-aarch64 machine with git and nix setup (8.2.2 is latest in Nixpkgs head, the same problem occurs with 9.0.0): + +``` +% git clone https://github.com/nixos/nixpkgs +% cd ./nixpkgs +% $(nix-build -A qemu)/bin/qemu-system-aarch64 -nographic -machine virt -accel hvf -cpu host -m 16M -device qemu-xhci -bios $(nix-build -E 'with import ./default.nix {system = "aarch64-linux";}; ubootQemuAarch64')/u-boot.bin + + +U-Boot 2024.04 (Apr 02 2024 - 10:58:58 +0000) + +DRAM: 16 MiB (effective 16 EiB) +Assertion failed: (isv), function hvf_vcpu_exec, file ../target/arm/hvf/hvf.c, line 1915. +zsh: abort $(nix-build -A qemu)/bin/qemu-system-aarch64 -nographic -machine virt -accel +```""" +additional = """I have not yet tried other u-boot binaries. I suppose it could be u-boots fault? Eyeballing hvf.c this seems to be an unhandled case in the MMIO callback? I'm far out of my element so that could be total nonsense.""" diff --git a/gitlab/issues/target_arm/host_arm/accel_HVF/2893.toml b/gitlab/issues/target_arm/host_arm/accel_HVF/2893.toml new file mode 100644 index 000000000..9c755f601 --- /dev/null +++ b/gitlab/issues/target_arm/host_arm/accel_HVF/2893.toml @@ -0,0 +1,22 @@ +id = 2893 +title = "with m4 mac mini windows 11 arm 64 iso not booting for installation" +state = "opened" +created_at = "2025-03-30T22:19:25.938Z" +closed_at = "n/a" +labels = ["accel: HVF", "guest: Windows", "host: arm", "target: arm"] +url = "https://gitlab.com/qemu-project/qemu/-/issues/2893" +host-os = "macOS" +host-arch = "- QEMU flavor: qemu-aarch64" +qemu-version = "9.3.2" +guest-os = "Windows 11 Latest" +guest-arch = "ARM64" +description = """Trying to run win11 arm 64 version in m4 mac mini and the ios failed to boot + +i went to the efi shell and tried to boot from there and it just hangs no problem reported + +when i attach the serial to stdio i get the error convertprogress failed to find range errors""" +reproduce = """1. In m4 mac mini download win11 arm 64 iso from microsoft site +2. run the above mentioned command and you will see that it does not boot + +/label ~"kind::Bug"""" +additional = "n/a" diff --git a/gitlab/issues/target_arm/host_arm/accel_HVF/2913.toml b/gitlab/issues/target_arm/host_arm/accel_HVF/2913.toml new file mode 100644 index 000000000..bd6e3adbd --- /dev/null +++ b/gitlab/issues/target_arm/host_arm/accel_HVF/2913.toml @@ -0,0 +1,15 @@ +id = 2913 +title = "vmapple machine unusable with macOS 15.4" +state = "opened" +created_at = "2025-04-03T12:06:33.662Z" +closed_at = "n/a" +labels = ["accel: HVF", "host: arm", "target: arm"] +url = "https://gitlab.com/qemu-project/qemu/-/issues/2913" +host-os = "n/a" +host-arch = "n/a" +qemu-version = "n/a" +guest-os = "n/a" +guest-arch = "n/a" +description = "n/a" +reproduce = "n/a" +additional = "n/a" diff --git a/gitlab/issues/target_arm/host_arm/accel_KVM/2551.toml b/gitlab/issues/target_arm/host_arm/accel_KVM/2551.toml new file mode 100644 index 000000000..08201c8c8 --- /dev/null +++ b/gitlab/issues/target_arm/host_arm/accel_KVM/2551.toml @@ -0,0 +1,21 @@ +id = 2551 +title = "RTC time could run slow 3s than host time when clock=vm & base=UTC" +state = "opened" +created_at = "2024-09-03T01:46:44.266Z" +closed_at = "n/a" +labels = ["accel: KVM", "host: arm", "target: arm"] +url = "https://gitlab.com/qemu-project/qemu/-/issues/2551" +host-os = "EulerOS" +host-arch = "ARM" +qemu-version = "QEMU emulator version 6.2.0 (qemu-6.2.0.oe2203sp1-2.12.0.5.399)" +guest-os = "EulerOS" +guest-arch = "ARM" +description = """When start qemu with `-rtc base=utc,clock=vm`, sometime guest time can slower 3s than host. There's no problem (also didn't be noticed) as we often start ntp service, who will adjust our system time. But let's talk about if we havn't enable NTP service(for example system just booted) + +After inspect into the code, i found that there are two problem we should think about: +#""" +reproduce = """1. start vm with `-rtc base=utc,clock=vm` +2. disable NTP (OS specific)`systemctl disable --now ntpd;systemctl disable --now ntpdate` +3. reboot in the guest +4. after guest started, compare guest time with host time(at the same time) `date +'%F %T.%3N'`""" +additional = """""" diff --git a/gitlab/issues/target_arm/host_arm/accel_TCG/1616.toml b/gitlab/issues/target_arm/host_arm/accel_TCG/1616.toml new file mode 100644 index 000000000..cf831f40e --- /dev/null +++ b/gitlab/issues/target_arm/host_arm/accel_TCG/1616.toml @@ -0,0 +1,15 @@ +id = 1616 +title = "convd on arm tcg test fails on arm64 (Apple M1)" +state = "closed" +created_at = "2023-04-24T07:14:08.323Z" +closed_at = "2023-08-14T08:26:34.155Z" +labels = ["accel: TCG", "host: arm", "target: arm", "workflow::Needs Info"] +url = "https://gitlab.com/qemu-project/qemu/-/issues/1616" +host-os = "n/a" +host-arch = "n/a" +qemu-version = "n/a" +guest-os = "n/a" +guest-arch = "n/a" +description = "n/a" +reproduce = "n/a" +additional = "n/a" diff --git a/gitlab/issues/target_arm/host_arm/accel_Xen/2173.toml b/gitlab/issues/target_arm/host_arm/accel_Xen/2173.toml new file mode 100644 index 000000000..15b54cb93 --- /dev/null +++ b/gitlab/issues/target_arm/host_arm/accel_Xen/2173.toml @@ -0,0 +1,15 @@ +id = 2173 +title = "Disable CPU dirty region tracking on Xen + Arm64 where xen migration is not supported." +state = "opened" +created_at = "2024-02-16T19:24:53.395Z" +closed_at = "n/a" +labels = ["accel: Xen", "host: arm", "target: arm", "workflow::In Progress"] +url = "https://gitlab.com/qemu-project/qemu/-/issues/2173" +host-os = "n/a" +host-arch = "n/a" +qemu-version = "n/a" +guest-os = "n/a" +guest-arch = "n/a" +description = "n/a" +reproduce = "n/a" +additional = "n/a" diff --git a/gitlab/issues/target_arm/host_arm/accel_missing/1167.toml b/gitlab/issues/target_arm/host_arm/accel_missing/1167.toml new file mode 100644 index 000000000..61fa71238 --- /dev/null +++ b/gitlab/issues/target_arm/host_arm/accel_missing/1167.toml @@ -0,0 +1,15 @@ +id = 1167 +title = "Does qemu-system-aarch64 support hyper-v elightenment feature for windows for arm guest?" +state = "closed" +created_at = "2022-08-22T02:16:26.062Z" +closed_at = "2022-08-26T18:36:24.560Z" +labels = ["host: arm", "kind::Feature Request", "target: arm"] +url = "https://gitlab.com/qemu-project/qemu/-/issues/1167" +host-os = "n/a" +host-arch = "n/a" +qemu-version = "n/a" +guest-os = "n/a" +guest-arch = "n/a" +description = "n/a" +reproduce = "n/a" +additional = "n/a" diff --git a/gitlab/issues/target_arm/host_arm/accel_missing/1776.toml b/gitlab/issues/target_arm/host_arm/accel_missing/1776.toml new file mode 100644 index 000000000..cba40af60 --- /dev/null +++ b/gitlab/issues/target_arm/host_arm/accel_missing/1776.toml @@ -0,0 +1,15 @@ +id = 1776 +title = "qemu-armel SEGFAULTs when trying to map a commpage on armel" +state = "closed" +created_at = "2023-07-21T15:29:42.247Z" +closed_at = "2023-08-24T12:02:03.890Z" +labels = ["host: arm", "kind::Bug", "linux-user", "target: arm"] +url = "https://gitlab.com/qemu-project/qemu/-/issues/1776" +host-os = "n/a" +host-arch = "n/a" +qemu-version = "n/a" +guest-os = "n/a" +guest-arch = "n/a" +description = "n/a" +reproduce = "n/a" +additional = "n/a" diff --git a/gitlab/issues/target_arm/host_arm/accel_missing/1857.toml b/gitlab/issues/target_arm/host_arm/accel_missing/1857.toml new file mode 100644 index 000000000..57effb592 --- /dev/null +++ b/gitlab/issues/target_arm/host_arm/accel_missing/1857.toml @@ -0,0 +1,60 @@ +id = 1857 +title = "Major qemu-aarch64 performance slowdown since commit 59b6b42cd3" +state = "closed" +created_at = "2023-09-01T14:00:23.709Z" +closed_at = "2023-09-01T15:15:06.829Z" +labels = ["host: arm", "host: loongarch64", "target: arm"] +url = "https://gitlab.com/qemu-project/qemu/-/issues/1857" +host-os = "Gentoo Linux & Ubuntu & Debian" +host-arch = "loongarch64 & aarch64 & x86_64" +qemu-version = "8.0.0, 8.1.0 and master" +guest-os = "Linux user" +guest-arch = "AArch64" +description = """I have observed a major performance slowdown between qemu 8.0.0 and 8.1.0: + + +qemu 8.0.0: 0.8s + +qemu 8.1.0: 6.8s + + +After bisecting the commits between 8.0.0 and 8.1.0, the offending commit is 59b6b42cd3: + + +commit 59b6b42cd3446862567637f3a7ab31d69c9bef51 +Author: Richard Henderson <richard.henderson@linaro.org> +Date: Tue Jun 6 10:19:39 2023 +0100 + + target/arm: Enable FEAT_LSE2 for -cpu max + + Reviewed-by: Peter Maydell <peter.maydell@linaro.org> + Signed-off-by: Richard Henderson <richard.henderson@linaro.org> + Message-id: 20230530191438.411344-21-richard.henderson@linaro.org + Signed-off-by: Peter Maydell <peter.maydell@linaro.org> + + +Reverting the commit in latest master fixes the problem: + +qemu 8.0.0: 0.8s + +qemu 8.1.0: 6.8s + +qemu master + revert 59b6b42cd3: 0.8s + +Alternatively, specify `-cpu cortex-a35` to disable LSE2: + +`time ./qemu-aarch64 -cpu cortex-a35`: 0.8s + +`time ./qemu-aarch64`: 6.77s + +The slowdown is also observed when running qemu-aarch64 on aarch64 machine: + +`time ./qemu-aarch64 /usr/bin/node -e 1`: 2.91s + +`time ./qemu-aarch64 -cpu cortex-a35 /usr/bin/node -e 1`: 1.77s + +The slowdown on x86_64 machine is small: 362ms -> 378ms.""" +reproduce = """1. Run `time ./qemu-aarch64 node-aarch64 -e 1` (node-aarch64 is NodeJS v16 built for AArch64) +2. Using qemu master, the output says `0.8s` +3. Using qemu master with commit 59b6b42cd3 reverted, the output says `6.77s`""" +additional = """""" diff --git a/gitlab/issues/target_arm/host_arm/accel_missing/2884.toml b/gitlab/issues/target_arm/host_arm/accel_missing/2884.toml new file mode 100644 index 000000000..9f9f7e14c --- /dev/null +++ b/gitlab/issues/target_arm/host_arm/accel_missing/2884.toml @@ -0,0 +1,43 @@ +id = 2884 +title = "Questions about vfio-pci" +state = "opened" +created_at = "2025-03-27T09:32:21.969Z" +closed_at = "n/a" +labels = ["VFIO", "host: arm", "target: arm"] +url = "https://gitlab.com/qemu-project/qemu/-/issues/2884" +host-os = "n/a" +host-arch = "ARM" +qemu-version = "qemu v6.2.0 (qemu v8.2.0 also reproduces)" +guest-os = "n/a" +guest-arch = "n/a" +description = """When I use VFIO-PCI to pass through an hns3 device and load the driver to the VM to enable the hns3 network port, there is a possibility that the failure occurs.""" +reproduce = """1. Start the VM and load the hns3 driver. +2. enable net port + + `ifconfig eth0 10.10.10.10/24 up` +3. ping host + + `ping 10.10.10.11 -c 3`""" +additional = """I have the following findings: + +1. The problem can be reproduced in different kernel versions and QEMU versions. +2. The problem does not recur when the number of vCPUs is 1. +3. It is irrelevant to the GIC version. + +the hns3 relately logic: + +{width="394" height="285"} + +If the VM has two vCPUs, "ifconfig eth0 10.10.10.10/24 up" command performs two sequential enable_irq operations(vector_num=2). The enable_irq will trap into KVM for interrupt configuration and exit to QEMU for PCI device emulation. When emulating interrupt enabling in QEMU, vfio\\_\\[intx/msi/msix\\]\\_enable calls vfio_disable_interrupts to disable all interrupts on the vdev. + +{width="455" height="266"} + +vfio_disable_interrupts in QEMU calls the kernel vfio driver interface vfio_pci_set_irqs_ioctl + +{width="404" height="127"} + +dump stack as above. and then its_irq_domain_deactivate will call its_send_discard to discard the interrupt on the device. + +If an interrupt is handled after the first enable_irq but the second enable_irq discards it, this inconsistency leads to network port enablement failures. + +It puzzles me. why does the vfio-pci disable all interrupts of the device before enabling irqs?""" |