vm workstation 17 and pxe boot not working

[mmoore5553]

I can confirm nothing has changed on the fog server. I can take a laptop and connect and pxe boot and it works with no issues. I currently have windows 11 running with uefi. I have no tpm set and can switch it to boot to regular bios , if needed.

I boot it up with bios or uefi and it does nothing. It goes to look for it and times out. I was on vm workstation 16 and this did work at one time but my pc died and I had to recreate all images.

I am not sure what to look for since the physical laptop I can get to the fog server and push and image.

[mmoore5553]

I can ping the fog server from my host machine. I have tried all the options and nothing has worked.

[Fog_Newb]

@mmoore5553
Assuming you’ve tried setting the VM to BIOS and UEFI and still no go… Do you have the VM set to use a bridged network connection? Also you have to make sure the boot order on the VM is set for network boot first.

[mmoore5553]

@Fog_Newb

yes. I have tried bios to uefi and bios. I still do not get anything. UEFI it does not even look like it goes out. Bios I get a boot file missing.

I swear 24h2 I did not have to change anything. I lost that image though. I might redo it to see .

Bios boot order is changed correctly.

[mmoore5553]

I have tried with virtualbox and same issue. I do get further …it says downloading nbp file but nothing happens. I have it on bridged mode too.

[mmoore5553]

I did update to the latest kernal to see if that was an issue and still no change.

[mmoore5553]

I did update the fog server to the latest version and still the same issue. I am not sure where to go. Virtualbox has the extension installed and vm workstation should work.

I did do this from broadcom

https://community.broadcom.com/vmware-cloud-foundation/discussion/disabling-hyper-v-hypervisor-on-windows-11-pro-host-to-get-vmware-17s-cpl0-vs-ulm-monitor-mode

[mmoore5553]

any updates ?

[Tom Elliott]

@mmoore5553 We dont’ ahve any information, examples of the problem, anything beyond “What’s the issue”

Please provide more information as you have already clearly stated that there’s nothing that seems to be wrong with FOG at all, but rather something specifica to VM Workstation 17.

I don’t know what VirtualBox extensions have ot do with this, but Omnissa is it’s own thing (was VMware).

We don’t know what you’ve tried, if you’ve tried back with Workstation 16 and all works? You have just said “something’s broke, what is it?”