Hi All,
I'm setting up a local LAVA scheduler+dispatcher (standalone).
I'm able to posts jobs, but I think I'm missing an initial configuration for some actions to complete, namely action deploy_linaro_image
the eMMC flash content of my BBB-RevB6 is pretty standard (debian-7.9 of 2015-11-03, 2gb image). Based on the log, the dispatcher expects the default "testboot" and "testrootfs" partitions with offset 2, I assuime this means that those partitions must be manually created the first time with index 3 and 4 in order for this to work.
I would appreciate some hints, to avoid unnecessary test-and-try, what would be the expected partitionning for BBB with LAVA ?
Thanks in advance, best regards, Marc.
I think what you are referring to is the master image layout - note that this uses a micro SD card, not the eMMC. It's safer to run tests on media which can be removed & replaced, especially if some of those tests could end up being destructive. Generally, LAVA is moving away from master images and you may find NFS to be a much easier way to test on the BBB, depending on what you are trying to test. The eMMC also isn't large enough to create partitions for the master image and the test image partitions needed for most tests.
Pre-built master images can be found here: http://images.validation.linaro.org/lava-masters/ but I would not recommend using these on eMMC. BBB in the Cambridge lab have made the eMMC into unused space and do everything on a microSD card - which also gives a lot more space than the 2Gb eMMC.
https://validation.linaro.org/static/docs/lava-image-creation.html#preparing...
Note also that the refactoring will simply need a bootloader and the need to have any predefined partitions anywhere on the BBB goes away completely. (There is a lot more documentation to write before the refactored becomes the default).
On 30 November 2015 at 18:03, Marc Titinger mtitinger@baylibre.com wrote:
Hi All,
I'm setting up a local LAVA scheduler+dispatcher (standalone).
I'm able to posts jobs, but I think I'm missing an initial configuration for some actions to complete, namely action deploy_linaro_image
the eMMC flash content of my BBB-RevB6 is pretty standard (debian-7.9 of 2015-11-03, 2gb image). Based on the log, the dispatcher expects the default "testboot" and "testrootfs" partitions with offset 2, I assuime this means that those partitions must be manually created the first time with index 3 and 4 in order for this to work.
I would appreciate some hints, to avoid unnecessary test-and-try, what would be the expected partitionning for BBB with LAVA ?
Thanks in advance, best regards, Marc.
Lava-users mailing list Lava-users@lists.linaro.org https://lists.linaro.org/mailman/listinfo/lava-users
On 01/12/2015 09:18, Neil Williams wrote:
I think what you are referring to is the master image layout - note that this uses a micro SD card, not the eMMC. It's safer to run tests on media which can be removed & replaced, especially if some of those tests could end up being destructive. Generally, LAVA is moving away from master images and you may find NFS to be a much easier way to test on the BBB, depending on what you are trying to test. The eMMC also isn't large enough to create partitions for the master image and the test image partitions needed for most tests.
Pre-built master images can be found here: http://images.validation.linaro.org/lava-masters/ but I would not recommend using these on eMMC. BBB in the Cambridge lab have made the eMMC into unused space and do everything on a microSD card - which also gives a lot more space than the 2Gb eMMC.
https://validation.linaro.org/static/docs/lava-image-creation.html#preparing...
Note also that the refactoring will simply need a bootloader and the need to have any predefined partitions anywhere on the BBB goes away completely. (There is a lot more documentation to write before the refactored becomes the default).
That makes a lot of sense, thank you Neil! I'll be happy to test the refactored version once it's available and I'm a bit seasoned with LAVA.
Best Regards, Marc.
On 30 November 2015 at 18:03, Marc Titinger mtitinger@baylibre.com wrote:
Hi All,
I'm setting up a local LAVA scheduler+dispatcher (standalone).
I'm able to posts jobs, but I think I'm missing an initial configuration for some actions to complete, namely action deploy_linaro_image
the eMMC flash content of my BBB-RevB6 is pretty standard (debian-7.9 of 2015-11-03, 2gb image). Based on the log, the dispatcher expects the default "testboot" and "testrootfs" partitions with offset 2, I assuime this means that those partitions must be manually created the first time with index 3 and 4 in order for this to work.
I would appreciate some hints, to avoid unnecessary test-and-try, what would be the expected partitionning for BBB with LAVA ?
Thanks in advance, best regards, Marc.
Lava-users mailing list Lava-users@lists.linaro.org https://lists.linaro.org/mailman/listinfo/lava-users
I think I went a bit further (with Pandaboard-es this time), but I get
Lava failed at action boot_linaro_image with error:Failed to boot test image.
what exactly triggers an exception ? browsing the python, at this point I would expect the tests commands to happen in client.boot_linaro_image(self): (mount, ls /, df, ifconfig). If I log manually into the board, the prompt and test commands are ok.
Many thanks, Marc.
2015-12-01 10:12 GMT+01:00 Marc Titinger mtitinger@baylibre.com:
On 01/12/2015 09:18, Neil Williams wrote:
I think what you are referring to is the master image layout - note that this uses a micro SD card, not the eMMC. It's safer to run tests on media which can be removed & replaced, especially if some of those tests could end up being destructive. Generally, LAVA is moving away from master images and you may find NFS to be a much easier way to test on the BBB, depending on what you are trying to test. The eMMC also isn't large enough to create partitions for the master image and the test image partitions needed for most tests.
Pre-built master images can be found here: http://images.validation.linaro.org/lava-masters/ but I would not recommend using these on eMMC. BBB in the Cambridge lab have made the eMMC into unused space and do everything on a microSD card - which also gives a lot more space than the 2Gb eMMC.
https://validation.linaro.org/static/docs/lava-image-creation.html#preparing...
Note also that the refactoring will simply need a bootloader and the need to have any predefined partitions anywhere on the BBB goes away completely. (There is a lot more documentation to write before the refactored becomes the default).
That makes a lot of sense, thank you Neil! I'll be happy to test the refactored version once it's available and I'm a bit seasoned with LAVA.
Best Regards, Marc.
On 30 November 2015 at 18:03, Marc Titinger mtitinger@baylibre.com wrote:
Hi All,
I'm setting up a local LAVA scheduler+dispatcher (standalone).
I'm able to posts jobs, but I think I'm missing an initial configuration for some actions to complete, namely action deploy_linaro_image
the eMMC flash content of my BBB-RevB6 is pretty standard (debian-7.9 of 2015-11-03, 2gb image). Based on the log, the dispatcher expects the default "testboot" and "testrootfs" partitions with offset 2, I assuime this means that those partitions must be manually created the first time with index 3 and 4 in order for this to work.
I would appreciate some hints, to avoid unnecessary test-and-try, what would be the expected partitionning for BBB with LAVA ?
Thanks in advance, best regards, Marc.
Lava-users mailing list Lava-users@lists.linaro.org https://lists.linaro.org/mailman/listinfo/lava-users
You didn't define anything for the device to do as a deploy, so LAVA could not tell what it should be expecting to find in the output to tell whether the boot operation succeeded or not. Just booting whatever happens to have been left on the device from the last test is not useful.
On 1 December 2015 at 16:36, Marc Titinger mtitinger@baylibre.com wrote:
I think I went a bit further (with Pandaboard-es this time), but I get
Lava failed at action boot_linaro_image with error:Failed to boot test image.
what exactly triggers an exception ? browsing the python, at this point I would expect the tests commands to happen in client.boot_linaro_image(self): (mount, ls /, df, ifconfig). If I log manually into the board, the prompt and test commands are ok.
Many thanks, Marc.
2015-12-01 10:12 GMT+01:00 Marc Titinger mtitinger@baylibre.com:
On 01/12/2015 09:18, Neil Williams wrote:
I think what you are referring to is the master image layout - note that this uses a micro SD card, not the eMMC. It's safer to run tests on media which can be removed & replaced, especially if some of those tests could end up being destructive. Generally, LAVA is moving away from master images and you may find NFS to be a much easier way to test on the BBB, depending on what you are trying to test. The eMMC also isn't large enough to create partitions for the master image and the test image partitions needed for most tests.
Pre-built master images can be found here: http://images.validation.linaro.org/lava-masters/ but I would not recommend using these on eMMC. BBB in the Cambridge lab have made the eMMC into unused space and do everything on a microSD card - which also gives a lot more space than the 2Gb eMMC.
https://validation.linaro.org/static/docs/lava-image-creation.html#preparing...
Note also that the refactoring will simply need a bootloader and the need to have any predefined partitions anywhere on the BBB goes away completely. (There is a lot more documentation to write before the refactored becomes the default).
That makes a lot of sense, thank you Neil! I'll be happy to test the refactored version once it's available and I'm a bit seasoned with LAVA.
Best Regards, Marc.
On 30 November 2015 at 18:03, Marc Titinger mtitinger@baylibre.com wrote:
Hi All,
I'm setting up a local LAVA scheduler+dispatcher (standalone).
I'm able to posts jobs, but I think I'm missing an initial configuration for some actions to complete, namely action deploy_linaro_image
the eMMC flash content of my BBB-RevB6 is pretty standard (debian-7.9 of 2015-11-03, 2gb image). Based on the log, the dispatcher expects the default "testboot" and "testrootfs" partitions with offset 2, I assuime this means that those partitions must be manually created the first time with index 3 and 4 in order for this to work.
I would appreciate some hints, to avoid unnecessary test-and-try, what would be the expected partitionning for BBB with LAVA ?
Thanks in advance, best regards, Marc.
Lava-users mailing list Lava-users@lists.linaro.org https://lists.linaro.org/mailman/listinfo/lava-users
On 01/12/2015 17:43, Neil Williams wrote:
You didn't define anything for the device to do as a deploy, so LAVA could not tell what it should be expecting to find in the output to tell whether the boot operation succeeded or not. Just booting whatever happens to have been left on the device from the last test is not useful.
Ah ok of course. sorry for that.
Now, adding the deploy as below, lava seems not to recognize the "tgz" and will try mounting it as is. The documented examples reference gziped files instead.
{ "command": "deploy_linaro_image", "parameters": { "image": "http://images.validation.linaro.org/lava-masters/panda-master.img.tgz" } },
PM DEBUG: Attempt 1: Executing on host : 'sudo mount -o loop,offset=0 /var/lib/lava/dispatcher/tmp/tmpgVMCHa/panda-master.img.tgz /tmp/tmpvcA7cT'
On 1 December 2015 at 16:36, Marc Titinger mtitinger@baylibre.com wrote:
I think I went a bit further (with Pandaboard-es this time), but I get
Lava failed at action boot_linaro_image with error:Failed to boot test image.
what exactly triggers an exception ? browsing the python, at this point I would expect the tests commands to happen in client.boot_linaro_image(self): (mount, ls /, df, ifconfig). If I log manually into the board, the prompt and test commands are ok.
Many thanks, Marc.
2015-12-01 10:12 GMT+01:00 Marc Titinger mtitinger@baylibre.com:
On 01/12/2015 09:18, Neil Williams wrote:
I think what you are referring to is the master image layout - note that this uses a micro SD card, not the eMMC. It's safer to run tests on media which can be removed & replaced, especially if some of those tests could end up being destructive. Generally, LAVA is moving away from master images and you may find NFS to be a much easier way to test on the BBB, depending on what you are trying to test. The eMMC also isn't large enough to create partitions for the master image and the test image partitions needed for most tests.
Pre-built master images can be found here: http://images.validation.linaro.org/lava-masters/ but I would not recommend using these on eMMC. BBB in the Cambridge lab have made the eMMC into unused space and do everything on a microSD card - which also gives a lot more space than the 2Gb eMMC.
https://validation.linaro.org/static/docs/lava-image-creation.html#preparing...
Note also that the refactoring will simply need a bootloader and the need to have any predefined partitions anywhere on the BBB goes away completely. (There is a lot more documentation to write before the refactored becomes the default).
That makes a lot of sense, thank you Neil! I'll be happy to test the refactored version once it's available and I'm a bit seasoned with LAVA.
Best Regards, Marc.
On 30 November 2015 at 18:03, Marc Titinger mtitinger@baylibre.com wrote:
Hi All,
I'm setting up a local LAVA scheduler+dispatcher (standalone).
I'm able to posts jobs, but I think I'm missing an initial configuration for some actions to complete, namely action deploy_linaro_image
the eMMC flash content of my BBB-RevB6 is pretty standard (debian-7.9 of 2015-11-03, 2gb image). Based on the log, the dispatcher expects the default "testboot" and "testrootfs" partitions with offset 2, I assuime this means that those partitions must be manually created the first time with index 3 and 4 in order for this to work.
I would appreciate some hints, to avoid unnecessary test-and-try, what would be the expected partitionning for BBB with LAVA ?
Thanks in advance, best regards, Marc.
Lava-users mailing list Lava-users@lists.linaro.org https://lists.linaro.org/mailman/listinfo/lava-users
The master image is not an image to deploy as part of the test. It is the image which is written to the SD card before tests start - when the device is first deployed.
https://validation.linaro.org/static/docs/lava-image-creation.html?highlight...
On 1 December 2015 at 17:16, Marc Titinger mtitinger@baylibre.com wrote:
On 01/12/2015 17:43, Neil Williams wrote:
You didn't define anything for the device to do as a deploy, so LAVA could not tell what it should be expecting to find in the output to tell whether the boot operation succeeded or not. Just booting whatever happens to have been left on the device from the last test is not useful.
Ah ok of course. sorry for that.
Now, adding the deploy as below, lava seems not to recognize the "tgz" and will try mounting it as is. The documented examples reference gziped files instead.
{ "command": "deploy_linaro_image", "parameters": { "image":"http://images.validation.linaro.org/lava-masters/panda-master.img.tgz" } },
PM DEBUG: Attempt 1: Executing on host : 'sudo mount -o loop,offset=0 /var/lib/lava/dispatcher/tmp/tmpgVMCHa/panda-master.img.tgz /tmp/tmpvcA7cT'
On 1 December 2015 at 16:36, Marc Titinger mtitinger@baylibre.com wrote:
I think I went a bit further (with Pandaboard-es this time), but I get
Lava failed at action boot_linaro_image with error:Failed to boot test image.
what exactly triggers an exception ? browsing the python, at this point I would expect the tests commands to happen in client.boot_linaro_image(self): (mount, ls /, df, ifconfig). If I log manually into the board, the prompt and test commands are ok.
Many thanks, Marc.
2015-12-01 10:12 GMT+01:00 Marc Titinger mtitinger@baylibre.com:
On 01/12/2015 09:18, Neil Williams wrote:
I think what you are referring to is the master image layout - note that this uses a micro SD card, not the eMMC. It's safer to run tests on media which can be removed & replaced, especially if some of those tests could end up being destructive. Generally, LAVA is moving away from master images and you may find NFS to be a much easier way to test on the BBB, depending on what you are trying to test. The eMMC also isn't large enough to create partitions for the master image and the test image partitions needed for most tests.
Pre-built master images can be found here: http://images.validation.linaro.org/lava-masters/ but I would not recommend using these on eMMC. BBB in the Cambridge lab have made the eMMC into unused space and do everything on a microSD card - which also gives a lot more space than the 2Gb eMMC.
https://validation.linaro.org/static/docs/lava-image-creation.html#preparing...
Note also that the refactoring will simply need a bootloader and the need to have any predefined partitions anywhere on the BBB goes away completely. (There is a lot more documentation to write before the refactored becomes the default).
That makes a lot of sense, thank you Neil! I'll be happy to test the refactored version once it's available and I'm a bit seasoned with LAVA.
Best Regards, Marc.
On 30 November 2015 at 18:03, Marc Titinger mtitinger@baylibre.com wrote:
Hi All,
I'm setting up a local LAVA scheduler+dispatcher (standalone).
I'm able to posts jobs, but I think I'm missing an initial configuration for some actions to complete, namely action deploy_linaro_image
the eMMC flash content of my BBB-RevB6 is pretty standard (debian-7.9 of 2015-11-03, 2gb image). Based on the log, the dispatcher expects the default "testboot" and "testrootfs" partitions with offset 2, I assuime this means that those partitions must be manually created the first time with index 3 and 4 in order for this to work.
I would appreciate some hints, to avoid unnecessary test-and-try, what would be the expected partitionning for BBB with LAVA ?
Thanks in advance, best regards, Marc.
Lava-users mailing list Lava-users@lists.linaro.org https://lists.linaro.org/mailman/listinfo/lava-users
On 01/12/2015 18:22, Neil Williams wrote:
The master image is not an image to deploy as part of the test. It is the image which is written to the SD card before tests start - when the device is first deployed.
https://validation.linaro.org/static/docs/lava-image-creation.html?highlight...
got it, nice use of the highlight keyword btw ;)
I think I'm going to look for an example of deploy using nfs/tftp to avoid the image flashing part. That's what we want to do anyway.
M.
On 1 December 2015 at 17:16, Marc Titinger mtitinger@baylibre.com wrote:
On 01/12/2015 17:43, Neil Williams wrote:
You didn't define anything for the device to do as a deploy, so LAVA could not tell what it should be expecting to find in the output to tell whether the boot operation succeeded or not. Just booting whatever happens to have been left on the device from the last test is not useful.
Ah ok of course. sorry for that.
Now, adding the deploy as below, lava seems not to recognize the "tgz" and will try mounting it as is. The documented examples reference gziped files instead.
{ "command": "deploy_linaro_image", "parameters": { "image":"http://images.validation.linaro.org/lava-masters/panda-master.img.tgz" } },
PM DEBUG: Attempt 1: Executing on host : 'sudo mount -o loop,offset=0 /var/lib/lava/dispatcher/tmp/tmpgVMCHa/panda-master.img.tgz /tmp/tmpvcA7cT'
On 1 December 2015 at 16:36, Marc Titinger mtitinger@baylibre.com wrote:
I think I went a bit further (with Pandaboard-es this time), but I get
Lava failed at action boot_linaro_image with error:Failed to boot test image.
what exactly triggers an exception ? browsing the python, at this point I would expect the tests commands to happen in client.boot_linaro_image(self): (mount, ls /, df, ifconfig). If I log manually into the board, the prompt and test commands are ok.
Many thanks, Marc.
2015-12-01 10:12 GMT+01:00 Marc Titinger mtitinger@baylibre.com:
On 01/12/2015 09:18, Neil Williams wrote:
I think what you are referring to is the master image layout - note that this uses a micro SD card, not the eMMC. It's safer to run tests on media which can be removed & replaced, especially if some of those tests could end up being destructive. Generally, LAVA is moving away from master images and you may find NFS to be a much easier way to test on the BBB, depending on what you are trying to test. The eMMC also isn't large enough to create partitions for the master image and the test image partitions needed for most tests.
Pre-built master images can be found here: http://images.validation.linaro.org/lava-masters/ but I would not recommend using these on eMMC. BBB in the Cambridge lab have made the eMMC into unused space and do everything on a microSD card - which also gives a lot more space than the 2Gb eMMC.
https://validation.linaro.org/static/docs/lava-image-creation.html#preparing...
Note also that the refactoring will simply need a bootloader and the need to have any predefined partitions anywhere on the BBB goes away completely. (There is a lot more documentation to write before the refactored becomes the default).
That makes a lot of sense, thank you Neil! I'll be happy to test the refactored version once it's available and I'm a bit seasoned with LAVA.
Best Regards, Marc.
On 30 November 2015 at 18:03, Marc Titinger mtitinger@baylibre.com wrote: > > Hi All, > > I'm setting up a local LAVA scheduler+dispatcher (standalone). > > I'm able to posts jobs, but I think I'm missing an initial > configuration > for some actions to complete, namely > action deploy_linaro_image > > the eMMC flash content of my BBB-RevB6 is pretty standard (debian-7.9 of > 2015-11-03, 2gb image). > Based on the log, the dispatcher expects the default "testboot" and > "testrootfs" partitions with offset 2, I assuime this means that those > partitions must be manually created the first time with index 3 and 4 in > order for this to work. > > I would appreciate some hints, to avoid unnecessary test-and-try, what > would > be the expected partitionning for BBB with LAVA ? > > Thanks in advance, > best regards, > Marc. > > > > _______________________________________________ > Lava-users mailing list > Lava-users@lists.linaro.org > https://lists.linaro.org/mailman/listinfo/lava-users >
lava-users@lists.lavasoftware.org
-
Marc Titinger -
Neil Williams