From: Michael Mey <michael.mey@to.com>
To: "Christopher G. Stach II" <cgs@ldsys.net>
Cc: xen-devel@lists.xensource.com
Subject: Re: update possibility for domain configuration files
Date: Wed, 8 Mar 2006 17:25:24 +0100 [thread overview]
Message-ID: <200603081725.31451.michael.mey@to.com> (raw)
In-Reply-To: <440EFB6B.1000203@ldsys.net>
[-- Attachment #1.1: Type: text/plain, Size: 1007 bytes --]
On Wednesday 08 March 2006 16:42, Christopher G. Stach II wrote:
> Michael Mey wrote:
> > In my opinion, it should be necessary to implement an option into the xm
> > command to save the current configuration of a running domain back into a
> > local file. Because if the domain is shut down and should be brought up
> > again with the same configuration as before, we have a problem.
>
> Do you mean something like ``xm list --long <domId> > <configfile>''?
Exactly. The output of 'xm list ---long <domID>' should be converted from sxp
format to config-file format.
--
----------------------------------------------------------------------------------------
Michael Mey
Thinking Objects Software GmbH | mailto: michael.mey@to.com
Lilienthalstrasse 2/1 | phone: +49 711 88770-147
70825 Stuttgart-Korntal, Germany | fax: +49 711 88770-449
----------------------------------------------------------------------------------------
[-- Attachment #1.2: Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
prev parent reply other threads:[~2006-03-08 16:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-08 12:17 update possibility for domain configuration files Michael Mey
2006-03-08 15:42 ` Christopher G. Stach II
2006-03-08 16:25 ` Michael Mey [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=200603081725.31451.michael.mey@to.com \
--to=michael.mey@to.com \
--cc=cgs@ldsys.net \
--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.