I encounter some issues with VB (1.5.6) networking under a winxp host with a Debian VM.
I'm on a network with some physical hosts, and using scp from guest to another host through a NAT interface leads to data transfert stall, often but not always, especially for "big enough" files (> 50 Kb).
Note that it's only happen with VB, a colleague use a Linux host and have no such issues with scp.
[quote='scp debug log']
debug1: Sending command: scp -v -t dir1/
debug2: channel 0: request exec confirm 0
debug2: fd 3 setting TCP_NODELAY
debug2: callback done
debug2: channel 0: open confirm rwindow 0 rmax 32768
debug2: channel 0: rcvd adjust 131072
Sending file modes: C0644 88891 file1
debug2: channel 0: rcvd ext data 23
Sink: C0644 88891 file1
debug2: channel 0: written 23 to efd 6
file1 100% 87KB 86.8KB/s 00:00
(after a while)
debug2: channel 0: rcvd adjust 65553
(nothing for some minutes...then)
debug2: channel 0: read<=0 rfd 4 len 0
debug2: channel 0: read failed
debug2: channel 0: close_read
debug2: channel 0: input open -> drain
debug2: channel 0: ibuf empty
debug2: channel 0: send eof
debug2: channel 0: input drain -> closed
debug2: channel 0: rcvd eof
debug2: channel 0: output open -> drain
debug2: channel 0: obuf empty
debug2: channel 0: close_write
debug2: channel 0: output drain -> closed
debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
debug2: channel 0: rcvd close
debug3: channel 0: will not send data after close
debug2: channel 0: almost dead
debug2: channel 0: gc: notify user
debug2: channel 0: gc: user detached
debug2: channel 0: send close
debug2: channel 0: is dead
debug2: channel 0: garbage collecting
debug1: channel 0: free: client-session, nchannels 1
debug3: channel 0: status: The following connections are open:
#0 client-session (t4 r0 i3/0 o3/0 fd -1/-1 cfd -1)
debug3: channel 0: close_fds r -1 w -1 e 6 c -1
debug1: fd 0 clearing O_NONBLOCK
debug1: fd 1 clearing O_NONBLOCK
debug1: Transferred: stdin 0, stdout 0, stderr 0 bytes in 329.7 seconds
debug1: Bytes per second: stdin 0.0, stdout 0.0, stderr 0.0
debug1: Exit status 0
[/quote]
(NAT Networking in VB seems to be always faulty
, before 1.5.6, VM freeze completely randomly on network activity, now it seems to just get this issue).Is someone else encounter such issue ? is it a know issue ?
Regards.