I cannot run Proxmox web interface and vm's.

[pilgrimage]

My Proxmox server was working fine but now I am getting the following errors. The only thing I have done is Proxmox 7.2.11 update, other than that I have made the following settings as Windows 10 is running very slow.which of these could have corrupted my system? I need your support to solve this problem and get the system up and running.

https://forum.proxmox.com/threads/high-cpu-load-for-windows-10-guests-when-idle.44531/

can you try another thing:

keep no-hpet, and change this (same QemuServer.pm file)

if ($winversion >= 7) {
push @$cpuFlags , 'hv_relaxed';
}

to
if ($winversion >= 7) {
push @$cpuFlags , 'hv_relaxed';
push @$cpuFlags , 'hv_synic';
push @$cpuFlags , 'hv_stimer';
}

then restart pvedaemon and stop/start vm .

Then I deleted this command, but I can't get it to work again. Could I have broken something in QemuServer.pm? Also QuemuServer.save



I wanted to run the vm via command with ssh because I could not enter the proxmox web interface, but it gave the following error message

Can't locate object method "pveversion" via package "vpackage" (perhaps you forgot to load "vpackage"?) at /usr/share/perl5/PVE/QemuServer.pm line 1, <DATA> line 960.
Compilation failed in require at /usr/share/perl5/PVE/API2/Qemu/Agent.pm line 8, <DATA> line 960.
BEGIN failed--compilation aborted at /usr/share/perl5/PVE/API2/Qemu/Agent.pm line 8, <DATA> line 960.
Compilation failed in require at /usr/share/perl5/PVE/CLI/qm.pm line 28, <DATA> line 960.
BEGIN failed--compilation aborted at /usr/share/perl5/PVE/CLI/qm.pm line 28, <DATA> line 960.
Compilation failed in require at /usr/sbin/qm line 6, <DATA> line 960.
BEGIN failed--compilation aborted at /usr/sbin/qm line 6, <DATA> line 960.


When I enter the command, it gives the following error message.

systemctl restart pveproxy.service pvedaemon.service


Sep 28 10:59:52 pve systemd[1]: pvedaemon.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit pvedaemon.service has entered the 'failed' state with result 'exit-code'.
Sep 28 10:59:52 pve systemd[1]: Failed to start PVE API Daemon.
░░ Subject: A start job for unit pvedaemon.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit pvedaemon.service has finished with a failure.
░░
░░ The job identifier is 3544 and the job result is failed.
Sep 28 10:59:52 pve systemd[1]: pveproxy.service: Start request repeated too quickly.
Sep 28 10:59:52 pve systemd[1]: pveproxy.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit pveproxy.service has entered the 'failed' state with result 'exit-code'.
Sep 28 10:59:52 pve systemd[1]: Failed to start PVE API Proxy Server.
░░ Subject: A start job for unit pveproxy.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit pveproxy.service has finished with a failure.
░░
░░ The job identifier is 3444 and the job result is failed.

 

[pilgrimage]

I replaced the QuemServer.pm.save file with the Quemuserver.pm file I had a problem with. It opens now. However, the Quemuserver.pm.save file is a file from February 2022 and I think the update I made as of today is not up to date in the quemuserver.pm file. How can I manually update the QuemuServer.pm file again. 7.2.11 Proxmox internal

 

[Matthias.]

apt install --reinstall qemu-server will reinstall the whole qemu-server package

 

[pilgrimage]

Thanks for the help. Problems Solved.