Migrating vm from esxi to pve: getting blank console screen

Oct 1, 2021
4
1
1
54
I migrated a ubuntu vm from esxi7 to pve using "qm importovf".

The vm actually started and I was able to ssh into it, everything seems to be working as expected, but the console screen is completely black, thus I can't logon to the vm via the console.

I have tried changing the display types etc to no avail.

Your help is greatly appreciated.
 
  • Like
Reactions: meichthys
Can you post the VMs config? qm config <vmid>
 
Hello, thanks for the response!
Here is the config:

-------------------
root@freedom-only:~# qm config 102
agent: 1,fstrim_cloned_disks=1
boot: order=scsi0
cores: 24
memory: 51200
name: miyakowasure
net0: virtio=16:65:2B:B4:DF:5C,bridge=vmbr8,firewall=1
net1: virtio=46:B8:56:D9:5A:D5,bridge=vmbr0,firewall=1
numa: 0
onboot: 1
scsi0: local-zfs:vm-102-disk-0
scsi1: bordata:vm-102-bordata-clone
scsihw: virtio-scsi-pci
smbios1: uuid=23413204-5ed4-4176-93ba-68145d693546
sockets: 1
vga: qxl
vmgenid: e4f52138-84f6-478b-a384-d2cf3523e702
----------------------------

Btw, this is only console problem, as the vm itself is up and running well.
I have tried other type of display like default, std, vmware compatible, spice, nothing worked.

The qemu-guest-agent is running in the vm. "qm agent 102 ping" returns nothing which means the agent is running fine.
Please let me know what you find out or would suggest.

-antony
 
@vklabs Did you ever find a solution? I'm experiencing the same issue. I can SSH into the VM without any issues and the Proxmox logo shows in the console when rebooting the VM, but after displaying "Connected (encrypted) to QEMU (nextcloud)" it goes to a blank/black screen. I do see the following in the browser console after trying to connect to the console:
`Error: n is undefined`
I've tried other browsers without any difference.
I've also tried using xjterm. It says "Starting serial terminal on interface serial0" but then doesn't get any further.
blank_screen.png
options.png
 
Last edited:
Try to boot with IDE HDD
or
boot the VM with rescue CD
mount root,/sys/, /dev/, /proc/ with all subdirectories to /mnt/
chroot /mnt
remove vmware tools
check bootloader options
Look for kernel parameters
reinstall bootloader
update bootloader config
exit chroot and reboot
If you see bootloader now, than you can change kernel parameters for you needs
 

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!