Need some help booting about openwrt_arm64_uefi HOT 10 CLOSED

This is what I do.

gunzip -d openwrt-arm64-efi-generic-ext4-combined.vmdk.gz
qemu-img convert -f vmdk openwrt-arm64-efi-generic-ext4-combined.vmdk -O qcow2 openwrt-arm64-efi-generic-ext4-combined.qcow2
qm importdisk 105 openwrt-arm64-efi-generic-ext4-combined.qcow2 local

from openwrt_arm64_uefi.

This is me, it seems the same?!?! no?!

from openwrt_arm64_uefi.

This is what I do.

gunzip -d openwrt-arm64-efi-generic-ext4-combined.vmdk.gz
qemu-img convert -f vmdk openwrt-arm64-efi-generic-ext4-combined.vmdk -O qcow2 openwrt-arm64-efi-generic-ext4-combined.qcow2
qm importdisk 105 openwrt-arm64-efi-generic-ext4-combined.qcow2 local

I finally got it working. My problem was due to my novice Proxmox skills. It is necessary to double click the added disk in the Hardware menu and press 'Add' from there. I was only highlighting the added disk and using the 'Add' in the menu-bar.

I will note that my disk is not the same size as yours even though I followed your above command example. Any idea why that would be? Mine is 1.1GB and yours over 2GB.

Thanks for your help on this, I hope this thread can help others.

from openwrt_arm64_uefi.

I dont have my pimox On at the moment but one think I remember is that I used the vmdk with convert and import tricks.
I found this... on my notes but Im not sure if did any other trick. Please test and report back and Ill boot my Pi to help you.

First "qemu-img convert" to raw then "qm importdisk ${vm_id} ${vmdisk_name} ${storage}"

from openwrt_arm64_uefi.

Thanks for looking at this with me. Here are the commands I am using from the PiMox console:

I created a VM with OVMF BIOS and 64M EFI disk.
Delete the CDROM drive.

wget https://github.com/varoudis/openwrt_arm64_uefi/releases/download/working_image_01/openwrt-arm64-efi-generic-ext4-combined.img.gz
gunzip -d openwrt-arm64-efi-generic-ext4-combined.img.gz
qemu-img create openwrt-arm64-efi-generic-ext4-combined.img 2G
qm importdisk 101 openwrt-arm64-efi-generic-ext4-combined.img local

Then in the VM I attach the created disk to the Virti IO SCSI controller and change the boot order to boot from new disk.

At start the VM console shows me being dumped into the UEFI interactive shell and nothing happens.

If you have a screen shot of your hardware settings that would be great to see.

from openwrt_arm64_uefi.

No, use the "vmdk" file!
Convert it to raw and then import. Not the IMG file.

from openwrt_arm64_uefi.

Thanks for your ideas but no change. Below are my settings and console screen.
Can you post your Hardware configuration screen shot?

from openwrt_arm64_uefi.

This is me, it seems the same?!?! no?!

Thanks for this info; I set the processor type to HOST during VM setup and then also found a few really useful things here:

• use the VMDK
• Add a serial device and set the display to serial0
• I had to edit the /etc/pve/qemu-server/{ID}.conf file to attach the disk as scsi0
• Edit the boot order so the attached drive is bootable and first
• Remove the IDE drive

from openwrt_arm64_uefi.

@varoudis Can you also share your /etc/config/network settings? I get DHCP, but I don't think it's routing any of my traffic out of the 'br-lan'.

from openwrt_arm64_uefi.

@cvocvo I dont have pimox around me at the moment. I havent done anything spacial as I run openwrt in a VM and it does all the routing for Pimox and all the VM/CTs.

from openwrt_arm64_uefi.