summary refs log tree commit diff stats
path: root/results/classifier/zero-shot/118/all/1656234
blob: b8c683abb1d79d692c5a4cfe1db51b6429303393 (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
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
permissions: 0.993
graphic: 0.991
debug: 0.991
semantic: 0.990
architecture: 0.989
assembly: 0.989
PID: 0.988
register: 0.988
files: 0.987
kernel: 0.986
arm: 0.985
performance: 0.985
socket: 0.984
x86: 0.982
risc-v: 0.980
ppc: 0.976
peripherals: 0.976
TCG: 0.975
network: 0.974
vnc: 0.973
boot: 0.973
mistranslation: 0.972
device: 0.972
virtual: 0.971
KVM: 0.969
hypervisor: 0.967
user-level: 0.966
i386: 0.958
VMM: 0.938

Qemu core dumped if using virtio-net

System Environment
=======
Qemu commit/branch: e92fbc75
Host OS: RHEL7.2 ia32e
Host Kernel: 4.9.0
Guest OS: RHEL7.2 ia32e
Guest Kernel: 4.9.0

Bug detailed description
=======
While create a kvm guest using virtio-net, the qemu will core dump with showing "Aborted (core dumped)".
Reproduce Steps
==============
create a guest:
qemu-system-x86_64 -enable-kvm -m 4096 -smp 4 -device virtio-net-pci,netdev=nic0,mac=00:16:3e:49:be:24 -netdev tap,id=nic0,script=/etc/kvm/qemu-ifup -drive file=/ia32e_rhel7u2_kvm.qcow2,if=none,id=virtio-disk0 -device virtio-blk-pci,drive=virtio-disk0 -serial file:serial.log

Current Result:
==============

qemu-system-x86_64: /workspace/ia32e/nightly/kvm-next-20170105-ef85b6-e92fbc/kvm/qemu/hw/virtio/virtio.c:214: virtio_queue_set_notification: Assertion `vq->notification_disabled > 0' failed.
Aborted (core dumped)

add info
========
[root@hsw-ep2 Desktop]# dmesg |grep -v virbr0 |tail -n 10
[ 1760.265000] device tap0 left promiscuous mode
[ 1879.148642] device tap0 entered promiscuous mode
[ 1885.213702] kvm [14186]: vcpu0, guest rIP: 0xffffffff81066784 disabled perfctr wrmsr: 0xc2 data 0xffff
[ 1912.258783] device tap0 left promiscuous mode
[ 1995.972267] device tap0 entered promiscuous mode
[ 2001.990207] kvm [14335]: vcpu0, guest rIP: 0xffffffff81066784 disabled perfctr wrmsr: 0xc2 data 0xffff
[ 2024.703072] device tap0 left promiscuous mode
[ 2145.374239] device tap0 entered promiscuous mode
[ 2151.409948] kvm [14541]: vcpu0, guest rIP: 0xffffffff81066784 disabled perfctr wrmsr: 0xc2 data 0xffff
[ 2178.281446] device tap0 left promiscuous mode



On Fri, Jan 13, 2017 at 08:40:22AM -0000, Robert Hu wrote:
> Public bug reported:
> 
> System Environment
> =======
> Qemu commit/branch: e92fbc75
> Host OS: RHEL7.2 ia32e
> Host Kernel: 4.9.0
> Guest OS: RHEL7.2 ia32e
> Guest Kernel: 4.9.0
> 
> Bug detailed description
> =======
> While create a kvm guest using virtio-net, the qemu will core dump with showing "Aborted (core dumped)".
> Reproduce Steps
> ==============
> create a guest:
> qemu-system-x86_64 -enable-kvm -m 4096 -smp 4 -device virtio-net-pci,netdev=nic0,mac=00:16:3e:49:be:24 -netdev tap,id=nic0,script=/etc/kvm/qemu-ifup -drive file=/ia32e_rhel7u2_kvm.qcow2,if=none,id=virtio-disk0 -device virtio-blk-pci,drive=virtio-disk0 -serial file:serial.log
> 
> Current Result:
> ==============
> 
> qemu-system-x86_64: /workspace/ia32e/nightly/kvm-next-20170105-ef85b6-e92fbc/kvm/qemu/hw/virtio/virtio.c:214: virtio_queue_set_notification: Assertion `vq->notification_disabled > 0' failed.
> Aborted (core dumped)

Thanks for reporting this assertion failure.  A patch is queued and will
be merged soon:
https://lists.gnu.org/archive/html/qemu-devel/2017-01/msg02277.html

Stefan


Fix had been included here:
https://git.qemu.org/?p=qemu.git;a=commitdiff;h=332fa82d0963409