blob: a9cec06c6eda2a986385f36e5c250aded91de530 (
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
|
graphic: 0.927
files: 0.901
performance: 0.899
network: 0.856
device: 0.829
debug: 0.820
vnc: 0.812
socket: 0.772
PID: 0.725
semantic: 0.655
permissions: 0.652
boot: 0.647
other: 0.388
KVM: 0.260
Replay got stuck with consecutive hardware interrupts coming
Description of problem:
I recorded bin file using **_rr=record_** command line. But it got stuck when replaying this record bin file. The icount number would never change after stucking if I typed _**info replay**_ with qmp command line.
I found that the following instructions should be a sequence of consecutive hardware interrupts after stucking once checking the trace log of
both replay and record log using _**-d in_asm,int**_.
Steps to reproduce:
1.pulling from remote which the newest commit ID is 156618d9ea67f2f2e31d9dedd97f2dcccbe6808c
2.emulating Windows 7 OS on aarch64 Host with TCG acceleration mechanism
3.using **_rr=record_** to make replay file and tracing guest code and interrupts using _**-d in_asm,int**_
4.replaying the previous file and also tracing guest code and interrupts
Additional information:
#
|