Re: [Xen-devel] failed to get IP for guest vm during running test-amd64-amd64-xl job

["Pang, LongtaoX" <longtaox.pang@xxxxxxxxx>]

Hi Ian,

Thanks for your reply.
Since my DHCP Server is another Machine which is separate from OSSTest 
Controller Machine, I execute the command "nc -l -k 6666 < 
/var/lib/dhcp/dhcpd.leases" to spite out the lease file on port 6666. On my 
OSSTest Controller Machine, update HostProp_DhcpWatchMethod setting in 
~/.xen-osstest/config as: 
HostProp_DhcpWatchMethod 192.168.199.3:6666
(192.168.199.3 is my DHCP Server's IP address)
After that, re-run job of test-amd64-amd64-xl, the result is as below: (refer 
to attach test.log for detailed info)

2014-07-29 06:31:15 Z ping 192.168.199.73 up
2014-07-29 06:31:15 Z guest debian.guest.osstest 5e:36:0e:f5:00:01 22 
link/ip/tcp: ok. (10s)
2014-07-29 06:31:15 Z executing ssh ... root@xxxxxxxxxxxxxx echo guest 
debian.guest.osstest: ok
guest debian.guest.osstest: ok
2014-07-29 06:31:15 Z guest debian.guest.osstest 5e:36:0e:f5:00:01 22 
link/ip/tcp: waiting 20s...
2014-07-29 06:31:15 Z guest debian.guest.osstest 5e:36:0e:f5:00:01 22 
link/ip/tcp: no active lease (waiting) ...
...
2014-07-29 06:31:36 Z FAILURE: guest debian.guest.osstest 5e:36:0e:f5:00:01 22 
link/ip/tcp: wait timed out: no active lease.
failure: guest debian.guest.osstest 5e:36:0e:f5:00:01 22 link/ip/tcp: wait 
timed out: no active lease.
+ rc=255

According to the logs, it's seems that the dhcp.leases file is fetched by 
Controller Machine, as it find the Guest VM's IP (192.168.199.73) and 
"link/ip/tcp" is ok at first time. But, when it failed to link/ip/tcp again due 
to no active lease.

Also, if I copy the dhcp.leases file from DHCP Server to Controller Machine, 
and update HostProp_DhcpWatchMethod setting in ~/.xen-osstest/config as: 
HostProp_DhcpWatchMethod leases dhcp3 /path/to/dhcp.leases
Re-run the job, the test result is passed.
So, do you ever meet this question before? Is it a issue of something wrong 
about my setting?

Thanks
Longtao


> -----Original Message-----
> From: Ian Campbell [mailto:Ian.Campbell@xxxxxxxxxx]
> Sent: Friday, July 25, 2014 6:00 PM
> To: Pang, LongtaoX
> Cc: Wei Liu; Ian.Jackson@xxxxxxxxxxxxx; xen-devel@xxxxxxxxxxxxx
> Subject: Re: [Xen-devel] failed to get IP for guest vm during running
> test-amd64-amd64-xl job
> 
> On Fri, 2014-07-25 at 09:40 +0000, Pang, LongtaoX wrote:
> > Could you please tell me how did the guest vm to get the IP address in
> OSSTest system?
> 
> As you've discerned this is the function of the DhcpWatchMethod thing.
> 
> osstest needs to have access to the DHCP server's leases file by some
> mechanism. For the production deployment we arrange for the DHCP server to
> spit out its leases file on TCP port 5556, hence the default is
>         'leases dhcp3 woking.cam.xci-test.com:5556'
> (since woking is our local DHCP server). i.e.
>         nc woking.cam.xci-test.com 5556
> gets us the leases.
> 
> If your DHCP server happens to be running on the same machine as the osstest
> scripts then I believe you can use
>         'leases dhcp3 /path/to/dhcp.leases'
> We used to do this when osstest ran on woking, see osstest.git
> 3bb184d4e882 for the switch over.
> 
> The current code only copes with leases files in the ISC DHCPD server's format
> (apparently documented in dhcpd.leases(5)).
> 
> If you are unable to obtain the live copy of the leases file or it is not in 
> ISC
> dhcp.leases format then you will probably need to implement a new
> Osstest/DhcpWatch/foo.pm or update Osstest/DHcpWatch/leases.pm to
> support whatever mechanism you are able to arrange.
> 
> Ian.

Attachment: test.log
Description: test.log

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel