Hi Neil!

On Thursday 20 July 2017 12:44:35 Neil Williams wrote:

> There is no need to create a LAVA specific variable. In this specific

> case, this can be handled in the existing environment support.

>

> LAVA V2 supports env.yaml

>

> /etc/lava-server/env.yaml

> /etc/lava-server/dispatcher-config/env.yaml

>

> # Configure the environment that will be used within the server and

> the dispatcher.

Perfect. Thanks for the pointer.

> If admins want to set QEMU_AUDIO_DRV=none then that would be the place

> to set it. It's not a default at the moment simply because we haven't

> had problems with QEMU tests in this way.

Agree, this is a new use-case we stumbled upon.

> However, there are lots of other environment variables which QEMU can

> use and plenty of command line options which are available which could

> let QEMU test jobs interfere with the performance of the worker as a

> whole. Care is needed here.

Full ack.

> If particular tests need to use the full functionality of QEMU, those

> tests must be performed by running QEMU on a suitable test device, not

> by running QEMU on the worker.

For our case above, we just need to present sound hardware to the guest. So it is fine to just let qemu throw the data away and use the worker directly.

I agree that more complex setups should go on a separate device.

Thanks for the pointer on the env.yaml, Neil. We'll try it.

--

Dipl.-Ing.

Jan-Simon Möller

jansimon.moeller@gmx.de