blob: b231659f84bec186f77aafddc2c0d48ddcf7f783 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
|
KVM: 0.943
device: 0.893
performance: 0.807
files: 0.767
graphic: 0.675
vnc: 0.663
boot: 0.652
semantic: 0.617
network: 0.550
socket: 0.485
other: 0.475
debug: 0.419
PID: 0.404
permissions: 0.359
data sent to serial interface gets truncated after 64kb
When sending more than 64kb of data to the serial interface in a short timespan, the data seems to disappear.
I tested it with the latest release (qemu-kvm-1.2.0-rc2.tar.gz) where the bug still occurs. I stumbled upon it when I upraged my qemu version. The bug did not occur in the last version i had (0.12.5).
You can reproduce it as follows:
1. Start a dd or cat command in one terminal and pipe the output to a netcat. The testfile has to be larger than 64kb. I used one that had 93kb and did contain only ascii text.
$ dd if=<TESTFILE> | nc -l 127.0.0.1 65432
or
$ cat <TESTFILE> | nc -l 127.0.0.1 65432
2. Start a qemu and let the first serial port connect to the listening netcat. I suppose that the testsystem can be any system that does not read from the serial port on its own (e.g. during boot process). I used a self compiled minimal linux.
$ qemu -cdrom <TESTSYSTEM> -serial tcp:127.0.0.1:65432
3. When the testsystem is booted, read from the serial device and write it to a file.
$ dd if=/dev/ttyS0 of=/tmp/testFile
or
$ cat /dev/ttyS0 > /tmp/testFile
The result in almost all of my testruns is, that the /tmp/testFile does only has the size of 64kb. The rest of the data vanished. In some cases the file was slightly bigger (65kb or 67kb) but allways under 70kb. The complete file (93kb) was not trasmitted in any of the runs.
I hope my explanation is exactly enough for you to reproduce it.
Triaging old bug tickets ... can you still reproduce this issue with the
latest version of QEMU (version 2.9)?
[Expired for QEMU because there has been no activity for 60 days.]
|