Hi Rob, You do not need to do anything special. If you have 'dhcp' in the ips property it will just get an IP from your normal DHCP server.
The build in DHCP server you mentioned only comes into play with static IP's are set in the ips array, rereading that it still looks a bit confusing... 'dhcp' in nics.X.ips => gets IP from normal DHCP server '172.16.123.8' in nics.X.ips => gets '172.16.123.8' from KVM's mini DHCP server (you can ofcourse use any static-ip here) It's been a very long while but I do believe that KVM will pxe boot, you need to set the boot order to 'n' if I remember correctly. Regards Jorge June 11, 2018 10:19 PM, "Rob Seastrom" <[email protected]> wrote: > In a recent thread, Brian mentioned the "mini DHCP server" in the KVM brand > zone. > > I had a couple of questions about that that have been rattling around in the > back of my head for a > while... > > First off, is there a way to turn this off and allow the guest in the KVM > zone to DHCP from another > server elsewhere on the vlan? Some combination of nics.*.allow_dhcp_spoofing > and configuring the > NIC with no IP address? I don't see any nics.*.dhcp_client in the vmadm man > page... > > Second, assuming the above is feasible, does the SeaBIOS (which I think is > what we're running in > qemu) know enough to PXEboot? I want to netboot http://ipxe.org and chain on > to doing other things. > > Goal here is development environment for custom ipxe builds and preseeds for > bare metal imaging. > > Anyone done anything like this before? I've been using vmware as a dev > environment and it is > wearing thin because of what a pain it is to do my repeated pave-and-rebuild > cycles. > > Thanks, > > -r > ------------------------------------------- smartos-discuss Archives: https://www.listbox.com/member/archive/184463/=now Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125 Powered by Listbox: http://www.listbox.com
