Recent content by Pyromancer

Update: It worked. As expected, the VM wouldn't boot with the disks set to scsi, so shut down, detach disk, then edit the disk and re-attach it as IDE, VM boots fine, and having a 1TB IDE disk doesn't seem to cause any issues.

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

For anyone interested in how this went: First, using the GUI, in Datacentre > Storage, tank2 was previously set to be available on M1 and M2. I edited this and removed it from M2. This removed it from the left hand column on M2, while it remained on M1. Next, logged in to M2 by SSH I did...

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

Thanks, appreciate the reply. Always wary of running updates on production systems, just in case, but noted. Upgrading means migrating all the VMs to other hosts, upgrade one, and move them all back again, which does tend to take some time, hence we don't tend to do it more often than needed...

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

Just for the record, I had the same problem when I stopped an import from ESXi, after I realised it was attempting to import to the local-lvm boot disk (quite a small SSD) rather than my 10TB /tank1 zfs mirror. Doing > qm unlock <VMID> > qm destroy <VMID> neatly solved the problem and I've now...

Though I did search the forum for answers I'd not seen your article, I will study this in detail. I'd been expecting SSH issues as I'd completely replaced the main servers with all-new installs but retaining their existing names and IP addresses, so wasn't particularly surprised but couldn't...

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

Fair enough, appreciate the reply and having reviewed your link I see what you mean, effectively a potential single point of failure. Haven't made any changes yet, not sure if removing the Qdevice is liable to cause a cluster reboot or not so waiting till I'm next on the actual premises so can...

I'm seeing the same thing, rebooting one node causes all nodes to reboot. We have a Proxmox cluster of three nodes plus a Qdevice. Originally it was a two node cluster, the two nodes being large and powerful servers with 120 cores and 300gig+ of memory each. In order to be able to use HA we...

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

Possibly related to this thread and may be of use to someone: I had a cluster of 3 nodes, two running 7.0, one running 7.3 (upgraded at different times). We wanted to upgrade all 3 to 7.4-16 preparatory to moving to v8. There was a major VM on the 7.3 node we didn't want to take risks with...

Thanks for replying, based on that I went ahead and did as proposed, and it worked perfectly. I took a backup of storage.cfg as well but it proved not to be needed as both main nodes have identical layouts, with zfs pool /tank1 as the main storage for VMs. Shut down the VM, copied then removed...

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