VMware 6.5 VM not able to capture image using EFI (UEFI)
-
@quinniedid This looks like VMware does not find your harddrive (or maybe the controller). I found something about the PIIX4 warning on bootup here - though this is about virtualbox not VMware.
Which IDE controller is configured in VMware?
-
I will do some testing with a single VM no configuration with EFI.
As for the controller it should be an LSI SCSI adapter. This does work and I am able to capture the UEFI image if I switch back to BIOS to run the capturing for the VM. It does not work so far with UEFI booting FOG.
-
@Wayne-Workman @Sebastian-Roth Finally able to get a fresh VM built. I am getting the same error that it cannot find the HardDisk. I will try changing the controller and see what happens. Its just strange that this behavior exists on EFI and not on BIOS.
-
Officially, it will work if the controller on the VM hard drive is set to use SATA instead of the default SCSI. SCSI works on BIOS but not on EFI.
Is there a way to reduce the timeout on the smbus issue? It really is close to 10 minutes before it does anything.
-
@quinniedid Great you found that disk controller issue. About the other one: I am not sure if it is actually the piix4_smbus thing causing the long delay. Please prop up the kernel debug level (FOG web UI -> FOG Configuration -> FOG Settings -> FOG Boot Settings -> Option
KERNEL LOGLEVEL) all the way to 7 and post a picture of where it hangs. -
@Sebastian-Roth This is what it is getting hung up on:
I removed the SCSI controller, in this case the LSI controller that it was complaining about and the long delay has now been resolved.
What I don’t understand is why this happens only on an UEFI boot vs a BIOS boot. The BIOS boot doesn’t have issues with the SCSI hard drive nor the SCSI controller.
Any ideas on that?
-
@quinniedid said in VMware 6.5 VM not able to capture image using EFI (UEFI):
What I don’t understand is why this happens only on an UEFI boot vs a BIOS boot. The BIOS boot doesn’t have issues with the SCSI hard drive nor the SCSI controller.
Sorry, I don’t have a good answer to that.
-
@quinniedid while I don’t have an answer for you, I wonder what is your vSphere build number for 6.5? (i.e. 6765664)
-
@george1421 The VMware version that we are running is 6.5 Build 5973321
-
@quinniedid OK in my test lab I’m running the build listed in my post. That is with 6.5u1 and the Oct 2017 patch. Point being if I can get a few minutes of time I want to see if I can duplicate what you are seeing to see if VMWare addressed/changed/fixed the issue with a vSphere update. I don’t know one way or the other, but this sounds like a uefi firmware issue to me.