Cannot create a Windows 11 VM on Ubuntu 22.04

[chribonn]

I installed VMWare 17 and am trying to create a Windows 11 x64 from the ISO I downloaded from Microsoft (Win11_22H2_English_x64v1.iso).

During the new VM configuration is ISO is identified as being Windows 11.

I configure the machine to boot from the ISO.

When I start the VM the CD icon on the status bar has a red cross on it and the machine never boots.  The message log reports "If you have an operating system installation disc, you can insert the disc into the system's CD-ROM drive and restart the virtual machine."  

I am not able to remove the red cross from the CD icon.

Also I'm not able to enter into the the BIOS of the newly created VM.

Thanks

---

Update

I copied a VM I had on a Windows platform and ran it.  It asked whether I moved or copied the VM and I selected copy.

The VM never came up.

[Technogeezer]

What is the configuration of the system you're running Workstation on?

You need to be a bit more specific on what happened. "the machine never boots" or "it never came up" are very vague descriptions.  

Does the boot hang? Does it drop into a PXE boot prompt?

Does the virtual machine configuration meet Windows 11 minimum configurations: TPM, UEFI Securie Boot, 2 CPU, 4GB memory, 64GB virtual hard drive?

Did you verify the checksum of the download ISO file?

[chribonn]

The M/B is ASUS PRIME Z690-P D4  with 64G RAM. Video is from the motherboard.

I tried numerous attempts at creating the VM accepting the defaults, at times exceeding them.

I specify the location of the ISO and VMWare identifies that it is a Windows 11 installation disk.

When I start the VM the ISO file is not load.

I'll uninstall VMWare and reinstall it again.  I'll post screen shots.  I'll post the log.

-----------------------------

I mentioned that I transferred a running VM (Windows 10) from an old computer and even this didn't load.

[chribonn]

Hello

As promised I am sharing my experience, screenshots and logs in the hope that I can resolve this blocking point. Below is some of the output of the sudo lshw.

acb-desktop
    description: Desktop Computer
    product: System Product Name (SKU)
    vendor: ASUS
    version: System Version
    serial: System Serial Number
    width: 64 bits
    capabilities: smbios-3.4.0 dmi-3.4.0 smp vsyscall32
    configuration: boot=normal chassis=desktop family=To be filled by O.E.M. sku=SKU uuid=c4cf9cc2-8627-23a8-30fc-a036bce58196
  *-core
       description: Motherboard
       product: PRIME Z690-P D4
       vendor: ASUSTeK COMPUTER INC.
       physical id: 0
       version: Rev 1.xx
       serial: 220808794600068
       slot: Default string
     *-firmware
          description: BIOS
          vendor: American Megatrends Inc.
          physical id: 0
          version: 1620
          date: 08/13/2022
          size: 64KiB
          capacity: 24MiB
          capabilities: pci upgrade shadowing cdboot bootselect socketedrom edd int13floppynec int13floppytoshiba int13floppy360 int13floppy1200 int13floppy720 int13floppy2880 int5printscreen int14serial int17printer int10video usb biosbootspecification uefi
     *-memory
          description: System Memory
          physical id: 46
          slot: System board or motherboard
          size: 64GiB
     *-cpu
          description: CPU
          product: 13th Gen Intel(R) Core(TM) i7-13700K
          vendor: Intel Corp.
          physical id: 5c
          bus info: cpu@0
          version: 6.183.1
          serial: To Be Filled By O.E.M.
          slot: LGA1700
          size: 3118MHz
          capacity: 5376MHz
          width: 64 bits
          clock: 100MHz
     *-pci
          description: Host bridge
          product: Intel Corporation
          vendor: Intel Corporation
          physical id: 100
          bus info: pci@0000:00:00.0
          version: 01
          width: 32 bits
          clock: 33MHz
        *-display
             description: VGA compatible controller
             product: Intel Corporation
             vendor: Intel Corporation
             physical id: 2
             bus info: pci@0000:00:02.0
             logical name: /dev/fb0
             version: 04
             width: 64 bits
             clock: 33MHz
             capabilities: pciexpress msi pm vga_controller bus_master cap_list rom fb
             configuration: depth=32 driver=i915 latency=0 mode=1920x1080 resolution=1920,1080 visual=truecolor xres=1920 yres=1080
             resources: iomemory:600-5ff iomemory:400-3ff irq:193 memory:6002000000-6002ffffff memory:4000000000-400fffffff ioport:6000(size=64) memory:c0000-dffff memory:4010000000-4016ffffff memory:4020000000-40ffffffff
        *-pci:0
             description: PCI bridge
             product: Intel Corporation
             vendor: Intel Corporation
             physical id: 6
             bus info: pci@0000:00:06.0
             version: 01
             width: 32 bits
             clock: 33MHz
             capabilities: pci pciexpress msi pm normal_decode bus_master cap_list
             configuration: driver=pcieport
             resources: irq:122 memory:85600000-856fffff
           *-nvme
                description: NVMe device
                product: Samsung SSD 980 PRO 2TB
                vendor: Samsung Electronics Co Ltd
                physical id: 0
                bus info: pci@0000:01:00.0
                logical name: /dev/nvme0
                version: 5B2QGXA7
                serial: S69ENX0TA28269Z
                width: 64 bits
                clock: 33MHz
                capabilities: nvme pm msi pciexpress msix nvm_express bus_master cap_list
                configuration: driver=nvme latency=0 nqn=nqn.1994-11.com.samsung:nvme:980PRO:M.2:S69ENX0TA28269Z state=live
                resources: irq:16 memory:85600000-85603fff

I uninstalled VMWare, redownloaded and installed again.  The installation appears to have gone OK.

I created a new VM. I went with the typical option and always exceeded the minimum suggested by VMWare. 

The source was the ISO of Windows 11 x 64 sourced from Microsoft. Before attempting to install I mounted it without any issues. I set the CD as being the ISO and VMWare detected that this was Windows 11 x64. 

After clicking the Finish nothing happened. I noticed that the icon for the CD had a red X on it. After a minute I got a message that no OS could be found.

I'm including the vmware log.

@Technogeezer could it be that the Intel 500 Chipset on this M/Board will not boot in UEFI with CSM when the video is the one on board?  This is because chipset does not support UEFI VBIOS graphic card, hence the integrated graphics mode does not support legacy boot and CSM option becomes non-configurable.

If that is the case can you maybe guide me on how to circumvent this,

Thanks

[chribonn]

Hi,

Are there others who have a similar problem.

Thanks

[chribonn]

I don't know whether VMWare is popular and used by Ubuntu users since I come from Windows. 

It would be helpful to establish whether people running Ubuntu 22.04 and VMWare 17 are able to boot from Windows ISOs in order to set up the guest VM.

I know that there are other virtualisation products popular with Ubuntu community but would like avoid having to port over VMs I've accumulated over the years (Windows 3.1, etc).

Thanks

[chribonn]

I created a video of the process I experience when I try to create a Windows 7 Guest on the Linux host.  

The boot drive is never detected and therefore there is no boot process from it.

Being new to VMWare on Linux I don't know if this is standard behaviour.

Is there a way to escalate the topic to someone more technical?

Thanks

[chribonn]

I can confirm that VMWare 17 for Windows (running on top of Windows 11) works.  The hardware is the exact hardware used on Linux.

The BIOS screen appears and the ISO boot works.