qemu: package qemu-cc

[gorozco1]

Currently our packaged qemu-lite is created from:

https://github.com/01org/qemu-lite

We need to move to use this:

https://github.com/clearcontainers/qemu/tree/qemu-lite-v2.9.0

[gorozco1]

From: https://github.com/clearcontainers/tests/blob/master/.ci/setup_env_ubuntu.sh

./configure --disable-tools --disable-libssh2 --disable-tcmalloc --disable-glusterfs
--disable-seccomp --disable-{bzip2,snappy,lzo} --disable-usb-redir --disable-libusb
--disable-libnfs --disable-tcg-interpreter --disable-debug-tcg --disable-libiscsi
--disable-rbd --disable-spice --disable-attr --disable-cap-ng --disable-linux-aio
--disable-brlapi --disable-vnc-{jpeg,png,sasl} --disable-rdma --disable-bluez
--disable-fdt --disable-curl --disable-curses --disable-sdl --disable-gtk
--disable-tpm --disable-vte --disable-vnc --disable-xen --disable-opengl
--disable-slirp --enable-trace-backend=nop --enable-virtfs --enable-attr
--enable-cap-ng --target-list=x86_64-softmmu

[gorozco1]

Closed because this is a duplicate of #25

[grahamwhaley]

Hi @gorozco1 /cc @sameo @jodh-intel @egernst @mcastelino @anthonyzxu
Need to check if we accidentally combined two closely related but different Issues here, and then closed the combined one and thus missed an item.....
This ticket talks about moving to qemu 2.9, and the other Issue talks about moving from pc-lite to pc machine model. Looks like we did the latter (moved to pc model), but may have missed this one (moving to qemu v2.9.0 from https://github.com/clearcontainers/qemu).
Can we confirm/clarify where we are at, and then probably re-open this Issue if necessary to get the transition to v2.9 on the list...
thx

[gorozco1]

@grahamwhaley yes you are right.

We move from pc-lite to pc (clearcontainers/runtime#391) with the old qemu-lite https://github.com/01org/qemu-lite/tree/qemu-2.7-lite .

The one build from https://github.com/clearcontainers/qemu is still pending in this PR #34 as we found issues with it.

[grahamwhaley]

Thanks. @egernst also pointed out we have clearcontainers/runtime#407 open to track the transition - so, we don't need to re-open this one, and @egernst and/or myself will add some more details of what and why to the runtime Issue.

[gorozco1]

being said that I am going to reopen this issue so #34 solves this.

[gorozco1]

@grahamwhaley we still need an issue here to track the packaging that's why I reopen this.

[grahamwhaley]

np. thx

[rarindam]

Why are both --disable-cap-ng and --enable-cap-ng are being used?
Should we keep this enabled or disabled?

[jodh-intel]

We should really be moving to the configure script (#46) as although we don't hard-code all those configuration options in setup_env_ubuntu.sh, we do specify them in two different files. By using the script, we can document each option clearly and have a central source for such config options.