Search results

Apr 22 19:49:02 ns3014725 corosync[8812]: [SERV ] Service engine 'corosync_quorum' failed to load for reason 'configuration error: nodelist or quorum.expected_votes must be configured!' What does your /etc/pve/corosync.conf and /etc/corosync.conf look like?

Is it possible to test/re-install with a Proxmox VE installation ISO from http://www.proxmox.com/en/downloads/item/proxmox-ve-4-1-iso-installer ?

Thanks! Just for the record /etc/lib/systemd/system/pve-cluster.service = /etc/systemd/system/pve-cluster.service :) What I did was the following: # cp /lib/systemd/system/pve-cluster.service /etc/systemd/system/pve-cluster.service # nano /etc/systemd/system/pve-cluster.service Changed...

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...

Hmm, no it should be there. For example, below is on a PVE 4.1-22 node: root@node02:~# ls -l /sys/module/kvm_intel/parameter /nested -r--r--r-- 1 root root 4096 Apr 21 21:25 /sys/module /kvm_intel/parameters/nested Are you sure you have a Intel CPU? What is the output of "cat /proc/cpuinfo"?

Please see https://pve.proxmox.com/wiki/Nested_Virtualization I'm pretty sure this is your solution. :)

I've seen similar problems which turns out to be a memory issue, also without anything in the logs (simply upgrade the system with more memory resolved the issue in my case). Did you ever run a "free -m" when it occurs? However, whenever it's a memory issue or not, I'm pretty sure it's hardware...

Don't forget your SWAP space (10 GB).

15-20 GB should be sufficient.

Sounds like a memory issue to me.

No possability to add the new server to the cluster and then migrate the VM using the GUI? Otherwise I would backup and restore, rsync seems to be risky for this to me.

Were all the shares available for the new node and can you for example show content of all shares on the new node? What does a "pvecm status" and "clusstat" on the new node and on a old node show? Did you run a omping to test multicast traffic? Are there differences when you login to the GUI via...

Did you upload your subscription key? Or if you don't have one disabled the pve-enterprise repo and added the pve-no-subscription repo? Please see https://pve.proxmox.com/wiki/Package_repositories After that run: apt-get update && apt-get dist-upgrade

And PVE is installed on the physical node? Or is PVE installed in a VM?

Done: https://bugzilla.proxmox.com/show_bug.cgi?id=943 https://bugzilla.proxmox.com/show_bug.cgi?id=944

Nice job! One small bug found so far in the bootorder of a new VM, the bootorder is by default "Disk, CD-ROM, Network", when you change this to only 2 devices (set the thirth to 'none') you get an error: Parameter verification failed. (400) boot: value does not match the regex pattern Edit...

Sorry for hijacking this thread, but is it recommended to stop watchdog fencing when performing an upgrade to prevent this kind of issues?

Great, thanks!

And another issue you may forget is the IP-space. If you move a VM from one datacenter/network to another, will the VM still switch the IP he use? Offcourse you can setup VPN-tunnels to use the IP-space on all locations, but this don't give you the (network) redundancy you are looking for. Only...

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...