Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
During Guest tranferring data from host to guest ,then do s3 , qemu-kvm process will quit due to "Guest moved used index from 114 to 0"
Version-Release number of selected component (if applicable):
2.6.32-307.el6.x86_64
qemu-kvm-rhev-0.12.1.2-2.312.el6.x86_64
virtio-win-prewhql-35
How reproducible:
2/2
Steps to Reproduce:
1.Start VM with virtio-serial-pci and virtserialport
CLI:/usr/libexec/qemu-kvm -M rhel6.4.0 -cpu SandyBridge -enable-kvm -m 4096 -smp 4 -name win7-ser -uuid 95f5b887-b59f-48ab-9a7c-4024e31de64b -rtc base=localtime,driftfix=slew -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/rhev/data-center/0bbd954a-b9dd-4075-accc-73da9f3f4f9f/adeb4775-27dc-4e92-a720-6609719abd49/images/e5b7e352-5bc3-437a-8958-905019614b0e/aa772688-9948-4ffa-b50b-14c20911e73e,if=none,id=drive-ide0-0-0,format=raw,serial=e5b7e352-5bc3-437a-8958-905019614b0e,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=2 -drive file=/rhev/data-center/0bbd954a-b9dd-4075-accc-73da9f3f4f9f/7db7d438-49c0-403c-98bb-86e1eb368cbf/images/11111111-1111-1111-1111-111111111111/en_windows_7_ultimate_with_sp1_x64_dvd_618240.iso,if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw,serial= -device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0,bootindex=1 -netdev tap,id=hostnet0 -device e1000,netdev=hostnet0,id=net0,mac=00:1a:4a:42:04:8b,bus=pci.0,addr=0x3,bootindex=3 -chardev socket,id=charchannel0,path=/tmp/tt,server,nowait -spice port=5902,disable-ticketing -k en-us -vga qxl -global qxl-vga.vram_size=67108864 -bios /usr/share/seabios/bios-pm.bin -fda /home/iso/7db7d438-49c0-403c-98bb-86e1eb368cbf/images/11111111-1111-1111-1111-111111111111/virtio-win.vfd -monitor stdio -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x4 -device virtserialport,bus=virtio-serial0.0,chardev=charchannel0,id=channel0,name=com.redhat.rhevm.vdsm -chardev socket,id=charchannel1,path=/tmp/tt1,server,nowait -device virtserialport,bus=virtio-serial0.0,chardev=charchannel1,name=com.redhat.rhevm.vdsm1
2.Transferring data from host to guest
eg : in the guest
for ((;;)) ; do python VirtIOChannel-guest-recieve.py com.redhat.rhevm.vsdm ;done
on the host
for ((;;)); do python serial-host-send.py /tmp/tt; echo `uuidgen`;sleep 0.5 ; done
3.sleep guest
Actual results:
qemu-kvm quit due to "Guest moved used index from 114 to 0"
Expected results:
sleep successfully
Additional info:
We did not find this bug during previous verison Testing ,this should be regression
Mike, is that an issue of qemu or the drivers? Is a previous version of qemu survive this?
In general, since we do have some s3 left over issues I rather wait w/ it for rhel6.5 but in case this is a new regression we can solve it now
(In reply to comment #3)
> Mike, is that an issue of qemu or the drivers? Is a previous version of qemu
> survive this?
>
should be the issues in the driver ,We have such test case and did not hit it before ,this should be virtio-win regression introduced recently.
> In general, since we do have some s3 left over issues I rather wait w/ it
> for rhel6.5 but in case this is a new regression we can solve it now
Verified this issue on virtio-win-prehwql-49
steps same as comment#0
Actual Results:
on build 49 ,qemu-kvm does not quit
Based on above ,this issue has been fixed in build 49 ald
Move status to verified.