Proxmox 4 - No display with kvm virtual machine

G

gizmo15

Member
Sep 20, 2015
12
0
21
Hello,

I installed a first server in proxmox 4 beta1 on a R210 without trouble.

i deploy a second one with the beta 2 and i meet a problem:
when i start a VM and want to see the console, i have this message:

guest has not initialized the display (yet)
Click to expand...

This command is used to launch the VM:
/usr/bin/kvm -id 100 -chardev socket,id=qmp,path=/var/run/qemu-server/100.qmp,server,nowait -mon chardev=qmp,mode=control -vnc unix:/var/run/qemu-server/100.vnc,x509,password -pidfile /var/run/qemu-server/100.pid -daemonize -smbios type=1,uuid=77edddbc-e3d5-4635-a806-cdae922cbbdd -name Debian -smp 1,sockets=1,cores=1,maxcpus=1 -nodefaults -boot menu=on,strict=on,reboot-timeout=1000 -vga cirrus -cpu kvm64,+lahf_lm,+sep,+kvm_pv_unhalt,+kvm_pv_eoi,enforce -m 512 -k fr -device pci-bridge,id=pci.2,chassis_nr=2,bus=pci.0,addr=0x1f -device pci-bridge,id=pci.1,chassis_nr=1,bus=pci.0,addr=0x1e -device piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2 -device usb-tablet,id=tablet,bus=uhci.0,port=1 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3 -iscsi initiator-name=iqn.1993-08.org.debian:01:76d7f7215e -drive file=/mnt/Raid1/images/100/vm-100-disk-1.qcow2,if=none,id=drive-virtio0,cache=writeback,format=qcow2,aio=threads,detect-zeroes=on -device virtio-blk-pci,drive=drive-virtio0,id=virtio0,bus=pci.0,addr=0xa,bootindex=100 -drive file=/var/lib/vz/template/iso/debian-8.2.0-amd64-netinst.iso,if=none,id=drive-ide2,media=cdrom,aio=threads -device ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200 -netdev type=tap,id=net0,ifname=tap100i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on -device virtio-net-pci,mac=D2:E7:E5:C9:A4:C7,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300
Click to expand...

Proxmox is up to date.

Have you an idea of the problem?

thanks
 
I'm also having this issue. My guess is it may be related to update of QEMU 2.4 or the Linux kernel update to 4.2

Proxmox VE 4.0 beta2

Released 10.09.2015: See Downloads

  • based on Debian Jessie 8.2.0
  • Linux kernel 4.2
  • QEMU 2.4
  • LXC improvements Linux Container
    • Containers can be created on local storage, NFS, Ceph RBD, DRBD9, ...
    • Migration (offline)
  • IPv6 support
  • DRBD9
  • Ceph Server packages
  • countless bug fixes and package updates (for all details see bugtracker and GIT)
Proxmox VE 4.0 beta1

Released 22.06.2015: See Downloads

 
"4.0Beta-26/5d4a6l5b" works best for me and I do not know how to get back that particular version. Even downloading the official PVE 4.0 beta1 do not give me that particular version. It installs this version instead - "4.0Beta-16|a7dc5694".
 
with the beta 1 it's ok but you do not need to upgrade because you pass on the beta 2.

I will try to blacklist the kernel and qemu packages to be able to still do the other update packages
 
so it's work ^^

my proxmox is in beta 2 but with the good kernel and the good qemu version.

for that, i create 3 files in /etc/apt/preferences.d/

kernel:
Package: pve-kernel-3.19.8-1-pve
Pin: version 3.19.8-3
Pin-priority: 1001

qemu:
Package: pve-qemu-kvm
Pin: version 2.3-5
Pin-priority: 1001

Package: qemu-server
Pin: version 4.0-12
Pin-priority: 1001

proxmox:
Package: proxmox-ve
Pin: version 4.0-3
Pin-priority: 1001

i update my installation without trouble.
 
gizmo15 said:
so it's work ^^

my proxmox is in beta 2 but with the good kernel and the good qemu version.

for that, i create 3 files in /etc/apt/preferences.d/

kernel:
Package: pve-kernel-3.19.8-1-pve
Pin: version 3.19.8-3
Pin-priority: 1001

qemu:
Package: pve-qemu-kvm
Pin: version 2.3-5
Pin-priority: 1001

Package: qemu-server
Pin: version 4.0-12
Pin-priority: 1001

proxmox:
Package: proxmox-ve
Pin: version 4.0-3
Pin-priority: 1001

i update my installation without trouble.
Click to expand...

Hi... Thanks for post this solution...
Actually, I just found this behavior in an HP Proliant Server, with PVE 4 beta2... With a Dell Server, everything works great...
 
Yeah, running mine on HP Blade server. Maybe only affecting HP servers.
 
Dell R710 same story - Proxmox 4 beta2
(Windows 2012 R2 guest)

root@pve:~# pveversion -v
proxmox-ve: 4.0-13 (running kernel: 4.2.0-1-pve)
pve-manager: 4.0-39 (running version: 4.0-39/ab3cc94a)
pve-kernel-4.2.0-1-pve: 4.2.0-13
lvm2: 2.02.116-pve1
corosync-pve: 2.3.5-1
libqb0: 0.17.2-1
pve-cluster: 4.0-19
qemu-server: 4.0-25
pve-firmware: 1.1-7
libpve-common-perl: 4.0-24
libpve-access-control: 4.0-8
libpve-storage-perl: 4.0-23
pve-libspice-server1: 0.12.5-1
vncterm: 1.2-1
pve-qemu-kvm: 2.4-8
pve-container: 0.9-23
pve-firewall: 2.0-11
pve-ha-manager: 1.0-7
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u1
lxc-pve: 1.1.3-1
lxcfs: 0.9-pve2
cgmanager: 0.37-pve2
criu: 1.6.0-1
zfsutils: 0.6.5-pve1~jessie



Any ideas?
 
You must log in or register to reply here.

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!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

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!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back