Bug 1743142 - Boot guest with multiple e1000 devices, qemu will crash after several guest reboots: kvm_mem_ioeventfd_add: error adding ioeventfd: No space left on device (28)
Summary: Boot guest with multiple e1000 devices, qemu will crash after several guest r...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux Advanced Virtualization
Classification: Red Hat
Component: qemu-kvm
Version: 8.1
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: 8.0
Assignee: Peter Xu
QA Contact: Pei Zhang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-19 08:16 UTC by Pei Zhang
Modified: 2020-02-03 04:32 UTC (History)
7 users (show)

Fixed In Version: qemu-kvm-4.1.0-6.module+el8.1.0+4164+854d66f5
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-06 07:18:55 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:3723 0 None None None 2019-11-06 07:19:11 UTC

Description Pei Zhang 2019-08-19 08:16:58 UTC
Description of problem:
Boot guest with 4 e1000 devices, then reboot guest several(> 3) times, qemu will crash.

Version-Release number of selected component (if applicable):
4.18.0-134.el8.x86_64
qemu-kvm-4.1.0-1.module+el8.1.0+3966+4a23dca1.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Boot guest with 4 e1000 devices

2. Reboot guest several times, qemu crash.

# reboot

(qemu) kvm_mem_ioeventfd_add: error adding ioeventfd: No space left on device (28)


Actual results:
qemu crash after rebooting guest with 4 e1000 devices several times.

Expected results:
qemu should keep working well.

Additional info:

Comment 1 Pei Zhang 2019-08-19 08:18:03 UTC
qemu cmd line:

# /usr/libexec/qemu-kvm -name rhel8.1 -machine pc \
-cpu Haswell-noTSX -m 4G \
-smp 4,sockets=2,cores=2,threads=1 \
-device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vgamem_mb=16 \
-vnc 0.0.0.0:1 \
-monitor stdio \
-serial unix:/tmp/monitor1,server,nowait \
-drive file=/home/images_nfv-virt-rt-kvm/rhel8.0.qcow2,format=qcow2,if=none,id=drive-virtio-blk0,werror=stop,rerror=stop \
-device virtio-blk-pci,drive=drive-virtio-blk0,id=virtio-blk0 \
-netdev tap,id=hostnet0 \
-device e1000,netdev=hostnet0,id=net0,mac=fa:5e:07:b4:08:01 \
-netdev tap,id=hostnet1 \
-device e1000,netdev=hostnet1,id=net1,mac=fa:5e:07:b4:08:02 \
-netdev tap,id=hostnet2 \
-device e1000,netdev=hostnet2,id=net2,mac=fa:5e:07:b4:08:03 \
-netdev tap,id=hostnet3 \
-device e1000,netdev=hostnet3,id=net3,mac=fa:5e:07:b4:08:04 \

Comment 9 Pei Zhang 2019-09-09 05:55:36 UTC
Verified with qemu-kvm-4.1.0-7.module+el8.1.0+4177+896cb282.x86_64:

Reboot guest with 4 e1000 NICs 20 times, both qemu and guest keep working very well.

So this bug has been fixed very well. Move to 'VERIFIED'.

Comment 11 errata-xmlrpc 2019-11-06 07:18:55 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:3723


Note You need to log in before you can comment on or make changes to this bug.