VM Migration from Esxi 6.7 to Proxmox - No Bootable Device

[twservices]

Hi! Can someone help me how to resolve my current issue on virtual machine that I imported using importovf. I am just following these steps https://pve.proxmox.com/wiki/Migration_of_servers_to_Proxmox_VE#VMware. However, when I start the newly imported VM on PromoxVE GUI its just giving a loop with an error "No bootable device". Thank you!

https://pve.proxmox.com/wiki/Migration_of_servers_to_Proxmox_VE#VMware

 

[fiona]

Hi,
please check that the bootable drive is selected in the Boot Order setting (in the Options tab of the VM).

 

[twservices]

Yes, it's selected. Please see below. Thank you.

 

[fiona]

What's the output of fdisk -l /dev/mapper/pve-vm--100--disk--0? Does your guest use Windows? If so, there are additional steps mentioned in the article you linked to.

 

[twservices]

My bad..I missed this part. Thank you for your help!!! Its working now

 

[duke8804]

I am having the exact same issue.
I followed the guide at Migration of servers to Proxmox, made sure I did the windows part as well.
Exported from VMware based on those instructions too.

Here is my fdisk output.
I am wondering, if I have to do a thick provision on VMware for it to work. EDIT - Nope I am thick provisioned. View Attached Image.

root@pokey:/dev/mapper# fdisk -l /dev/mapper/pve-vm--100--disk--0
GPT PMBR size mismatch (62560255 != 62562303) will be corrected by write.
The backup GPT table is not on the end of the device.
Disk /dev/mapper/pve-vm--100--disk--0: 29.83 GiB, 32031899648 bytes, 62562304 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes
Disklabel type: gpt
Disk identifier: F6C56812-B557-4625-9101-D26560EE96AA

Device                                   Start      End  Sectors  Size Type
/dev/mapper/pve-vm--100--disk--0-part1    2048   641063   639016  312M Windows recovery environment
/dev/mapper/pve-vm--100--disk--0-part2  643072   847871   204800  100M EFI System
/dev/mapper/pve-vm--100--disk--0-part3  847872  1110015   262144  128M Microsoft reserved
/dev/mapper/pve-vm--100--disk--0-part4 1110016 62558207 61448192 29.3G Microsoft basic data

 

[fiona]

Hi,

I am having the exact same issue.
I followed the guide at Migration of servers to Proxmox, made sure I did the windows part as well.
Exported from VMware based on those instructions too.

Here is my fdisk output.
I am wondering, if I have to do a thick provision on VMware for it to work. EDIT - Nope I am thick provisioned. View Attached Image.

root@pokey:/dev/mapper# fdisk -l /dev/mapper/pve-vm--100--disk--0
GPT PMBR size mismatch (62560255 != 62562303) will be corrected by write.
The backup GPT table is not on the end of the device.
Disk /dev/mapper/pve-vm--100--disk--0: 29.83 GiB, 32031899648 bytes, 62562304 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes
Disklabel type: gpt
Disk identifier: F6C56812-B557-4625-9101-D26560EE96AA

Device                                   Start      End  Sectors  Size Type
/dev/mapper/pve-vm--100--disk--0-part1    2048   641063   639016  312M Windows recovery environment
/dev/mapper/pve-vm--100--disk--0-part2  643072   847871   204800  100M EFI System
/dev/mapper/pve-vm--100--disk--0-part3  847872  1110015   262144  128M Microsoft reserved
/dev/mapper/pve-vm--100--disk--0-part4 1110016 62558207 61448192 29.3G Microsoft basic data

please share your VM config qm config 100 and the output of pveversion -v.

 

[duke8804]

Hi,

please share your VM config qm config 100 and the output of pveversion -v.

PVEVersion

root@pokey:~# pveversion -v
proxmox-ve: 7.1-1 (running kernel: 5.13.19-2-pve)
pve-manager: 7.1-7 (running version: 7.1-7/df5740ad)
pve-kernel-helper: 7.1-6
pve-kernel-5.13: 7.1-5
pve-kernel-5.13.19-2-pve: 5.13.19-4
ceph-fuse: 15.2.15-pve1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve2
libproxmox-acme-perl: 1.4.0
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.1-5
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.0-14
libpve-guest-common-perl: 4.0-3
libpve-http-server-perl: 4.0-4
libpve-storage-perl: 7.0-15
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.11-1
lxcfs: 4.0.11-pve1
novnc-pve: 1.2.0-3
proxmox-backup-client: 2.1.2-1
proxmox-backup-file-restore: 2.1.2-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.4-4
pve-cluster: 7.1-2
pve-container: 4.1-2
pve-docs: 7.1-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.3-3
pve-ha-manager: 3.3-1
pve-i18n: 2.6-2
pve-qemu-kvm: 6.1.0-3
pve-xtermjs: 4.12.0-1
qemu-server: 7.1-4
smartmontools: 7.2-1
spiceterm: 3.2-2
swtpm: 0.7.0~rc1+2
vncterm: 1.7-1
zfsutils-linux: 2.1.1-pve3

100.conf

    IW   /etc/pve/qemu-server/100.conf                                             Row 1    Col 1   
bios: ovmf
boot: order=ide0
cores: 2
ide0: local-lvm:vm-100-disk-0,size=30548M
memory: 8192
name: WS6-Template
smbios1: uuid=d6c7345f-1a5f-4bb7-bd86-aa4e5f62efef
vmgenid: 1b513b8a-a987-4f03-bc96-a62943cc771d