iPxe environment works great with virtual box win + linux... except after dnsmasq
Posted: 6. Feb 2018, 10:35
Have a 10 host ipxe environment booting tinycore and lubuntu images.
Originally setup on a windows server running tiny pxe server on windows (http://mistyrebootfiles.altervista.org/ ... _about.htm).
Everything worked great. Originally had more windows hosts but have slowly migrated to linux hosts except a few machines.
During this process we switched the pxe server from windows tinypxe server to dnsmasq + busybox httpd. This actually worked great, didn't have to change any pxe configs at all. All the linux hosts and stand alone machines continue to boot pxe just fine.
However the same windows hosts, running the same virtualbox and OS, with same virtual box session settings... can no longer get a dhcp address. updating software, changing configs, disabling firewalls, nothing solves it on the windows hosts. we can still switch back to the windows-based tinypxe servers and works great. have tried every possible network setting on the host machine with respect to configuring the guest session. the only time I can get a dhcp and boot file (again) is when I disable the network session but configure it to boot from the network. it looks like a bug.
this is pretty rare we attempt this so wondering if I run a linux guest on the windows hosts and re-run virtual box if that will fix it. the linux hosts have never had an issue either way.
I have not seen very good support for these type of issues, hence my ticket. I don't really expect a solution but since it's supposed to work and generally does work, I figured I'd post this edge case.
v5.2.4
Originally setup on a windows server running tiny pxe server on windows (http://mistyrebootfiles.altervista.org/ ... _about.htm).
Everything worked great. Originally had more windows hosts but have slowly migrated to linux hosts except a few machines.
During this process we switched the pxe server from windows tinypxe server to dnsmasq + busybox httpd. This actually worked great, didn't have to change any pxe configs at all. All the linux hosts and stand alone machines continue to boot pxe just fine.
However the same windows hosts, running the same virtualbox and OS, with same virtual box session settings... can no longer get a dhcp address. updating software, changing configs, disabling firewalls, nothing solves it on the windows hosts. we can still switch back to the windows-based tinypxe servers and works great. have tried every possible network setting on the host machine with respect to configuring the guest session. the only time I can get a dhcp and boot file (again) is when I disable the network session but configure it to boot from the network. it looks like a bug.
this is pretty rare we attempt this so wondering if I run a linux guest on the windows hosts and re-run virtual box if that will fix it. the linux hosts have never had an issue either way.
I have not seen very good support for these type of issues, hence my ticket. I don't really expect a solution but since it's supposed to work and generally does work, I figured I'd post this edge case.
v5.2.4