Quoting "Gustau Pérez" :
Al 19/07/2011 08:40, En/na Peter Ross ha escrit:
Quoting "Gustau Pérez" :
Al 13/07/2011 23:57, En/na Peter Ross ha escrit:
I have a problem with the network while running VirtualBox.
As soon as I _run_ a VirtualBox I am not able to copy large files
(e.g. virtual d
Al 19/07/2011 08:40, En/na Peter Ross ha escrit:
Quoting "Gustau Pérez" :
Al 13/07/2011 23:57, En/na Peter Ross ha escrit:
I have a problem with the network while running VirtualBox.
As soon as I _run_ a VirtualBox I am not able to copy large files
(e.g. virtual disks or ZFS snapshots) using
Quoting "Gustau Pérez" :
Al 13/07/2011 23:57, En/na Peter Ross ha escrit:
I have a problem with the network while running VirtualBox.
As soon as I _run_ a VirtualBox I am not able to copy large files
(e.g. virtual disks or ZFS snapshots) using ssh/scp to another
machine.
The ssh crashes
Quoting "Adam Vande More" :
On Mon, Jul 18, 2011 at 12:30 AM, Peter Ross
wrote:
I tried FTP (to have something completely different) and it fails as well:
(ftp: netout: Cannot allocate memory)
I watched vmstat -z, and every time it fails, I have another failure
reported for "NetGraph data it
Al 13/07/2011 23:57, En/na Peter Ross ha escrit:
Hi all,
I have a problem with the network while running VirtualBox.
As soon as I _run_ a VirtualBox I am not able to copy large files
(e.g. virtual disks or ZFS snapshots) using ssh/scp to another machine.
The ssh crashes with "Write failed: C
On Mon, Jul 18, 2011 at 12:30 AM, Peter Ross
wrote:
> I tried FTP (to have something completely different) and it fails as well:
> (ftp: netout: Cannot allocate memory)
>
> I watched vmstat -z, and every time it fails, I have another failure
> reported for "NetGraph data items".
>
> Regards
> Pet
Quoting "Adam Vande More" :
On Wed, Jul 13, 2011 at 10:02 PM, Adam Vande More
wrote:
I suspect this has less to do with actual memory and more to do with some
other buffer-like bottleneck. Does tuning any of the network buffers make
any difference? A couple to try:
net.inet.ip.intr_queue_
On Wed, Jul 13, 2011 at 10:02 PM, Adam Vande More wrote:
> I suspect this has less to do with actual memory and more to do with some
> other buffer-like bottleneck. Does tuning any of the network buffers make
> any difference? A couple to try:
>
> net.inet.ip.intr_queue_maxlen
> net.link.ifqmaxl
On Wed, Jul 13, 2011 at 8:55 PM, Peter Ross
wrote:
> I am running named on the same box. I have overtime some errors there as
> well:
>
> Apr 13 05:17:41 bind named[23534]: internal_send: 192.168.50.145#65176:
> Cannot allocate memory
> Jun 21 23:30:44 bind named[39864]: internal_send: 192.168.50.
Quoting "Adam Vande More" :
On Wed, Jul 13, 2011 at 6:57 PM, Peter Ross
wrote:
Hi all,
I have a problem with the network while running VirtualBox.
As soon as I _run_ a VirtualBox I am not able to copy large files (e.g.
virtual disks or ZFS snapshots) using ssh/scp to another machine.
The ss
On Wed, Jul 13, 2011 at 6:57 PM, Peter Ross
wrote:
> Hi all,
>
> I have a problem with the network while running VirtualBox.
>
> As soon as I _run_ a VirtualBox I am not able to copy large files (e.g.
> virtual disks or ZFS snapshots) using ssh/scp to another machine.
>
> The ssh crashes with "Wri
Hi all,
I have a problem with the network while running VirtualBox.
As soon as I _run_ a VirtualBox I am not able to copy large files
(e.g. virtual disks or ZFS snapshots) using ssh/scp to another machine.
The ssh crashes with "Write failed: Cannot allocate memory"
thrown by a write(2) in /
12 matches
Mail list logo
