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
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
|
PID: 0.959
user-level: 0.958
semantic: 0.914
mistranslation: 0.913
ppc: 0.913
graphic: 0.909
architecture: 0.906
device: 0.904
performance: 0.894
peripherals: 0.885
permissions: 0.885
TCG: 0.868
risc-v: 0.867
i386: 0.858
debug: 0.844
assembly: 0.830
register: 0.825
x86: 0.818
vnc: 0.818
hypervisor: 0.805
VMM: 0.804
socket: 0.761
kernel: 0.750
KVM: 0.722
arm: 0.708
boot: 0.699
network: 0.697
files: 0.693
virtual: 0.620
qemu segfault error when using pcie to dual pci adapter
All the information I have is located in the Unraid forum on post "https://forums.unraid.net/topic/78545-internal-error-qemu-unexpectedly-closed-the-monitor"
I am happy to provide any addition information requested. Please let me know. Reporting bug here based on recommendation by admin in that forum.
hmm that's a fun board.
It looks like qemu has segfaulted;
1) is this a qemu build you built yourself? If so, exactly which version, built on which distro?
2) Could you get a backtrace of qemu crashing - this might be easiest if your distro records core dumps somewhere.
FYI: I was happy to find the board and I'm hopeful to get it working. My goal is to use old hardware to make a retro gaming machine for my girls to play games I used to play growing up.
1)No its the qemu installed with unraid version 6.6.7, which i believe is qemu 3.0
2)im willing to get any notes, logs, or dumps you wish. I just need to know how to do it.
I don't know anything about unraid unfortunately; so I suggest you go back to their forums and ask how to get the backtrace.
I have requested additional info in the other forum. While I wait on reply there, i will say, since you dont know it well, that Unraid is a disto built on top of slackware. Are there any basic command line commands that i could run to get the output you requested, or something to keep things moving while i wait on additional info from the other forum.
Hi! Did you ever get a backtrace? ... otherwise I think we have to close this ticket due to insufficient data...
No I never did. I reached out to try and get info on how to run or get a backtrack and never heard anything. I finally gave up and ended up selling the computer since I never got it working how I wanted to.
> On Nov 25, 2020, at 10:20 AM, Thomas Huth <email address hidden> wrote:
>
> Hi! Did you ever get a backtrace? ... otherwise I think we have to close
> this ticket due to insufficient data...
>
> ** Changed in: qemu
> Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1821054
>
> Title:
> qemu segfault error when using pcie to dual pci adapter
>
> Status in QEMU:
> Incomplete
>
> Bug description:
> All the information I have is located in the Unraid forum on post "https://forums.unraid.net/topic/78545-internal-error-qemu-unexpectedly-closed-the-monitor"
> I am happy to provide any addition information requested. Please let me know. Reporting bug here based on recommendation by admin in that forum.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/qemu/+bug/1821054/+subscriptions
Ok, thanks for getting back. So I'm closing this now due to insufficient data.
|