blob: 6b88698f10b9ef3abb93efd4bfbda529182c0833 (
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
|
semantic: 0.282
instruction: 0.259
device: 0.239
graphic: 0.177
mistranslation: 0.134
assembly: 0.093
socket: 0.089
other: 0.088
network: 0.077
vnc: 0.074
boot: 0.067
KVM: 0.066
Breakpoint on Memory address fails with KVM
Using QEMU version 0.12.50 under ubuntu Karmic x64
To reproduce the error using a floppy with a bootloder:
qemu-system-x86_64 -s -S -fda floppy.img -boot a -enable-kvm
connect with gdb:
(gdb) set arch i8086
The target architecture is assumed to be i8086
(gdb) target remote localhost:1234
Remote debugging using localhost:1234
0x0000fff0 in ?? ()
(gdb) break *0x7c00
Breakpoint 1 at 0x7c00
(gdb) continue
Continuing.
The breakpoint is not hit.
If you close qemu and start it without kvm support:
qemu-system-x86_64 -s -S -fda floppy.img -boot a
(gdb) set arch i8086
The target architecture is assumed to be i8086
(gdb) target remote localhost:1234
Remote debugging using localhost:1234
0x0000fff0 in ?? ()
(gdb) break *0x7c00
Breakpoint 1 at 0x7c00
(gdb) continue
Continuing.
Breakpoint 1, 0x00007c00 in ?? ()
(gdb)
The breakpoint is hit. If you wait until after the bootloader has been loaded into memory, you can properly set breakpoints with or without kvm enabled.
Triaging old bug tickets ... can you still reproduce this issue with the
latest version of QEMU (currently version 2.8)?
[Expired for QEMU because there has been no activity for 60 days.]
|