Providing custom arguments/environment to network scripts

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

 



I'm trying to build a setup where the VMs only have point-to-point
Ethernet connections to the hypervisor, which will then act as a layer-3
router. When the VM starts, the hypervisor needs to UP the assigned tap
interface and configure an IP/mask on it (that will be the VMs default
gateway). So I'm currently looking at a config looking like this:

<interface type='ethernet'>
  <script path='/sbin/vm-ifup'/>
</interface>

The problem I'm facing is that there appears to be no way supply
information to the script by way of command-line arguments or custom
environment variables. So something like:

<script path='/sbin/vm-ifup 2001:db8::/64'/>

...fails because it tries to execute the whole string, space included,
as the script file.

The only information I have available in the script is the assigned tap
device in the hypervisor (which is automatically passed in as the first
argument to the script). As the device name is automatically assigned on
VM start, it is useless as a lookup key of sorts for finding more
information. One workaround would be to have one network script per VM
that hard-codes all the necessary information, but if you have a large
number of hypervisors with an even larger number of VMs, this quickly
becomes impractical.

So my question is, is there some other way to pass configuration
information to the network script or to accomplish what I'm trying to do?

Best regards,
-- 
Tore Anderson
Redpill Linpro AS - http://www.redpill-linpro.com

--
libvir-list mailing list
libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list


[Index of Archives]     [Virt Tools]     [Libvirt Users]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]     [Fedora Tools]