Search results

Solve: A network cable was disconnected ;-)

One node in a cluster of two nodes. One node shows proper statistic but the other does not for any VM's. Clicking on the node itself gives this error message: api error (status = 400 Bad Request): api error (status = 595 <unknown status code>): See attached screendump.

Try read the entire thread before making assumptions. The reason is explained here: https://forum.proxmox.com/threads/pve-8-0-and-8-1-hangs-on-boot.137033/post-609320 which also explains why this has nothing todo with the kernel but was related to living out a module from the initramfs which was...

Try read the entire thread before making assumptions. The reason is explained here: https://forum.proxmox.com/threads/pve-8-0-and-8-1-hangs-on-boot.137033/post-609320 which also makes it obviously way you see no problems on proxmox 7.4

Yep, that did the trick :) The fix enables booting on these kernels: - 5.15.126-1-pve - 6.2.16-19-pve - 6.5.11-4-pve Thank's Thomas :cool: To recap in case other comes to this thread: echo "simplefb" >> /etc/initramfs-tools/modules update-initramfs -u -k 6.5.11-4-pve (or update-initramfs -u...

Seems it is the initrd build system on 8.0 and 8.1 which is making unbootable initrd files because if I build a initrd file for pve-kernel-5.15.126-1-pve: 5.15.126-1 on 8.1 the system cannot boot using the pve-kernel-5.15.126-1-pve: 5.15.126-1 an showing exactly the same as for kernel > 6.1...

proxmox-kernel-6.2.16-19-pve same problem

nomodeset was enabled. This is wat I see after adding earlyprintk=vga which is exactly the same as I saw before, no output what so ever To me it looks like a kernel segfault . networking is enabled (management interface: $ ping -c1 esx2 PING esx2.datanom.net (172.16.3.9) 56(84) bytes of data...

Forgot: $ sudo pveversion -v [sudo] password for mir: proxmox-ve: 8.1.0 (running kernel: 5.15.126-1-pve) pve-manager: 8.1.3 (running version: 8.1.3/b46aac3b42da5d15) proxmox-kernel-helper: 8.0.9 pve-kernel-5.15: 7.4-7 proxmox-kernel-6.5.11-4-pve-signed: 6.5.11-4 proxmox-kernel-6.5: 6.5.11-4...

Hi all, Serious problem with proxmox-kernel-6.2 (proxmox-kernel-6.2.16-19-pve) and proxmox-kernel-6.5 (proxmox-kernel-6.5.11-4-pve-signed) previous kernels proxmox-kernel-6.1 and the one I currently boots on pve-kernel-5.15.126-1-pve works as expected. The symptom is that when boot sequence...

After upgrading to this kernel sensor readings through i2c is broken. The console is spammed with these messages: [24271.599465] i2c i2c-0: Failed! (01) Booting on kernel pve-kernel-5.15.83-1-pve and sensor reading is restored and no i2c errors in the log. Hardware: System Information...

Are you referring to Windows? Debian less documented! Are you serious?

I can recommend using OmniosCE. Have been running it here for more than 10 years without any problems or issues just remember to separate iSCSI traffic on a different network than the network for proxmox cluster. Preferably using 10Gbit or better is using it in an enterprise setup.

A question: Is it the optimal way that mounts should be blocking? Would it not be better if mounts was not blocking and used a timeout instead and in case mount observed timeout refuse starting VM's/PCT's with block devices on these mounts?

Sorry, missed that info ;-) New information: Only problems with NFS mounts to Qnap. NFSv4.2 does not work NFSv4.1 does not work NFSv4.0 work NFSv3 does not work.

As can be read here: https://forum.proxmox.com/threads/proxmox-ve-7-2-released.108970/post-468736 kernel pve-kernel-5.15.30-2-pve does not fix the issue. As a remark I have a Qnap which have a iscsi and nfs mount but have other storages as well but apparently if the Qnap mount fails the GUI...

pve-kernel-5.15.30-2-pve completely brakes GUI functionality. The cluster works as expected and can be managed via CLI on the different nodes (stop, start, and migrate - also VM's running in HA mode) but no way to do it from the GUI. Booting nodes using pve-kernel-5.13.19-6-pve and the GUI...

Not only that but if you run micro services or docker based services spooling a complete operating system is a waste of ressorces. Only if your micro services or docker based services must have a 100% uptime then go for a VM since LXC containers cannot live migrate still.

So you convert from unprivileged to a privileged container, sounds contradictory to me:rolleyes:

I think that part is from a time where unprivileged containers was not production ready and default was to run using a privileged container. A privileged containers root is mapped to the host root so breaking out of the container means that you get root privileges on the host while breaking out...