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:
when guest try to transfer data to host with no listening side,it prompt :"The system can not write to the specified device".
Version-Release number of selected component (if applicable):
kernel-2.6.32-358.6.3.el6.x86_64
qemu-kvm-rhev-0.12.1.2-2.355.el6_4.5.x86_64
virtio-win-prewhql-0.1-62
spice-server-0.12.0-12.el6.x86_64
seabios-0.6.1.2-28.el6.x86_64
sgabios-0-0.3.20110621svn.el6
vgabios-0.6b-3.7.el6.noarch
How reproducible:
100%
Steps to Reproduce:
1. Start Guest with virtio serial port
/usr/libexec/qemu-kvm -drive file=win2012-serial-64-lijin,if=none,cache=none,media=disk,format=qcow2,id=drive-ide0-0-1 -device ide-drive,id=ide0-0-1,drive=drive-ide0-0-1,bootindex=0 -global PIIX4_PM.disable_s3=0 -global PIIX4_PM.disable_s4=0 -vnc :1 -vga cirrus -usb -device usb-tablet -netdev tap,id=hostnet0 -device e1000,netdev=hostnet0,id=net0,mac=52:54:00:7f:f9:F6,bus=pci.0 -monitor unix:/tmp/tt,server,nowait -chardev file,path=/root/console.log,id=serial1 -device isa-serial,chardev=serial1,id=s1 -cpu Penryn,hv_relaxed,+sep -M rhel6.4.0 -smp 4,maxcpus=4,cores=2,threads=2,sockets=1 -m 6G -enable-kvm -device virtio-serial-pci,id=virtio-serial0,max_ports=16 -chardev socket,path=/tmp/tt0,server,nowait,id=channel0 -device virtserialport,chardev=channel0,name=com.redhat.rhevm.vdsm,bus=virtio-serial0.0,id=port0
2.Transering data from guest to host via virtserialport w/o listening side
guest:echo hello world >> \\.\global\.\com.redhat.rhevm.vdsm
3.open the listening side on host:
host:nc -U /tmp/tt0
Actual results:
after step2:guest prompts:"The system can not write to the specified device";
after step3:host can not receive any data.
Expected results:
after step2:guest can write to the virtio serial port,no warning prompts;
after step3:host can receive the data guest just send.
Additional info:
build 61 did not hit this issue,so it is a regression
Just to be clear.
In the past two modes were supported, Blocking (wait indefinitely for the write to succeed), and non-blocking (immediately return success/failure).
Now only non-blocking is supported, which is fine.
(In reply to Ronen Hod from comment #5)
> Just to be clear.
> In the past two modes were supported, Blocking (wait indefinitely for the
> write to succeed), and non-blocking (immediately return success/failure).
> Now only non-blocking is supported, which is fine.
Ronen,Gal
Will this change influence RHEV-Agent or Spice-Agent ?
blocking mode is not supported for windows guests ,how about RHEL Guests ?
Thanks,
Mike