Search results

  1. R

    Upgrading to new SANs, but can't live storage migrate iSCSI -> iSCSI

    We've got some SANs providing iSCSI LVM storage to Proxmox VMs and we're in the process of replacing them with new SANs (iSCSI LVM again). Is there any way to live migrate the storage for running VMs from the old SANs' iSCSI to the new SANs' iSCSI? I can't believe this is an uncommon feature...
  2. R

    /run/lxcfs permissions in 4.2 cause Nagios disk check failure

    When upgrading from 4.0 to 4.2, I noticed there's a new tmpfs mount point called "/run/lxcfs/controllers" created that wasn't there in 4.0. Although almost all the contents of that mount point have world read access, for some reason the dirs /run/lxcfs and /run/lxcfs/controllers themselves only...
  3. R

    Live migration between 4.0 and 4.2 fails in both directions

    We skipped Proxmox 4.1, but decided to upgrade our 4.0 Proxmox servers (5 machines in a cluster, with iSCSI shared storage) to 4.2 recently, mainly because of the GUI changes. It should be noted here that 4.0 -> 4.0 live migration has always worked perfectly for us between any combination of the...
  4. R

    Can't live migrate between Proxmox 4.0-16 and 4.0-19

    I'm getting a live migration failure between any two Proxmox nodes in a cluster (of 5) where one node is version 4.0-16 of proxmox-ve and the other node is version 4.0-19. The end of the pretty unhelpful error mesages is no doubt familiar: Nov 04 16:54:17 ERROR: online migrate failure -...
  5. R

    Proxmox 4.0 installer has bizarre "Britain (UK)" country

    It's a minor issue I know, but the Country prompt in the Proxomox 4.0 installer has a very bizarre "Britain (UK)" setting for people in the United Kingdom. This is weird for 3 reasons: 1. It should be Great Britain and not Britain. 2. Adding "(UK)" is a little redundant, though technically that...
  6. R

    Live migration machine type issue between 3.1 and 3.3 (and maybe 3.4?)

    We added a new Proxmox server to our cluster a while back and it's happily running Proxmox 3.3 (we will schedule a 3.4 update on it at some point soon). The older machines in the cluster are running 3.1 and I wanted to bring them up to 3.3 (or 3.4). To avoid downtime, the standard practice is...