[Xen-devel] failed to boot into kernel during osstest standalone mode

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

Hi Wei,

Have a nice day!
Currently, I am confused about below problem When I doing OSSTest.

Create a global config file in ~/.xen-osstest/config[refer to config.log for 
detail]. 
In osstest.git directory, execute command "./standalone-reset", then execute 
the command "./sg-run-job build-amd64", power off / power on test host machine 
manually according to the prompted on Controller machine, then the test host 
machine will boot from PXE server which I have setup on Controller machine, but 
hangs at "booting the kernel" screen[refer to hangs.jpg]. 
On controller side, it prompted "connection refused": [refer to build-amd64.log 
for detail]

I have setup PXE, tftp, http, dhcp service on Controller machine and the 
function is fine. Also, after I execute command "./standalone-reset", the 
Debian Installer files(version: wheezy) could be fetched from mirrors server 
and the standalone.db could be created successfully.
root@OSSTEST:/tftpboot/root/osstest/debian-installer/amd64# ls 
2014-07-01-wheezy/
initrd.gz  initrd.gz-xen  linux  vmlinuz-xen

So, do you think what the problem might be and give some suggest?
Well, what's the function of "192.168.199.68_preseed" file during OSSTest which 
is generated automatically? I think it's NOT necessary for PXE remote installed 
OS for test host machine, right?

Thanks a lot!
Best Regards,
Longtao

> -----Original Message-----
> From: Wei Liu [mailto:wei.liu2@xxxxxxxxxx]
> Sent: Tuesday, June 24, 2014 6:34 PM
> To: Pang, LongtaoX
> Cc: wei.liu2@xxxxxxxxxx
> Subject: Re: Qustions about OSSTest
> 
> Hello
> 
> On Tue, Jun 24, 2014 at 07:23:31AM +0000, Pang, LongtaoX wrote:
> > Hi Wei,
> >
> > Nice to meet you!  I am Longtao and I am a Xen Virtualization test engineer
> in Intel Corporation.
> >
> > Currently, I am learning Xen automatic test system OSSTest. Fortunately, I
> found your blog of "OSSTest Standalone Mode Step by Step" from blog.xen.org.
> >
> > That's very useful and give me a lot of help.
> > I tried to setup OSSTest environment according your blog, but always failed 
> > to
> run the test and hangs at "fetch 192.168.199.63_preseed: (none) (waiting) ..."
> [Refer to sg-run-job_build-amd64.log for detailed info]. Because there is 
> little
> knowledge about OSSTest, I am very confused to setup the test environment
> successfully and need your help.
> >
> 
> I use hostname instead of IP address. But I think IP address works as well.
> 
> Have you setup your webserver and make sure it can be accessed by the host
> that runs testcases? I seem to remember "fetch XXX" means fetching from
> webserver.
> 
> There's a section describing several services that needed by OSSTest in my 
> blog
> post. But your steps only mentioned TFTP, not sure if you've successfully set 
> up
> other services.
> 
> > Detailed steps I did as below:
> > 1. Setup two machines, one is controller another is test host, both manually
> installed with Debian 7.5 OS.
> > 2. SSH with authentication key between these two machines, IP_addr of
> Controller:192.168.199.69, IP_addr of test_host: 192.168.199.63.
> > 3. Under controller machine, install the necessary packages listed in 
> > README,
> and then git clone OSSTest.
> > 4. Create config file[Refer to config for detailed info] under 
> > "~/.xen-osstest"
> directory.
> > 5. Create necessary directories manually, such as: logs, $TFTPROOT/osstest,
> $httpd_root/osstest.
> > 6. Execute the command: " ./standalone-reset".
> > 7. Try to run a job "./sg-run-job build-amd64", but failed.
> >
> > Could you give some advice about this problem or some detailed documents
> about how to setup OSSTest?
> >
> > Also, I found that when I execute command " ./sg-run-job build-amd64", it 
> > will
> write a file at "/tftpboot/pxelinux.cfg/C0A8C73F" automatically, open
> C0A8C73F, detailed info as below:
> > serial 0 115200
> > timeout 5
> > label overwrite
> >         menu label ^Overwrite
> >         menu default
> >         kernel /root/osstest/debian-installer/amd64/current-wheezy/linux
> >         append vga=normal auto=true preseed
> hw-detect/load_firmware=false DEBCONF_DEBUG=5
> DEBIAN_FRONTEND=text hostname=192.168.199.63
> url=192.168.199.69/var/www/osstest/192.168.199.63_preseed
> netcfg/dhcp_timeout=150 netcfg/choose_interface=auto
> initrd=/root/osstest/tmp/192.168.199.63--initrd.gz domain=uk.xensource.com
> -- console=ttyS0,115200n8
> >         ipappend 2
> > default overwrite
> > This seems like pxe config file, does it means we will use PXE server for
> OSSTest?
> 
> Yes. The host that runs testcases is booted via PXE. OSSTest will alter the
> content of that file as it sees fit.
> 
> > Thanks a lot!
> > Longtao
> 
> > root@OSSTEST:~/osstest# ./sg-run-job build-amd64
> [...]
> > 2014-06-24 05:40:11 Z skipping host key for nonexistent host
> > 192.168.199.63.uk.xensource.com
> > 2014-06-24 05:40:11 Z wrote
> > /var/www//osstest/192.168.199.63_known_hosts (stashed as
> >
> webspace-192.168.199.63_known_hosts+++++++++++++++++++++++++++++++
> ++++
> > ++++++++++)
> > 2014-06-24 05:40:11 Z wrote
> > /var/www//osstest/192.168.199.63_overlay.tar
> > 2014-06-24 05:40:11 Z wrote
> > /var/www//osstest/192.168.199.63_overlay-local.tar
> > 2014-06-24 05:40:11 Z wrote
> > /var/www//osstest/192.168.199.63_X2flibX2fpartmanX2finitX2edX2f000over
> > ride-parted-devices (stashed as
> > webspace-192.168.199.63_X2flibX2fpartmanX2finitX2edX2f000override-part
> > ed-devices+++++++++++++++++++++++++++++++++++++++++++++)
> > 2014-06-24 05:40:11 Z wrote
> > /var/www//osstest/192.168.199.63_early_command-0 (stashed as
> >
> webspace-192.168.199.63_early_command-0+++++++++++++++++++++++++++
> ++++
> > ++++++++++++++)
> > 2014-06-24 05:40:11 Z wrote
> > /var/www//osstest/192.168.199.63_X2flibX2fpartmanX2finitX2edX2f25erase
> > -other-disks (stashed as
> > webspace-192.168.199.63_X2flibX2fpartmanX2finitX2edX2f25erase-other-di
> > sks+++++++++++++++++++++++++++++++++++++++++++++)
> > 2014-06-24 05:40:11 Z wrote
> > /var/www//osstest/192.168.199.63_early_command-1 (stashed as
> >
> webspace-192.168.199.63_early_command-1+++++++++++++++++++++++++++
> ++++
> > ++++++++++++++)
> > 2014-06-24 05:40:11 Z wrote
> > /var/www//osstest/192.168.199.63_late_command-0 (stashed as
> >
> webspace-192.168.199.63_late_command-0++++++++++++++++++++++++++++
> ++++
> > +++++++++++++)
> > 2014-06-24 05:40:11 Z wrote /var/www//osstest/192.168.199.63_preseed
> > (stashed as
> >
> webspace-192.168.199.63_preseed+++++++++++++++++++++++++++++++++++
> ++++
> > ++++++)
> 
> So the file was created ...
> 
> > tmp/t.192.168.199.63.initrd.cpio:        93.4% -- replaced with
> tmp/t.192.168.199.63.initrd.cpio.gz
> > 2014-06-24 05:40:11 Z using initrds:
> > /tftpboot//root/osstest/debian-installer/amd64/current-wheezy/initrd.g
> > z tmp/t.192.168.199.63.initrd.cpio.gz
> > 2014-06-24 05:40:11 Z wrote /tftpboot/pxelinux.cfg/C0A8C73F (stashed
> > as 192.168.199.63-pxelinux.cfg+++++++++++++++++++++++++++++)
> > 2014-06-24 05:40:16 Z power: setting 1 for 192.168.199.63
> > 2014-06-24 05:40:16 Z fetch 192.168.199.63_preseed: waiting 350s...
> > 2014-06-24 05:40:16 Z fetch 192.168.199.63_preseed: (none) (waiting) ...
> 
> but it cannot be fetched from the webserver.
> 
> You might want to check you WebSpace setting in config. Relevant code is in
> Osstest/TestSupport.pm:1812.
> 
> You might also want to change other occurences of "xensource" in config file 
> to
> appropriate values.
> 
> Further more, OSSTest is under constant development. For any further
> questions it's better to send to Xen-devel and CC Ian Jackson and Ian 
> Campbell,
> they might have a better idea of the current status of testing system.
> 
> Wei.

Attachment: build-amd64.log
Description: build-amd64.log

Attachment: config.log
Description: config.log

Attachment: hangs.jpg
Description: hangs.jpg

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