Bug 824802 - data lost when transfer from host to guest with virtio serial
data lost when transfer from host to guest with virtio serial
Status: CLOSED DUPLICATE of bug 677886
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: qemu-kvm (Show other bugs)
Unspecified Unspecified
medium Severity medium
: rc
: ---
Assigned To: Amit Shah
Virtualization Bugs
Depends On:
  Show dependency treegraph
Reported: 2012-05-24 06:01 EDT by Suqin Huang
Modified: 2012-05-28 17:24 EDT (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-05-28 17:24:53 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Suqin Huang 2012-05-24 06:01:25 EDT
Description of problem:

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. cmd
-device virtio-serial-pci,id=virtio-serial-pci0 \

-chardev socket,path=/tmp/virtio-console-3XQGtS0,id=vs0,server,nowait \
-device virtserialport,chardev=vs0,name=serialport-0,id=serialport-0,bus=virtio-serial-pci0.0 \

-chardev socket,path=/tmp/virtio-console-3XQGtS1,id=vs1,server,nowait \
-device virtserialport,chardev=vs1,name=serialport-1,id=serialport-1,bus=virtio-serial-pci0.0

2. in host
# dd if=/dev/zero of=/root/file bs=1M count=1024 
# echo /root/file | nc -U /tmp/virtio-console-3XQGtS0

3. in guest
# cat /dev/virtio-ports/serialport-0 > bak
Actual results:
# md5sum bak 
4220a50fc53acd4abdea136bc42ec656  bak

# md5sum file 
cd573cfaace07e7949bc0c46028904ff  file

Expected results:

Additional info:
Comment 1 juzhang 2012-05-24 07:33:43 EDT
FYI, similar bugs
Bug 677886 - MD5 of file is different from the original one after transferred via virtio serial 
Bug 702611 - Some files were not integrated after transferring four files from host to guest
Comment 2 Ademar Reis 2012-05-28 17:24:53 EDT
Appears to be the same issue reported in Bug 677886. I've added your testcase there, so closing this as a dupe.

*** This bug has been marked as a duplicate of bug 677886 ***

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