blob: a2351eae2c5d83322e73e3396fe6300da2238bca (
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
59
60
61
62
|
graphic: 0.813
virtual: 0.787
architecture: 0.745
x86: 0.681
performance: 0.619
device: 0.600
network: 0.533
boot: 0.483
files: 0.481
socket: 0.455
PID: 0.435
mistranslation: 0.431
semantic: 0.431
VMM: 0.426
vnc: 0.423
ppc: 0.421
debug: 0.413
user-level: 0.411
register: 0.402
permissions: 0.388
assembly: 0.370
hypervisor: 0.368
arm: 0.353
risc-v: 0.350
KVM: 0.307
kernel: 0.277
TCG: 0.261
peripherals: 0.189
i386: 0.182
After upgrade qemu to 5.0.0-0.3.rc2.fc33 the virtual machine with Windows 10 after a while starts to work very slowly
Description of problem:
After upgrade qemu to 5.0.0-0.3.rc2.fc33 the virtual machine with Windows 10 after a while starts to work very slowly
I created the virtual machine with Windows 10 with the following config:
- 1 CPU
- 2GB RAM
- With network access
I launch there a web browser there with flash content.
And usually, the system (Windows 10) does not work there for more than an hour.
When the system starts to work very slowly it doesn't respond to "Reboot" and "Shut Down" commands. Only works "Force Reset" and "Force Off". But when I reboot the system with "Force Reset" it usually stuck at boot at the Windows splash screen. https://imgur.com/yGyacDG
The last version of qemu which not contain this issue is 5.0.0-0.2.rc0.fc33
When VM starts work very slowly System interrupts in Windows Task Manager eats up 99% of all CPU resources.
Please try this patch series: https://lists.gnu.org/archive/html/qemu-devel/2020-05/msg02728.html
Unofficial x86_64 build of v5.0.0 with those 2 patches for Arch is here: [1].
[1] https://download.opensuse.org/repositories/home:/post-factum/Arch/x86_64/
I confirm that with patches https://lists.gnu.org/archive/html/qemu-devel/2020-05/msg02728.html Win 10 in QEMU working already more than 24 hours without issue.
The patches mentioned in the previous comments have been released with QEMU v5.1, so I'm marking this bug as fixed now. If you still have problems, please open a new ticket.
|
