All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@citrix.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
	Zhigang Wang <zhigang.x.wang@oracle.com>
Subject: Re: xl list -l doesn't work for incoming domain
Date: Mon, 10 Nov 2014 14:05:49 +0000	[thread overview]
Message-ID: <1415628349.25176.19.camel@citrix.com> (raw)
In-Reply-To: <20141110135419.GB32371@zion.uk.xensource.com>

On Mon, 2014-11-10 at 13:54 +0000, Wei Liu wrote:
> > Can we write a stub json file at the beginning of migrate receive, a bit
> > like we do on create?
> > 
> 
> No, we don't generate stub for normal domain at the moment.

Oh, I thought we did.

SO what happens if someone runs "xl list" while a domain create is in
progress? 

> Whether we should do it or not, it depends on whether we want libxl user
> to see incomplete (and certainly incorrect) domain configuration. I
> think not, because libxl user doesn't know how to distinguish stub
> (invalid) configuration from a valid one.
> 
> > Otherwise code like xl list is going to have start special casing
> > domains which have no json, which we've tried hard to avoid I think.
> > 
> 
> From xl's (and other tools on the same level) point of view, that means
> invocation of library function fails, which it should always be ready to
> cope with.

So your opinion is that the bug is the "libxl: error:
libxl.c:6535:libxl_retrieve_domain_configuration: fail to get domain
configuration for domain 7" message which should be removed?

I'd be happy enough with domain 7 being listed with an empty cfg in that
case.

Ian.

  reply	other threads:[~2014-11-10 14:06 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-06 19:14 xl list -l doesn't work for incoming domain Zhigang Wang
2014-11-07 10:47 ` Wei Liu
2014-11-07 16:34   ` Zhigang Wang
2014-11-10 12:35     ` Wei Liu
2014-11-10 12:38       ` Ian Campbell
2014-11-10 13:54         ` Wei Liu
2014-11-10 14:05           ` Ian Campbell [this message]
2014-11-10 14:16             ` Wei Liu
2014-11-10 15:01       ` Zhigang Wang
2014-11-10 15:25         ` Wei Liu
2014-11-10 17:08           ` Zhigang Wang
2014-11-10 17:24             ` Wei Liu
2014-11-10 17:54               ` Zhigang Wang
2014-11-11 11:01                 ` Wei Liu
2014-11-11 14:41                   ` Zhigang Wang
2014-11-11 15:20                     ` Wei Liu
2014-11-11 16:42                       ` Zhigang Wang
2014-11-12 11:31                         ` Wei Liu
2014-11-12 14:36                           ` Zhigang Wang
2014-11-12 14:40                             ` Ian Campbell
2014-11-12 14:48                               ` Zhigang Wang
2014-11-12 14:52                                 ` Ian Campbell
2014-11-12 15:04                                   ` Zhigang Wang
2014-11-12 15:40                                     ` Wei Liu
2014-11-13 11:44                                     ` Ian Campbell

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=1415628349.25176.19.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xenproject.org \
    --cc=zhigang.x.wang@oracle.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 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.