special circumstances
Cadet
- Joined
- Apr 22, 2023
- Messages
- 2
I've just made the move to SCALE from CORE mainly to replace bhyve with kvm - it went well really.
However one problem I found is (as far as I can tell) there is no method to configure a guest VM to primarily boot using the NIC (and permanently so)
The device order settings appear to have no effect with regards to boot device order (fair enough - they don't claim to).
I've looked at the running config for the VMs, and I can see that '-boot strict=on' is set, that the harddisk device is always set to have 'bootindex=1' and that there is no bootindex set at all for the NIC. This combination I think has the effect of preventing any possibility of PXE boot for the VM.
This is a real shame, because I was hoping to use my TrueNAS VMs with Openstack (which really does appreciate network booting nodes).
I can of course overwrite the config files with virsh, but as TrueNAS re-writes these when the VM is launched that's no help really.
Have I missed a checkbox somewhere?
Is there any way of adjusting/affecting the VM configuration/options further?
Is adding this simple option to the API anywhere in the roadmap?
However one problem I found is (as far as I can tell) there is no method to configure a guest VM to primarily boot using the NIC (and permanently so)
The device order settings appear to have no effect with regards to boot device order (fair enough - they don't claim to).
I've looked at the running config for the VMs, and I can see that '-boot strict=on' is set, that the harddisk device is always set to have 'bootindex=1' and that there is no bootindex set at all for the NIC. This combination I think has the effect of preventing any possibility of PXE boot for the VM.
This is a real shame, because I was hoping to use my TrueNAS VMs with Openstack (which really does appreciate network booting nodes).
I can of course overwrite the config files with virsh, but as TrueNAS re-writes these when the VM is launched that's no help really.
Have I missed a checkbox somewhere?
Is there any way of adjusting/affecting the VM configuration/options further?
Is adding this simple option to the API anywhere in the roadmap?