VMware vSphere

 View Only

  • 1.  running uefi sct tool on vm

    Posted Apr 06, 2013 10:15 PM

    I installed esxi5.0 with virtual machine setting to UEFI BIOS support. I tried to run the uefi sct (self-certification tool) on uefi shell however the installation stops saying unable to copy the stallforkey.efi file. However on normal physical machine, I am able to boot to efi shell and can install the same tool without any incidence. I wonder why it does not work on virtual machine. Thanks!



  • 2.  RE: running uefi sct tool on vm

    Broadcom Employee
    Posted Apr 06, 2013 10:29 PM

    Hi guyenvmware000,

    Our EFI implementation does not include full support for long filenames on FAT filesystems, so by default you'll be unable to create non-"8.3" filenames from within EFI.  If you need long filename support, you'll have to obtain or build a FAT filesystem driver with that support, and load it into the EFI environment.  (The driver source is here).

    Cheers,

    --

    Darius



  • 3.  RE: running uefi sct tool on vm

    Posted Apr 06, 2013 11:54 PM

    thanks Davis, that is very well looks like the issue. I am going to try building it and see how it happens and let you know of the result.



  • 4.  RE: running uefi sct tool on vm

    Posted Apr 11, 2013 12:49 AM

    Hi I had some issue building howevre I found there is already fat.efi driver built on following location. I was not sure if it is really enhanced fat driver or not but I presumed since it is under EnhancedFatDxe folder. However once I load, it still does not work.

    https://edk2.svn.sourceforge.net/svnroot/edk2/trunk/edk2/FatBinPkg/EnhancedFatDxe/X64/

    vs. original location you gave me

    https://edk2-fatdriver2.svn.sourceforge.net/svnroot/edk2-fatdriver2/trunk/FatPkg/EnhancedFatDxe/

    I simply loaded using "load fat.efi" from efi shell and it says success loading. However I found this driver seems to be already loaded because once it is loaded it shows as "FAT file system driver" twice in the list of drivers using "drivers" command. (Attached is the diff comparison of "drivers" command output before and after loading fat.efi).

    Therefore, it looks like I am loading the normal fat file system driver twice. However the binary was under enhancedFatDxe under sourceforge.  I am confused now. Thanks!



  • 5.  RE: running uefi sct tool on vm

    Posted Oct 05, 2013 04:37 AM

    no support on this issue for several months, so I turned to open source open source implementation option OVMF binary in conjunction with qemu in linux environment. It works flawlessly there. Was able to install SCT in an instant only remaining thing to do is to add OVMF binary with networking support so I can really do what i needed to. In this aspect of UEFI support, I believe open source is steps ahead of vmware in terms of flexbility because even with latest version of Esxi 5.5 the issue stated in this thread still remains. If I managed to build OVMF binary the networking support,  there is no need to use vmware.esxi anymore.



  • 6.  RE: running uefi sct tool on vm
    Best Answer

    Broadcom Employee
    Posted Oct 05, 2013 06:46 AM

    Sorry I failed to follow up on this thread in a timely fashion.  I try to help where I can, but it can be difficult to follow it all and make sure I reply to everything.

    The driver you found is the correct one, and it looks like you loaded it correctly too.

    You probably just need to use "reconnect" in the EFI Shell in order to disconnect our FAT filesystem driver from the SCT volume and connect the FAT filesystem driver which you installed (which has a higher driver version number, so it should be preferred to our driver)... Then you should have long filename support on the SCT volume.  There is some trickery required in order to obtain the correct handle ID(s) for the "reconnect" command, or you can try "reconnect -r", which will take a while longer to run.  You need to ensure that the EFI Shell's current working directory is not on the filesystem that you want to reconnect.

    It sounds like you're making good progress with OVMF+qemu anyway, so I just post the above for the sake of completeness, and just in case you find yourself stuck and looking again for another way forward.  Sorry once again that I missed responding to your post.

    Cheers,

    --

    Darius



  • 7.  RE: running uefi sct tool on vm

    Posted Nov 01, 2013 08:02 PM

    Hi Darius, thanks for help. I was able to run this time by disconnect original fat driver with new enhanced fat driver after doing some digging through efi shell commands:

    disconnect <fs0 handle> <old fat handle>

    connect <fs0 handle> <new e-fat handle> and this basically adds long file name support to fs0: partition therefore able to install sct tool and progress further. Thanks for great hint!.

    Also command such as drivers and dh -d <handle> can provide good information on each driver/device connection to see what I am dealing with.

    I may try this on OVMF later with time permitting.