proxmox ve 7 watchdog: BUG: soft lockup - CPU # 0 stuck for ...

[insight]

hello i can't install any os on any vm in proxmox i always get an error: watchdog: BUG: soft lockup - CPU # 0 stuck for ... s


thanks.

# pveversion --verbose
proxmox-ve: 7.1-1 (running kernel: 5.13.19-2-pve)
pve-manager: 7.1-7 (running version: 7.1-7/df5740ad)
pve-kernel-helper: 7.1-6
pve-kernel-5.13: 7.1-5
pve-kernel-5.4: 6.4-11
pve-kernel-5.13.19-2-pve: 5.13.19-4
pve-kernel-5.4.157-1-pve: 5.4.157-1
ceph: 16.2.7
ceph-fuse: 16.2.7
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown: 0.8.36+pve1
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve2
libproxmox-acme-perl: 1.4.0
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.1-5
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.0-14
libpve-guest-common-perl: 4.0-3
libpve-http-server-perl: 4.0-4
libpve-storage-perl: 7.0-15
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.9-4
lxcfs: 4.0.8-pve2
novnc-pve: 1.2.0-3
proxmox-backup-client: 2.1.2-1
proxmox-backup-file-restore: 2.1.2-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.4-4
pve-cluster: 7.1-2
pve-container: 4.1-2
pve-docs: 7.1-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.3-3
pve-ha-manager: 3.3-1
pve-i18n: 2.6-2
pve-qemu-kvm: 6.1.0-3
pve-xtermjs: 4.12.0-1
qemu-server: 7.1-4
smartmontools: 7.2-pve2
spiceterm: 3.2-2
swtpm: 0.7.0~rc1+2
vncterm: 1.7-1
zfsutils-linux: 2.1.1-pve3

 

[Moayad]

Hello,

Is your Proxmox VE installed on VPS or on a dedicated server?

 

[insight]

contabo vds

Hello,

Is your Proxmox VE installed on VPS or on a dedicated server?

https://contabo.com/en/vds/

could this be the problem?

https://forum.proxmox.com/threads/kernel-5-11.86225/post-417637

 

[Moayad]

I would try to install the old pve-kernel or the newest one.

have you seen any error messages in the Syslog from the PVE side during starting the VM?

 

[insight]

I would try to install the old pve-kernel or the newest one.

how can i do it?





my logs:

Dec 15 09:17:43 vm.coxx.net sshd[190325]: Unable to negotiate with 125.124.3.200 port 60286: no matching key exchange method found. Their offer: diffie-hellman-group14-sha1,diffie-hellman-group-exchange-sha1,diffie-hellman-group1-sha1 [preauth]
Dec 15 09:17:59 vm.coxx.net sshd[190367]: Unable to negotiate with 125.124.3.200 port 40088: no matching key exchange method found. Their offer: diffie-hellman-group14-sha1,diffie-hellman-group-exchange-sha1,diffie-hellman-group1-sha1 [preauth]
Dec 15 09:18:02 vm.coxx.net sshd[190371]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=175.100.120.111  user=root
Dec 15 09:18:04 vm.coxx.net sshd[190371]: Failed password for root from 175.100.120.111 port 52317 ssh2
Dec 15 09:18:04 vm.coxx.net sshd[190371]: Received disconnect from 175.100.120.111 port 52317:11: Bye Bye [preauth]
Dec 15 09:18:04 vm.coxx.net sshd[190371]: Disconnected from authenticating user root 175.100.120.111 port 52317 [preauth]
Dec 15 09:18:14 vm.coxx.net sshd[190398]: Unable to negotiate with 125.124.3.200 port 48122: no matching key exchange method found. Their offer: diffie-hellman-group14-sha1,diffie-hellman-group-exchange-sha1,diffie-hellman-group1-sha1 [preauth]
Dec 15 09:18:26 vm.coxx.net sshd[190420]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.100.243.210  user=root
Dec 15 09:18:28 vm.coxx.net sshd[190420]: Failed password for root from 180.100.243.210 port 45174 ssh2
Dec 15 09:18:28 vm.coxx.net sshd[190420]: Received disconnect from 180.100.243.210 port 45174:11: Bye Bye [preauth]
Dec 15 09:18:28 vm.coxx.net sshd[190420]: Disconnected from authenticating user root 180.100.243.210 port 45174 [preauth]
Dec 15 09:18:30 vm.coxx.net sshd[190442]: Unable to negotiate with 125.124.3.200 port 56156: no matching key exchange method found. Their offer: diffie-hellman-group14-sha1,diffie-hellman-group-exchange-sha1,diffie-hellman-group1-sha1 [preauth]
Dec 15 09:18:44 vm.coxx.net sshd[190464]: Unable to negotiate with 125.124.3.200 port 35958: no matching key exchange method found. Their offer: diffie-hellman-group14-sha1,diffie-hellman-group-exchange-sha1,diffie-hellman-group1-sha1 [preauth]
Dec 15 09:19:00 vm.coxx.net sshd[190506]: Unable to negotiate with 125.124.3.200 port 43992: no matching key exchange method found. Their offer: diffie-hellman-group14-sha1,diffie-hellman-group-exchange-sha1,diffie-hellman-group1-sha1 [preauth]
Dec 15 09:19:16 vm.coxx.net sshd[190538]: Unable to negotiate with 125.124.3.200 port 52026: no matching key exchange method found. Their offer: diffie-hellman-group14-sha1,diffie-hellman-group-exchange-sha1,diffie-hellman-group1-sha1 [preauth]
Dec 15 09:19:32 vm.coxx.net sshd[190577]: Unable to negotiate with 125.124.3.200 port 60060: no matching key exchange method found. Their offer: diffie-hellman-group14-sha1,diffie-hellman-group-exchange-sha1,diffie-hellman-group1-sha1 [preauth]
Dec 15 09:19:47 vm.coxx.net sshd[190602]: Unable to negotiate with 125.124.3.200 port 39862: no matching key exchange method found. Their offer: diffie-hellman-group14-sha1,diffie-hellman-group-exchange-sha1,diffie-hellman-group1-sha1 [preauth]
Dec 15 09:20:01 vm.coxx.net sshd[190643]: Unable to negotiate with 125.124.3.200 port 47896: no matching key exchange method found. Their offer: diffie-hellman-group14-sha1,diffie-hellman-group-exchange-sha1,diffie-hellman-group1-sha1 [preauth]
Dec 15 09:20:18 vm.coxx.net sshd[190673]: Unable to negotiate with 125.124.3.200 port 55930: no matching key exchange method found. Their offer: diffie-hellman-group14-sha1,diffie-hellman-group-exchange-sha1,diffie-hellman-group1-sha1 [preauth]
Dec 15 09:20:24 vm.coxx.net sshd[190692]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.100.243.210  user=root

more long in file

 

[Moayad]

how can i do it?

apt install pve-kernel-5.15.5-1-pve on your Proxmox VE, restart the PVE after install the new kernel.

 

[insight]

apt install pve-kernel-5.15.5-1-pve on your Proxmox VE, restart the PVE after install the new kernel.

same problem with new kernel

proxmox-ve: 7.1-1 (running kernel: 5.15.5-1-pve)
pve-manager: 7.1-7 (running version: 7.1-7/df5740ad)
pve-kernel-helper: 7.1-6
pve-kernel-5.13: 7.1-5
pve-kernel-5.4: 6.4-11
pve-kernel-5.15.5-1-pve: 5.15.5-1
pve-kernel-5.13.19-2-pve: 5.13.19-4
pve-kernel-5.4.157-1-pve: 5.4.157-1
ceph: 16.2.7
ceph-fuse: 16.2.7
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown: 0.8.36+pve1
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve2
libproxmox-acme-perl: 1.4.0
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.1-5
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.0-14
libpve-guest-common-perl: 4.0-3
libpve-http-server-perl: 4.0-4
libpve-storage-perl: 7.0-15
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.9-4
lxcfs: 4.0.8-pve2
novnc-pve: 1.2.0-3
proxmox-backup-client: 2.1.2-1
proxmox-backup-file-restore: 2.1.2-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.4-4
pve-cluster: 7.1-2
pve-container: 4.1-2
pve-docs: 7.1-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.3-3
pve-ha-manager: 3.3-1
pve-i18n: 2.6-2
pve-qemu-kvm: 6.1.0-3
pve-xtermjs: 4.12.0-1
qemu-server: 7.1-4
smartmontools: 7.2-pve2
spiceterm: 3.2-2
swtpm: 0.7.0~rc1+2
vncterm: 1.7-1
zfsutils-linux: 2.1.1-pve3

 

[insight]

help

 

[tom]

help

Running Proxmox VE on a virtual server is probably not the best idea for performance and stability. Proxmox VE should run on bare metal.

In any case, contact first your virtual server provider, they should know what is working on their platform and what is not working.

 

[insight]

I did not solve the problem with the changes in the attached photo

https://forum.proxmox.com/threads/c...-lockup-cpu-0-stock-for-24s.84212/post-493942

 

[RolandK]

Is your Proxmox VE installed on VPS or on a dedicated server?

> https://contabo.com/en/vds/

> could this be the problem?

yes

and you cannot solve this within the guest.

if your virtual machine is not getting scheduled - it is not getting scheduled.

period

what hypervisor does contabo use ?

 

[ksceniev]

Running Proxmox VE on a virtual server is probably not the best idea for performance and stability. Proxmox VE should run on bare metal.

I having the same issue. But it isn't a virtualized hypervisor, Contabo Proxmox VDS runs on bare metal.

 

[UdoB]

Contabo Proxmox VDS runs on bare metal.

Please excuse my ignorance... does it? They offer for example "Cloud VDS M -- 4 Physical Cores -- AMD EPYC 7282 2.8 GHz -- 32 GB RAM ..."

How does this work without virtualization layer on Ring 0? Do EPYC with only four cores really exist

Probably I've missed some parts of the newer development...

 

[RolandK]

> Contabo Proxmox VDS runs on bare metal.

how can a proxmox virtual dedicated server with 4 Epyc cores run on bare metal ?

btw, i don't see that they offer proxmox with this, can you provide a link @ksceniev ?

 

[_gabriel]

contabo use proxmox itself for their vds.
You can see "Proxmox" boot logo in a Windows instance.

you are in nested virtualization in shared host, don't except great performance.

 

[ksceniev]

Please excuse my ignorance... does it? They offer for example "Cloud VDS M -- 4 Physical Cores -- AMD EPYC 7282 2.8 GHz -- 32 GB RAM ..

Excuse mine, haven't realized it was a nested environment. Btw was exactly this one i bought, migrating to a bare metal instance today....