04-19-2021 08:08 AM
I've been trying to get a custom Windows 10 and CentOS 8 VM loaded into CML to act as a client and to act as an Ansible server.
I'm building the VM's and exporting the vmdk then converting the vmdk to qcow2 and uploading to cml and creating the node and image.
But when I launch these vm's i get stuck at the bios screen where it's trying to boot the OS from HDD. (see attached)
I'm following David Bombal's video about running Windows 10 VM's in CML.
Solved! Go to Solution.
04-22-2021 06:36 AM
I've found the fix.
If you are going to build a VM in ESXi to be used in CML.
Make sure to do the following.
Edit Settings -> VM Options -> Boot Options
Firmware: BIOS <- By default this is set to EFI
This will allow your VM to be run properly in CML.
04-20-2021 07:18 AM
In my mind this has to do with Secure boot vs Legacy boot. Is this the case here? Does anyone have any ideas?
04-22-2021 06:36 AM
I've found the fix.
If you are going to build a VM in ESXi to be used in CML.
Make sure to do the following.
Edit Settings -> VM Options -> Boot Options
Firmware: BIOS <- By default this is set to EFI
This will allow your VM to be run properly in CML.
12-04-2021 08:31 AM
Hello JPeterson,
I'm facing same problem where I can't create Image definition.
I'm first downloading the ISO from the microsoft and then I create a VM in VMWARE Workstation. When I want to Convert the VMDK to QCOW 2, I end up with 2 VMDK File, -flat.vmdk and .vmdk. When I use either of them in CML I get the error no bootable media same screen as yours. Please lemme know how to make this happen and I'll really appreciate your help.
Thanks in advance!
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide