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:
Guest failure in adding port for device virtio-serial after resume from F4 during transferring data from guest to host
Version-Release number of selected component (if applicable):
kernel-2.6.32-351.el6.x86_64
qemu-kvm-rhev-0.12.1.2-2.351.el6.x86_64
virtio-win-prewhql-0.1-51
How reproducible:
100%
Steps to Reproduce:
1.Start guest with CLI:
/usr/libexec/qemu-kvm -M rhel6.4.0 -m 2G -smp 2 -usb -device usb-tablet,id=tablet0 -drive file=win7-32.qcow2,if=none,id=drive-virtio0-0-0,format=qcow2,werror=stop,rerror=stop,cache=none -device ide-drive,drive=drive-virtio0-0-0,id=virti0-0-0,bootindex=1 -netdev tap,id=hostnet0,vhost=on,script=/etc/qemu-ifup -device rtl8139,netdev=hostnet0,id=net0,mac=00:12:10:94:a3:f8 -uuid 8677bf9b-3cf6-47a1-b3e9-94213b801c87 -monitor stdio -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=0 -vga std -device virtio-serial-pci,id=virtio-serial0,max_ports=16 -chardev socket,id=channel0,path=/tmp/helloworld,server,nowait -device virtserialport,chardev=channel0,name=com.redhat.rhevm.vdsm,bus=virtio-serial0.0,id=port0 -vnc :1
2.Transerring data from guest to host
eg: in the host : #python serial-host-receive.py /tmp/helloworld
in the guest: #for ((;;))
do
python VirtIOChannel_guest_send.py com.redhat.rhevm.vdsm;
done
3.Doing hibernate in the guest
4.Resuming guest by start guest CLI again.
Actual results:
Guest can resuming with error from qemu side and serial function fails to work.
(qemu) qemu-kvm: virtio-serial-bus: Guest failure in adding port 1 for device virtio-serial0.0
Expected results:
Guest should resume without any error,and serial function works well.
Additional info:
when reboot guest, all can work well.
(In reply to comment #3)
> Isn't this a duplicate of bz#902150?
Hi Gal Hammer,
yes, duplicate maybe caused when I hit bugzillar error when I submitted this bug, so I re-submitted it again, will close this bug as duplicate with bz#902150.
Thanks for reminder,
Best Regards,
Dawn
*** This bug has been marked as a duplicate of bug 902150 ***
Description of problem: Guest failure in adding port for device virtio-serial after resume from F4 during transferring data from guest to host Version-Release number of selected component (if applicable): kernel-2.6.32-351.el6.x86_64 qemu-kvm-rhev-0.12.1.2-2.351.el6.x86_64 virtio-win-prewhql-0.1-51 How reproducible: 100% Steps to Reproduce: 1.Start guest with CLI: /usr/libexec/qemu-kvm -M rhel6.4.0 -m 2G -smp 2 -usb -device usb-tablet,id=tablet0 -drive file=win7-32.qcow2,if=none,id=drive-virtio0-0-0,format=qcow2,werror=stop,rerror=stop,cache=none -device ide-drive,drive=drive-virtio0-0-0,id=virti0-0-0,bootindex=1 -netdev tap,id=hostnet0,vhost=on,script=/etc/qemu-ifup -device rtl8139,netdev=hostnet0,id=net0,mac=00:12:10:94:a3:f8 -uuid 8677bf9b-3cf6-47a1-b3e9-94213b801c87 -monitor stdio -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=0 -vga std -device virtio-serial-pci,id=virtio-serial0,max_ports=16 -chardev socket,id=channel0,path=/tmp/helloworld,server,nowait -device virtserialport,chardev=channel0,name=com.redhat.rhevm.vdsm,bus=virtio-serial0.0,id=port0 -vnc :1 2.Transerring data from guest to host eg: in the host : #python serial-host-receive.py /tmp/helloworld in the guest: #for ((;;)) do python VirtIOChannel_guest_send.py com.redhat.rhevm.vdsm; done 3.Doing hibernate in the guest 4.Resuming guest by start guest CLI again. Actual results: Guest can resuming with error from qemu side and serial function fails to work. (qemu) qemu-kvm: virtio-serial-bus: Guest failure in adding port 1 for device virtio-serial0.0 Expected results: Guest should resume without any error,and serial function works well. Additional info: when reboot guest, all can work well.