On Thu, 2009-01-22 at 15:20 +0000, Daniel P. Berrange wrote: > On Thu, Jan 22, 2009 at 03:12:39PM +0000, Richard W.M. Jones wrote: > > On Tue, Jan 20, 2009 at 02:05:26PM +0300, Dmitry Guryanov wrote: > > > But for working PXE boot it should have also something like > > > --dhcp-boot=pxelinux.0,itchy,192.168.107.1 > > > > This isn't supported by libvirt at the moment, but it would great to > > have a patch which enabled this. PXE-booting using dnsmasq is very > > reliable, and there's no particular reason why we shouldn't support > > it. > > Well the virtual network stuff is local to the host only, and so it > is even more reliable if you just boot the guest in question from > the kernel+initrd directly, instead indirectly giving it the kernel+ > initrd via a dodgy PXE server. > > We have a hammer, but I don't think we should use it in this case. When you NAT the virtual network to the outside world (like Dmitry does), there's no reason why the TFTP part of a PXE boot should not work. And if you're on a laptop, connected to a network with a working TFTP server, I don't see why you should have to screw around with kernel +initrd. I always felt it's a mistake to work so hard to hide the actual dnsmasq config from users - it would be much more extensible if we plonked a config file into /etc/dnsmasq.d David -- Libvir-list mailing list Libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list