summary refs log tree commit diff stats
path: root/results/classifier/zero-shot/118/VMM/1946
blob: 8cdb58dc6d16f70a3502a7fa463ea9e5e619910d (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
VMM: 0.929
performance: 0.903
graphic: 0.867
kernel: 0.861
files: 0.810
device: 0.803
ppc: 0.782
vnc: 0.752
network: 0.738
semantic: 0.735
socket: 0.663
PID: 0.620
virtual: 0.619
debug: 0.604
register: 0.594
KVM: 0.588
user-level: 0.574
hypervisor: 0.567
permissions: 0.550
architecture: 0.546
risc-v: 0.538
boot: 0.525
arm: 0.462
x86: 0.443
mistranslation: 0.442
i386: 0.433
TCG: 0.389
peripherals: 0.325
assembly: 0.191

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