[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: mirage-platform commit on June 26



Hi Vincent,

Thx for porting to mirari.  I see how it is done now.  

I tried the mirage-skeleton version (B=--xen make).  A few things:

In the .conf file I had to change ip-use-dhcp to false.  Then with all the latest versions I see the same behavior - no packets make it back to the VIF.  If I revert your commit on June 26, I see arp pkts on the bridge as expected and I see them on the VIF as well.  However for some reason the mirage-skeleton version brings up all my VIFs with IP 10.0.0.2, instead of the ones I have used in the test (10.100.100.101 and 10.100.100.102).  If I can make it come up with the my IP addrs (or at least different IP addrs), then I think it will work as expected.

I am not sure why it crashes for you.  That's worrying.

Balraj



On Mon, Jul 1, 2013 at 12:39 PM, Anil Madhavapeddy <anil@xxxxxxxxxx> wrote:
I can't seem to reproduce Balraj's failure on my Ubuntu laptop.  I'll try
on my Debian box later on this afternoon.

-anil

On 1 Jul 2013, at 12:29, Vincent Bernardoff <vb@xxxxxxxxxxxxxx> wrote:

> On 30/06/2013 17:47, Balraj Singh wrote:
>> Hi Vincent,
>>
>> I'm still using ocamlbuild.  From the mirage-net/direct directory I simply
>> call "ocamlbuild tests/iperf_self/iperf_self.xen".  But for ocamlbuild to
>> work right I make the following change to myocamlbuild.ml:
>>
>> --- a/myocamlbuild.ml
>> +++ b/myocamlbuild.ml
>> @@ -63,7 +63,7 @@ module Configure = struct
>>    (* Flags for building and using syntax extensions *)
>>    let ppflags () =
>>      (* Syntax extensions for the libraries being built *)
>> -    flag ["ocaml"; "pp"; "use_syntax"] & S [config_sh "syntax.deps"];
>> +    flag ["ocaml"; "pp"(*; "use_syntax"*)] & S [config_sh "syntax.deps"];
>>      (* Include the camlp4 flags to build an extension *)
>>      flag ["ocaml"; "pp"; "build_syntax"] & S [config_sh "syntax.build"];
>>      flag ["ocaml"; "pp"; "build_syntax_r"] & S [config_sh
>> "syntax.build.r"];
>>
>>
>> I then simply use the cfg file in the tests directory.  Apologies if this
>> is unclear and non-standard, I will try to get this working with mirari
>> etc, soon.
>>
>> Balraj
>
> Hey Balraj,
>
> No problem.
>
> I've ported the test to mirari:
>
> See git://github.com/vbmithr/mirage-skeleton.git
>
> In directory tcp
> Just do make
>
> On my machine, I can correctly build the kernel, but when I am running it, it is immediately crashing. Tell me how it works for you.
>
> I'm going to try to compile under standard released versions of mirage/mirage-net. Hope we'll fix this! I'm quite happy about my various mirage refactorings, it would be a pity that I've really broken something..
>
> Cheers,
>
> Vincent
>
>
> PS: I have updated all mirage-skeleton. Now the Makefiles correctly detect the backend, (either mirage-xen or mirage-unix).
>




 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.