Seconding this request, PXE booting the VMs is pretty standard and needed.

I see there are no Assignees. Has this dropped off the radar?

From my own use of Harvester it can handle PXE but it's just not nicely exposed to the admin via the GUI.

After VM creation you can edit the YAML and add "bootOrder: 1" under domain.devices.interfaces plus change the existing "bootOrder:1" under domain.devices.disks to "bootOrder:2". See screenshot below

I've used this to PXE boot a node on an isolated network (configured within Harvester) from another node (dual connected within Harvester to the isolated network and external network).

So what's required is a way to set the boot order of devices, not just disks.

To chime in, a year ago, I had to drop evaluating Harvester for our needs because we require PXE installing VMs. Documenting a work around is great, but we also need visibility at VM creation.

@torchiaf please check what is needed to add UI for the above (to add a different device to the boot order)

Pre Ready-For-Testing Checklist

• If labeled: require/HEP Has the Harvester Enhancement Proposal PR submitted?
  The HEP PR is at:

• Where is the reproduce steps/test steps documented?
  The reproduce steps/test steps are at:

• Is there a workaround for the issue? If so, where is it documented?
  The workaround is at:

• Have the backend code been merged (harvester, harvester-installer, etc) (including backport-needed/*)?
  The PR is at:

  • Does the PR include the explanation for the fix or the feature?

  • Does the PR include deployment change (YAML/Chart)? If so, where are the PRs for both YAML file and Chart?
    The PR for the YAML change is at:
    The PR for the chart change is at:

• If labeled: area/ui Has the UI issue filed or ready to be merged?
  The UI issue/PR is at:

• If labeled: require/doc, require/knowledge-base Has the necessary document PR submitted or merged?
  The documentation/KB PR is at:

• If NOT labeled: not-require/test-plan Has the e2e test plan been merged? Have QAs agreed on the automation test case? If only test case skeleton w/o implementation, have you created an implementation issue?

  • The automation skeleton PR is at:
  • The automation test case PR is at:

• If the fix introduces the code for backward compatibility Has a separate issue been filed with the label release/obsolete-compatibility?
  The compatibility issue is filed at:

Automation e2e test issue: harvester/tests#1069