BIOS and UEFI boot, in VMware WinPE boot
-
Hi,
both Vbox and VMW cannot boot via EFI over Network.
If you like to create a golden image done in a vm set booting to legacy at the moment when you capture.Regards X23
-
It seems another bug left in project, if i’m trying update update kernel image.
In Kernel Update is Kernel - 4.15.2 TomElliott
but after update I see :bzImage Version: 4.13.4 bzImage32 Version: 4.13.4 -
@x23piracy said in BIOS and UEFI boot, in VMware WinPE boot:
If you like to create a golden image done in a vm set booting to legacy at the moment when you capture.
I’m trying to boot MDT - deployment tool, to install OS…
p.s.: very strange, I do not remember exactly, but it seems to me that UEFI’s work was earlier
-
I do not remember what I did all the time, but VMware workstation works with uEFI, the problem is closed.
Unfortunately I did not know exactly what I did…
-
@poizzon what version of fog are you using?
-
latest - Fog version 1.5.0
WinPE via BIOS and UEFI working - this problem closed.
it seems there is bug with kernel update - it did’t updating to latest : Kernel - 4.15.2 TomElliott
-
@poizzon What is the problem? You think it’s the kernel that’s impacting VMWare WinPE boot? Other systems have no problems with WinPE Booting?
I’m not understanding the problem. Using 1.5.0 is good, and sorry I missed it in your first post (as it’s kind of hidden between all the code blocks).
I guess what I’m trying to understand, what does the bzImage kernel have to do with WinPE?
-
I wanted to add, the 4.13.4 kernel issue is now resolved. Not a bug in the sense that the base code didn’t need any changes to get this working. Apparently on one of the updates it copied the same old file over instead of the freshly built 4.15.2 kernels. I just reupdated them on the fogproject side and double checked their value is correct.
-
first problem was when apache always redirecting to default site. When I put it to subfolder all started to work.
What would be the best place for a WinPE folder ?
I also noticed that after the upgrade, the WinPE directory is moved to the backup, and I always have to manually move back to it.Secondly, I did not understand why the WinPE did not start in UEFI mode but suddenly started running …
Third - bzImage - just sow that it is not updating and wanna report
For now case is closed.
-
@poizzon said in BIOS and UEFI boot, in VMware WinPE boot:
What would be the best place for a WinPE folder ?
I also noticed that after the upgrade, the WinPE directory is moved to the backup, and I always have to manually move back to it.This might get you going here: https://forums.fogproject.org/topic/10944/using-fog-to-pxe-boot-into-your-favorite-installer-images/7
