Today I installed some minor updates on a small PVE 4.4 cluster, since the updates I noticed the Software Watchdog Initial Countdown has changed from 120 seconds to 600 seconds. Isn't this value a bit high? Is it possible for us to change it back to 120 seconds?
Timer Use...
If I want to use software watchdog, is it a good idea to disable NMI Watchdog? Like you should disable NMI Watchdog when using a hardware watchdog? Why I'm asking:
I use the software watchdog (everything default) and sometimes when I do a reboot of the node, it comes back online with the...
We had 5 exactly the same physical nodes for our PVE 4.4 cluster. Now we needed to expand our capacity, so we bought 2 more servers, but this new servers aren't the same as the first servers. All 7 servers have dual Intel Xeon CPU's, but different models. Clockspeed of the first servers is...
Situation:
Physical host has 2 CPU-sockets with each 6-core's and HT-enabled. So, 2 x 6 x 2 = 24 vCPU's
Each CPU have 48 GB of memory installed in dual-channel configuration:
[ 16 GB ] [ 8 GB ]
[ 16 GB ] [ 8 GB ]
So, total system memory is 96 GB. Host is running PVE 4.3-9.
When I have a VM...
What's the preffered watchdog for PVE 4.x, hardware or software based? I'm asking because I've had a issue last days with a Dell idrac module in one of my nodes (https://forum.proxmox.com/threads/ipmi-couldnt-get-irq-info-and-runs-to-slow.27846/). It seems this module is faulty and it will be...
On a 5-node cluster (all Dell servers with idrac enterprise) running fine for some months, yesterday a node had a watchdog timer expired and rebooted. Last night same issue twice, but since second reboot the logs are full of:
Jun 14 05:59:59 host01 kernel: [ 3527.075573] ipmi_si ipmi_si.0...
Since Linux 4.x kernel there are built-in posibility's to upgrade the Linux kernel without a reboot. Since PVE 4.x uses Linux 4.x kernel, are there plans to support this feature out-of-the-box? And if yes, is there an ETA for this?
I think this feature is less important on HA clusters, but can...
Why is it that almost every update there are VM config format changes? And if needed, why don't automaticly change the config format for all VM's that exists already? For example:
On PVE 4.1-22 it was
virtio0: SSD-cluster:vm-103-disk-1,size=40G
net0: virtio=3A:A8:A8:DB:EC:F5,bridge=vmbr0209...
Hi,
We use Proxmox VE 4.x for our VPS service. Customers buy resources (CPU, memory, HDD etc, and also data traffic, for example 500 GB a month). What tools do others use for measuring this? All experiences would be appreciated.
On a small 3-node cluster, running 16 VM's, I did a upgrade from 4.1-22 to 4.2-2. Each node also has one CEPH OSD onboard. Cluster (Proxmox VE and CEPH) was completly healthy before the upgrade started. I did the upgrade node-by-node and before I finished a node and started with the following...
Since new GUI (PVE 4.2) a right click on a VM redirects you to the VM summary. With the old GUI this wasn't the case and you stayed where you are. I don't like this new behavior and hope it can be changed back? Thanks!
Is somewhere showed what version is currently the latest for each repository? So for example a webpage (or even on the PVE homepage?) with a block like:
Latest releases:
pve-enterprise: 4.1-22
no-subscription: 4.1-34
pve-test: 4.1-??
For exmple like FreeBSD (http://www.freebsd.org) does...
On a 3 node cluster we have a issue since we use PVE 4.1-22 (did a clean install, not upgraded). The PVE cluster is also the CEPH storage cluster (same nodes). Systemd-timesyncd seems to be less stable/accurate then NTP, therefor the CEPH cluster sees "clock skews" every couple of hours (we...
Since Proxmox VE 4.x it is possible to Manage HA-groups, which is a very nice feature. However, currently the only way to see to which group a VM belongs is to go to Datacenter - HA - Resources, it would be nice if this info is also available in the status info of the VM, see example attached...
This weekend I upgraded a Proxmox VE 3.4 cluster to Proxmox VE 4.1. Everything works as expected, but on the 3.4 cluster we had "hpet=disable" in the /etc/default/grub because if we don't, we get many (strange) log entries about hpet. After the upgrade I removed the "hpet=disable", to see if the...
If im right, today, April 15, 2016, is Proxmox VE's 8th birthday! So, I was wondering when we are welcome at Proxmox HQ to eat cake? ;)
Happy Birthday and congrats to you all guys, and keep up the good work!
Currently we use the pve-no-subscription repo, but since we are very happy with Proxmox VE we are planning to buy subscriptions soon. How about the change to pve-enterprise repo? Will packages installed from pve-no-subscription be updated from pve-enterprise (when we remove the...
When hot adding vCPU's to a VM running Debian Jessie in Proxmox 4.1-22 the console of the VM gives the following error one time for each vCPU that is added:
The VM gives the following error logs:
/var/log/syslog:
/var/log/messages:
However, the extra vCPU's are added and working. Google...
When memory hotplug is enabled you can't downgrade memory properly for that VM. I know it's not possible to hot unplug/downgrade the memory, but when the VM is running and you downgrade the memory the new memory config should be highlighted red and will be active when you stop/start the VM. This...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.