canonical-ci-engineering team mailing list archive
-
canonical-ci-engineering team
-
Mailing list archive
-
Message #00872
Touch emulator and clouds (or nested kvm vs MAAS and Juju)
Yesterday I got a request from the SDK team to help them set up some
automated testing by October. As one might imagine, this requires a
phone or the emulator:
https://docs.google.com/a/canonical.com/document/d/1D7J8TgxqDBpuilE8z1EGtUF4OK_kGQm39DodzVbbOKY/edit?usp=drive_web
I've directed us down the path of running the emulator on top of bare
metal, provisioned using MAAS and Juju, because nested kvm has been
problematic in the past. This came with the backing of IS.
Still, the more requests I get for services that would require either
nested kvm or a more complex setup, the more I want to see for myself
how much of a problem it really is. So in the background last night I
started to investigate.
After some false starts with the wrong emulator package¹, I managed to
piece together the following:
sudo add-apt-respository ppa:phablet-team/tools # for the correct
emulator package and phablet-tools
sudo apt-get install bzr ubuntu-emulator xvfb
sudo ubuntu-emulator create --arch=i386 myinstance
xvfb-run ubuntu-emulator run --memory=1024 myinstance
Unfortunately this isn't enough to get a working environment:
buntu@juju-lcy-machine-0:~$ LIBGL_DEBUG=verbose xvfb-run glxinfo
name of display: :99
libGL: screen 0 does not appear to be DRI3 capable
libGL: OpenDriver: trying /usr/lib/i386-linux-gnu/dri/tls/swrast_dri.so
libGL: OpenDriver: trying /usr/lib/i386-linux-gnu/dri/swrast_dri.so
libGL: driver does not expose __driDriverGetExtensions_swrast():
/usr/lib/i386-linux-gnu/dri/swrast_dri.so: undefined symbol:
__driDriverGetExtensions_swrast
libGL: Can't open configuration file /home/ubuntu/.drirc: No such file
or directory.
libGL: Can't open configuration file /home/ubuntu/.drirc: No such file
or directory.
libGL error: failed to load driver: swrast
Error: couldn't find RGB GLX visual or fbconfig
Error: couldn't find RGB GLX visual or fbconfig
Dimitri and I tried to work through this a bit. Thinking it was due to
missing GL packages, I installed the ubuntu-desktop metapackage. This
didn't help.
So that's where we're at. It looks like nested kvm might work after
all, but we now have a problem getting gallium and llvmpipe to step in
and provide software-based 3D rendering.
¹ https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1347737
Follow ups