Issues getting disk mounted after importing from vmdk with qm

iopsdd

Member
Jan 25, 2022
7
0
6
I just ran the qm importdisk tool (Followed steps from this article: https://www.itsfullofstars.de/2019/07/import-ova-as-proxmox-vm/ ) to import a vmdk file I exported from a past esxi server. The VM I exported was an encrypted Ubuntu 20.04 machine. I've since changed the disk that is attached to proxmox to the converted file, and edited the VMs boot order. Once I boot the machine I get the normal GUI boot prompt to enter the decryption password. I type the password, It accepts the password and then I simply get a black background with a single white line as if it was expecting a command, but i can't actually type anything - and that just stays there blinking forever. Any thoughts? I'm thinking there's something wrong with the disk/partition setup, but I'm not really sure where to go next.
 
Please provide the output of pveversion -v as well as the VM config (qm config <VMID>).
 
Thanks for the response!

Here is pveversion:

Code:
root@pve:~# 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

And here is qm config 103:
Code:
root@pve:~# qm config 103
boot: order=scsi0;net0;ide2
cores: 1
ide2: none,media=cdrom
memory: 2048
meta: creation-qemu=6.1.0,ctime=1643074073
name: Name
net0: virtio=4E:17:05:A7:30:2A,bridge=vmbr0,firewall=1
numa: 0
ostype: l26
scsi0: local-zfs:vm-103-disk-1,discard=on,size=24G
scsihw: virtio-scsi-pci
smbios1: uuid=f6552802-595f-4577-9786-f9137035089a
sockets: 2
unused0: local-zfs:vm-103-disk-0
vga: std
vmgenid: f7cdd1ec-de1c-417c-916b-a53d657af5b4
 
This VM has a web server that should automatically start on boot, even when this screen is displayed, the webserver is not accessible and the IP of the VM can't be pinged.

After changing to vmware, I get a different output. I get a less-pretty ubuntu GUI, enter the encryption password, and then the display gets stuck here after a few seconds:

Capture.PNG
 
Last edited:
Try IDE and/or SATA instead of SCSI for the disk.
 

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!