qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>, qemu-devel@nongnu.org
Cc: "Fam Zheng" <fam@euphon.net>, "Ed Maste" <emaste@freebsd.org>,
	"Eduardo Habkost" <ehabkost@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>,
	"Kamil Rytarowski" <kamil@netbsd.org>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	"Li-Wen Hsu" <lwhsu@freebsd.org>,
	"Brad Smith" <brad@comstyle.com>
Subject: Re: [Qemu-devel] [PATCH 00/13] tests/vm: serial console autoinstall, misc fixes.
Date: Thu, 9 May 2019 13:53:33 +0200	[thread overview]
Message-ID: <38ea2334-b819-a439-7a43-92b52263b402@redhat.com> (raw)
In-Reply-To: <20190508085645.11595-1-kraxel@redhat.com>

On 08/05/2019 10.56, Gerd Hoffmann wrote:
> This patch series changes the way virtual machines for test builds are
> managed.  They are created locally on the developer machine now.  The
> installer is booted on the serial console and the scripts walks through
> the dialogs to install and configure the guest.
> 
> That takes the download.patchew.org server out of the loop and makes it
> alot easier to tweak the guest images (adding build dependencies for
> example).
> 
> The install scripts take care to apply host proxy settings (from *_proxy
> environment variables) to the guest, so any package downloads will be
> routed through the proxy and can be cached that way.  This also makes
> them work behind strict firewalls.
> 
> There are also a bunch of smaller tweaks for tests/vm to fix issues I
> was struggling with.  See commit messages of individual patches for
> details.
> 
> Known issue:  NetBSD package install is not working for me right now.
> It did work a while ago.  Not sure what is going on here.

I now gave your series another try and replaced patch 3 with the python3
fix from Eduardo locally here. FreeBSD works great. OpenBSD is fine too,
except for the known issue that the "gmake check" does not work - but
this issue has been there before already. NetBSD also does not work for
me, so I guess you should hold off that patch for now?

So for patches 1, 2 and 4 - 10 (I did not check the Linux images yet):

Tested-by: Thomas Huth <thuth@redhat.com>

> Do we have accelerator support for the BSDs?  A "make check" for a full
> build takes ages, and I suspect tcg being used is part of the problem.
> I did my tests using "TARGET_LIST=x86_64-softmmu" because of that.

I think they should be running with "--enable-kvm". Did you make sure
that you've enabled multiple CPUs with J=8 for example? ... but for me,
the compilation is also quite a bit slower, indeed. I think part of the
problem might be clang which is compiling a little bit slower than GCC
as far as I know...?

 Thomas


  parent reply	other threads:[~2019-05-09 11:54 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-08  8:56 [Qemu-devel] [PATCH 00/13] tests/vm: serial console autoinstall, misc fixes Gerd Hoffmann
2019-05-08  8:56 ` [Qemu-devel] [PATCH 01/13] scripts: use git archive in archive-source Gerd Hoffmann
2019-05-08  8:56 ` [Qemu-devel] [PATCH 02/13] tests/vm: send proxy environment variables over ssh Gerd Hoffmann
2019-05-08  8:56 ` [Qemu-devel] [PATCH 03/13] tests/vm: send locale " Gerd Hoffmann
2019-05-09  7:35   ` Thomas Huth
2019-05-09  8:18     ` Gerd Hoffmann
2019-05-08  8:56 ` [Qemu-devel] [PATCH 04/13] tests/vm: use ssh with pty unconditionally Gerd Hoffmann
2019-05-08  8:56 ` [Qemu-devel] [PATCH 05/13] tests/vm: run test builds on snapshot Gerd Hoffmann
2019-05-08  8:56 ` [Qemu-devel] [PATCH 06/13] tests/vm: add vm-boot-{ssh, serial}-<guest> targets Gerd Hoffmann
2019-05-08  8:56 ` [Qemu-devel] [PATCH 07/13] tests/vm: add DEBUG=1 to help text Gerd Hoffmann
2019-05-08  8:56 ` [Qemu-devel] [PATCH 08/13] tests/vm: serial console support helpers Gerd Hoffmann
2019-05-08  8:56 ` [Qemu-devel] [PATCH 09/13] tests/vm: openbsd autoinstall, using serial console Gerd Hoffmann
2019-05-08  8:56 ` [Qemu-devel] [PATCH 10/13] tests/vm: freebsd " Gerd Hoffmann
2019-05-08  8:56 ` [Qemu-devel] [PATCH 11/13] tests/vm: netbsd " Gerd Hoffmann
2019-05-08 19:30   ` Kamil Rytarowski
2019-05-09  6:47     ` Gerd Hoffmann
2019-05-09 16:39       ` Richard Henderson
2019-05-09 19:07         ` Kamil Rytarowski
2019-05-09 17:01       ` Kamil Rytarowski
2019-05-08  8:56 ` [Qemu-devel] [PATCH 12/13] tests/vm: fedora " Gerd Hoffmann
2019-05-09 12:00   ` Thomas Huth
2019-05-09 13:10     ` Gerd Hoffmann
2019-05-09 13:23       ` Daniel P. Berrangé
2019-05-08  8:56 ` [Qemu-devel] [PATCH 13/13] tests/vm: ubuntu.i386: apt proxy setup Gerd Hoffmann
2019-05-09 12:12   ` Philippe Mathieu-Daudé
2019-05-09 13:17     ` Gerd Hoffmann
2019-05-09 11:53 ` Thomas Huth [this message]
2019-05-09 12:04   ` [Qemu-devel] [PATCH 00/13] tests/vm: serial console autoinstall, misc fixes Philippe Mathieu-Daudé
2019-05-09 12:35     ` Thomas Huth
2019-05-09 13:50   ` Gerd Hoffmann
2019-05-09 13:57     ` Thomas Huth
2019-05-09 19:11       ` Kamil Rytarowski
2019-05-09 18:52 ` Kamil Rytarowski
2019-05-10  4:23   ` Gerd Hoffmann

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=38ea2334-b819-a439-7a43-92b52263b402@redhat.com \
    --to=thuth@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=brad@comstyle.com \
    --cc=ehabkost@redhat.com \
    --cc=emaste@freebsd.org \
    --cc=fam@euphon.net \
    --cc=kamil@netbsd.org \
    --cc=kraxel@redhat.com \
    --cc=lwhsu@freebsd.org \
    --cc=philmd@redhat.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).