Search results

  1. F

    VM performance degradation after Proxmox upgrade to 6.2-4

    Please, make this test. Stop all vms on proxmox host. After, do: modprobe -r kvm_intel modprobe kvm_intel enable_apicv=N cat /sys/module/kvm_intel/parameters/enable_apicv The output must be N. Start vms again. Report the result.
  2. F

    HA, Replication and iSCSI.

    Hi. Thank for you feedback. Is this i trying to archive: one OS to operate everything. I making this test: watch -n 60 vzdump 300610 --mode snapshot --storage DC2-GN-HD01 --remove 0 --node PV-01-GN Every 60 seconds i send the differential to the backup-proxmox server. Any chance to got node...
  3. F

    HA, Replication and iSCSI.

    Hi. I use the FreeBSD ZFS. But, i changing the the view where storage is local, with low complexity. In this new view, the servers is zfs and replication is from hypervisor to other.
  4. F

    HA, Replication and iSCSI.

    Hi. I have this scenario 1: 1. A ISCSI server give the Harddisk to every VM. 2. 6 Hosts is used in HA, and all see this iSCSI server. 3. I want to replicate each minute this VM to outside building. For this i have a VPN and is working (the 6 hosts + iSCSI Server see my other place network and...
  5. F

    VM Migration - local storage (zfs)

    Hi. I read some docs and one question is not totally clear to me. If i have servers with only a local storage (each server have 10 disks, zfs and storage name is the same in all servers) and this servers is on cluster, can i migrate vms online, offline or none of both ?. The second question...
  6. F

    VM performance degradation after Proxmox upgrade to 6.2-4

    Same here. I make a comparative in versions performance. The best version so far in performance was pve-manager/6.1.8/806edfe1 running kernel 5.3.18-3-pve. Iscsi performance and CPU inside vms was the best. The worst was 6.1-5/9bf06119 running kernel 5.3.13-1 with Very low performance inside...
  7. F

    Add node to cluster and not reboot all nodes

    The problem is Ghost node. cat /etc/pve/ha/manager_status : {"node_status":{"":"fence","PV-... https://forum.proxmox.com/threads/lrm-unable-to-read-lrm-status.65415 https://forum.proxmox.com/threads/cannot-delete-ghost-node.13752 Suggestion: When generating /etc/pve/ha/manager_status check...
  8. F

    Add node to cluster and not reboot all nodes

    The VMs normally do live migration. Everything is normal until i add a new node, then all host servers reboot at same time.
  9. F

    Add node to cluster and not reboot all nodes

    I'm cheking the logs. This is output: ha-manager status --verbose unable to read file '/etc/pve/nodes//lrm_status' quorum OK master PV-02-XXX (active, Sun May 24 13:01:57 2020) lrm (unable to read lrm status) lrm PV-01-XXX (active, Sun May 24 13:02:00 2020) lrm PV-02-XXX (active, Sun May 24...
  10. F

    Add node to cluster and not reboot all nodes

    I add now and again every node in cluster down.... That way, proxmox is unstable.
  11. F

    Add node to cluster and not reboot all nodes

    Hi. I have 4 nodes and today i wll add one more. Last time i do this, all nodes reboot without reason. So, how i can add a node to cluster without reboot all other nodes ?. Some secure procedure to not reboot all servers. Best regards.
  12. F

    Add node - reboot all vm's

    Happened to me now the same thing. I add one new node (was 3) and all 3 reboot, let all vms offline. pve-manager/6.1-11/f2f18736 (running kernel: 5.3.18-3-pve) I will look other option after today. The evaluation ended.