On Mon, Sep 26, 2011 at 7:10 AM, Doude wrote:
> I tried the 'ovs-vlan-test' program and it failed.
> Server log:
> 172.16.0.143 - - [26/Sep/2011 15:58:24] "GET /start/recv HTTP/1.1" 200 -
> 172.16.0.143 - - [26/Sep/2011 15:58:24] "GET /result/15 HTTP/1.1" 404 -
> 172.16.0.143 - - [26/Sep/2011 15:5
There's nothing surprising about a particular module not being loaded by
default. It just means that it is not used by default. If you want to
use it, you just load it.
But the main issue with running OVS in a guest, as you describe, is that
it isn't likely to be useful for controlling traffic i
I tried the 'ovs-vlan-test' program and it failed.
Server log:
172.16.0.143 - - [26/Sep/2011 15:58:24] "GET /start/recv HTTP/1.1" 200 -
172.16.0.143 - - [26/Sep/2011 15:58:24] "GET /result/15 HTTP/1.1" 404 -
172.16.0.143 - - [26/Sep/2011 15:58:24] "GET /result/15 HTTP/1.1" 404 -
172.16.0.143 - - [2
Hi,
Just to up my problem, I always need help.
Do you think it could be a driver incompatibility ?
I remember, I already do that conf a year ago. I used other hardware
with drivers r8169, e1000e and tg3 (only 2 of them but I don't
remember which ones).
Here my OVS setup:
# modprobe openvswitch_m
