RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1460073 - Guest reboot during data transfer with virtio serial port triggers "Virtqueue size exceeded"
Summary: Guest reboot during data transfer with virtio serial port triggers "Virtqueue...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: qemu-kvm
Version: 7.3
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: pagupta
QA Contact: Sitong Liu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-09 01:54 UTC by Sitong Liu
Modified: 2017-07-10 12:01 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-06-14 06:52:24 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Sitong Liu 2017-06-09 01:54:43 UTC
Description of problem:
Guest reboot during data transfer with virtio serial port triggers "Virtqueue size exceeded", qemu process quits.

Version-Release number of selected component (if applicable):
qemu-kvm-1.5.3-126.el7_3.9 (fail)
qemu-kvm-1.5.3-126.el7_3.8 (fail)
qemu-kvm-1.5.3-126.el7_3.7 (fail)

kernel 3.10.0-514.el7.x86_64 (host and guest) (fail)
kernel 3.10.0-668.el7.x86_64 (host and guest) (fail)

How reproducible:
(4/4)

Steps to Reproduce:
1.boot up guest with the following cli

/usr/libexec/qemu-kvm -M pc -name seabios-test -enable-kvm -m 4G -cpu SandyBridge -smp 4,cores=4,threads=1,sockets=1,maxcpus=4 -nodefconfig \
-nodefaults -chardev socket,id=charmonitor,path=/tmp/126NICW10S64SOB,server,nowait \
-mon chardev=charmonitor,id=monitor,mode=control \
-rtc base=localtime,driftfix=slew -boot order=ncd,menu=on \
-vga std \
-vnc :2 \
-device virtio-serial-pci,id=virtio-serial0,max_ports=16,bus=pci.0,addr=0x4 \
-chardev socket,id=channel0,host=127.0.0.1,port=12345,server,nowait \
-device virtserialport,chardev=channel0,name=org.linux-kvm.port.0,bus=virtio-serial0.0,id=port1 \
-qmp tcp:0:6666,server,nowait \
-drive file=/home/kvm_autotest_root/images/rhel73-64-virtio.qcow2,if=none,id=drive-ide0-0-0,cache=none,werror=stop,rerror=stop,aio=threads \
-device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1 -boot menu=on \
-device virtio-net-pci,netdev=tap10,mac=64:31:50:23:6d:63 \
-netdev tap,id=tap10 \
-monitor stdio

2. Transfering data from guest to host via port1 in a loop
//guest
for(;;)
do
    echo $a > /dev/vport1p1
    a=$(($a+1))
done

//host
nc 127.0.0.1 12345

3. ctrl+c host and guest, reboot guest, and repeat step 2.
repeat several times.

Actual results:
Qemu process quits, triggers "Virtqueue size exceeded".

Expected results:
Qemu works well after reboot.

Additional info:
It is not a regression bug.


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