From: Ian Campbell <Ian.Campbell@citrix.com>
To: "Pang, LongtaoX" <longtaox.pang@intel.com>
Cc: "Ian.Jackson@eu.citrix.com" <Ian.Jackson@eu.citrix.com>,
Wei Liu <wei.liu2@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: failed to get IP for guest vm during running test-amd64-amd64-xl job
Date: Fri, 25 Jul 2014 11:00:08 +0100 [thread overview]
Message-ID: <1406282408.29480.113.camel@dagon.hellion.org.uk> (raw)
In-Reply-To: <86C3224E41A7434B904EC364302132D80E3B15E4@SHSMSX101.ccr.corp.intel.com>
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.
next prev parent reply other threads:[~2014-07-25 10:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-25 9:40 failed to get IP for guest vm during running test-amd64-amd64-xl job Pang, LongtaoX
2014-07-25 10:00 ` Ian Campbell [this message]
2014-07-29 8:24 ` Pang, LongtaoX
2014-07-29 8:37 ` Ian Campbell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1406282408.29480.113.camel@dagon.hellion.org.uk \
--to=ian.campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=longtaox.pang@intel.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).