Search results

vi /etc/aliases newaliases

I cannot precisely help you (I do not use OVS), but enabling ARP proxy on your gateway can help. Be aware of security problems it can generate. For information, I have used shorewall on PVE host with manual ARP proxy configuration. Now I use a mikrotik VM with ARP proxy.

I do not have the answer. For SSH, try to remove SSH server keys and reboot node (works almost in any case/distro). For debian based distro, do : rm /etc/ssh/ssh_host_* dpkg-reconfigure openssh-server The host keys will be regenerated. Anyway, a clone is a byte to byte copy. Do not forget to...

FS loop over an other one always produces IO amplification. Maybe try noatime and nodiratime on the host (if /var/lib/vz is a separated FS) and VM guests (if your VM daemons does not require atime and diratime). Furthermore, try to alginate FS cluster sizes between VM (FS) and host (VM +...

Why would you disarm fencing ? You are supposed to migrate VMs before rebooting a node. For HW watchdogs, be aware that a server has several ones nowadays. Spend some time to master your hardware and configurations of it. For example, here are my notes for a R730, with proxmox 4.1 : Watchdog...

look in /var/lib/vz/template/

Suggestion : wait for the PVE v5 : - migrate from local storage VMs (qemu) - ZFS sync interface And one other : do never use more than 75% of your pool

I don't have this problem. Look at swapiness kernel configuration, and try to play with it ?

Just a remark : if you use your 1st server as switch, then you should not use HA on the cluster (if 1st server is down, all the cluster will go down). And an other : if the pfSense is not in HA, then if the pfSense VM is down, you will not be able to assignate IPs to your servers. In brief : buy...

I may be mistaken, but I always saw errors on SATA buses with atom based "servers" I build at home. I think that unrecoverable errors comes from that. After all, this is a high speed bus, subject to perturbation, and with consumer grade hardware :-) Concerning the endurance, I don't know, this...

I spent several days at my precedent job in order to understand the SSD technology and in order to choose the right disk for the right usage. The disk I use is not a professional one, but there is a good warranty :-) Disk is installed with Proxmox since around 20 days.

Dan : read the manual about minimum node number for HA (cluster concept : quorum), and read about watchdog fencing.

As for reference, the SSD with proxmox on it (at home) : - used for proxmox installation root - used for VMs (for the moment 2 VMs with very low activity) I didn't went to the manufacturer spec for SMART values, but everything seems to be OK : root@ruche:~# smartctl -x /dev/sda smartctl 6.4...

Interesting thread ! My two cents : - write amplification is on rotational disks and RAID arrays too (to my knowledge, the job is always : Read/Modify/Write) - buffered logs and noatime/nodiratime can help, but I don't know if Proxmox daemons will be pleased with that - an other improvment : use...

Advised method is backup on old PVE / restore on new PVE. It implies more downtime but you are sure to get a good migration. You don't ever know if the VM config files have new defaults settings or format change...

try : "apt-get install python-pyinotify"

PVE does not provides 0 downtime. When High Availability occurs, the VMS are restarted on an other node. If you want IPSEC High Availability, look otherwhere (ex : double IPSEC link + BGP ?).

did you tryed "echo 0 > /sys/devices/virtual/net/vmbr0/bridge/multicast_snooping" ? do you use multi queue on device ? is there a debug mode in the ethernet card module ?

Try disabling snooping. And maybe try virtio network for the VMs ?

https://pve.proxmox.com/wiki/Two-Node_High_Availability_Cluster https://forum.proxmox.com/threads/best-practise-for-a-two-node-proxmox-storage-cluster.26370/#post-132488 3 nodes is OK. But when you lost one node, you are in the hurry :-)