Comment 31 for bug 1545913

Steve Langasek [2016-04-11 6:29 -0000]:
> > + lxd-images import ubuntu yenial --alias ubuntu-yenial

Also, no such release :-)

Do you actually need to do this? lxd automatically downloads images
from the remote when needed.

> > Also, we don't have coverage for lxd on armhf or s390x as they can't
> > provide machine-level isolation. That's probably fine, but can maybe be
> > improved when we have more confidence lxd/juju won't blow things up as
> > much as the dev versions have tended to.
>
> Unless the tests themselves actually require machine-level isolation, I
> would suggest that the 'breaks-testbed' restriction that's been declared is
> sufficient, and there's no need to specify 'isolation-machine' as well - and
> that you can leave it to the autopkgtest implementors to ensure that the
> testbed is appropriately isolated.

If the tests work in LXC (i. e. the whole thing works in nested
containers), then restriction-container is enough. But please test
this locally before. Otherwise, if the tests fail with the lxc runner
but work in qemu, keep the i-machine for now.

Not sure what the "breaks-testbed" does, but this does nothing wrt.
selecting/skipping tests between lxc and full VMs. It merely means
that a new instance/container will be created after running this test
(and also that the test will be skipped with the "null" runner, but
that's irrelevant here).