xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@citrix.com>
To: Teck Choon Giam <giamteckchoon@gmail.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Lin Ming <mlin@ss.pku.edu.cn>
Subject: Re: Upgrade from xen-4.1-testing to xen-unstable report
Date: Thu, 12 Apr 2012 07:08:59 +0000	[thread overview]
Message-ID: <1334214539.12209.219.camel@dagon.hellion.org.uk> (raw)
In-Reply-To: <CAEwRVpM20XwC54SoyM44Ya=_MS_uNkLLnwOTT0rOoxhBX+yvbA@mail.gmail.com>

On Wed, 2012-04-11 at 22:23 +0100, Teck Choon Giam wrote:
> Hi,
> 
> This is just my experience about issues I encountered when upgrade
> from xen-4.1-testing changeset 23277:80130491806f to xen-unstable
> changeset 25191:a95fc7decc83.
> 
> 1. Immediately after upgrade, xl list show such error:
> 
> # xl list
> libxl: error: libxl.c:506:libxl_list_domain: geting domain info list:
> Permission denied
> libxl_domain_infolist failed.
> 
> After a reboot, it is fine.  Any idea why such behaviour?  Imagine if
> there are running domUs... this might cause issues to shutdown?  I
> will downgrade and repeat such test to confirm.  Might be worth a note
> in upgrading note about this if this is intended?

The tools and the hypervisor are a matched pair so you would need to
reboot the system in order to use the new tools. This has always been
the case with Xen upgrades.

> 2. localtime setting not working.  Set to localtime=1 doesn't seems to
> work whereby setting rtc_timeoffset works.  Any idea?

I've CC'd Lin Ming who implemented both of those.

> 3. xl trigger hvmdomain power still never remove those related
> iptables forward rules.  This is the same problem when I test in
> xen-4.1-testing.  Refer to
> http://lists.xen.org/archives/html/xen-devel/2012-02/msg00771.html
> about past report.  When test in xen-4.1-testing, one funny behaviour
> is if I start hvmdomain using xm then use xl trigger hvmdomain power
> does remove those iptables related rule chain.

I think this is an issue with the hotplug scripts not being run at the
right time. There are some improvements to this in the pipeline which I
hope will help here.

> I shall do more testing when time permit and sorry if this report is
> useless to anyone.

On the contrary it is always useful to hear about these things, thank
you.

Ian.

  reply	other threads:[~2012-04-12  7:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-11 21:23 Upgrade from xen-4.1-testing to xen-unstable report Teck Choon Giam
2012-04-12  7:08 ` Ian Campbell [this message]
2012-04-12 11:44   ` Teck Choon Giam
2012-04-12 12:50   ` Lin Ming
2012-04-12 14:03     ` Ian Campbell
2012-04-12 14:42       ` Lin Ming
2012-04-12 14:50         ` Ian Campbell
2012-04-12 15:25           ` Teck Choon Giam
2012-04-12 16:27             ` Teck Choon Giam

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=1334214539.12209.219.camel@dagon.hellion.org.uk \
    --to=ian.campbell@citrix.com \
    --cc=giamteckchoon@gmail.com \
    --cc=mlin@ss.pku.edu.cn \
    --cc=xen-devel@lists.xensource.com \
    /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).