vm workstation 17 and pxe boot not working
-
@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. -
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.
-
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.
-
I did update to the latest kernal to see if that was an issue and still no change.
-
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
-
any updates ?
-
@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?”
-
what information do you need ? I am trying virtual workstation and vm workstation 17 . I have tried UEFI and Bios. It is windows 25h2. I have even went back to 24h2. I will try vm workstation 16. I am using just a standard iso.
-
@mmoore5553 Hi,
I create my golden images using VMWare Workstation Pro, so unsure if this is applicable. I have found the network settings on the virtual machine to be very important in this process.
Firstly, NAT just doesn’t work for capturing the image so ensure your connection is bridged.
Secondly I have found if you have multiple network connections (VPN, WIFI, Ethernet etc.) it will randomly pick which one to PXE boot via. I have found the “Replicate physical network connection state” setting is also required.
For safety I would suggest the host machine only has one network available (ie. temporarily disable WIFI and VPN) while using a bridged connection.
The other thought would be to check if there’s any network monitoring you can look at so diagnosis may be easier.
-
I am shocked and thought i would update the post. I found out a windows update messed up vm workstation. I tried the older version and it did not work and went back to 17. As soon as I reloaded my computer and went to 25h2 everything started to work.
It was shocked and wanted to let people know. I had to install on another spare computer and move my images and they worked .
Thank you all though .
-
@mmoore5553 Understood and appreciate the return with new information.
i’m not sure what caused it but glad it has since been addressed/fixed.
Thank you! And yes, I gave an upvote!
