ISO file downloaded, VM keeps showing errors when running

Installation
1

image
image840×282 1.99 KB
After downloading the ISO file, configure the virtual machine and an error occurs when running.

2

What virtual machine are you using? It seems the ISO image is not mounted, or it’s mounted but the first boot priority is not set to CD-ROM, causing the system to proceed with the PXE network installation process instead.

3

VMware Workstation Pro

4

Below is the flowchart for creating a new virtual machine. After completion, the system immediately throws an error. The ISO image was downloaded and its hash value was verified to be identical.

image
image815×693 47.8 KB

image
image713×674 22.1 KB

image
image710×567 21.5 KB

image
image710×567 11.9 KB

image
image710×567 9.8 KB

image
image710×567 6.29 KB

image
image710×567 17.6 KB

image
image710×567 21.1 KB

image
image710×567 13 KB

image
image710×567 8.85 KB

image
image710×567 20.4 KB

image
image710×567 22.8 KB

image
image710×567 10.1 KB

image
image710×657 20.4 KB

5

Check if everything here is selected:

image
image1388×1513 99.3 KB

7

Selected

8

image
image1061×1229 35.8 KB

9

你的宿主机是什么架构，我看你用的是 aarch64 架构的镜像：

image
image1231×172 51.9 KB

10

I created it on my own Windows computer using a VM virtual machine.

11

That won’t work; Windows is x86_64 architecture, so the virtual machine installed can only be x86_64 architecture as well.

12

OK, got it.

13

The content is AI-generated and for reference only:

:pushpin: Summary

Root Cause Solution
ISO not mounted or not enabled Correctly mount the ISO and check “Connect at power on”
Incorrect boot order Set CD-ROM as the first boot device in BIOS/UEFI
Using a debug version ISO Switch to the standard DVD ISO image
Network boot interference Disable PXE or use Host-only network
Click here to view detailed analysis and solution

Troubleshooting “Operating System not found” Error During Virtual Machine Boot

You encountered the following error when configuring and running an openEuler virtual machine using VMware Workstation Pro:

Network boot from Intel E1000
Copyright (C) 2003-2021 VMware, Inc.
Copyright (C) 1997-2000 Intel Corporation
CLIENT MAC ADDR: 00 BC 29 0A 3C BD  GUID: 564D2E36-FE14-8333-661B-73B5330A3CBD
PXE-E53: No boot filename received
PXE-M0F: Exiting Intel PXE ROM.
Operating System not found

This error indicates that the virtual machine failed to boot from the ISO image and instead attempted network boot (PXE) — which failed — resulting in the “Operating System not found” message. Below is a detailed analysis and step-by-step resolution.

:magnifying_glass_tilted_left: Problem Analysis

Based on the provided knowledge graph and user discussion, the following points are clear:

  1. Core Issue: PXE Network Boot Failure

    • PXE-E53: No boot filename received means the virtual machine’s network adapter (Intel E1000) tried to perform a network boot (PXE), but did not receive a boot filename from a DHCP/TFTP server.
    • PXE-M0F: Exiting Intel PXE ROM indicates the PXE boot process has terminated.
    • The final Operating System not found occurs because neither a valid operating system nor a properly mounted installation medium was detected.

  2. Root Cause: ISO Not Set as Primary Boot Device

    • Despite having downloaded the ISO and configured the VM, the system did not boot from the optical drive but instead prioritized network boot.
    • This typically happens due to:
      • The ISO image not being correctly mounted to the virtual CD/DVD drive;
      • Incorrect boot order settings, with CD-ROM not set as the first boot device;
      • Using UEFI mode (EFI) without proper configuration.

  3. Support Evidence

    • As noted by user yanzhicong: “It seems the ISO image was not mounted, or it was mounted but the first boot order is not the optical drive, so the PXE network installation process was triggered.”
    • The Intel E1000 is a VMware virtual NIC that supports network booting. Without a valid PXE server, this leads to the PXE-E53 error.
    • The Use EFI option being enabled suggests UEFI boot mode is used, so ensure the ISO supports UEFI.

:white_check_mark: Solutions

Follow these steps in order to resolve the issue:

:white_check_mark: Step 1: Confirm ISO is Correctly Mounted

  1. Open the virtual machine settings in VMware Workstation.
  2. Select the CD/DVD (IDE) device.
  3. Check “Use ISO image file”, then browse and select your downloaded openEuler ISO (e.g., openEuler-22.03-LTS-x86_64-dvd.iso).
  4. Ensure both “Connect at power on” and “Connect” are checked.

:warning: Note: Some ISO versions (e.g., debug.iso) may lack critical components (like grub2, lvm2). Use the standard DVD version instead.

:white_check_mark: Step 2: Fix Boot Order (BIOS/UEFI Settings)

Method 1: Set Boot Order in VMware BIOS

  1. Start the virtual machine and immediately press F2 to enter BIOS Setup (or ESC for UEFI boot menu).
  2. Go to the Boot tab.
  3. Move CD-ROM Drive or DVD-ROM Drive to the top of the boot order list.
  4. Save and exit (usually F10).

If using UEFI mode (Use EFI enabled), press Esc at startup to access the UEFI boot menu and select “EFI DVD-ROM”.

Method 2: Set ISO as Installation Source During VM Creation

  • During the “Install guest operating system” step:
    • Choose “Installer disc image file (iso)”;
    • Point to the correct ISO path;
    • Select guest OS as Linux > Other Linux 4.x/5.x kernel 64-bit;
    • Recommended: Uncheck “Install operating system later”.

:white_check_mark: Step 3: Verify ISO File Integrity

Ensure the downloaded ISO is not corrupted:

  1. Obtain the official MD5 checksum from the openEuler official mirror site.
  2. Calculate the MD5 hash of your local ISO file using a tool:
    md5sum openEuler-*.iso
  3. Compare the output with the official value.

:magnifying_glass_tilted_right: As emphasized by user xnlu, always verify ISO integrity via MD5.

:white_check_mark: Step 4: Avoid Using Debug Version ISOs

  • The error log suggests you may be using a debug ISO such as:
    openEuler-22.03-LTS-SP1-everything-debug-x86_64-dvd.iso
  • Debug ISOs are not suitable for direct installation and may lack essential packages.
  • :white_check_mark: Replace it with the standard installation version:
    openEuler-22.03-LTS-SP1-x86_64-dvd.iso

:white_check_mark: Step 5: Optional — Disable Network Boot

If you do not intend to use PXE installation:

  1. In VMware settings, go to Network Adapter.
  2. Change the network connection mode to NAT or Host-only (to prevent bridge mode from triggering PXE).
  3. Or, in BIOS, disable the Network Boot option.

:hammer_and_wrench: Recommended Configuration Example (VMware + openEuler)

Item Recommended Setting
Virtual Machine Software VMware Workstation Pro 17.x
OS Type Linux
Version Other Linux 5.x kernel 64-bit
ISO Mount :white_check_mark: Enabled, with “Connect at power on” checked
Boot Order CD-ROM before Hard Drive
Firmware Type UEFI (recommended) or BIOS
Memory ≥ 4096 MB
CPU ≥ 2 cores
Disk ≥ 32 GB

:pushpin: Summary

Root Cause Solution
ISO not mounted or not enabled Correctly mount ISO and check “Connect at power on”
Incorrect boot order Set CD-ROM as first boot device in BIOS/UEFI
Using debug ISO Switch to standard DVD ISO image
Network boot interference Disable PXE or use Host-only network

:white_check_mark: Final Recommended Steps

  1. Download the standard openEuler ISO (e.g., openEuler-22.03-LTS-x86_64-dvd.iso);
  2. Verify its MD5 checksum to ensure integrity;
  3. Create a new virtual machine and specify the ISO as the installation source;
  4. Boot the VM and press F2 to enter BIOS, then set CD-ROM as the first boot device;
  5. Successfully enter the installation interface.

If the issue persists, please provide your virtual machine’s hardware configuration screenshot and the full ISO filename for further diagnosis.