summary refs log tree commit diff stats
path: root/gitlab/issues/target_missing/host_missing/accel_TCG/1684.toml
diff options
context:
space:
mode:
Diffstat (limited to 'gitlab/issues/target_missing/host_missing/accel_TCG/1684.toml')
-rw-r--r--gitlab/issues/target_missing/host_missing/accel_TCG/1684.toml53
1 files changed, 53 insertions, 0 deletions
diff --git a/gitlab/issues/target_missing/host_missing/accel_TCG/1684.toml b/gitlab/issues/target_missing/host_missing/accel_TCG/1684.toml
new file mode 100644
index 00000000..e5746668
--- /dev/null
+++ b/gitlab/issues/target_missing/host_missing/accel_TCG/1684.toml
@@ -0,0 +1,53 @@
+id = 1684
+title = "QEMU doesn't use multi-threaded TCG on aarch64 host with x86-64 guest"
+state = "closed"
+created_at = "2023-06-04T00:55:59.561Z"
+closed_at = "2023-06-27T11:36:35.497Z"
+labels = ["Closed::Fixed", "accel: TCG", "kind::Feature Request"]
+url = "https://gitlab.com/qemu-project/qemu/-/issues/1684"
+host-os = "Debian 11"
+host-arch = "aarch64"
+qemu-version = "QEMU emulator version 5.2.0 (Debian 1:5.2+dfsg-11+deb11u2)"
+guest-os = "Debian 11"
+guest-arch = "amd64"
+description = """Even configured to emulate more than one vCPU, at the host it only uses 1 CPU at 100%. The same test was made using same architecture (aarch64 on aarch64), and it archieves to use all phisical cores. The first VM uses TGC, the second one uses KVM. Screenshots attached."""
+reproduce = """1. Use official Debian distro from Rock Pi 5B
+2. Install XFCE4 and VirtManager, qemu aarch64 and qemu x86_64
+3. Download debian x64 netinstall iso
+4. Install system with basic features, then install stress-ng
+5. Stop, configure -smp to 1 socket, 4 cores, 2 threads, it will result on 8 vCPUs
+6. Login as root and run stress-ng to 8 CPU
+7. Ctrl+Right to another TTY, install and run htop, you will see 8 CPUs on 100% usage
+8. At host, open Terminal, install and run htop, you will see just one core at 100%"""
+additional = """Both VMs tested. aarch64 as KVM that works fine, x86_64 as TGC that uses only one CPU.
+![Captura_de_tela_2023-06-03_212555](/uploads/970abc27e3adf29b14abea17c5faeff9/Captura_de_tela_2023-06-03_212555.jpg)
+
+VirtManager VM #1 config for x86_64 on aarch64
+![Captura_de_tela_2023-06-03_212617](/uploads/1884d4808cb24aae688dace64cdd275d/Captura_de_tela_2023-06-03_212617.jpg)
+
+VirtManager VM #2 config for aarch64 on aarch64
+![Captura_de_tela_2023-06-03_212711](/uploads/11e785a1a798423dfd9e7a56db8a8a35/Captura_de_tela_2023-06-03_212711.jpg)
+
+VirtManager VM #2 hypervisor used as KVM
+![Captura_de_tela_2023-06-03_212727](/uploads/996783f4141f8e296885ebe79b3b53f2/Captura_de_tela_2023-06-03_212727.jpg)
+
+VirtManager VM #1 hypervisor used as TGC
+![Captura_de_tela_2023-06-03_212742](/uploads/a9ee42aa217ba150be8cc34de716a8a4/Captura_de_tela_2023-06-03_212742.jpg)
+
+100% on host of all cores being used with stress-ng at aarch64 guest
+![Captura_de_tela_2023-06-03_212822](/uploads/880f7a7f69bb4eb87eab5c6912b2ff91/Captura_de_tela_2023-06-03_212822.jpg)
+
+All cores at 100% on aarch64 guest
+![Captura_de_tela_2023-06-03_212853](/uploads/8c154c0c403a06964b7f3439b7e5b2bf/Captura_de_tela_2023-06-03_212853.jpg)
+
+100% on host of just one core being used with stress-ng at x86_64 guest
+![Captura_de_tela_2023-06-03_212932](/uploads/ba82f08f1ceba18d35006689cacaafa4/Captura_de_tela_2023-06-03_212932.jpg)
+
+Cool down after both VMs ended stress-ng process
+![Captura_de_tela_2023-06-03_212959](/uploads/ed91dba107929c93d0ca7062ae4c3b05/Captura_de_tela_2023-06-03_212959.jpg)
+
+virsh version
+![Captura_de_tela_2023-06-03_213026](/uploads/bf5529e6f3a02eb11ad20d31380e3d5b/Captura_de_tela_2023-06-03_213026.jpg)
+
+"dmesg | head -n50" at host machine
+![Captura_de_tela_2023-06-03_213637](/uploads/87737c69a2a178c9062dcc6340b03d3e/Captura_de_tela_2023-06-03_213637.jpg)"""