Linux Foundation Wiki

project collaboration site

User Tools

Site Tools


B@D Known Issues, Workarounds and Troubleshooting Guide

This page details the known issues and any workarounds when working with the B@D VM. The issues are tracked in the CIP bugtracker on Links to the issues are given when possible. Additionally, the CIP testing team has started compiling a troubleshooting guide for some common problems we've seen that are not bugs.

B@D Virtual Machine Known Issues and their Workarounds

Known issues of the VM created within the CIP project including LAVAv2 and KernelCI.

Issue #84: Disk Space Filling up

There is a known issue with LAVA2 that it does not clear out some temporary files see

Issue #53: U Boot Prompt Detection

LAVA looks for the U-Boot prompt but due to differing forms of this prompt may not find it, see for background.

Issue #87: Test times may be shown incorrectly

If you suspend your host with Vagrant still running, when you awaken it the VM still has the time when suspended and it does not get updated to the time now. See for the associated issue.

Issue #56: LAVA health check wastes 30 seconds waiting for initramfs shell

LAVA's health check will pause at the auto-login-action see for the associated issue.

Issue #92: Virtualbox GUI reports "Invalid settings detected"

This shows up on Settings dialog of the B@D VM. See for the associated issue.

Issue #99: Issues with installing when running behind a web proxy

When attempting to install B@D on a machine behind a web proxy you may experience the issues detailed here:

Issue #103: Build artifacts referenced in the Beaglebone black health check are no longer accessible

The beaglebone black health check and other tests for that device reference files on the linaro website that have now moved location. See for the history of this issue.

* Important * These changes need applying whether the user is using b@d from git or the pre-provisioned box.

The installation procedure is as follows:

1. On the VM


2. Check the integrity of the download - see these instructions for the box replace with the appropriate file names.

cd /vagrant
sudo tar zxf $DOWNLOADDIR/tests-0.1.tgz

3. If you have already created a Beaglebone black health check then you need to replace it with the new /vagrant/tests/bbb_debian_ramdisk_test.yaml

In the longer term there will be a 0.9.2 release of b@d which will include a local version of initramfs and versions of the BBB kernel to provide an initial health check.

B@D Virtual Machine Troubleshooting Guide

1. Dealing With Stalled Bring-up of Vagrant Devices

If during “vagrant up” the VM becomes unresponsive at the “Configuring and enabling network interfaces” step.

Press Ctrl-C twice to force a shutdown of the VM and restart it by issuing the vagrant up command again. Normal vagrant control should be possible after the restart.

Note: You can also force a shutdown using the Virtualbox GUI.

2. Warnings and Errors during Vagrant Up Process

Below are a list of errors you might see during the vagrant up process:

A. GetPassWarning: This warning is safe to ignore on our Board-at-Desk Single-Developer VM. It does not affect the operation of the KernelCI/LAVA VM.

  1. GetPassWarning: Can not control echo on the terminal." - "Warning: Password input may be echoed."

B. CommaSeparatedIntegerField: This warning is safe to ignore on our Board-at-Desk Single-Developer VM. It does not affect the operation of the KernelCI/LAVA VM.

  1. ==> default: lava_scheduler_app.Notification.job_status_trigger: (fields.W901) CommaSeparatedIntegerField has been deprecated. Support for it (except in historical migrations) will be removed in Django 2.0.
  2. ==> default: HINT: Use CharField(validators=[validate_comma_separated_integer_list]) instead.

3. Adding extra resources to the Virtual Machine

The Vagrant instance by default is configured with 2GB of memory, if you require more memory, and have sufficient local resources on your machine, edit line 26 of the Vagrantfile so that vbox.customize [“modifyvm”, :id, “–memory”, “2048”] is given a larger value.

Similarly, if you need a larger disk storage capacity, there are several ways you can accomplish that. The preferred method is shown below.

1. To Add a new hard drive to the B@D Virtual Machine, shutdown the VM using vagrant halt

2. Using the GUI, add a hard drive to the VM (/dev/sda)

3. Boot the VM using vagrant up

4. Create a new partition table on the new disk using fdisk

5. Create a new primary partition (/dev/sda1)

6. Write your changes to disk

7. Make a directory where you want to mount the new disk to (/storage)

8. Mount /dev/sdb1 to /storage

9. Consider moving the /var directory to the new drive since that is where the build artifacts are stored.

Back to the B@D Features page

civilinfrastructureplatform/ciptestingknownissues.txt · Last modified: 2017/06/14 12:06 by rajmarshall