Re: [MirageOS-devel] Passing tap devices to the main module

[Mindy <mindy@xxxxxxxxxxxxxxxxxxx>]

Hi Masoud,

I had a similar question and ended up with this chunk of config.ml for a 
Mirage program that needed two network interfaces.  Basically, get a 
different interface by calling `netif` with an integer represented in a 
string to try for a different interface than the lowest-numbered 
usable-looking one (tap0 for unix, the vif numbered 0 for xen).  I 
haven't verified that this actually works with Unix, but it does at 
least configure and build.
From a config.ml:

let client_netif = (netif "0")  (* equivalent to let client_netif = tap0 *)
let server_netif = (netif "1") (*netif actually needs an integer, shoved
into a string, which maps to a device ID number assigned by Xen, to do 
anything
helpful when xen is the target.  Stuff that can't be turned into an int
is silently dropped in that case and we just get the first Xen network 
iface. *)
Hope this helps,
Mindy

On 08/05/2014 10:25 AM, Masoud Koleini wrote:
> Hi,
>
> I am passing tap0 as a parameter from config to the main module in 
> unikernel.ml. Changing tap0 to tap1 or any other tap device produces 
> an error in compiling config file. How it is possible to pass tap 
> devices other than tap0 from config to the main module?
> Thanks.
>
>
> This message and any attachment are intended solely for the addressee 
> and may contain confidential information. If you have received this 
> message in error, please send it back to me, and immediately delete 
> it.   Please do not use, copy or disclose the information contained in 
> this message or in any attachment.  Any views or opinions expressed by 
> the author of this email do not necessarily reflect the views of the 
> University of Nottingham.
> This message has been checked for viruses but the contents of an 
> attachment
> may still contain software viruses which could damage your computer 
> system, you are advised to perform your own checks. Email 
> communications with the University of Nottingham may be monitored as 
> permitted by UK legislation.
>
>
>
>
> _______________________________________________
> MirageOS-devel mailing list
> MirageOS-devel@xxxxxxxxxxxxxxxxxxxx
> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@xxxxxxxxxxxxxxxxxxxx
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel