Closed devimc closed 6 years ago
@sameo @bergwolf @gnawux @laijs please take a look
/cc @sameo @bergwolf @gnawux @laijs
LGTM
@bergwolf Could you please review?
@bergwolf yout have to patch the configure
@bergwolf you have to patch the configure
file
https://github.com/kata-containers/qemu/pull/1/files#diff-e2d5a00791bce9a01f99bc6fd613a39d
@devimc - can you clarify why the patching is needed for configure, compared to just using a set of "supported" flags? I have been able to build successfully when not patching by updating the flag set.
@bergwolf @egernst PR updated
@devimc please drop the commit configure: don't fail in case of unknown option
. configure
script SHOULD fail on unknown options.
@bergwolf what do you propose to have a script compatible between qemu versions? or should we have different script for each version ?
@devimc I see the PR is raised against stable-2.7
branch. Is there particular reason to pick the specific qemu version? Or is it just a random stable version?
@bergwolf stable version, and works with CRIO
@bergwolf changes applied, thanks
@bergwolf fixed, thanks
lgtm.
But I do wonder if we should call it just configure-qemu.sh
(or similar) and have the script check the value of arch(1)
to add arch-specific flags (like "--target-list=x86_64-softmmu
").
@jodh-intel good point, @bergwolf what do you think?, configure options are the same for other architectures ? or should we have a script for each architecture?
@devimc I agree with @jodh-intel. You can define a arch
variable in the script and make it work with different architectures.
@bergwolf @jodh-intel changes applied, thanks
lgtm
@jodh-intel @bergwolf fixed
lgtm
lgtm
thanks @devimc
this script enables a little set of qemu features needed to run virtual containers
Signed-off-by: Julio Montes julio.montes@intel.com