From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Fam Zheng <famz@redhat.com>
Cc: qemu-devel@nongnu.org, "Brad Smith" <brad@comstyle.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [Qemu-devel] [PATCH] tests: vm: auto_install OpenBSD
Date: Fri, 24 Aug 2018 10:06:32 +0100 [thread overview]
Message-ID: <20180824090632.GB3430@redhat.com> (raw)
In-Reply-To: <20180824085220.GF31581@lemon.usersys.redhat.com>
On Fri, Aug 24, 2018 at 04:52:20PM +0800, Fam Zheng wrote:
> On Fri, 08/24 09:22, Daniel P. Berrangé wrote:
> > On Fri, Aug 24, 2018 at 09:21:26AM +0800, Fam Zheng wrote:
> > > Upgrade OpenBSD to 6.3 using auto_install. Especially, drop SDL1,
> > > include SDL2.
> > >
> > > One limitation of this patch is that we need a temporary HTTP server on
> > > host 80 port for auto_install, because slirp cannot do guest forward on
> > > "host addr".
> >
> > That's a pretty big limitation, as port 80 requires root privileges,
> > and that's a pretty strict no for automated testing IMHO.
> >
> > Why does it have to be port 80 in particular - is it not possible
> > to use 8080 or even better, detect a random free port ?
>
> OpenBSD autoinstall[1] is hardcoded to fetch from port 80. Maybe we can instead
> persuade it into fetching from a different http server than 10.0.2.2. To do that
> we'd need to implement a new slirp option for either "option tftp-server-name"
> or "next-server" according to the manpage. I'll have to experiment with it to
> see if it will work.
>
> Or, do you think there are better options to configure the VM network to serve
> the file?
Why not use guestfwd eg
guestfwd:tcp:10.0.2.1:80-tcp:127.0.0.1:8080
would redirect the guest IP address port 80, to the loopback interface on the
host port 8080. Now you can tell autoinstall to use 10.0.2.1 ?
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2018-08-24 9:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-24 1:21 [Qemu-devel] [PATCH] tests: vm: auto_install OpenBSD Fam Zheng
2018-08-24 8:22 ` Daniel P. Berrangé
2018-08-24 8:52 ` Fam Zheng
2018-08-24 9:06 ` Peter Maydell
2018-08-24 9:47 ` Fam Zheng
2018-08-24 9:06 ` Daniel P. Berrangé [this message]
2018-08-24 14:36 ` Brad Smith
2018-08-24 14:43 ` Daniel P. Berrangé
2018-08-24 14:46 ` Peter Maydell
2018-08-24 14:48 ` Daniel P. Berrangé
2018-08-24 14:53 ` Peter Maydell
2018-08-24 22:13 ` Brad Smith
2018-08-27 9:05 ` Gerd Hoffmann
2018-09-05 12:54 ` Brad Smith
2018-09-05 14:24 ` Gerd Hoffmann
2018-09-05 14:43 ` Fam Zheng
2018-08-27 9:18 ` Fam Zheng
2018-08-27 13:48 ` Brad Smith
2018-09-05 12:56 ` Brad Smith
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=20180824090632.GB3430@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=brad@comstyle.com \
--cc=f4bug@amsat.org \
--cc=famz@redhat.com \
--cc=peter.maydell@linaro.org \
--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).