On Wed, Jan 13, 2010 at 11:48:05AM -0500, Darryl L. Pierce wrote:
On Wed, Jan 13, 2010 at 05:03:59PM +0100, Paolo Bonzini wrote:
>
> ><network>
> ><name>testbr31018</name>
> ><forward mode='nat' />
> ><bridge name='testbr31018' stp='on' forwardDelay='0'
/>
> ><ip address='192.168.163.1' netmask='255.255.255.0'>
> ><tftp root='/tmp/tmp.6LUTF06Gkm/tftpboot' />
> ><dhcp>
> ><bootp file='pxelinux.0' />
> ><range start='192.168.163.100' end='192.168.163.199' />
> ></dhcp>
> ></ip>
> ></network>
> >
> >Are there any relative pathing values that should be used by the tftp
> >and bootp tags? Should the tftp->root attribute point to the work
> >directory and then bootp->file refer to tftpboot/pxelinux.0?
>
> No, the above seems fine (I should have pointed you to
> tests/networkxml2xmlin/netboot-network.xml before). Can you post
> the generated dnsmasq command line?
Here is what's output by libvirtd:
11:36:57.608: debug : virRun:809 : /usr/sbin/dnsmasq --strict-order --bind-interfaces
--pid-file=/var/run/libvirt/network/testbr6762.pid --conf-file= --listen-address
192.168.132.1 --except-interface lo --dhcp-range 192.168.132.100,192.168.132.199
--dhcp-lease-max=100 --enable-tftp --tftp-root /tmp/tmp.HRG19a7Udi --dhcp-boot
tftpboot/pxelinux.0
Now, this command line matches, WRT the pxe booting elements, our
pre-0.7 libvirtd test script that worked just fine. And I do see in the
vm getting an address via dhcp. But i'm still getting the error
"No filename or root path specified."
> Also, have you tried using wireshark to see what's going on?
No, I haven't.
Following up on this: I'm still unable to get the tftp element for this
to work with our autotesting script.
--
Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc.
Delivering value year after year.
Red Hat ranks #1 in value among software vendors.
http://www.redhat.com/promo/vendor/