All of lore.kernel.org
 help / color / mirror / Atom feed
From: "W. Michael Petullo" <mike@flyn.org>
To: xen-devel@lists.xensource.com
Subject: Recent xl and network-route scripts
Date: Wed, 16 Feb 2011 19:13:31 -0600	[thread overview]
Message-ID: <20110217011331.GA3090@imp.local> (raw)

I've been testing recent Xen 4.1 release candidates, and it seems that
"xl" does not want to play nicely with the vif-route script.

First, the udev subsystem executes vif-setup after Xen creates the
vif device. For some reason, this script does not have $script defined
and so it defaults to running vif-bridge (even though xend-config.sxp
specifies vif-route). Once I changed vif-setup by hand to run vif-route
things went further. I'm not entirely sure how $script is supposed to
be set, but it worked fine with xm.

Next, vif-route does not pick up $ip from my domain configuration's
"vif = [ 'ip=w.x.y.z' ]." When using xm, vif-route finds $ip set and
creates a route based on its value.

I have most recently tested this with Xen 4.1.0 RC4.

-- 
Mike

:wq

         reply	other threads:[~2011-02-17  1:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-04 10:02 [PATCH 0 of 2] vif hotplug script configuration fixes Ian Campbell
2011-02-17  1:13 ` W. Michael Petullo [this message]
2011-02-17  7:29   ` Recent xl and network-route scripts Pasi Kärkkäinen
2011-02-17  9:19     ` Ian Campbell
2011-02-17 10:10       ` Ian Campbell
2011-02-18 15:32         ` Ian Jackson
2011-03-13 18:53           ` W. Michael Petullo
2011-03-14  9:35             ` Ian Campbell
2011-03-15 18:12               ` Ian Jackson
2011-03-15 19:25                 ` Ian Campbell
2011-03-04 10:02 ` [PATCH 1 of 2] libxl: use full path to vif hotplug script script Ian Campbell
2011-03-16 16:45   ` Recent xl and network-route scripts [and 1 more messages] Ian Jackson
2011-03-04 10:02 ` [PATCH 2 of 2] tools/hotplug/Linux: read script for tapX.Y devices from xenstore 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=20110217011331.GA3090@imp.local \
    --to=mike@flyn.org \
    --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.