summary refs log tree commit diff stats
path: root/results/classifier/zero-shot/118/none/779151
blob: 7b145f57b6d507474e7d1839ccf96334c3c0c3fb (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
63
64
65
virtual: 0.789
performance: 0.581
user-level: 0.528
device: 0.499
debug: 0.478
graphic: 0.466
architecture: 0.461
PID: 0.426
permissions: 0.424
ppc: 0.423
vnc: 0.411
files: 0.405
mistranslation: 0.402
semantic: 0.373
hypervisor: 0.371
network: 0.350
register: 0.321
boot: 0.315
x86: 0.296
i386: 0.295
socket: 0.293
VMM: 0.275
kernel: 0.267
peripherals: 0.211
risc-v: 0.206
assembly: 0.198
TCG: 0.173
arm: 0.160
KVM: 0.109

qemu-nbd crash during using with chroot

I use qemu-nbd to mount my image. And after some times, qemu-nbd crashes and so the chroot freeze.

ps aux | grep qemu :
root      2223  0.0  0.0   9776   548 ?        Ss   18:03   0:00 qemu-nbd --connect=/dev/nbd0 /chroots/test/virtual.img
root      2224  0.0  0.0  10800   544 ?        D    18:03   0:00 qemu-nbd --connect=/dev/nbd0 /chroots/test/virtual.img
root      2227  0.0  0.0      0     0 ?        Z    18:03   0:00 [qemu-nbd] <defunct>
root      2357  0.0  0.0   5212   768 pts/0    D+   18:07   0:00 grep qemu

mount :
/dev/nbd0p1 on /chroots/test/amd64 type ext3 (rw,errors=remount-ro,commit=0)
/dev on /chroots/test/amd64/dev type devtmpfs (rw,mode=0755)
/dev/pts on /chroots/test/amd64/dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
/proc on /chroots/test/amd64/proc type proc (rw)
/sys on /chroots/test/amd64/sys type sysfs (rw,noexec,nosuid,nodev)



After reboot and mount the image, qemu-nbd crashes directly.

Please provide some gdb backtrace from the failing qemu-nbd process, ie, show the root cause of the problem instead of showing multiple symptoms.

Run qemu-nbd under gdb and when it crashes, run "bt" command.  Before doing so, ensure you've debugging symbols for your qemu-nbd binary.

And the most important part - what's the format of the image you're running qemu-nbd against, and what version of qemu-nbd you're using?

Without all this, your bugreport is useless.

Thanks.

Ok i try to get the informations

[Expired for QEMU because there has been no activity for 60 days.]