Qemu launch is showing the error "failed to load Boot0003"

[ptsarath]

Tried the qemu launch after the flash and it was throwing an error as below and its fall back to the "shell>".

`BdsDxe: failed to load Boot0003 "UEFI QEMU HARDDISK QM00001 " from PciRoot(0x0)/Pci(0x1,0x1)/Ata(Primary,Master,0x0): Not Found
BdsDxe: failed to load Boot0001 "UEFI QEMU DVD-ROM QM00003 " from PciRoot(0x0)/Pci(0x1,0x1)/Ata(Secondary,Master,0x0): Not Found

iPXE 1.0.0+git-20190125.36a4c85-5.1 -- Open Source Network Boot Firmware -- http://ipxe.org
Features: DNS HTTP iSCSI NFS TFTP AoE EFI Menu

net0: 52:54:00:12:34:56 using 82540em on 0000:00:03.0 (open)
[Link:up, TX:0 TXE:0 RX:0 RXE:0]
Configuring (net0 52:54:00:12:34:56)...... ok
net0: 10.0.2.15/255.255.255.0 gw 10.0.2.2
net0: fec0::5054:ff:fe12:3456/64 gw fe80::2
net0: fe80::5054:ff:fe12:3456/64
Nothing to boot: No such file or directory (http://ipxe.org/2d03e18e)

BdsDxe: failed to load Boot0004 "UEFI PXEv4 (MAC:525400123456)" from PciRoot(0x0)/Pci(0x3,0x0)/MAC(525400123456,0x1): Not Found

Start PXE over IPv4.
PXE-E16: No valid offer received.
BdsDxe: failed to load Boot0005 "UEFI PXEv4 (MAC:525400123456) 2" from PciRoot(0x0)/Pci(0x3,0x0)/MAC(525400123456,0x1)/IPv4(0.0.0.0,0x0,DHCP,0.0.0.0,0.0.0.0,0.0.0.0): Not Found

Start HTTP Boot over IPv4.....
Error: Could not retrieve NBP file size from HTTP server.

Error: Server response timeout.
BdsDxe: failed to load Boot0006 "UEFI HTTPv4 (MAC:525400123456)" from PciRoot(0x0)/Pci(0x3,0x0)/MAC(525400123456,0x1)/IPv4(0.0.0.0,0x0,DHCP,0.0.0.0,0.0.0.0,0.0.0.0)/Uri(): Not Found
BdsDxe: loading Boot0007 "EFI Internal Shell" from Fv(7CB8BDC9-F8EB-4F34-AAEA-3EE4AF6516A1)/FvFile(7C04A583-9E3E-4F1C-AD65-E05268D0B4D1)
BdsDxe: starting Boot0007 "EFI Internal Shell" from Fv(7CB8BDC9-F8EB-4F34-AAEA-3EE4AF6516A1)/FvFile(7C04A583-9E3E-4F1C-AD65-E05268D0B4D1)
UEFI Interactive Shell v2.2
EDK II
UEFI v2.70 (EDK II, 0x00010000)
Mapping table
FS0: Alias(s):HD1a0b:;BLK3:
PciRoot(0x0)/Pci(0x1,0x2)/USB(0x0,0x0)/HD(1,GPT,68620F3A-C6F6-4A80-89EE-16AEF3B58D8E,0x800,0x80C0)
FS1: Alias(s):HD1a0c:;BLK4:
PciRoot(0x0)/Pci(0x1,0x2)/USB(0x0,0x0)/HD(2,GPT,2413153C-3FF9-4D6D-B219-E057822472E5,0x9000,0x10020)
FS2: Alias(s):HD1a0d:;BLK5:
PciRoot(0x0)/Pci(0x1,0x2)/USB(0x0,0x0)/HD(3,GPT,3ECD09B0-A8BB-435E-947E-BED2C31AC64D,0x19800,0x10020)
BLK0: Alias(s):
PciRoot(0x0)/Pci(0x1,0x1)/Ata(0x0)
BLK1: Alias(s):
PciRoot(0x0)/Pci(0x1,0x1)/Ata(0x0)
BLK2: Alias(s):
PciRoot(0x0)/Pci(0x1,0x2)/USB(0x0,0x0)
BLK6: Alias(s):
PciRoot(0x0)/Pci(0x1,0x2)/USB(0x0,0x0)/HD(4,GPT,FEDCBA98-7654-3210-CAFE-5E0710000001,0x2A000,0x200000)
BLK7: Alias(s):
PciRoot(0x0)/Pci(0x1,0x2)/USB(0x0,0x0)/HD(5,GPT,FEDCBA98-7654-3210-CAFE-5E0710000002,0x22A000,0x200000)
BLK8: Alias(s):
PciRoot(0x0)/Pci(0x1,0x2)/USB(0x0,0x0)/HD(6,GPT,D0663272-F7F8-458B-ACFE-62B3BC24AC89,0x42A000,0x299998)
BLK9: Alias(s):
PciRoot(0x0)/Pci(0x1,0x2)/USB(0x0,0x0)/HD(7,GPT,B5D059A1-1047-4DA9-86A6-183066DD3BE9,0x6C4000,0x533332)
Shell> SC in 1 seconds to skip startup.nsh or any other key to continue.`

Have tried the below steps for reproducing it.

`KVM support via MTDA

let's stop mtda so we can create larger disk images

$ sudo systemctl stop mtda

let's now create blank disk images

$ sudo install -m 0755 -d /var/lib/mtda
$ sudo dd if=/dev/zero of=/var/lib/mtda/usb-shared-storage.img bs=1G count=16
$ sudo dd if=/dev/zero of=/var/lib/mtda/ssd.img bs=1G count=32

restart mtda

$ sudo systemctl start mtda

Installing KVM on Debian
$ sudo apt install qemu-kvm

The user running the MTDA agent should be added to the kvm group:
$ sudo addgroup $USER kvm

#mtda-kvm may be installed as follows:

$ sudo apt-get install mtda-kvm
$ sudo mkdir -p /etc/mtda/
$ sudo cp /usr/share/doc/mtda-kvm/examples/qemu.ini /etc/mtda/config

check if qemu was properly started

$ sudo journalctl -u mtda|tail -n 5

write my installer image to the shared storage device

$ mtda-cli target off
$ mtda-cli storage host
$ mtda-cli storage write service-stick.iso

configure virtual target to boot from USB

$ mtda-cli storage target
$ mtda-cli setenv boot-from-usb 1

power virtual target

$ mtda-cli target on

interactive console

$ mtda-cli`

[chombourger]

Many thanks for all the details. One question though: on which Debian/Ubuntu distro was this tried on?

[ptsarath]

@chombourger have tried on debian bullseye.