Hi There
So I have seen a few other threads that have addressed pxe booting issues but none that seem to cover this.
I have built an iPXE iso with an embedded script to boot from in networks without DHCP. Been using this setup a while and it has worked fine.
I go to rebuild this iso on a new Cluster that is freshly installed but it looks like iPXE doesn't detect virtio nics anymore.
I tested with e1000e and it is picked up. I tested in a cluster I hadn't upgraded recently (pve-manager/9.1.1/42db4a6cf33dac83) and the iso I built worked and detected the virtio nic.
This suggests something has changed in between that version and the current no-sub version (pve-manager/9.1.11/8eac2c86f015bdda) and I was wondering if this was know.
I am using a SeaBios VM and i440fx system (basically next next on the creation screen). iPXE ma
Just wondering if this is something that was expected and if there is a fix?
--- Answer
So found an answer as I was typing this out, checking out the tag v2.0.0 of iPXE rather than using the master branch seems to have resolved the issue. Maybe something in between both later proxmox and ipxe causes this issue.
So I have seen a few other threads that have addressed pxe booting issues but none that seem to cover this.
I have built an iPXE iso with an embedded script to boot from in networks without DHCP. Been using this setup a while and it has worked fine.
I go to rebuild this iso on a new Cluster that is freshly installed but it looks like iPXE doesn't detect virtio nics anymore.
I tested with e1000e and it is picked up. I tested in a cluster I hadn't upgraded recently (pve-manager/9.1.1/42db4a6cf33dac83) and the iso I built worked and detected the virtio nic.
This suggests something has changed in between that version and the current no-sub version (pve-manager/9.1.11/8eac2c86f015bdda) and I was wondering if this was know.
I am using a SeaBios VM and i440fx system (basically next next on the creation screen). iPXE ma
Just wondering if this is something that was expected and if there is a fix?
--- Answer
So found an answer as I was typing this out, checking out the tag v2.0.0 of iPXE rather than using the master branch seems to have resolved the issue. Maybe something in between both later proxmox and ipxe causes this issue.