From: Julien Grall <julien.grall@arm.com>
To: Lars Kurth <lars.kurth@citrix.com>,
Andrii Anisov <andrii_anisov@epam.com>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: Xen 4.9 rc4
Date: Fri, 12 May 2017 16:12:32 +0100 [thread overview]
Message-ID: <c8fd24b0-a727-a8c5-4f50-9a57fc0d93eb@arm.com> (raw)
In-Reply-To: <D53B85DF.37075%lars.kurth@citrix.com>
Hello,
On 12/05/17 15:33, Lars Kurth wrote:
> Removing the announce and user list.
>
>> Could you please clarify if this [1] is still relevant?
> Yes
>
> I will let Julien answer the rest: the main goal is really to ensure that
> Xen 4.9 works with the HW you care about.
>
> Lars
>
> On 12/05/2017 15:29, "Andrii Anisov" <andrii_anisov@epam.com> wrote:
>
>> Dear Julien,
>>
>>
>> On 08.05.17 21:41, Julien Grall wrote:
>>> As a reminder, there will be another Xen Test Day tomorrow (Tuesday 9th
>>> May),
>>> for the instructions see:
>>>
>>>
>>> https://blog.xenproject.org/2017/04/13/announcing-xen-project-4-9-rc-and-
>>> test-day-schedule/
>>>
>>> Cheers,
>>
>> I'm asked to perform a XEN 4.9.0-rcX testing on Renesas R-Car Gen3 board
>> (Salvator-X, H3).
>>
>> Could you please clarify if this [1] is still relevant?
>> And if the smoke test described here [2] is enough for RC testing?
The smoke test will create VMs and check if it boots. Feel free to test
more if you have time (e.g device passthrough, network traffic...).
Let us know the results :).
Cheers,
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-05-12 15:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-08 18:41 Xen 4.9 rc4 Julien Grall
2017-05-12 14:29 ` Andrii Anisov
2017-05-12 14:33 ` Lars Kurth
2017-05-12 15:12 ` Julien Grall [this message]
2017-05-15 23:45 ` Goel, Sameer
2017-05-16 8:08 ` Julien Grall
2017-05-16 10:46 ` Andrii Anisov
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=c8fd24b0-a727-a8c5-4f50-9a57fc0d93eb@arm.com \
--to=julien.grall@arm.com \
--cc=andrii_anisov@epam.com \
--cc=lars.kurth@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 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).