David Edmondson wrote: > On Mon, Dec 01, 2008 at 12:37:24PM -0500, Bob Scheifler wrote: > >> On 11/28/08 09:39, John Levon wrote: >> >>> id=`virsh domid $1` >>> backend=`xenstore-read /local/domain/$id/device/vif/0/backend` >>> echo `xenstore-read $backend/nic` >>> >> Umm, but the xenstore commands aren't a public interface, are they? >> > > Even if they are, the path in the store isn't stable - you can't rely > on us not changing it. > > What's the problem we're trying to solve here?
First of all, I have to say, the original question was about obtaining the VNIC used by a running guest, and the answer worked and was very educational. Thank you. In fact, it looks like our ultimate goal here is we need to be able to additionally configure the VNIC created for a guest before the guest is even started. "Additionally configure" could include adding IP Filter rules, Crossbow properties, etc. To do so, do we need to hack /usr/lib/xen/scripts/vif-vnic? Or can we create VNICs ourselves and use e.g. /usr/lib/xen/scripts/vif-dedicated to pass them to xVM? What would be the recommended mechanism, in both xm and virsh realms? Are there any hook scripts called on VNIC creation/destruction intended specifically for this, maybe? Thank you, Vasiliy _______________________________________________ xen-discuss mailing list [email protected]
