On 04.06.2012 10:53, Gleb Natapov wrote:
> On Sun, Jun 03, 2012 at 06:25:33PM +0200, Johannes Bauer wrote:
>> Therefore, I've uploaded the compressed trace.dat file, so you can maybe
>> have a look why the "report" tool barfs and interpret it correctly. I
>> can't figure it out. The trace is here:
>>
>> http://spornkuller.de/trace.dat.bz2
>>
> I can read this trace.

Hm, weird. But good that it works on your side. I get a lot of:

trace-cmd: No such file or directory
  bad op token {
  failed to read event print fmt for kvm_emulate_insn
version = 6
CPU 0 is empty
cpus=4
 qemu-system-x86-10775 [001]  2512.220779: kvm_fpu:              load
 qemu-system-x86-10775 [001]  2512.220782: kvm_entry:            vcpu 0
 qemu-system-x86-10775 [001]  2512.220785: kvm_exit:             reason
EXCEPTION_NMI rip 0xfff0 info ffff0 80000b0e
 qemu-system-x86-10775 [001]  2512.220787: kvm_page_fault:       address
ffff0 error_code 14
 qemu-system-x86-10775 [001]  2512.220796: kvm_entry:            vcpu 0
 qemu-system-x86-10775 [001]  2512.220798: kvm_exit:             reason
EXCEPTION_NMI rip 0xc81e info 0 80000b0d
 qemu-system-x86-10775 [001]  2512.220803: kvm_emulate_insn:     [FAILED
TO PARSE] rip=51230 csbase=983040 len=3 insn= �f%����"���f flags=0 failed=0
 qemu-system-x86-10775 [001]  2512.220806: kvm_entry:            vcpu 0
 qemu-system-x86-10775 [001]  2512.220807: kvm_exit:             reason
EXCEPTION_NMI rip 0xc827 info 0 80000b0d
 qemu-system-x86-10775 [001]  2512.220808: kvm_emulate_insn:     [FAILED
TO PARSE] rip=51239 csbase=983040 len=3 insn="���f�flags=0 failed=0
[...]

> Can you do "info pci" in qemu's monitor
> after failure? 

(qemu) info pci
  Bus  0, device   0, function 0:
    Host bridge: PCI device 8086:1237
      id ""
  Bus  0, device   1, function 0:
    ISA bridge: PCI device 8086:7000
      id ""
  Bus  0, device   1, function 1:
    IDE controller: PCI device 8086:7010
      BAR4: I/O at 0xc000 [0xc00f].
      id ""
  Bus  0, device   1, function 3:
    Bridge: PCI device 8086:7113
      IRQ 9.
      id ""
  Bus  0, device   2, function 0:
    VGA controller: PCI device 1013:00b8
      BAR0: 32 bit prefetchable memory at 0xf0000000 [0xf1ffffff].
      BAR1: 32 bit memory at 0xf2000000 [0xf2000fff].
      BAR6: 32 bit memory at 0xffffffffffffffff [0x0000fffe].
      id ""
  Bus  0, device   3, function 0:
    Ethernet controller: PCI device 8086:100e
      IRQ 11.
      BAR0: 32 bit memory at 0xf2020000 [0xf203ffff].
      BAR1: I/O at 0xc040 [0xc07f].
      BAR6: 32 bit memory at 0xffffffffffffffff [0x0001fffe].
      id ""
  Bus  0, device   4, function 0:
    SCSI controller: PCI device 1af4:1001
      IRQ 11.
      BAR0: I/O at 0xc080 [0xc0bf].
      BAR1: 32 bit memory at 0xf2060000 [0xf2060fff].
      id ""


>What is your command line?

bin/qemu-system-x86_64 -cpu host -enable-kvm -net nic -net
user,smb=Share,restrict=on -drive
media=disk,file=Windows7_x32.qcow2,if=virtio -m 2048 -smp 1 -nographic

(added "-nographic" to be able to enter the console)

Also, as per Avi's request:

(qemu) x/256b 0x2b0000
00000000002b0000: 0xeb 0x26 0x27 0x00 0x00 0x00 0x2b 0x00
00000000002b0008: 0xff 0xff 0x00 0x00 0x00 0x9a 0xcf 0x00
00000000002b0010: 0xff 0xff 0x00 0x00 0x00 0x92 0xcf 0x00
00000000002b0018: 0xff 0xff 0x00 0x00 0x2b 0x9f 0x00 0x00
00000000002b0020: 0xff 0xff 0x00 0x02 0x00 0x93 0x00 0x00
00000000002b0028: 0x8a 0x15 0x68 0xbc 0x00 0x00 0xa1 0xbf
00000000002b0030: 0x00 0x2b 0x00 0x85 0xc0 0x74 0x06 0x8b
00000000002b0038: 0x1d 0xbb 0x00 0x2b 0x00 0xa1 0xc7 0x00
00000000002b0040: 0x2b 0x00 0x85 0xc0 0x74 0x06 0x8b 0x15
00000000002b0048: 0xc3 0x00 0x2b 0x00 0xbe 0x00 0x00 0x20
00000000002b0050: 0x00 0x31 0xc0 0x31 0xff 0x66 0x8b 0x3d
00000000002b0058: 0xb5 0x00 0x2b 0x00 0xc1 0xe7 0x04 0x66
00000000002b0060: 0xa1 0xb3 0x00 0x2b 0x00 0x01 0xc7 0x8b
00000000002b0068: 0x0d 0xb7 0x00 0x2b 0x00 0xfc 0xf3 0xa4
00000000002b0070: 0x0f 0x01 0x15 0x02 0x00 0x2b 0x00 0x66
00000000002b0078: 0xb8 0x20 0x00 0x8e 0xd8 0x8e 0xc0 0x8e
00000000002b0080: 0xe0 0x8e 0xe8 0x8e 0xd0 0xbc 0x00 0x02
00000000002b0088: 0x00 0x00 0xea 0x91 0x00 0x00 0x00 0x18
00000000002b0090: 0x00 0x0f 0x20 0xc0 0x66 0x83 0xe0 0xfe
00000000002b0098: 0x0f 0x22 0xc0 0x66 0x31 0xc0 0x8e 0xd8
00000000002b00a0: 0x8e 0xc0 0x8e 0xd0 0x66 0xbc 0x00 0x04
00000000002b00a8: 0x00 0x00 0x8e 0xe0 0x8e 0xe8 0xea 0x00
00000000002b00b0: 0x00 0x00 0x20 0x00 0x00 0x00 0x20 0x4a
00000000002b00b8: 0xda 0x05 0x00 0x80 0x00 0x00 0x00 0x01
00000000002b00c0: 0x00 0x00 0x00 0x80 0x00 0x00 0x00 0x01
00000000002b00c8: 0x00 0x00 0x00 0x01 0x00 0x00 0x00 0x90
00000000002b00d0: 0x90 0x90 0x55 0x89 0xe5 0x57 0x8b 0x7d
00000000002b00d8: 0x0c 0x56 0x53 0x8b 0x5d 0x08 0x6a 0x23
00000000002b00e0: 0x6a 0x00 0x68 0x80 0x05 0x00 0x00 0xe8
00000000002b00e8: 0xf3 0xcf 0x00 0x00 0x83 0xc4 0x0c 0x83
00000000002b00f0: 0x3d 0xe0 0x04 0x03 0x00 0x00 0xc6 0x05
00000000002b00f8: 0x80 0x05 0x00 0x00 0x13 0x74 0x0d 0x53

Best regards,
Joe
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to