All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexandre Bezroutchko <abb@gremwell.com>
To: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: extra parameters for a custom vif-script
Date: Wed, 10 Apr 2013 15:21:26 +0200	[thread overview]
Message-ID: <51656756.3020200@gremwell.com> (raw)

Hello,

I am trying to develop custom xen vif- and network- scripts and can't
figure out how to passing parameters. When creating a domain, I would
like to be able to specify two additional parameters for each vif and
get access to them via from my custom vif-script.

I have done some research and found I can easiliy extend the list of
parameters accepted by 'xm create' command by editing
/usr/lib/xen-4.0/lib/python/xen/xm/create.py. It all works just fine in
the dry mode, I see the parameters and their value dumped on the output.
But when the domain gets created these values don't see to be retained
in the config, I see no traces of them in the output of 'xm list VMID'.

I have also attempted to edit vif_params in main.py to add same two
parameters to 'network-attach' command handler. It has not helped, the
parameter don't seem to make it into the config nor xenstore anyway.

I could use an advice how this can be implemented properly. I thinking
about customizing create.py further, to store values I need to persist
in xenstore under /vm/UUID/device/vif/NNN/. Just wondering if I am
overlooking some more elegant solution. Any advise is appreciated.

PS. I use xm toolstack on Xen 4.0.1 on Debian.

Best regards,
Alex

                 reply	other threads:[~2013-04-10 13:21 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=51656756.3020200@gremwell.com \
    --to=abb@gremwell.com \
    --cc=xen-devel@lists.xen.org \
    /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.