Lava document contains content of how to add simple qemu devices and how to write its job define. But it does not contain how to add real machine device and how to write its test job like uboot image and linex kernel specifications,etc.
Is there any document on how to step by step to build real machine testing?
I have an important question neet to clarify.
For exampe when I manunl boot kernel by uboot, once board startup and into uboot interactive environment, I manual input follow command as:
setenv image zImage_mx....
setenv nfsroot /rootfs/rootfs001....
...
if I whan to dispatcher to boot the board kernel, I need write job definition,Is it written like this?:
boot:
# list of boot methods which this device supports.
methods:
- u-boot:
parameters:
...
oe:
commands:
- setenv image zImage_mx....
- setenv nfsroot /rootfs/rootfs001....
Through web admin interface,I had added qemu device,and web devices list can display qemu device. It seems qemu device had startuped ok.
We know that if linux device startup successfully it must included uboot and kernel image. But where are the uboot image and kernel image of qemu ? In which config file is described the path of uboot and kernel image?
I am building lava test system and currently add new addvice.
According to document than step of "Adding a dictionary to the first QEMU device",follow config items neet to write to .jianja2 file.
{% extends 'qemu.jinja2' %}
{% set mac_addr = '52:54:00:12:34:59' %}
{% set memory = '1024' %}
Which file is to be writen to above config items ?does its directory path must be at path:/etc/lava-server/dispatcher-config/device-types/?
How to make these items take effect immediatly?which command to use to take effect above config items? the document is not said.
Hi,
I using LAVA version 2018.5-post1 to boot from USB thumb drive using Yocto Project's image. The LAVA job definition contain 2 deployments and booting actions. The first deployment is deploy the image to NFS server and boot using TFTP method. The second deployment is download an image to DUT and flash it on USB thumb drive. The DUT was able to download the image however it failed at flash to thumb drive. I'm use dd command as my tool to flash the image. Below is an example on lava-job definition and output message from LAVA. Due to this issue, I unable to boot from USB thumb drive. Did anyone know what is the problem?
Snipped code from lava-job definition to deploy on USB thumb drive
- deploy:
timeout:
minutes: 30
to: usb
image:
url: file:///home/user/image/yocto-image.xz
compression: xz
root_partition: 1
device: 'boot'
download:
tool: '/usr/bin/wget'
prompt: 'HTTP request sent, awaiting response...'
options: '--S {DOWNLOAD_URL}'
os: oe
The command from LAVA
wget http://lavadisptcher.com/tmp/storage/image/yocto-image.xz | dd of=/dev/disk/by-id/<myusbthumdriveid> bs=4M
This is the output message form LAVA after download flash the image
0+0 records in
0+0 records out
0 bytes copied
Regards,
Alim Hussin
Hi,
I think the lava web document is relatively simple.I still have some basic questions that didn’t understand.
I want to add new real board(for example the arm development board,includes serial,ethernet interface etc)into lava environment. The board had ordinary uboot program, and uboot can download linux kernel image by ethernet interface. If treat it as DUT to run test,do the uboot and kernel program need to be modified or both configuration need to be modified?
When used real board(not qemu),is the uboot image location specified in the job definition file? If so, what keyword is used to indicate the uboot image location?
The lava document description is not enough.
Hello
I have a cubietruck in LAVA, but its devicetype does not follow the rule "devicetype should be the same as devicetree name".
Diverting from this rule, make difficult to find if the device is already handled by LAVA.
I have lots of other boards which suffer the same problem (odroid-xu3 for example)
Do you already have a process for renaming devicetype ?
If not, why about duplicating to the correct name (sun7i-a20-cubietruck) and adding some tags (comment like "{# set deprecated = true}") to the old one.
The deprectation warning could be printed by the LAVA web interface like the warning about not having health checks.
After some release, the deprecated devicetype could be removed.
Regards
Does board test system must include PDU device?
If test system has no PDU and in job definition the boot action method is u-boot. When board had startup to enter linux interactive environment and submit job at this time. Then how does dispatcher restart the board?
Hi LAVA team,
I meet one critical error.
We restart our LAVA server host machine. We can’t know how to restart our LAVA server service.
Could you tell me how to restart LAVA server master service with detail steps? Thanks!
The LAVA server is not installed by us. So we are not clear about this.
BR/Zhanghui