How to Fix “No Bootable Device Found” Error in PNETLab for QEMU Images

Updated On:

If you’re working with PNETLab (PnetLAB) and encountering the “No Bootable Device Found” error when booting a QEMU image, don’t worry—you’re not alone. This issue is often due to incorrect image or folder naming. Fortunately, it can be quickly fixed by following the proper naming conventions for QEMU images.

Why Does the “No Bootable Device Found” Error Happen?

The “No Bootable Device Found” error typically occurs in PNETLab when the image folder name or the image file name does not match the required naming structure. When PNETLab attempts to boot a virtual machine (VM), it looks for a specific folder and image file structure to locate the bootable file. If this structure is incorrect, the image won’t boot.

How to Fix the Error

To resolve the issue, you need to ensure that both the folder name and the image file name match the required format specified by PNETLab for QEMU images. You can refer to this official documentation for the correct folder and image naming conventions.

Step-by-Step Fix with Example

Let’s walk through an example where you’re trying to boot a Windows 10 virtual machine in PNETLab and you get the “No Bootable Device Found” error.

  1. Correct Folder Naming:
    • For a Windows 10 machine, the folder name should be named correctly to ensure PNETLab can locate it.
    • Example folder name: win-10
    • The folder should be placed in the correct directory within your PNETLab setup.
  2. Correct Image Naming:
    • Inside the win-10 folder, the actual disk image file should follow the proper naming convention.
    • Example image name: hda.qcow2
    • This is the primary image file that PNETLab will use to boot the Windows 10 VM.

If you don’t follow the naming convention, PNETLab will fail to locate the boot file, and you’ll see the “No Bootable Device Found” error.

Folder and Image Naming Example for Windows 10 VM

  • Folder Name: win-10
  • Image File Name: hda.qcow2

Make sure that the image file inside the folder is named hda.qcow2, as this is the file that PNETLab will try to boot from. Similarly, the folder name should be set correctly (win-10 in this case) according to the VM version.

Conclusion

In PNETLab, if you encounter the “No Bootable Device Found” error, it’s most likely due to incorrect folder or image naming. By following the correct QEMU image naming conventions—like ensuring the folder is named win-10 and the image is hda.qcow2 for a Windows 10 VM—you can resolve the issue and boot the image successfully. For more details and naming examples, check the official naming documentation.

With the right configuration, you’ll have your VM up and running smoothly in no time!

Follow Us On

Leave a Comment