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

On Thu, 2012-04-12 at 07:08 +0000, Ian Campbell wrote:
> 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.

Just did a quick gdb debug, seems libxl__domain_build_info_setdefault
was called 3 times. So below statement was executed 3 times too.

b_info->rtc_timeoffset += tm->tm_gmtoff;

Will look at this issue later.

(gdb) bt
#0  libxl__domain_build_info_setdefault (gc=0x7fffffffdc40, b_info=0x7fffffffdd90) at libxl_create.c:70
#1  0x00007ffff7991fd4 in libxl_domain_need_memory (ctx=0x626050, b_info=0x7fffffffdd90, need_memkb=0x7fffffffdc84) at libxl.c:2696
#2  0x000000000040b0ca in freemem (b_info=0x7fffffffdd90) at xl_cmdimpl.c:1399
#3  0x000000000040bd6d in create_domain (dom_info=0x7fffffffe040) at xl_cmdimpl.c:1656
#4  0x000000000041142c in main_create (argc=1, argv=0x7fffffffe638) at xl_cmdimpl.c:3446
#5  0x00000000004069d8 in main (argc=2, argv=0x7fffffffe630) at xl.c:165
(gdb) 

(gdb) bt
#0  libxl__domain_build_info_setdefault (gc=0x7fffffffdc70, b_info=0x7fffffffdd90) at libxl_create.c:70
#1  0x00007ffff799739c in do_domain_create (gc=0x7fffffffdc70, d_config=0x7fffffffdd50, cb=0, priv=0x7fffffffdd34, domid_out=0x625dc8, restore_fd=-1)
    at libxl_create.c:571
#2  0x00007ffff7997cdd in libxl_domain_create_new (ctx=0x626050, d_config=0x7fffffffdd50, cb=0, priv=0x7fffffffdd34, domid=0x625dc8) at libxl_create.c:738
#3  0x000000000040be4a in create_domain (dom_info=0x7fffffffe040) at xl_cmdimpl.c:1679
#4  0x000000000041142c in main_create (argc=1, argv=0x7fffffffe638) at xl_cmdimpl.c:3446
#5  0x00000000004069d8 in main (argc=2, argv=0x7fffffffe630) at xl.c:165
(gdb)

(gdb) bt
#0  libxl__domain_build_info_setdefault (gc=0x7fffffffdaa0, b_info=0x7fffffffdd90) at libxl_create.c:70
#1  0x00007ffff79b2146 in libxl_run_bootloader (ctx=0x626050, info=0x7fffffffdd90, disk=0x626b20, domid=9) at libxl_bootloader.c:349
#2  0x00007ffff7997464 in do_domain_create (gc=0x7fffffffdc70, d_config=0x7fffffffdd50, cb=0, priv=0x7fffffffdd34, domid_out=0x625dc8, restore_fd=-1)
    at libxl_create.c:580
#3  0x00007ffff7997cdd in libxl_domain_create_new (ctx=0x626050, d_config=0x7fffffffdd50, cb=0, priv=0x7fffffffdd34, domid=0x625dc8) at libxl_create.c:738
#4  0x000000000040be4a in create_domain (dom_info=0x7fffffffe040) at xl_cmdimpl.c:1679
#5  0x000000000041142c in main_create (argc=1, argv=0x7fffffffe638) at xl_cmdimpl.c:3446
#6  0x00000000004069d8 in main (argc=2, argv=0x7fffffffe630) at xl.c:165
(gdb) 

  parent reply	other threads:[~2012-04-12 12:50 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
2012-04-12 11:44   ` Teck Choon Giam
2012-04-12 12:50   ` Lin Ming [this message]
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=1334235037.4001.3.camel@hp6530s \
    --to=mlin@ss.pku.edu.cn \
    --cc=Ian.Campbell@citrix.com \
    --cc=giamteckchoon@gmail.com \
    --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).