From: Fam Zheng <famz@redhat.com>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: qemu-devel@nongnu.org, berrange@redhat.com,
"Alex Bennée" <alex.bennee@linaro.org>,
"Peter Maydell" <peter.maydell@linaro.org>,
stefanha@redhat.com, "Cleber Rosa" <crosa@redhat.com>,
pbonzini@redhat.com, eblake@redhat.com,
"Kamil Rytarowski" <kamil@netbsd.org>
Subject: Re: [Qemu-devel] [PATCH v11 07/13] tests: Add FreeBSD image
Date: Fri, 22 Sep 2017 14:45:33 +0800 [thread overview]
Message-ID: <20170922064533.GH1397@lemon.lan> (raw)
In-Reply-To: <49d5d158-9103-d14d-8ce6-35196754aafb@amsat.org>
On Fri, 09/22 03:09, Philippe Mathieu-Daudé wrote:
> On 09/21/2017 12:07 PM, Fam Zheng wrote:
> > The image is prepared following instructions as in:
> >
> > https://wiki.qemu.org/Hosts/BSD
> >
> > Signed-off-by: Fam Zheng <famz@redhat.com>
>
> $ QEMU=`pwd`/x86_64-softmmu/qemu-system-x86_64 make vm-build-freebsd V=1
> [...]
> CC tests/test-io-channel-socket.o
> CC tests/io-channel-helpers.o
> LINK tests/test-io-channel-socket
>
> the build hang here, stopping to use the cpu, keeping 2GB of resident
> physical memory until I hit ^C ... not enough ram for the guest? guest tmpfs
> full?
For how long? The four images doing "J=8" takes 1~2 hours here usually. This
worked for me on at least two machines (one laptop and one server). :-/
>
> useful enough for:
> Tested-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
Fam
next prev parent reply other threads:[~2017-09-22 6:45 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-21 15:07 [Qemu-devel] [PATCH v11 00/13] tests: Add VM based build tests (for non-x86_64 and/or non-Linux) Fam Zheng
2017-09-21 15:07 ` [Qemu-devel] [PATCH v11 01/13] gitignore: Ignore vm test images Fam Zheng
2017-09-21 15:23 ` Eric Blake
2017-09-22 2:43 ` Fam Zheng
2017-09-21 15:07 ` [Qemu-devel] [PATCH v11 02/13] qemu.py: Add "wait()" method Fam Zheng
2017-09-21 15:07 ` [Qemu-devel] [PATCH v11 03/13] scripts: Add archive-source.sh Fam Zheng
2017-09-21 15:22 ` Eric Blake
2017-09-22 2:42 ` Fam Zheng
2017-09-21 15:07 ` [Qemu-devel] [PATCH v11 04/13] tests: Add a test key pair Fam Zheng
2017-09-21 15:07 ` [Qemu-devel] [PATCH v11 05/13] tests: Add vm test lib Fam Zheng
2017-09-21 15:07 ` [Qemu-devel] [PATCH v11 06/13] tests: Add ubuntu.i386 image Fam Zheng
2017-09-21 15:07 ` [Qemu-devel] [PATCH v11 07/13] tests: Add FreeBSD image Fam Zheng
2017-09-22 3:17 ` Philippe Mathieu-Daudé
2017-09-22 5:31 ` Fam Zheng
2017-09-22 6:09 ` Philippe Mathieu-Daudé
2017-09-22 6:45 ` Fam Zheng [this message]
2017-09-21 15:07 ` [Qemu-devel] [PATCH v11 08/13] tests: Add NetBSD image Fam Zheng
2017-09-21 15:07 ` [Qemu-devel] [PATCH v11 09/13] tests: Add OpenBSD image Fam Zheng
2017-09-22 12:21 ` Philippe Mathieu-Daudé
2017-09-21 15:07 ` [Qemu-devel] [PATCH v11 10/13] Makefile: Add rules to run vm tests Fam Zheng
2017-09-21 15:07 ` [Qemu-devel] [PATCH v11 11/13] MAINTAINERS: Add tests/vm entry Fam Zheng
2017-09-21 15:07 ` [Qemu-devel] [PATCH v11 12/13] tests: Add README for vm tests Fam Zheng
2017-09-21 15:07 ` [Qemu-devel] [PATCH v11 13/13] docker: Use archive-source.py Fam Zheng
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=20170922064533.GH1397@lemon.lan \
--to=famz@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=crosa@redhat.com \
--cc=eblake@redhat.com \
--cc=f4bug@amsat.org \
--cc=kamil@netbsd.org \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.