My Oracle Support Banner

OLVM: Importing a Legacy BIOS OVA Fails Due to virt-v2v Recognizes It as UEFI (Doc ID 2797285.1)

Last updated on MARCH 24, 2025

Applies to:

Linux OS - Version Oracle Linux 7.8 with Unbreakable Enterprise Kernel [4.14.35] and later
Information in this document applies to any platform.

Symptoms

A Legacy BIOS VM exported from third party platform as OVA, then import this OVA file into OLVM fails:

The import-<uuid>.log shows error below:
(snip)
libguestfs: trace: v2v: find "/boot/efi/EFI"
libguestfs: trace: v2v: find0 "/boot/efi/EFI" "/tmp/libguestfsAiRBdM/find3.txt"
guestfsd: => glob_expand (0x71) took 0.00 secs
guestfsd: <= find0 (0xc4) request length 60 bytes
guestfsd: error: /boot/efi/EFI: No such file or directory
guestfsd: => find0 (0xc4) took 0.00 secs
libguestfs: trace: v2v: find0 = -1 (error)
libguestfs: trace: v2v: find = NULL (error)
virt-v2v: error: could not find bootloader mount point (/boot/efi/EFI):
find0: /boot/efi/EFI: No such file or directory

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.