From: Lars Kurth <lars.kurth.xen@gmail.com>
To: Rich Persaud <persaur@gmail.com>
Cc: Juergen Gross <jgross@suse.com>,
xen-devel <xen-devel@lists.xenproject.org>,
Committers <committers@xenproject.org>,
Ian Jackson <ian.jackson@eu.citrix.com>
Subject: Re: Guest Testing in OSSTEST - What distros and versions should we test against
Date: Fri, 24 May 2019 15:26:47 -0600 [thread overview]
Message-ID: <3E953F72-A7B5-40B6-9974-FD1B99788439@gmail.com> (raw)
In-Reply-To: <E687A54C-0781-4674-A7F9-F62064E9B310@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1120 bytes --]
> On 9 May 2019, at 19:43, Rich Persaud <persaur@gmail.com> wrote:
>
> On May 9, 2019, at 21:28, Lars Kurth <lars.kurth.xen@gmail.com <mailto:lars.kurth.xen@gmail.com>> wrote:
>
>> 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.
>
> Are the 90-day test/eval versions of Windows incompatible with OSSTEST?
>
> https://www.microsoft.com/en-us/evalcenter/evaluate-windows-10-enterprise <https://www.microsoft.com/en-us/evalcenter/evaluate-windows-10-enterprise>
> https://www.microsoft.com/en-us/evalcenter/ <https://www.microsoft.com/en-us/evalcenter/>
>
Actually, that's a possibility. Our use may not be compatible with the T&D's of the eval license though. It wasn't when we checked last time. But that can be checked.
Lars
[-- Attachment #1.2: Type: text/html, Size: 2167 bytes --]
[-- Attachment #2: Type: text/plain, Size: 157 bytes --]
_______________________________________________
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: Rich Persaud <persaur@gmail.com>
Cc: Juergen Gross <jgross@suse.com>,
xen-devel <xen-devel@lists.xenproject.org>,
Committers <committers@xenproject.org>,
Ian Jackson <ian.jackson@eu.citrix.com>
Subject: Re: [Xen-devel] Guest Testing in OSSTEST - What distros and versions should we test against
Date: Fri, 24 May 2019 15:26:47 -0600 [thread overview]
Message-ID: <3E953F72-A7B5-40B6-9974-FD1B99788439@gmail.com> (raw)
Message-ID: <20190524212647.1ws-L_s9VXDF1zDZZv2r5AUSI5LFKRN3MVDqKV_Rj3M@z> (raw)
In-Reply-To: <E687A54C-0781-4674-A7F9-F62064E9B310@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1120 bytes --]
> On 9 May 2019, at 19:43, Rich Persaud <persaur@gmail.com> wrote:
>
> On May 9, 2019, at 21:28, Lars Kurth <lars.kurth.xen@gmail.com <mailto:lars.kurth.xen@gmail.com>> wrote:
>
>> 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.
>
> Are the 90-day test/eval versions of Windows incompatible with OSSTEST?
>
> https://www.microsoft.com/en-us/evalcenter/evaluate-windows-10-enterprise <https://www.microsoft.com/en-us/evalcenter/evaluate-windows-10-enterprise>
> https://www.microsoft.com/en-us/evalcenter/ <https://www.microsoft.com/en-us/evalcenter/>
>
Actually, that's a possibility. Our use may not be compatible with the T&D's of the eval license though. It wasn't when we checked last time. But that can be checked.
Lars
[-- Attachment #1.2: Type: text/html, Size: 2167 bytes --]
[-- Attachment #2: Type: text/plain, Size: 157 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-05-24 21:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-10 1:28 Guest Testing in OSSTEST - What distros and versions should we test against Lars Kurth
2019-05-10 1:28 ` [Xen-devel] " 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 [this message]
2019-05-24 21:26 ` 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=3E953F72-A7B5-40B6-9974-FD1B99788439@gmail.com \
--to=lars.kurth.xen@gmail.com \
--cc=committers@xenproject.org \
--cc=ian.jackson@eu.citrix.com \
--cc=jgross@suse.com \
--cc=persaur@gmail.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.