@widget
your point is?
We are beyond running round in circles looking for linux-header-3.2.46
I did suggest ( ok not directly ) linux-headers-3.2.0-48-generic
it was ignored, and the cycle restarted.
Now we know why they want to install these headers.
http://networkstatic.net/open-vswitch-on-virtualbox/
But the question now is , why do they need OpenVSwitch?
http://openvswitch.org/
Quote:
Supported Platforms
Open vSwitch can operate both as a soft switch running within the hypervisor, and as the control stack for switching silicon. It has been ported to multiple virtualization platforms and switching chipsets. It is the default switch in XenServer 6.0, the Xen Cloud Platform and also supports Xen, KVM, Proxmox VE and VirtualBox. It has also been integrated into many virtual management systems including OpenStack, openQRM, OpenNebula and oVirt. The kernel datapath is distributed with Linux, and packages are available for Ubuntu, Debian, and Fedora. The Open vSwitch release in development also supports FreeBSD.
The bulk of the code is written in platform-independent C and is easily ported to other environments.
|
now lets think about what "emulab.net virtual PC" is
is it a "virtualization platform"?
I think it is
can it already do networking switching?
I guess it can, seeing as
http://emulab.net/ mentions
Quote:
|
"Emulab is a network testbed, giving researchers a wide range of environments in which to develop, debug, and evaluate their systems."
|
Going off the sparse (practically non-existent ) details we have been given, they don't even need it.
