libvirt/tests/networkxml2xmlin/netboot-proxy-network.xml

<network>
  <name>netboot</name>
  <uuid>81ff0d90-c91e-6742-64da-4a736edb9a9b</uuid>
  <bridge name="virbr1" stp='off' delay='1'/>
  <domain name="example.com"/>
  <forward/>
  <ip address="192.168.122.1" netmask="255.255.255.0">
    <dhcp>
      <range start="192.168.122.2" end="192.168.122.254" />
      <bootp file="pxeboot.img" server="10.20.30.40" />
    </dhcp>
  </ip>
</network>
Add support for an external TFTP boot server This patch adds an optional attribute to the <bootp> tag, that allows to specify a TFTP server address other than the address of the DHCP server itself. This can be used to forward the BOOTP settings of the host down to the guest. This is something that configurations such as Xen's default network achieve naturally, but must be done manually for NAT. * docs/formatnetwork.html.in: Document new attribute. * docs/schemas/network.rng: Add it to schema. * src/conf/network_conf.h: Add it to struct. * src/conf/network_conf.c: Add it to parser and pretty printer. * src/network/bridge_driver.c: Put it in the dnsmasq command line. * tests/networkxml2xmlin/netboot-proxy-network.xml tests/networkxml2xmlout/netboot-proxy-network.xml tests/networkxml2xmltest.c: add new tests 2009-10-28 14:57:49 +00:00			`<network>`
			`<name>netboot</name>`
			`<uuid>81ff0d90-c91e-6742-64da-4a736edb9a9b</uuid>`
			`<bridge name="virbr1" stp='off' delay='1'/>`
			`<domain name="example.com"/>`
			`<forward/>`
			`<ip address="192.168.122.1" netmask="255.255.255.0">`
			`<dhcp>`
			`<range start="192.168.122.2" end="192.168.122.254" />`
			`<bootp file="pxeboot.img" server="10.20.30.40" />`
			`</dhcp>`
			`</ip>`
			`</network>`