VNC Stopped Working On Eve-ng Vm After The Upgrade Of Proxmox ...

• Home
• Forums New posts Search forums
• What's new Featured content New posts Latest activity
• Members Current visitors New profile posts Search profile posts

Log in Register What's new

Search

Everywhere Threads This forum This thread Search titles only Note By: Search Advanced search… Everywhere Threads This forum This thread Search titles only By: Search Advanced…

• New posts
• Search forums

Menu Install the app Install How to install the app on iOS

Follow along with the video below to see how to install our site as a web app on your home screen.

Note: This feature may not be available in some browsers.

VNC stopped working on Eve-ng vm after the upgrade of proxmox from v6 to V 7.2.1

• Thread starter Thread starter Jean_G
• Start date Start date Jul 3, 2022

• Home
• Forums
• Proxmox Virtual Environment
• Proxmox VE: Installation and configuration

You are using an out of date browser. It may not display this or other websites correctly.You should upgrade or use an alternative browser. J

Jean_G

Member

Jun 3, 2021 2 0 6 30 Hello I have a "bare-metal" proxmox server that was working fine on version 6. .Since I upgraded to version 7.2, I can't open an eve-ng object anymore. For example, my Fortigate or Fortimanager boot up but when i try to open a console(VNC), I have an error: -for FortiManager: "Guest has not initialized the display (yet)" -For FortiGate VM: nothing happened and I can't even configure Interface. I know It looks like I should talk to eve-ng but I'm quite sure that it's due to the upgrade because I have looked at some threads. So could anyone help me fixe those issues ? Thank you in advance Here are some checks: Code: root@pve:~# pveversion -v proxmox-ve: 7.2-1 (running kernel: 5.15.35-1-pve) pve-manager: 7.2-4 (running version: 7.2-4/ca9d43cc) pve-kernel-5.15: 7.2-3 pve-kernel-helper: 7.2-3 pve-kernel-5.4: 6.4-16 pve-kernel-5.15.35-1-pve: 5.15.35-3 pve-kernel-5.4.178-1-pve: 5.4.178-1 pve-kernel-5.4.143-1-pve: 5.4.143-1 pve-kernel-5.4.114-1-pve: 5.4.114-1 pve-kernel-5.4.106-1-pve: 5.4.106-1 ceph-fuse: 14.2.21-1 corosync: 3.1.5-pve2 criu: 3.15-1+pve-1 glusterfs-client: 9.2-1 ifupdown: residual config 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.2 libproxmox-backup-qemu0: 1.3.1-1 libpve-access-control: 7.1-8 libpve-apiclient-perl: 3.2-1 libpve-common-perl: 7.2-2 libpve-guest-common-perl: 4.1-2 libpve-http-server-perl: 4.1-2 libpve-storage-perl: 7.2-4 libqb0: 1.0.5-1 libspice-server1: 0.14.3-2.1 lvm2: 2.03.11-2.1 lxc-pve: 4.0.12-1 lxcfs: 4.0.12-pve1 novnc-pve: 1.3.0-3 proxmox-backup-client: 2.2.1-1 proxmox-backup-file-restore: 2.2.1-1 proxmox-mini-journalreader: 1.3-1 proxmox-widget-toolkit: 3.5.1 pve-cluster: 7.2-1 pve-container: 4.2-1 pve-docs: 7.2-2 pve-edk2-firmware: 3.20210831-2 pve-firewall: 4.2-5 pve-firmware: 3.4-2 pve-ha-manager: 3.3-4 pve-i18n: 2.7-2 pve-qemu-kvm: 6.2.0-8 pve-xtermjs: 4.16.0-1 qemu-server: 7.2-3 smartmontools: 7.2-pve3 spiceterm: 3.2-2 swtpm: 0.7.1~bpo11+1 vncterm: 1.7-1 zfsutils-linux: 2.1.4-pve1

Attachments

• Proxmox VM.PNG 32.6 KB · Views: 12

fiona

Proxmox Staff Member

Staff member Aug 1, 2019 6,727 2,069 278 Hi,

Jean_G said: Hello I have a "bare-metal" proxmox server that was working fine on version 6. Click to expand...

why is "bare-metal" quoted?

Jean_G said: .Since I upgraded to version 7.2, I can't open an eve-ng object anymore. Click to expand...

Just so I understand, this error happens within the guest?

Jean_G said: For example, my Fortigate or Fortimanager boot up but when i try to open a console(VNC), I have an error: -for FortiManager: "Guest has not initialized the display (yet)" -For FortiGate VM: nothing happened and I can't even configure Interface. Click to expand...

But those errors are when you access the other VMs through the Console in the web UI? Are there any errors in the VM XYZ - Start tasks? What about /var/log/syslog? How do you see that the VM booted up? Why did you mark two settings in the screenshot? You could also try to downgrade pve-qemu-kvm and/or the kernel to see if the issue disappears then. Toggle signature Best regards, Fiona Do you already have a Commercial Support Subscription? - If not, Buy now and read the documentation D

duk2nuk

New Member

Jul 28, 2022 2 0 1 Hello! I have the same issue. How it can be resolved?

fiona said: You could also try to downgrade pve-qemu-kvm and/or the kernel to see if the issue disappears then. Click to expand...

Hello, I have the same issue. How can it be resolved? Or how can I downgrade me kernel to 5.11?

fiona

Proxmox Staff Member

Staff member Aug 1, 2019 6,727 2,069 278 Hi,

duk2nuk said: Hello! I have the same issue. How it can be resolved? Hello, I have the same issue. How can it be resolved? Or how can I downgrade me kernel to 5.11? Click to expand...

can you please describe the issue in more detail? What are you trying to do and what error messages do you get? Please also answer the questions relevant for you from my previous post. You can select installed older kernels during the boot menu (or pin it if you are using proxmox-boot-tool). If it's not installed anymore, use apt install pve-kernel-<version>. Toggle signature Best regards, Fiona Do you already have a Commercial Support Subscription? - If not, Buy now and read the documentation You must log in or register to reply here. Share: Bluesky LinkedIn Reddit Email Share Link

• Home
• Forums
• Proxmox Virtual Environment
• Proxmox VE: Installation and configuration

Top Bottom

• We value your privacy

  We use essential cookies to make this site work, and optional cookies to enhance your experience.

  See further information and configure your preferences

  Accept all cookies Reject optional cookies
  • Essential cookies
  These cookies are required to enable core functionality such as security, network management, and accessibility. You may not reject these.
  • Optional cookies
  We deliver enhanced functionality for your browsing experience by setting these cookies. If you reject them, enhanced functionality will be unavailable.
  • Third-party cookies
  Cookies set by third parties may be required to power functionality in conjunction with our captcha service provider for security and anti-spam purposes.
  • Detailed cookie usage
  • Privacy policy
  Save cookie preferences