[Qemu-devel] make vm-test [was: [PATCH] maintainers: Add myself as a OpenBSD maintainer]

[Eric Blake]

On 02/16/2018 11:44 AM, Philippe Mathieu-Daudé wrote:
> On 02/16/2018 02:41 PM, Kamil Rytarowski wrote:
> > On 16.02.2018 18:30, Philippe Mathieu-Daudé wrote:
> > > But before announcing the host OS being supported again, I'd rather see
> > > reproducible build/tests logs, in a (public - if possible) continuous
> > > integration system. Else it is hard to notice when it get broken.
> >
> > This is already done for FreeBSD, NetBSD and OpenBSD.
>
> We have the ability to run those, but afaik no CI are using them.
>
> $ make vm-test
> vm-test: Test QEMU in preconfigured virtual machines
>
>    vm-build-ubuntu.i386            - Build QEMU in ubuntu i386 VM
>    vm-build-freebsd                - Build QEMU in FreeBSD VM
>    vm-build-netbsd                 - Build QEMU in NetBSD VM
>    vm-build-openbsd                - Build QEMU in OpenBSD VM
>
> > CC: Fam who can confirm this.

Thanks for this; today was my first day trying the various vm-build- 
targets.

Question: is this expected behavior?

$ make vm-build-ubuntu.i386
    VM-IMAGE ubuntu.i386
...
Image resized.
debconf: unable to initialize frontend: Dialog
debconf: (TERM is not set, so the dialog frontend is not usable.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (This frontend requires a controlling tty.)
debconf: falling back to frontend: Teletype
dpkg-preconfigure: unable to re-open stdin:
Connection to 127.0.0.1 closed by remote host.
...
Cloning into 
'/home/eblake/qemu/vm-test-VoVkBv.tmp/data-5ba3c.tar.vroot/ui/keycodemapdb'...
sudo: unable to resolve host ubuntu-guest
make[1]: flex: Command not found
...
make[1]: flex: Command not found
Could not access KVM kernel module: No such file or directory
qemu-system-i386: failed to initialize KVM: No such file or directory
qemu-system-i386: Back to tcg accelerator

I'm wondering if the image initialized incorrectly, and as a result 
can't do as much as it's supposed to do, or runs way slower than it 
needs to?  The command eventually completed with status 0, but failed to 
find a 32-bit compile error in the rdma code, and the output log does 
not look like it actually attempted to compile anything in qemu (unless 
it did compile it, but the logs were not output to stdout/stderr).

make vm-build-freebsd was a lot faster at completing for me (but shows 
that we still have a lot of clang warnings about address of a packed 
struct member).

--
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3266
Virtualization:  qemu.org | libvirt.org