summary refs log tree commit diff stats
path: root/gitlab/issues_text/target_i386/host_x86/accel_missing/1946
diff options
context:
space:
mode:
authorChristian Krinitsin <mail@krinitsin.com>2025-05-30 16:52:07 +0200
committerChristian Krinitsin <mail@krinitsin.com>2025-05-30 16:52:17 +0200
commit9260319e7411ff8281700a532caa436f40120ec4 (patch)
tree2f6bfe5f3458dd49d328d3a9eb508595450adec0 /gitlab/issues_text/target_i386/host_x86/accel_missing/1946
parent225caa38269323af1bfc2daadff5ec8bd930747f (diff)
downloadqemu-analysis-9260319e7411ff8281700a532caa436f40120ec4.tar.gz
qemu-analysis-9260319e7411ff8281700a532caa436f40120ec4.zip
gitlab scraper: download in toml and text format
Diffstat (limited to 'gitlab/issues_text/target_i386/host_x86/accel_missing/1946')
-rw-r--r--gitlab/issues_text/target_i386/host_x86/accel_missing/194628
1 files changed, 28 insertions, 0 deletions
diff --git a/gitlab/issues_text/target_i386/host_x86/accel_missing/1946 b/gitlab/issues_text/target_i386/host_x86/accel_missing/1946
new file mode 100644
index 000000000..0c912f0b1
--- /dev/null
+++ b/gitlab/issues_text/target_i386/host_x86/accel_missing/1946
@@ -0,0 +1,28 @@
+High CPU Load after QEMU 8.1.1
+Description of problem:
+Since the update there is a massive CPU load and this affects the CPU load of the router.
+The VMs are partially for about 3min sporadically not accessible.
+The VMs themselves were not adjusted and I have in the console.
+
+Using the VMM, I was able to see the message recorded below.
+
+`watchdog:_ BUG: soft lockup - CPU#0 stuck for 21s! [swapper/0:0]`
+
+I will also add some data like a XML file of a VM.
+Additional information:
+![webproxy](/uploads/5df86f9adfdd257ca2f43697603567c3/webproxy.PNG)
+[webproxy.log](/uploads/1d428f4c59b2397b9343a62dd8c4bce2/webproxy.log)
+
+[webproxy.xml](/uploads/04221c88956c49d76b4896dd8f6fd1f0/webproxy.xml)
+[Host_Kernel.log](/uploads/f145bf599bf2003b89c17daaabb07143/Host_Kernel.log)
+
+Unfortunately I can't revert to the old QEMU version in the router OS but in the current state all my VM are not really 100% usable anymore.
+
+I would be very grateful if you could take a look at my case.
+
+many thanks in advance.
+
+
+
+
+Paul