All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: jdsw <jdsw2002@yahoo.com>
Cc: xendevel <xen-devel@lists.xensource.com>
Subject: Re: Running dom and associated conf file and cmdline
Date: Wed, 15 Nov 2006 18:03:13 +0000	[thread overview]
Message-ID: <20061115180313.GK17466@redhat.com> (raw)
In-Reply-To: <20061115175559.12783.qmail@web35805.mail.mud.yahoo.com>

On Wed, Nov 15, 2006 at 09:55:59AM -0800, jdsw wrote:
> Hi
> 
>    It would be convenient to have access to the config file (full path)
> and the command line  (startup parameters) through xml-rpc (DomInfo) interface. 
>    Currently I have seen, our product and others reading files... and 
> trying to match dom names etc...which is quite error prone and kludgy.

I think you mean you want the ability to see 'inactive'  domains from
from the APIs ?  If so this capability became available when the recent
Xen-API work was merged. If you do an 'xm list' it'll show both running
and inactive guests - the latter have an id of -1. This is only available
in xen-unstable tree & thus will be in 3.0.4 release.

Until then, reading/parsing the config files from /etc/xen is only option.
I've added support for doing just this in libvirt so we can work on older
3.0.2, and 3.0.3 releases, as well as making use of the new APIs in 3.0.4

Regards,
Dan.
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=| 

      reply	other threads:[~2006-11-15 18:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-15 17:55 Running dom and associated conf file and cmdline jdsw
2006-11-15 18:03 ` Daniel P. Berrange [this message]

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=20061115180313.GK17466@redhat.com \
    --to=berrange@redhat.com \
    --cc=jdsw2002@yahoo.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 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.