Hi Ondrej,

Thank you so much! It works! This looks like rocket science!  You are a magician!

One more question, currently I am trying a sample ping test with the recipe file come with the package. I want to know is there any more sample recipes which I can get from Lnst? I want to build a test suite which includes a bunch of test cases such as ping test that could cover the basic network facilities. I am wondering if I can get some more sample recipes from Lnst.

Thanks again for your time and help!

Xing

> Date: Wed, 19 Jun 2013 10:24:25 +0200
> From: olichtne@redhat.com
> To: dymfangxing@hotmail.com
> CC: lnst-developers@lists.fedorahosted.org
> Subject: Re: can lnst be used on Linux distributions other that Fedora 18?
>
> Hi,
>
> thanks for the logs and the recipe you sent, it helped a lot and I think
> I will be able to help you properly. I tried your recipe, and recieved
> the same kind of errors at first, so I fixed it on my side and it will
> hopefully work for you as well.
>
> First of all the phys_id attribute in the <netdevice> and <interface>
> tags has no relation to what the devices are called on the machine-
> phys_id="1" for eth device does not mean eth1. In fact, it doesn't even
> have to be a number, you could do phys_id="foo" and it could still
> work. The attribute is actually just used to create a relation between
> the <netdevice> and the <interface> tags. This is the old way we did
> this and it will be changed in the next release.
>
> Anyway, to make this part of the recipe functional you need to change it
> to look something like this:
> <netdevice type="eth" network="tnet" hwaddr="MAC_ADDR_OF_ETH1" phys_id="0"/>
> and
> <interface id="testifc1" phys_id="0" type="eth">
> note that phys_id is the same for both the tags.
>
> Do this for both the machines and it should work.
>
> Also don't forget to replace the hwaddr attributes with correct values-
> I noticed you used the same values as in Mondays email, so I assume that
> mac address is the mac address of the eth0 interface which you are
> trying to avoid since it's the one connected to the controller.
>
> And one last suggestion, we don't recommend using NetworkManager yet as
> it conflicts with how we configure the devices. You can turn it off, but
> it will suffice to set the test devices to not be managed by
> NetworkManager. This is done by editing
> /etc/sysconfig/network-scripts/ifcfg-eth1 (or your ubuntu equivalent)
> and setting NM_CONTROLLED="no".
>
> Hopefully this works correctly.
>
> -Ondrej
>
> On Wed, Jun 19, 2013 at 12:41:47PM +0800, FangXinglorrie wrote:
> > Hi Ondrej,
> > I tried your suggestion by adding a new interface on each slaves. Now both slave 1 and slave 2 have two eth inferface, which is eth0 and eth1. eth0 will be used to receive control signal from controller and eth1 will be used in real testing. Both eth0 and eth1 on two slaves are valid and could ping each other.
> > However, I still get the error message like: " phys_id passed but doesn not match any device on machine." I attached my log file as well as the recipe within this email and hope to hearing from you soon!
> > Thanks again for your kindness!
> > Xing