Search results

I've been importing a set of cPanel VMs from VMware to Proxmox. The VM running CentOS6 migrated perfectly and came up on first boot attempt. We have several more running CentOS7. Most of those required the fix where they fail to boot on initial import, so you shut them down, detach the disks...

Summary: I need to know how to remove a zpool from one machine in a cluster while leaving it on the others. I have a three node cluster, of two matching main servers (M1 and M2) and a third smaller (S3) machine which provides the third vote for failover and hosts a limited range of VMs. Each...

I know the correct method for a Proxmox upgrade is apt-get update, then apt-get dist-upgrade. First I forgot it's meant to be apt-get, and then I managed to type "apt upgrade" when I'd meant to type "apt update". Realised my mistake straight away but as upgrade was running didn't want to stop...

Outline: I'm wondering if there's any detailed documentation anywhere about exactly how the various SSH key files are used within a Proxmox cluster? In particular, what is the relationship between /root/.ssh/known_hosts, /etc/ssh/ssh_known_hosts, and /etc/pve/priv/known_hosts, and if replacing...

Assuming a setup where there is a separate boot disk or disks, and then ZFS storage pools for the actual VMs to live on, how much traffic, on a general basis, and especially write traffic, should be going to the root disk of a Proxmox server? We have two large, multi-core hypervisors with over...

The question: I see from the documentation at https://pve.proxmox.com/wiki/Cluster_Manager that "All existing configuration in /etc/pve is overwritten when joining a cluster. In particular, a joining node cannot hold any guests, since guest IDs could otherwise conflict, and the node will inherit...

Trying to follow the upgrade process, and the pve7to8 check script, even after a restart, throws this error: "proxmox-ve package is too old, please upgrade to >= 7.4-1!" Which doesn't make a great deal of sense when: root@covenstead:~# pveversion pve-manager/7.4-15/a5d2a31e (running kernel...

I have two large Proxmox 7.0-11 hosts in a cluster, with 50TB ZFS local storage each, and most VMs replicating between them. On one of these hosts are two large (5TB) VMs, both shut down and out of use, which were nested hypervisors, one Xen, one VMware. One is VM replicated to the other host...

We have a Proxmox cluster comprising two identical large machines, with 120 cores and 370+ gig of memory, and with each machine having two ZFS disk pools, Tank1 of 50TB HDD, and Tank2 of 2TB of SSD, and a third less powerful machine with just one ZFS pool, a mirrored paid of 10TB disks...

Odd issue came up today, shutting down one machine in a 3-node, 4-vote cluster caused both other nodes to unexpectedly reboot. We have a cluster consisting of two identical high capacity Supermicro servers running Proxmox 7, one less powerful Dell blade server running Proxmox 6.2 (planned to...

I have a Proxmox cluster, running V7 and V6 versions (am upgrading one machine at a time). On all the machines, regardless of version, the VM data disk files do not show up at all using the normal Linux file commands like ls and df. Is this expected behaviour or do we have a weird fault...

I have a pool, configured as a raidz-1, of 5 SSD drives plus 2 spares, and in the most recent scrub, two of the main pool SSDs have been marked FAULTED. The spares have automatically taken over so at the moment the pool still has full redundancy, and I want to replace the faulty drives...

We have an existing cluster of VMware ESXi and XenServer 6 and 7 hypervisors, running multiple Lunix and Windows VMs of various vintages. We plan to migrate all the VMs to Proxmox on new hardware, using ZFS replication to give us failover and HA. For the more modern Linux VMs this seems...