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

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

[Pang, LongtaoX]

Deay Ian,

Have a nice day!
After a period of time studying, I have completed to setup OSSTest environment and could run "build-*" jobs successfully. 
But, when I trying to run test job of "test-amd64-amd64-xl", the below failure occurred which confused me for a long time.
The guest vm could be created, but it seems that the Guest VM(debian.guest.osstest) failed to get IP address. 

2014-07-23 08:38:09 Z toolstack xl
2014-07-23 08:38:09 Z executing ssh ... root@192.168.199.69 xl create /etc/xen/debian.guest.osstest.cfg
Parsing config from /etc/xen/debian.guest.osstest.cfg
2014-07-23 08:38:10 Z executing ssh ... root@192.168.199.69 xl list
2014-07-23 08:38:10 Z guest debian.guest.osstest state is b
2014-07-23 08:38:10 Z guest debian.guest.osstest 5e:36:0e:f5:00:01 22 link/ip/tcp: waiting 40s...
Use of uninitialized value $leases in <HANDLE> at Osstest/DhcpWatch/leases.pm line 104.
readline() on unopened filehandle at Osstest/DhcpWatch/leases.pm line 104.
Use of uninitialized value $leases in <HANDLE> at Osstest/DhcpWatch/leases.pm line 75.
readline() on unopened filehandle at Osstest/DhcpWatch/leases.pm line 75.
...
Can't call method "eof" on an undefined value at Osstest/DhcpWatch/leases.pm line 76.
+ rc=255
+ date -u +%Y-%m-%d %H:%M:%S Z exit status 255
2014-07-23 08:38:10 Z exit status 255
+ exit 255
2014-07-23 08:38:10 Z standalone.test-amd64-amd64-xl 9 status status fail

Could you please tell me how did the guest vm to get the IP address in OSSTest system?

According README in OSSTest, I set the item of " HostProp_DhcpWatchMethod" as "HostProp_DhcpWatchMethod leases dhcp3 192.168.199.3:67".
192.168.199.3 is the IP address of my DHCP Server. (In my test environment, the DHCP Server is separate from OSSTest Controller mechine)
67 is the port number.

my global config file in ~/.xen-osstest/config is as below:
DnsDomain tsp.org
NetNameservers 192.168.199.5 172.16.1.11 172.16.16.12
TestHost testhost
HostProp_DhcpWatchMethod leases dhcp3 192.168.199.3:67
HostProp_testhost_Build_Make_Flags -j8
TftpPath /tftpboot/
WebspaceFile /var/www
WebspaceCommon /osstest/
WebspaceUrl http://controller.tsp.org
WebspaceLog /var/log/apache2/access.log
DebianSuite wheezy
TftpDiVersion current
DebianArches amd64
DebianMirrorHost linux-ftp.sh.intel.com
DebianMirrorSubpath /pub/mirrors/debian

So, could you give some suggestion about this question? 
Any help will be appreciated.

Best Regards,
Longtao

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

[Ian Campbell]

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.

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

[Pang, LongtaoX]

[-- Attachment #1: Type: text/plain, Size: 3544 bytes --]

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@192.168.199.73 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@citrix.com]
> Sent: Friday, July 25, 2014 6:00 PM
> To: Pang, LongtaoX
> Cc: Wei Liu; Ian.Jackson@eu.citrix.com; xen-devel@lists.xen.org
> 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 #2: test.log --]
[-- Type: application/octet-stream, Size: 13557 bytes --]

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!     @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the ECDSA key sent by the remote host is
ad:99:f6:ec:13:9e:76:bb:12:ae:e7:5e:c2:98:d7:95.
Please contact your system administrator.
Add correct host key in tmp/t.known_hosts_standalone.test-amd64-amd64-xl to get rid of this message.
Offending ECDSA key in tmp/t.known_hosts_standalone.test-amd64-amd64-xl:2
Keyboard-interactive authentication is disabled to avoid man-in-the-middle attacks.
2014-07-29 06:31:02 Z executing ssh ... root@192.168.199.69 readlink /dev/testhost/debian.guest.osstest-disk
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!     @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the ECDSA key sent by the remote host is
ad:99:f6:ec:13:9e:76:bb:12:ae:e7:5e:c2:98:d7:95.
Please contact your system administrator.
Add correct host key in tmp/t.known_hosts_standalone.test-amd64-amd64-xl to get rid of this message.
Offending ECDSA key in tmp/t.known_hosts_standalone.test-amd64-amd64-xl:2
Keyboard-interactive authentication is disabled to avoid man-in-the-middle attacks.
2014-07-29 06:31:02 Z executing ssh ... root@192.168.199.69 lvdisplay --colon /dev/testhost/debian.guest.osstest-disk
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!     @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the ECDSA key sent by the remote host is
ad:99:f6:ec:13:9e:76:bb:12:ae:e7:5e:c2:98:d7:95.
Please contact your system administrator.
Add correct host key in tmp/t.known_hosts_standalone.test-amd64-amd64-xl to get rid of this message.
Offending ECDSA key in tmp/t.known_hosts_standalone.test-amd64-amd64-xl:2
Keyboard-interactive authentication is disabled to avoid man-in-the-middle attacks.
+ rc=0
+ date -u +%Y-%m-%d %H:%M:%S Z exit status 0
2014-07-29 06:31:03 Z exit status 0
+ exit 0
2014-07-29 06:31:03 Z standalone.test-amd64-amd64-xl 8 status status pass
2014-07-29 06:31:03 Z finished standalone.test-amd64-amd64-xl ts-debian-fixup debian pass
2014-07-29 06:31:03 Z starting standalone.test-amd64-amd64-xl ts-guest-start debian guest-start
2014-07-29 06:31:03 Z standalone.test-amd64-amd64-xl ========== 9 testid guest-start ==========
2014-07-29 06:31:03 Z awaiting standalone.test-amd64-amd64-xl ts-guest-start debian
+ OSSTEST_JOB=test-amd64-amd64-xl
+ export OSSTEST_JOB
+ ./ts-guest-start debian
2014-07-29 06:31:03 Z starting standalone.test-amd64-amd64-xl
2014-07-29 06:31:03 Z setting all_hostflags=arch-amd64,arch-xen-amd64,suite-wheezy,purpose-test
2014-07-29 06:31:03 Z setting arch=amd64
2014-07-29 06:31:03 Z setting buildjob=build-amd64
2014-07-29 06:31:03 Z setting console=hvc0
2014-07-29 06:31:03 Z setting debian_arch=amd64
2014-07-29 06:31:03 Z setting debian_boot_timeout=40
2014-07-29 06:31:03 Z setting debian_cfgpath=/etc/xen/debian.guest.osstest.cfg
2014-07-29 06:31:03 Z setting debian_console=hvc0
2014-07-29 06:31:03 Z setting debian_disk_lv=debian.guest.osstest-disk
2014-07-29 06:31:03 Z setting debian_domname=debian.guest.osstest
2014-07-29 06:31:03 Z setting debian_ether=5e:36:0e:f5:00:01
2014-07-29 06:31:03 Z setting debian_hostname=debian.guest.osstest
2014-07-29 06:31:03 Z setting debian_kernkind=pvops
2014-07-29 06:31:03 Z setting debian_rootdev=xvda
2014-07-29 06:31:03 Z setting debian_swap_lv=debian.guest.osstest-swap
2014-07-29 06:31:03 Z setting debian_tcpcheckport=22
2014-07-29 06:31:03 Z setting debian_vg=testhost
2014-07-29 06:31:03 Z setting host=testhost
2014-07-29 06:31:03 Z setting kernbuildjob=build-amd64-pvops
2014-07-29 06:31:03 Z setting kernkind=pvops
2014-07-29 06:31:03 Z setting toolstack=xl
2014-07-29 06:31:03 Z setting xen_kernel_path=/boot/vmlinuz-3.4.99+
2014-07-29 06:31:03 Z setting xen_kernel_ver=3.4.99+
2014-07-29 06:31:03 Z setting xenbuildjob=build-amd64
2014-07-29 06:31:03 Z TftpScope is default
2014-07-29 06:31:03 Z OSSTEST_HOST_REUSE
2014-07-29 06:31:03 Z host: selected testhost <unknown-ether> 192.168.199.69
2014-07-29 06:31:03 Z executing ssh ... root@192.168.199.69 readlink /dev/testhost/debian.guest.osstest-disk
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!     @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the ECDSA key sent by the remote host is
ad:99:f6:ec:13:9e:76:bb:12:ae:e7:5e:c2:98:d7:95.
Please contact your system administrator.
Add correct host key in tmp/t.known_hosts_standalone.test-amd64-amd64-xl to get rid of this message.
Offending ECDSA key in tmp/t.known_hosts_standalone.test-amd64-amd64-xl:2
Keyboard-interactive authentication is disabled to avoid man-in-the-middle attacks.
2014-07-29 06:31:03 Z executing ssh ... root@192.168.199.69 lvdisplay --colon /dev/testhost/debian.guest.osstest-disk
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!     @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the ECDSA key sent by the remote host is
ad:99:f6:ec:13:9e:76:bb:12:ae:e7:5e:c2:98:d7:95.
Please contact your system administrator.
Add correct host key in tmp/t.known_hosts_standalone.test-amd64-amd64-xl to get rid of this message.
Offending ECDSA key in tmp/t.known_hosts_standalone.test-amd64-amd64-xl:2
Keyboard-interactive authentication is disabled to avoid man-in-the-middle attacks.
2014-07-29 06:31:03 Z toolstack xl
2014-07-29 06:31:03 Z executing ssh ... root@192.168.199.69 xl create /etc/xen/debian.guest.osstest.cfg
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!     @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the ECDSA key sent by the remote host is
ad:99:f6:ec:13:9e:76:bb:12:ae:e7:5e:c2:98:d7:95.
Please contact your system administrator.
Add correct host key in tmp/t.known_hosts_standalone.test-amd64-amd64-xl to get rid of this message.
Offending ECDSA key in tmp/t.known_hosts_standalone.test-amd64-amd64-xl:2
Keyboard-interactive authentication is disabled to avoid man-in-the-middle attacks.
Parsing config from /etc/xen/debian.guest.osstest.cfg
2014-07-29 06:31:04 Z executing ssh ... root@192.168.199.69 xl list
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!     @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the ECDSA key sent by the remote host is
ad:99:f6:ec:13:9e:76:bb:12:ae:e7:5e:c2:98:d7:95.
Please contact your system administrator.
Add correct host key in tmp/t.known_hosts_standalone.test-amd64-amd64-xl to get rid of this message.
Offending ECDSA key in tmp/t.known_hosts_standalone.test-amd64-amd64-xl:2
Keyboard-interactive authentication is disabled to avoid man-in-the-middle attacks.
2014-07-29 06:31:05 Z guest debian.guest.osstest state is r
2014-07-29 06:31:05 Z guest debian.guest.osstest 5e:36:0e:f5:00:01 22 link/ip/tcp: waiting 40s...
2014-07-29 06:31:05 Z guest debian.guest.osstest: 5e:36:0e:f5:00:01 192.168.199.73
2014-07-29 06:31:11 Z ping 192.168.199.73 down
2014-07-29 06:31:11 Z guest debian.guest.osstest 5e:36:0e:f5:00:01 22 link/ip/tcp: ping gave (256): PING 192.168.199.73 (192.168.199.73) 56(84) bytes of data. | From 192.168.199.68 icmp_seq=1 Destination Host Unreachable | From 192.168.199.68 icmp_seq=2 Destination Host Unreachable | From 192.168.199.68 icmp_seq=3 Destination Host Unreachable | From 192.168.199.68 icmp_seq=4 Destination Host Unreachable | From 192.168.199.68 icmp_seq=5 Destination Host Unreachable |  | --- 192.168.199.73 ping statistics --- | 5 packets transmitted, 0 received, +5 errors, 100% packet loss, time XXXms | pipe 3 |  (waiting) ...
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@192.168.199.73 echo guest debian.guest.osstest: ok
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!     @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the ECDSA key sent by the remote host is
ad:99:f6:ec:13:9e:76:bb:12:ae:e7:5e:c2:98:d7:95.
Please contact your system administrator.
Add correct host key in tmp/t.known_hosts_standalone.test-amd64-amd64-xl to get rid of this message.
Offending ECDSA key in tmp/t.known_hosts_standalone.test-amd64-amd64-xl:3
Keyboard-interactive authentication is disabled to avoid man-in-the-middle attacks.
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
+ date -u +%Y-%m-%d %H:%M:%S Z exit status 255
2014-07-29 06:31:36 Z exit status 255
+ exit 255
2014-07-29 06:31:36 Z standalone.test-amd64-amd64-xl 9 status status fail
2014-07-29 06:31:36 Z finished standalone.test-amd64-amd64-xl ts-guest-start debian fail child process exited abnormally
2014-07-29 06:31:36 Z standalone.test-amd64-amd64-xl run-job/test-debian failed: test script failed
2014-07-29 06:31:36 Z starting standalone.test-amd64-amd64-xl ts-logs-capture host capture-logs(10)
2014-07-29 06:31:36 Z standalone.test-amd64-amd64-xl ========== 10 testid capture-logs(10) ==========
2014-07-29 06:31:36 Z awaiting standalone.test-amd64-amd64-xl ts-logs-capture host
+ OSSTEST_JOB=test-amd64-amd64-xl
+ export OSSTEST_JOB
+ ./ts-logs-capture host
2014-07-29 06:31:36 Z starting standalone.test-amd64-amd64-xl
2014-07-29 06:31:36 Z setting all_hostflags=arch-amd64,arch-xen-amd64,suite-wheezy,purpose-test
2014-07-29 06:31:36 Z setting arch=amd64
2014-07-29 06:31:36 Z setting buildjob=build-amd64
2014-07-29 06:31:36 Z setting console=hvc0
2014-07-29 06:31:36 Z setting debian_arch=amd64
2014-07-29 06:31:36 Z setting debian_boot_timeout=40
2014-07-29 06:31:36 Z setting debian_cfgpath=/etc/xen/debian.guest.osstest.cfg
2014-07-29 06:31:36 Z setting debian_console=hvc0
2014-07-29 06:31:36 Z setting debian_disk_lv=debian.guest.osstest-disk
2014-07-29 06:31:36 Z setting debian_domname=debian.guest.osstest
2014-07-29 06:31:36 Z setting debian_ether=5e:36:0e:f5:00:01
2014-07-29 06:31:36 Z setting debian_hostname=debian.guest.osstest
2014-07-29 06:31:36 Z setting debian_kernkind=pvops
2014-07-29 06:31:36 Z setting debian_rootdev=xvda
2014-07-29 06:31:36 Z setting debian_swap_lv=debian.guest.osstest-swap
2014-07-29 06:31:36 Z setting debian_tcpcheckport=22
2014-07-29 06:31:36 Z setting debian_vg=testhost
2014-07-29 06:31:36 Z setting host=testhost
2014-07-29 06:31:36 Z setting kernbuildjob=build-amd64-pvops
2014-07-29 06:31:36 Z setting kernkind=pvops
2014-07-29 06:31:36 Z setting toolstack=xl
2014-07-29 06:31:36 Z setting xen_kernel_path=/boot/vmlinuz-3.4.99+
2014-07-29 06:31:36 Z setting xen_kernel_ver=3.4.99+
2014-07-29 06:31:36 Z setting xenbuildjob=build-amd64
2014-07-29 06:31:36 Z log capturing not enabled
+ rc=0
+ date -u +%Y-%m-%d %H:%M:%S Z exit status 0
2014-07-29 06:31:36 Z exit status 0
+ exit 0
2014-07-29 06:31:36 Z standalone.test-amd64-amd64-xl 10 status status pass
2014-07-29 06:31:36 Z finished standalone.test-amd64-amd64-xl ts-logs-capture host pass
2014-07-29 06:31:36 Z at least one test failed
root@OSSTEST:~/osstest#

[-- Attachment #3: Type: text/plain, Size: 126 bytes --]

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

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

[Ian Campbell]

On Tue, 2014-07-29 at 08:24 +0000, Pang, LongtaoX wrote:
> 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: 
[...]
> So, do you ever meet this question before? Is it a issue of something wrong about my setting?

The nc command you used is one shot. You've used -k which makes it
listen again, but you've only piped dhcpd.leases to stdin once, so the
second connection won't have anything to say. osstest needs to be able
to retrieve the leases repeatedly.

I don't know how to get netcat to do what you want. We have it setup
using inetd, e.g. in /etc/inetd.conf:
5556		stream	tcp	nowait		nobody	/bin/cat cat /var/lib/dhcp3/dhcpd.leases

You might be able to build something with a shell while loop instead of
-k, but I would imagine it wouldn't be very robust against multiple
osstest sessions running in parallel. Some netcat variants support -c to
execute a command on connect, which you might be able to use together
with -k.

Ian.