Guest has not initialized the display (yet)

Hi,

I'm not using the latest version. I saw problems with lxc and network, so I've decided to wait...

proxmox-ve: 5.1-26 (running kernel: 4.13.4-1-pve)
pve-manager: 5.1-36 (running version: 5.1-36/131401db)
pve-kernel-4.13.4-1-pve: 4.13.4-26
pve-kernel-4.10.17-4-pve: 4.10.17-24
pve-kernel-4.10.17-3-pve: 4.10.17-23
libpve-http-server-perl: 2.0-6
lvm2: 2.02.168-pve6
corosync: 2.4.2-pve3
libqb0: 1.0.1-1
pve-cluster: 5.0-15
qemu-server: 5.0-17
pve-firmware: 2.0-3
libpve-common-perl: 5.0-20
libpve-guest-common-perl: 2.0-13
libpve-access-control: 5.0-7
libpve-storage-perl: 5.0-16
pve-libspice-server1: 0.12.8-3
vncterm: 1.5-2
pve-docs: 5.1-12
pve-qemu-kvm: 2.9.1-2
pve-container: 2.0-17
pve-firewall: 3.0-3
pve-ha-manager: 2.0-3
ksm-control-daemon: 1.2-2
glusterfs-client: 3.8.8-1
lxc-pve: 2.1.0-2
lxcfs: 2.0.7-pve4
criu: 2.11.1-1~bpo90
novnc-pve: 0.6-4
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.7.3-pve1~bpo9
ceph: 12.2.1-pve3
 
you should upgrade at least the kernel.

e.g . pve-kernel-4.13.8-3-pve (or pve-kernel-4.13.8-2-pve)
 
Hi,

I just updated the cluster with kernel 4.13.8-3.
Wait and see.

But I don't know why the kernel should be involved. Seems that bug may be related to qemu instead ?
 
Hi,

did it helped? I have a single node cluster with some windows server 2016 instances on it. Backup somtimes hangs the qemu in stop mode (after succesfull backup).

regards
andy
 
Hi, yesterday I installed a new supermicro server with 64G of ram with latst proxmox 5.
As of now there's only a windows 2012 R2 guest with 48G of ram.
As storage backend it's using SCSI (virtio).
I installed the latest virtio driver available (0.1.141) and qemu guest agent.
I have a script that
- shut down the guest by 'qm shutdown 100'
- create and mount a snapshot
- copy some data
- unmount and remove snapshot
- start again the guest by 'qm start 100'.

Once again I get windows blue screen posted previously in this topic.
 
Valerio Pachera said:
Hi, yesterday I installed a new supermicro server with 64G of ram with latst proxmox 5.
As of now there's only a windows 2012 R2 guest with 48G of ram.
As storage backend it's using SCSI (virtio).
I installed the latest virtio driver available (0.1.141) and qemu guest agent.
I have a script that
- shut down the guest by 'qm shutdown 100'
- create and mount a snapshot
- copy some data
- unmount and remove snapshot
- start again the guest by 'qm start 100'.

Once again I get windows blue screen posted previously in this topic.
Click to expand...

please post the full output of "pveversion -v" and the complete blue screen info.
 
Code: 
proxmox-ve: 5.1-25 (running kernel: 4.13.4-1-pve)
pve-manager: 5.1-35 (running version: 5.1-35/722cc488)
pve-kernel-4.13.4-1-pve: 4.13.4-25
libpve-http-server-perl: 2.0-6
lvm2: 2.02.168-pve6
corosync: 2.4.2-pve3
libqb0: 1.0.1-1
pve-cluster: 5.0-15
qemu-server: 5.0-17
pve-firmware: 2.0-3
libpve-common-perl: 5.0-20
libpve-guest-common-perl: 2.0-13
libpve-access-control: 5.0-7
libpve-storage-perl: 5.0-16
pve-libspice-server1: 0.12.8-3
vncterm: 1.5-2
pve-docs: 5.1-12
pve-qemu-kvm: 2.9.1-2
pve-container: 2.0-17
pve-firewall: 3.0-3
pve-ha-manager: 2.0-3
ksm-control-daemon: 1.2-2
glusterfs-client: 3.8.8-1
lxc-pve: 2.1.0-2
lxcfs: 2.0.7-pve4
criu: 2.11.1-1~bpo90
novnc-pve: 0.6-4
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.7.2-pve1~bpo90

I can't stop the vm because it's on production right now.
 
Please always upgrade to latest version. You run an outdated version with a kernel triggering bluescreens on windows.

your version:
> proxmox-ve: 5.1-25 (running kernel: 4.13.4-1-pve)

latest kernel:
> proxmox-ve: 5.1-35 (running kernel: 4.13.13-4-pve)

For a detailed upgrade guide, please read our documentation.
 
You must log in or register to reply here.
Top Bottom