Opened 17 years ago
Closed 16 years ago
#1023 closed enhancement (fixed)
Unable to capture serial port to text file => Fixed in SVN
Reported by: | aicom | Owned by: | |
---|---|---|---|
Component: | uart | Version: | VirtualBox 1.5.4 |
Keywords: | Cc: | ||
Guest type: | other | Host type: | other |
Description
I don't get the option to capture data sent to the COM port to a text file as I do in VMware. I use this feature a lot when debugging my OS.
Change History (8)
comment:1 by , 17 years ago
comment:2 by , 17 years ago
On linux hosts you can use an application like minicom which is able to capture the output of the serial port. Select 'host pipe' in the VM settings and select unix#path_to_the_pipe in the minicom settings. Ctrl-A L starts the minicom capture mode.
comment:3 by , 17 years ago
and what should be the "path" to the pipe? (its the first time i have to do it and i have no idea)
comment:4 by , 16 years ago
Component: | other → uart |
---|
follow-up: 7 comment:5 by , 16 years ago
Summary: | Unable to capture serial port to text file → Unable to capture serial port to text file => Fixed in SVN |
---|
Added an option to redirect the output of a serial port to a raw file on the host.
comment:6 by , 16 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:7 by , 16 years ago
Resolution: | fixed |
---|---|
Status: | closed → reopened |
Replying to frank:
Added an option to redirect the output of a serial port to a raw file on the host.
The serial output in raw file is garbled when guest logs out at a fast rate (VirtualBox 2.2.4 r47978) Guest: Fedora 10 (kernel: 2.6.29.4-75.fc10.x86_64) Host: Fedora 10 (kernel: 2.6.29.3-60.fc10.x86_64)
Grub command line: console=tty0 console=ttyS0 Also, tried: console=tty0 console=ttyS0,115200
comment:8 by , 16 years ago
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
That works fine here, tested with a Fedora 11 guest on a Debian/Lenny host. If this doesn't work for you the cause is probably more a problem of the current 16450 emulation, see #1548. So lets continue to discuss there.
same problem here