Bug 759019
Summary: | [virtio-win][serial]Qemu-kvm quit with "Guest move used index from 0 to 256" after hot unplug/plug virtio-serial-port while it is in use | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Mike Cao <bcao> |
Component: | virtio-win | Assignee: | Gal Hammer <ghammer> |
Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | high | Docs Contact: | |
Priority: | urgent | ||
Version: | 6.3 | CC: | acathrow, amit.shah, bcao, bsarathy, juzhang, mdeng, michen, mst, rhod, tburke, virt-maint, yvugenfi |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | virtio-win-prewhql-0.1-51 | Doc Type: | Bug Fix |
Doc Text: |
This was noticed by hot-unplugging a virtio console port and then plugging in a new one on the same number (re-using the vqs which were just 'disowned'). qemu reported 'Guest moved used index from 0 to 256' when any IO was attempted on the new port.
When detaching a buffer from a vq, the avail.idx value should be decremented as well.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2013-11-21 23:55:48 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Mike Cao
2011-12-01 09:11:42 UTC
(In reply to comment #0) > > How reproducible: > 1 times ,other time hit Bug 759011 > Retried ,very easy to reproduce . Seems to be identical to https://bugzilla.redhat.com/show_bug.cgi?id=781292. The other bug is pure Linux, maybe better to close this one. mst, any comments? Seems like a different problem to me. Let me check this issue, before we move forward. best, Vadim. Raise the priority because half of the functional test cases for virtio serial is related to pci hot plug/unplug. (In reply to comment #5) > Raise the priority because half of the functional test cases for virtio serial > is related to pci hot plug/unplug. It's not urgent since hotplug of virtio-serial is not common so I deferred it to the next release. Please add technical notes to the issue (In reply to comment #6) > (In reply to comment #5) > > Raise the priority because half of the functional test cases for virtio serial > > is related to pci hot plug/unplug. > > It's not urgent since hotplug of virtio-serial is not common so I deferred it > to the next release. Please add technical notes to the issue Ok. Will do it tmr . and FYI ,there is a similar Bug 681122 for RHEL guest which has already been fixed in RHEL6.2 Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: This was noticed by hot-unplugging a virtio console port and then plugging in a new one on the same number (re-using the vqs which were just 'disowned'). qemu reported 'Guest moved used index from 0 to 256' when any IO was attempted on the new port. When detaching a buffer from a vq, the avail.idx value should be decremented as well. In work- need to test with the next version - in 2-3 weeks I still can reproduce the issue on virtio-win-prewhql-35 on win7-32 OS. Too late for such issue in RHEL6.4. Deferring to 6.5. Maybe worth checking again since it seems since a related bug 801423 is fixed. Checking latest build virtio-win-prewhql-41 on win7-32, still hit the issue. Reproduce this bug with virtio-win-prewhql-41 on win7-32,verified this bug with virtio-win-prewhql-51 with steps as comment #0 Actually Results: on version virtio-win-prewhql-41,qemu-kvm quit with "Guest move used index from 0 to 256" on version virtio-win-prewhql-51, guest works well without any error. Based on above, this issue has been fixed. Thanks! Best Regards, Dawn Based on comment#16 This issue has been fixed already .Since build49 will be shipped out ,move status to VERIFIED and keep product flag to rhel6.5.0 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. http://rhn.redhat.com/errata/RHBA-2013-1729.html |