[SOLVED] Migration ESXI to Proxmox => No bootable device

Oct 28, 2020
32
2
13
36
Bayreuth
Hi,

I migrate a VM from ESXI to Proxmox with these steps:

Bash:
qm importovf 100 SVDCBAY002.ovf PURELVM

Then I edit the CPU settings:

Bash:
qm set 100 --cpu x86-64-v2-AES --scsihw virtio-scsi-single
I added a network card, detached the disk and readded it with IDE as BUS.
I still get the "No bootable device" error.

100.conf
Bash:
root@PROX-WIN-01:~/DC# cat /etc/pve/qemu-server/100.conf
boot: order=ide0
cores: 4
cpu: x86-64-v2-AES
ide0: PURELVM:vm-100-disk-0,cache=writeback,discard=on,size=90G,ssd=1
ide2: local-btrfs:iso/virtio-win.iso,media=cdrom,size=612812K
memory: 8192
name: SVDCBAY002
net0: virtio=BC:24:11:B7:AA:36,bridge=vmbr0,firewall=1,tag=101
scsihw: virtio-scsi-single
smbios1: uuid=4337ea0f-0c03-4687-8c96-9538161bfc8d
vmgenid: 747f0f80-53ee-4238-a2a8-aea6886a5ee0

pveversion -v
Bash:
proxmox-ve: 8.2.0 (running kernel: 6.8.8-3-pve)
pve-manager: 8.2.4 (running version: 8.2.4/faa83925c9641325)
proxmox-kernel-helper: 8.1.0
proxmox-kernel-6.8: 6.8.8-3
proxmox-kernel-6.8.8-3-pve-signed: 6.8.8-3
proxmox-kernel-6.8.4-2-pve-signed: 6.8.4-2
ceph-fuse: 17.2.7-pve3
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx9
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-4
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.1
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.3
libpve-access-control: 8.1.4
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.0.7
libpve-cluster-perl: 8.0.7
libpve-common-perl: 8.2.1
libpve-guest-common-perl: 5.1.3
libpve-http-server-perl: 5.1.0
libpve-network-perl: 0.9.8
libpve-rs-perl: 0.8.9
libpve-storage-perl: 8.2.3
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 6.0.0-1
lxcfs: 6.0.0-pve2
novnc-pve: 1.4.0-3
proxmox-backup-client: 3.2.7-1
proxmox-backup-file-restore: 3.2.7-1
proxmox-firewall: 0.4.2
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.2.3
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.6
proxmox-widget-toolkit: 4.2.3
pve-cluster: 8.0.7
pve-container: 5.1.12
pve-docs: 8.2.2
pve-edk2-firmware: 4.2023.08-4
pve-esxi-import-tools: 0.7.1
pve-firewall: 5.0.7
pve-firmware: 3.13-1
pve-ha-manager: 4.0.5
pve-i18n: 3.2.2
pve-qemu-kvm: 9.0.0-6
pve-xtermjs: 5.3.0-3
qemu-server: 8.2.2
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.4-pve1
 
Last edited:
Hello, did you try to change from ide to sata aswell? Please try and post again, after booting successfully youll need to temporarily add a virtio-scsi disk, install the driver in windows, poweroff, remove the temporary disk and switch the bootdisk from sata to scsi0 and boot again.
 
Same behavior:

Bash:
boot: order=scsi0
cores: 4
cpu: x86-64-v2-AES
ide2: local-btrfs:iso/virtio-win.iso,media=cdrom,size=612812K
memory: 8192
name: SVDCBAY002
net0: virtio=BC:24:11:B7:AA:36,bridge=vmbr0,firewall=1,tag=101
scsi0: PURELVM:vm-100-disk-0,cache=writeback,discard=on,iothread=1,size=90G,ssd=1
scsihw: virtio-scsi-single
smbios1: uuid=4337ea0f-0c03-4687-8c96-9538161bfc8d
vmgenid: 747f0f80-53ee-4238-a2a8-aea6886a5ee0
 
Last edited:
Same behavior:

Bash:
boot: order=scsi0
cores: 4
cpu: x86-64-v2-AES
ide2: local-btrfs:iso/virtio-win.iso,media=cdrom,size=612812K
memory: 8192
name: SVDCBAY002
net0: virtio=BC:24:11:B7:AA:36,bridge=vmbr0,firewall=1,tag=101
scsi0: PURELVM:vm-100-disk-0,cache=writeback,discard=on,iothread=1,size=90G,ssd=1
scsihw: virtio-scsi-single
smbios1: uuid=4337ea0f-0c03-4687-8c96-9538161bfc8d
vmgenid: 747f0f80-53ee-4238-a2a8-aea6886a5ee0
You do not have sata enabled. try to boot with sata0: PURELVM:vm-100-disk-0,cache=writeback,discard=on,iothread=1,size=90G,ssd=1
Make sure this works, if this works, process with my instructions above.
 
Same thing:

Bash:
root@PROX-WIN-01:~# cat /etc/pve/qemu-server/100.conf
boot: 
cores: 4
cpu: x86-64-v2-AES
ide2: local-btrfs:iso/virtio-win.iso,media=cdrom,size=612812K
memory: 8192
name: SVDCBAY002
net0: virtio=BC:24:11:B7:AA:36,bridge=vmbr0,firewall=1,tag=101
onboot: 1
sata0: PURELVM:vm-100-disk-0,cache=writeback,discard=on,size=90G,ssd=1
scsihw: virtio-scsi-single
smbios1: uuid=4337ea0f-0c03-4687-8c96-9538161bfc8d
vmgenid: 747f0f80-53ee-4238-a2a8-aea6886a5ee0
 
Was this a legacy (bios) vm or uefi? If uefi try: qm set 100 --bios ovmf
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!