Hi! So this is my problem, I had an image of my disk and I tried to boot it up from my VM workstation but it failed. I added in the line firmware = "efi". I used to be able to boot up without a problem in VM with my disk images before I changed to a new Win 8 laptop. So I was wondering does the secure boot somehow affects it? Would appreciate help on this!
I have Player not Workstation so don't know if there is a difference but I have secure boot turned on and have no problems. From what I know, VMWare runs entirely within Windows so I don't see how secure boot would have any affect.
And welcome to the forum!
Edit: If you are talking booting from scratch with a VM image that is a different story. I will bow out as I have zero experience with that.
If Popeye did not have the problem then I would assume that you should not have problem with secure boot. Maybe it's just the way you set it up in Windows 8.
I helped another person in this forum a while back on how to set up a VHD using VmPlayer/VmWare Workstation. Maybe you want to compare your setup with the Video below:
NOTE: yes, you also need to add firmware = "efi" and do not mount it.
But I think I may not be clear with my question. I'm trying to convert my system into a virtual system. But somehow I'm having problem with it so I'm wondering does secureboot not works with VM?
With a Virtual machine you are NOT doing a PHYSICAL boot. Secure boot only is of concern to the HOST machine which prevents non authorized boot devices from booting -- for example if you want to boot from a USB stick you won't be able to (you can enable LEGACY boot in the BIOS to allow external devices to boot - you don't have to disable UEFI either.)
A Virtual machine boots in Software and is a Virtual boot - the Virtual machine is running under control of VMWARE / VBOX etc which is a normal application program as far as your HOST machine is concerned -- a bit like running say EXCEL.
You can enable UEFI on a virtual machine if you want to even if your HOST doesn't have it --you need to edit the configuration file for the VM (it's a .vmx file for VMware but there's similar configuration files for VBOX).