Search results

The NAS which is used by my proxmox as a backup datastorage had a problem. The problem led to the nas being very unresponsive/hanging. It looks like this behaviour also influenced pvestatd is such a way that it has became a zombie process. dmesg shows the following errors. I can say for sure...

Is there already a bug report for this which I could follow? I plan to set up the server in a way that if the UPS looses power the server waits for 5min for the power to come back and then it suspends all VMs and shuts down. Gracefully shutting down all VMs might take way to long, especially...

It would make sense in a home-server environment. There, the server does not need to run 24/7. I do the same with my backup NAS. It just WoL it, do Backups and it goes to sleep by itself 1 hour after the last connection was terminated.

Does qm suspend --todisk 1 also work if the pve node is rebooted afterwards? So: suspend VM, reboot node, resume VM. I found this bug report https://bugzilla.proxmox.com/show_bug.cgi?id=426 where it looks like this would work, but I am not completley sure if it really applies to this case.

I did a lot of reasearch on corosync (especially since things changed with corosync 3.x). What I could not find out is: what exactly happens if corosync fails. Let's take the extreme case: all switches which serve corosync (event if a redundant setup is present) fail. Everything else works fine...

I am a little confused about how to setup a small proxmox cluster. My goal is to have 3-4 nodes in a cluster. I do not want to use Ceph nor GlusterFS. Obviously, also no HA or live migration. I do want to use replication though. The goal is in case of failures to recover within hours (not days)...

Seems like the exact same problem as I had, including that you have the same Intel Chip. Since I did a clean Proxmox 6 install and you used Debian, I am guessing that the error is unrelated to proxmox. Still, the question remains why Debian does not name the interfaces properly but falls back to...

I have basically the same problem but without the complication of a cluster, i.e., just a single proxmox 5.4 node which I would like to move to new hardware and proxmox 6.0. Downtime is acceptable. The hardware is nearly the same, just a slightly faster CPU (same generation) and SSD storage...

The problem is/was not in the interfaces file. The interfaces there had the exact same names. Since this was a fresh install (I had proxmox 5.4 on the same hardware, but removed the disk where it was installed and did a fresh install). After a lot of googling I found the problem to be more of...

I just installed a clean proxmox 6.0 on a machine and the network card does no longer function properly. It worked with Proxmox 5.4 Hardware: HP server with 2x gigabit on-board card + HP NC364T PCIe (4x gigabit card, with 2x Intel 82571EB chips). The problem is, that 2 of the 4 ports get...

Geat, thanks! I know %iowait and iostat. Would be nice if proxmox called it this way or included some mouse-over hint to it or at least something in the manual when I click the "help" button. As a suggestion: a different metric for IO might be better. %iowait can be highly missleading...

I am new to proxmox and want to understand it better. A node shows me the "IO delay" value. What is IO delay? How is it calculated? Knowing this would make it easy to answer questions like: what IO delay is acceptable? Is 5% a high value or is 50% acceptable? etc. I tried searching the...