Re: [MirageOS-devel] Unikernel debugging

[Masoud Koleini <masoud.koleini@xxxxxxxxxxxxxxxx>]

On 27/10/14 19:30, Anil Madhavapeddy wrote:
> > On 27 Oct 2014, at 19:28, Masoud Koleini <masoud.koleini@xxxxxxxxxxxxxxxx> 
> > wrote:
> >
> >
> > On 27/10/14 16:50, Anil Madhavapeddy wrote:
> > > On 27 Oct 2014, at 15:37, Masoud Koleini <masoud.koleini@xxxxxxxxxxxxxxxx> 
> > > wrote:
> > > > Hi all,
> > > >
> > > > I am looking for advices on debugging a Mirage unikernel with multiple tap 
> > > > devices for the following problems:
> > > >
> > > > 1. The same MAC address is assigned to all tap devices.
> > > Could you please provide more details about the xl file you used to create the 
> > > vif?  Did you set the `mac=xx` in the .xl file?
> > vif = [ 
> > 'mac=00:86:3E:51:27:4B,bridge=xenbr0','mac=00:86:3E:51:27:4C,bridge=tapbr1','mac=00:86:3E:51:27:4D,bridge=tapbr2'
> >  ]
> >
> > A one-to-one assignments of tap devices to vifs is necessary for the proper 
> > operation.
> >
> > > > 2. Calling TCPV4 create_connection function produces no traffic on virtual 
> > > > interfaces.
> > > A small reproducible program demonstrating the problem would help here.
> > I found that this happens when NETWORK "listen" function is called on tap1 and 
> > tap2 devices. It looks to be a consequence of the first problem.
> So it doesn't happen with one VIF, and only when you have multiple network 
> interfaces attached to the VM?
Number of VIFs defined in xl file doesn't matter (if that is what you 
are asking). Switch says MAC address of tap devices are the first MAC 
defined (in my case, I can see tap1 and tap2 both have the MAC 
00:86:3E:51:27:4B.)

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