All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Xen-devel List <xen-devel@lists.xen.org>
Subject: Re: Xen-4.5-rc1 test day results from XenServer
Date: Thu, 30 Oct 2014 10:52:26 +0000	[thread overview]
Message-ID: <5452186A.2030306@citrix.com> (raw)
In-Reply-To: <54513BF1.3010004@citrix.com>

On 29/10/14 19:11, Andrew Cooper wrote:
> Hi,
>
> Within XenServer, I have an experimental branch running on top of
> Xen-4.5 which is currently being tested by our basic verification tests.
>
> It is a CentOS 6.5-based dom0, with Xapi as a toolstack and
> qemu-traditional for device model.  It is based on staging, which is a
> good enough approximation to -rc1 for testing purposes.
>
> The following bugs are present in -rc1, but have fixes already present
> in staging.
>
> * Specifying a LIBXL_API_VERSION causes a build failure in libxl_uuid.h 
> (fixed by c/s 67d95d0)
> * Migrating windows VMs from older versions of Xen fails (fixed by c/s
> 66d0c0a)
>
> The following bugs are present in -rc1 and are not fixed in current
> staging.  Patches fixing each of these are on xen-devel.
>
> * pygrub can't parse grub1 config files
> (1414425614-43267-1-git-send-email-simon.rowe@eu.citrix.com)
> * TOCTOU race in pygrub
> (1414591781-19376-1-git-send-email-andrew.cooper3@citrix.com)

In addition,  (This was discovered against 4.4, but its also affected
4.5 testing)

* libxl reports invalid value for shutdown_code during domain shutdown
(1413985962-31909-1-git-send-email-dave.scott@citrix.com)

~Andrew

  reply	other threads:[~2014-10-30 10:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-29 19:11 Xen-4.5-rc1 test day results from XenServer Andrew Cooper
2014-10-30 10:52 ` Andrew Cooper [this message]
2014-10-30 17:59   ` Konrad Rzeszutek Wilk

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=5452186A.2030306@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=xen-devel@lists.xen.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.