Virtualbox + IPv6

[Jared Mauch]

On Feb 15, 2013, at 3:34 PM, Daniel Roesen wrote:

> On Fri, Feb 15, 2013 at 09:34:30AM -0500, Jared Mauch wrote:
>> i'm curious if there's anyone here that has seen this ipv6 performance issue with hosts in a VM:
>> 
>> https://www.virtualbox.org/ticket/9380
> 
> Nothing noticed in my vbox Linux guests yet when connected to wired
> network, but as those are all on laptops, connectivity is usually WiFi
> anyway, where Virtualbox unfortunately fails completely:
> 
> https://www.virtualbox.org/ticket/5503
> 
> There seems to be no interest to fix that. I'm pretty sure that VMware
> _is_ able to do bridged IPv6 on WiFi, I remember testing that in the
> past. Perhaps my memory fails...
> 
> Analysis of what's going wrong is in comment #14. Too bad this
> "half-brokeness" is apparantly considered acceptable, see #12.
> 
> I have to manually pimp my Linux guests (disabling IPv6) to avoid
> endless fallback timeouts.


What I've noticed is something 'weird'. There may be something inversely related to latency.

When doing to a 'far-away' host with iperf, I see results like:

puck:~$ iperf -V -c mx
------------------------------------------------------------
Client connecting to mx, TCP port 5001
TCP window size: 22.7 KByte (default)
------------------------------------------------------------
[  3] local 2001:418:3f4::5 port 55090 connected with 2001:418:0:7011:20c:f1ff:fe7e:7d27 port 5001
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-10.1 sec  91.8 MBytes  76.2 Mbits/sec
puck:~$ iperf -V -c 2001:418:3f4::f00d
------------------------------------------------------------
Client connecting to 2001:418:3f4::f00d, TCP port 5001
TCP window size: 22.7 KByte (default)
------------------------------------------------------------
[  3] local 2001:418:3f4::5 port 53175 connected with 2001:418:3f4::f00d port 5001
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-10.0 sec   594 MBytes   498 Mbits/sec


but the other direction ...

jail-lnx:~$ iperf -V -c puck
------------------------------------------------------------
Client connecting to puck, TCP port 5001
TCP window size: 22.7 KByte (default)
------------------------------------------------------------
[  3] local 2001:418:3f4::f00d port 49921 connected with 2001:418:3f4::5 port 5001
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-10.1 sec   640 KBytes   518 Kbits/sec

npd:~> iperf -V -c puck
------------------------------------------------------------
Client connecting to puck, TCP port 5001
TCP window size: 32.1 KByte (default)
------------------------------------------------------------
[  3] local 2001:418:0:7011:20c:f1ff:fe7e:7d27 port 36025 connected with 2001:418:3f4::5 port 5001
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-10.0 sec  77.6 MBytes  64.9 Mbits/sec

A loopback test on the jail-lnx box results in 44.7Gbit/sec
^C^[[A^Cjail-lnx:~$ iperf -V -c 2001:418:3f4::f00d
------------------------------------------------------------
Client connecting to 2001:418:3f4::f00d, TCP port 5001
TCP window size:  648 KByte (default)
------------------------------------------------------------
[  3] local 2001:418:3f4::f00d port 44706 connected with 2001:418:3f4::f00d port 5001
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-10.0 sec  52.0 GBytes  44.7 Gbits/sec

And loopback on puck (inside VirtualBox) something "similar"

[  3] local 2001:418:3f4::5 port 49479 connected with 2001:418:3f4::5 port 5001
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-10.0 sec  17.3 GBytes  14.8 Gbits/sec

I'm hoping that someone from the VirtualBox team responds to the tickets and I can point them at a test environment to poke at this some more..

- Jared