From: Eric Blake <eblake@redhat.com>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Kamil Rytarowski" <n54@gmx.com>,
"Brad Smith" <brad@comstyle.com>,
qemu-devel@nongnu.org, "Fam Zheng" <famz@redhat.com>
Subject: [Qemu-devel] make vm-test [was: [PATCH] maintainers: Add myself as a OpenBSD maintainer]
Date: Mon, 19 Mar 2018 17:06:37 -0500 [thread overview]
Message-ID: <128f62e5-9184-57e5-88c1-d5cc4bf27d4f@redhat.com> (raw)
In-Reply-To: <e625c026-2fa4-f3ea-d85e-080c65a4885f@amsat.org>
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
next prev parent reply other threads:[~2018-03-19 22:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-16 16:46 [Qemu-devel] [PATCH] maintainers: Add myself as a OpenBSD maintainer Brad Smith
2018-02-16 17:12 ` Kamil Rytarowski
2018-02-16 17:30 ` Philippe Mathieu-Daudé
2018-02-16 17:37 ` Peter Maydell
2018-02-16 17:44 ` Daniel P. Berrangé
2018-02-16 17:41 ` Kamil Rytarowski
2018-02-16 17:44 ` Philippe Mathieu-Daudé
2018-02-23 8:33 ` Fam Zheng
2018-03-19 22:06 ` Eric Blake [this message]
2018-03-21 8:11 ` [Qemu-devel] make vm-test [was: [PATCH] maintainers: Add myself as a OpenBSD maintainer] Fam Zheng
2018-03-21 13:14 ` Eric Blake
2018-03-21 14:07 ` Fam Zheng
2018-02-23 14:41 ` [Qemu-devel] [PATCH] maintainers: Add myself as a OpenBSD maintainer Peter Maydell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=128f62e5-9184-57e5-88c1-d5cc4bf27d4f@redhat.com \
--to=eblake@redhat.com \
--cc=brad@comstyle.com \
--cc=f4bug@amsat.org \
--cc=famz@redhat.com \
--cc=n54@gmx.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).