[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] Inconsistent domain parameter passed to vif-bridge

It seems that the "domain" parameter passed to the vif-bridge script
isn't always consistent.  When calling "vif-bridge up", domain refers to
the name assigned to the domain.  When "vif-bridge down" is called,
domain is of the form "DOM<n>", where <n> is the numeric identifier for
the domain.

This is a problem since I'm using modifying the vif-bridge script for a
different network configuration, and was encoding the vmid used when
creating the domain into the domain's name.  The vmid is then used in
configuring network settings.  This works fine when bringing the network
up, but I have trouble when bringing the network down--specifically, I
want to remove a firewall rule, but need to know the vmid to specify the
firewall rule to delete.

Passing the name seems a more useful behavior to me, or perhaps both
name and id should be supplied to vif-bridge.  In any case, the current
behavior (different for up and down) seems broken.

So far I've tracked the problem as far as noticing that NetDev.destroy
in python/xen/xend/server/netif.py isn't passed the name of the domain,
but I haven't figured out how to best fix this.  I'm willing to work on
it a bit; any suggestions for how to approach it?

--Michael Vrable

This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.