All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Christoph Badura <bad@bsd.de>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Ian Campbell <ian.campbell@citrix.com>
Subject: Re: netbsd in Xen testing environment
Date: Tue, 13 Oct 2015 13:02:06 +0200	[thread overview]
Message-ID: <561CE4AE.9080805@citrix.com> (raw)
In-Reply-To: <20150805160917.GW559@irregular-apocalypse.k.bsd.de>

Hello,

Sorry for the delay. Ccing Ian Jackson and Ian Campbell, which are the
maintainers of OSSTest (our in-house Xen CI loop tool).

El 05/08/15 a les 18.09, Christoph Badura ha escrit:
> Hi Roger,
> 
> we talk during FOSDEM about setting up NetBSD in your testing environment.
> We agreed to get in touch again after you guys finshed the move to the
> public enviroment and after my projects have become less hectic.
> 
> Are you guys still interested?

AFAIK the move to the new colo is finished, so I guess it's a right time
to start looking into this. The first step would probably be to add a
NetBSD 32 and 64bit PV DomUs, and then we can look into also adding a
NetBSD Dom0 (host).

Some time ago I've added support for a FreeBSD 32/64bit HVM DomU, not
sure if that's very helpful since it's HVM and not PV, but it might be a
good starting point. In any case, OSSTest code can be fetched from:

http://xenbits.xen.org/gitweb/?p=osstest.git;a=summary

Take a look at the ts-freebsd-install script in order to see how DomUs
are set up.

Roger.

       reply	other threads:[~2015-10-13 11:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20150805160917.GW559@irregular-apocalypse.k.bsd.de>
2015-10-13 11:02 ` Roger Pau Monné [this message]
2015-10-27 14:47   ` netbsd in Xen testing environment Christoph Badura

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=561CE4AE.9080805@citrix.com \
    --to=roger.pau@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=bad@bsd.de \
    --cc=ian.campbell@citrix.com \
    --cc=xen-devel@lists.xenproject.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 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.