From: Carsten Schiers <carsten@schiers.de>
Cc: xen-devel <xen-devel@lists.xensource.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Subject: AW: [PATCH 1 of 2] xl: improve compatibility with xm
Date: Mon, 30 May 2011 16:49:20 +0200 [thread overview]
Message-ID: <24392476.41306766960044.JavaMail.root@uhura> (raw)
In-Reply-To: <14318239.191306486529002.JavaMail.root@uhura>
Just close enough. BR, Carsten.
----- Originalnachricht -----
Von: Ian Campbell <Ian.Campbell@eu.citrix.com>
Gesendet: Fre, 27.5.2011 10:41
An: Carsten Schiers <carsten@schiers.de>
Cc: xen-devel <xen-devel@lists.xensource.com> ; Ian Jackson <Ian.Jackson@eu.citrix.com> ; Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Betreff: Re: [Xen-devel] [PATCH 1 of 2] xl: improve compatibility with xm
On Thu, 2011-05-26 at 19:26 +0100, Carsten Schiers wrote:
> xl: improve compatibility with xm
>
> /etc/init.d/xendomains relies on simple pattern matching from sructures
> being
> printed by "xl list -l" command. so update xl implementation to match.
Thanks. Does this mean that "xl list -l" now matches "xm list -l" for
you, or just that it is close enough to make xendomains happy?
>
> Signed-off-by: Carsten Schiers <carsten@schiers.de>
>
> diff -r 37c77bacb52a tools/libxl/xl_cmdimpl.c
> --- a/tools/libxl/xl_cmdimpl.c Mon May 23 17:38:28 2011 +0100
> +++ b/tools/libxl/xl_cmdimpl.c Thu May 26 19:58:46 2011 +0200
> @@ -294,7 +294,7 @@
> libxl_domain_build_info *b_info = &d_config->b_info;
>
> printf("(domain\n\t(domid %d)\n", domid);
> - printf("\t(domain_create_info)\n");
> + printf("\t(create_info)\n");
> printf("\t(hvm %d)\n", c_info->hvm);
> printf("\t(hap %d)\n", c_info->hap);
> printf("\t(oos %d)\n", c_info->oos);
> @@ -321,7 +321,7 @@
> printf("\t(platformdata (null))\n");
>
>
> - printf("\t(domain_build_info)\n");
> + printf("\t(build_info)\n");
> printf("\t(max_vcpus %d)\n", b_info->max_vcpus);
> printf("\t(tsc_mode %d)\n", b_info->tsc_mode);
> printf("\t(max_memkb %d)\n", b_info->max_memkb);
> @@ -381,7 +381,7 @@
> printf("\t(device\n");
> printf("\t\t(tap\n");
> printf("\t\t\t(backend_domid %d)\n",
> d_config->disks[i].backend_domid);
> - printf("\t\t\t(domid %d)\n", domid);
> + printf("\t\t\t(frontend_domid %d)\n", domid);
> printf("\t\t\t(physpath %s)\n", d_config->disks[i].pdev_path);
> printf("\t\t\t(phystype %d)\n", d_config->disks[i].backend);
> printf("\t\t\t(virtpath %s)\n", d_config->disks[i].vdev);
> @@ -396,7 +396,7 @@
> printf("\t(device\n");
> printf("\t\t(vif\n");
> printf("\t\t\t(backend_domid %d)\n",
> d_config->vifs[i].backend_domid);
> - printf("\t\t\t(domid %d)\n", domid);
> + printf("\t\t\t(frontend_domid %d)\n", domid);
> printf("\t\t\t(devid %d)\n", d_config->vifs[i].devid);
> printf("\t\t\t(mtu %d)\n", d_config->vifs[i].mtu);
> printf("\t\t\t(model %s)\n", d_config->vifs[i].model);
> @@ -426,7 +426,7 @@
> printf("\t(device\n");
> printf("\t\t(vfb\n");
> printf("\t\t\t(backend_domid %d)\n",
> d_config->vfbs[i].backend_domid);
> - printf("\t\t\t(domid %d)\n", domid);
> + printf("\t\t\t(frontend_domid %d)\n", domid);
> printf("\t\t\t(devid %d)\n", d_config->vfbs[i].devid);
> printf("\t\t\t(vnc %d)\n", d_config->vfbs[i].vnc);
> printf("\t\t\t(vnclisten %s)\n", d_config->vfbs[i].vnclisten);
>
parent reply other threads:[~2011-05-30 14:49 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <14318239.191306486529002.JavaMail.root@uhura>]
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=24392476.41306766960044.JavaMail.root@uhura \
--to=carsten@schiers.de \
--cc=Ian.Jackson@eu.citrix.com \
--cc=Stefano.Stabellini@eu.citrix.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.