All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lars Kurth <lars.kurth.xen@gmail.com>
To: xen-devel <xen-devel@lists.xenproject.org>
Cc: Juergen Gross <jgross@suse.com>,
	Committers <committers@xenproject.org>,
	Ian Jackson <ian.jackson@eu.citrix.com>
Subject: Guest Testing in OSSTEST - What distros and versions should we test against
Date: Thu, 9 May 2019 19:28:47 -0600	[thread overview]
Message-ID: <9FCB2022-A547-4FA2-88E7-91DA3C023438@gmail.com> (raw)

Hi all,

following a discussion with committers about Guest testing in OSSTEST, it surfaced that we have not updated what distros we test in OSSTEST for a very long time. All agreed that we should regularly review what we test against: maybe at the beginning of a release cycle

In any case, currently we test against

x86 HVM guests:
  debian-9.4.0-{i386,amd64}-CD-1.iso
  rhel-server-6.1-i386-dvd.iso
  win10v1703-x86.iso
  win7-x64.iso
  ws16-x64.iso
  FreeBSD-10.1-CUSTOM-{i386,amd64}-20150525.raw.xz
  Debian HVM {i386,amd64} via debian-installer netinst [1]

x86 PV guests:
  Debian PV {i386,amd64} via debian-installer netinst [1]

ARM guests:
  Debian PV via debian-installer netinst [1]

[1] whatever Debian release osstest itself mostly runs

So I am opening the floor to suggestions.

With regards to Windows testing we have some restrictions. We have tried several times to buy additional test licenses, but this never went anywhere (some of the VM licenses are not available for our environment, unless you bulk buy, which is very expensive). The only approach that would allow us to test against different windows versions would be to require everyone who may touch OSSTEST which is not doable.

I can bring this up with the MS open source office, if there are strong feelings about this and try again

Lars

  
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

WARNING: multiple messages have this Message-ID (diff)
From: Lars Kurth <lars.kurth.xen@gmail.com>
To: xen-devel <xen-devel@lists.xenproject.org>
Cc: Juergen Gross <jgross@suse.com>,
	Committers <committers@xenproject.org>,
	Ian Jackson <ian.jackson@eu.citrix.com>
Subject: [Xen-devel] Guest Testing in OSSTEST - What distros and versions should we test against
Date: Thu, 9 May 2019 19:28:47 -0600	[thread overview]
Message-ID: <9FCB2022-A547-4FA2-88E7-91DA3C023438@gmail.com> (raw)
Message-ID: <20190510012847.dm5b1BP8MyjpPltCmNE5XeTs9iyF9ry2Bo4nJfbbQ-A@z> (raw)

Hi all,

following a discussion with committers about Guest testing in OSSTEST, it surfaced that we have not updated what distros we test in OSSTEST for a very long time. All agreed that we should regularly review what we test against: maybe at the beginning of a release cycle

In any case, currently we test against

x86 HVM guests:
  debian-9.4.0-{i386,amd64}-CD-1.iso
  rhel-server-6.1-i386-dvd.iso
  win10v1703-x86.iso
  win7-x64.iso
  ws16-x64.iso
  FreeBSD-10.1-CUSTOM-{i386,amd64}-20150525.raw.xz
  Debian HVM {i386,amd64} via debian-installer netinst [1]

x86 PV guests:
  Debian PV {i386,amd64} via debian-installer netinst [1]

ARM guests:
  Debian PV via debian-installer netinst [1]

[1] whatever Debian release osstest itself mostly runs

So I am opening the floor to suggestions.

With regards to Windows testing we have some restrictions. We have tried several times to buy additional test licenses, but this never went anywhere (some of the VM licenses are not available for our environment, unless you bulk buy, which is very expensive). The only approach that would allow us to test against different windows versions would be to require everyone who may touch OSSTEST which is not doable.

I can bring this up with the MS open source office, if there are strong feelings about this and try again

Lars

  
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

             reply	other threads:[~2019-05-10  1:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-10  1:28 Lars Kurth [this message]
2019-05-10  1:28 ` [Xen-devel] Guest Testing in OSSTEST - What distros and versions should we test against Lars Kurth
2019-05-10  1:43 ` Rich Persaud
2019-05-10  1:43   ` [Xen-devel] " Rich Persaud
2019-05-24 21:26   ` Lars Kurth
2019-05-24 21:26     ` [Xen-devel] " Lars Kurth
2019-05-10  7:48 ` Jan Beulich
2019-05-10  7:48   ` [Xen-devel] " Jan Beulich
2019-05-10 12:41   ` Lars Kurth
2019-05-10 12:41     ` [Xen-devel] " Lars Kurth
2019-05-27 11:56   ` Roger Pau Monné
2019-05-27 11:56     ` [Xen-devel] " Roger Pau Monné
2019-05-24 21:57 ` Lars Kurth
2019-05-24 21:57   ` [Xen-devel] " Lars Kurth

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=9FCB2022-A547-4FA2-88E7-91DA3C023438@gmail.com \
    --to=lars.kurth.xen@gmail.com \
    --cc=committers@xenproject.org \
    --cc=ian.jackson@eu.citrix.com \
    --cc=jgross@suse.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.