Custom Query (16363 matches)
Results (895 - 897 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #11620 | obsolete | serial port doesn't work | ||
| Description |
Hi, I'm using VirtualBox 4.26 on Windows 7, and the guest system is also Windows 7, in VirtualBox of the host machine I've set the serial port number to COM1, host mode is host device, port/file path is COM1:(I've tried COM1 as well), under the device manager, the host machine's serial port number is COM1/LPT1; and in the guest system, it automatically detects COM1/LPT1 in the device manager, I don't need to add legacy hardware(I've tried to add it, it created a COM3, and didn't give me the option to choose the COM port number, and it got a yellow warning mark), but when I tried to use the port, it has no respond at all, so can someone please help me, thank you. |
|||
| #12597 | fixed | sendfile syscall returns cached content => Fixed in SVN / 6.0.6 | ||
| Description |
When using shared folder and copying file with sendfile syscall (either by just creating another file or sending content over network socket), the receiving end always gets the same content (the content that was in source file when sendfile called for the first time). Repro steps:
You will see "foo" instead of "bar". |
|||
| #2921 | fixed | sendfile => Fixed in SVN | ||
| Description |
Hi, Using Perlbal as a webserver with a document root hosted on a vboxsf mount share, I noticed that no content was sent to the socket, Perlbal was erroring with the following message: "Error w/ sendfile: Value too large for defined data type" I believe Perlbal is not the only one impacted by this issue (might be a regression of ticket #819?) Perlbal has some external dependencies (Sys::Syscall, IO::AIO etc...) that I tried to remove for you. Using perl 5.10 of ubuntu 32bits and the following test script reproduces the error: #!/usr/bin/perl
use strict;
use warnings;
use Config;
use POSIX;
use IO::Socket::INET;
my $src = shift;
open (my $s, "<$src") or die "cannot open $src";
my $d = open_sock();
doit($s, $d);
sub doit {
my ($fhs, $fhd) = @_;
my $src_fd = fileno($fhs);
my $dst_fd = fileno($fhd);
my $size = -s $fhs;
my $SYS_sendfile = 187;
my $machine = (POSIX::uname())[4];
unless ($^O eq "linux") {
die "I don't know if not under linux";
}
if ($machine eq "x86_64" && $Config{ptrsize} == 4) {
$machine = "i386";
}
unless ($machine =~ m/^i[3456]86$/) {
die "I can't tell for $machine";
}
my $res = syscall(
$SYS_sendfile,
$dst_fd,
$src_fd,
0,
$size,
);
if ($res < 0) {
warn "FAIL: $!";
}
else {
print "SUCCESS\n";
}
}
sub open_sock {
my $port = shift || 9245;
print "now connect to localhost:$port, thanks\n";
my $listen = IO::Socket::INET->new(
Listen => 1,
LocalAddr => 'localhost',
LocalPort => $port,
Proto => 'tcp',
Timeout => 15,
ReuseAddr => 1,
);
die "problem $!" unless $listen;
return $listen->accept or die "accept failed";
}
you will need to:
Broken case: when the filepath is in the vboxsf mount: yann@dev:~/dev$ perl repro.pl /in/vboxsf now connect to localhost:9245, thanks FAIL: Value too large for defined data type at repro2.pl line 40. Normal case: when the filepath is in the normal filesystem: yann@dev:~/dev$ perl repro.pl /tmp/src now connect to localhost:9245, thanks SUCCESS here is a strace() of the failing system call: sendfile(5, 3, NULL, 1497) = -1 EOVERFLOW (Value too large for defined data type) write(2, "FAIL: Value too large for define"..., 66FAIL: Value too large for defined data type at repro.pl line 39. ) = 66 here is my mount: $ mount -t vboxsf devel on /home/yann/dev type vboxsf (uid=1000,gid=1000,rw) $ uname -a Linux dev 2.6.27-9-server #1 SMP Thu Nov 20 22:53:41 UTC 2008 i686 GNU/Linux Thanks! Yann Kerherve |
|||

