Search results

SSH into your PVE node and edit /etc/default/grub like you want it. After changes are made run "update-grub" and reboot te node. Edit: You can also just remove unused kernels (first run dpkg -l | grep 'pve-kern' to search for kernels, then run apt-get --purge remove pve-kernel-version for each...

Ah ok. Can you try to start a graphical install of Debian Jessie 8.4.0 via IPMI? To check if the problem is with Debian or with PVE only. Just to be sure: PVE 4.0 also not working and 3.4 is working OK?

Hmm, I think only options you have right now is to install from PVE 4.1 ISO and upgrade to 4.2 once installation is done or do a clean Debian Jessie install and then install PVE. If I look at other topics the last days there seems to be some issues with the new PVE 4.2 ISO and Dell and HP hardware.

Update: I did some more testing and don't know for sure, but seems that this has something to do with hpet. After I had disabled systemd-timesyncd (https://forum.proxmox.com/threads/pve-4-1-systemd-timesyncd-and-ceph-clock-skew.27043/), installed ntp and added "hpet=disable" (hpet=disable with...

I Agree. I think the switch to systemd-timesyncd, that came with Jessie, was a bad one. I think it's better Proxmox disable systemd-timesyncd and install ntp by default in the PVE image. Also another issue I had with hpet=disable was caused by systemd-timesyncd...

Update: problem seems to be solved when disabling systemd-timesyncd and enable ntp (https://forum.proxmox.com/threads/pve-4-1-systemd-timesyncd-and-ceph-clock-skew.27043/). A couple of days ago I re-added "hpet=disable" and until now it's stable.

What does "pvecm status" show? I think you lost quorum (multicast working?) and therefor activity is blocked, so you can't write a temp. file to /etc/pve. If this is the case you can try to regain quorum or try to run "pvecm expected 1" and try again.

Did you wait 15 mins before you tried? You are now recognized as PVE subscriber, so try again now.

Latest version of PVE 3.x branche is 3.4-13 in pve-no-subscription and pve-enterprise. So no changes/updates to be expected. No, you should only comment out pve-no-subscription and enable pve-enterprise. Also the default debian repositories (incl. security!) should be enabled.

May be related to https://forum.proxmox.com/threads/proxmox-ve40-incompatible-with-hp-proliant-servers.24793/

Best way to do this is to setup a IPsec or SSL VPN to the internal network, after that you can reach the local IP's secure from anywhere in the world, but others can't. Other possability is to NAT to local IP's in your WAN router. For example: NAT 1.1.1.1:8001 to 192.168.0.60:8006 and...

Any APC that can switch power off/on will work. We've had it running with much different models when we were using PVE 3.x Currently I only have 1 PVE 3.4 cluster left (all the others are on PVE 4.x now) and that cluster is using APC AP8653's with firmware 6.3.3.

Today I rebooted the nodes (and updated to Ceph 0.94.7) and the same issue occurs, again 2 of the CEPH VM images are corrupted (input/output errors), but not the same VM's as last time, only thing they have in common is they all are Elastix 2.x (CentOS 5.x with 2.6.x kernel) VM's. I thought it...

Do you use ILO as fencing device? If so, that is the issue on PVE 3.x, because if you unplug your complete server from power the other node can't reach your fencing device and thus can't fence it (and therefor don't migrate the VM). You can add a second fencing device outside your server (APC...

No. No.

Do you use PVE 4.x and have CEPH storage and PVE on the same node? Probably timesyncd is your problem. Please see https://forum.proxmox.com/threads/pve-4-1-systemd-timesyncd-and-ceph-clock-skew.27043/

True, but counter don't reset at the 1st of a new month. Also the VM can be hosted at multiple nodes during the month.

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.

See this for a fix of the clock skew errors, because they will come back: https://forum.proxmox.com/threads/pve-4-1-systemd-timesyncd-and-ceph-clock-skew.27043/

Strange, 4 CPU's/cores seems to be offline. Do you have any eco/energy savings options in BIOS? Try to disable them. If you don't have them, or already disabled them, try to manually bring online the other 4 CPU's/cores to see if that is working...