Search results

  1. R

    Big proxmox installations

    We have a 5-node Proxmox cluster and in the early days tried out GlusterFS and found it was a buggy-as-hell and slow disaster :-( It doesn't help that Proxmox bundled ancient horrendously buggy versions of GlusterFS for a long time (and weren't interested in updating them when I queried it in...
  2. R

    Meltdown and Spectre Linux Kernel fixes

    We have some fairly old Dell PowerEdge servers (just about in warranty) that haven't had BIOS updates in over a year . so I suspect they won't get a BIOS update for Meltdown/Spectre. I was wondering if adding the intel-microcode package from the non-free Debian repo would help (assuming that's...
  3. R

    Live KVM migration without share storage

    I'm wondering if a "double rsync" would work here to reduce the pause-time when migrating local filestore: Rsync node1 local filestore to node2 with no VM pausing/migration Live migrate node1 VM to node2, but pause node2's VM rather than running it at the end of the migration (node1's VM would...
  4. 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...
  5. R

    Upgrade 4.1 cluster to 4.2

    I had a very similar issue trying to live migrate from 4.0 to 4.2 which was fixed by updating just qemu-server and its dependencies. Whilst 4.0 -> 4.2 is a 2-version jump and might not be tested by devs, the fact this issue also applied to 4.1 -> 4.2 live migrations is, yet again, a sign that...
  6. R

    Live migration between 4.0 and 4.2 fails in both directions

    The snag with "apt-get update qemu-server" on 4.0 is that it brings in the entire 4.2 release as an update, which is a little risky with running VMs on a 4.0 server. I found these commands did the trick on 4.0 though: apt-get update apt-get install qemu-server pve-cluster pve-manager...
  7. 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...
  8. R

    Proxmox VE 4.1 released!

    We've got a few Proxmox 3.4 nodes that I've been waiting patiently for an update to the glusterfs-client (3.5.2) in any later Proxmox release to hopefully fix a terrible "create 1,000,000 open file handles in 2 hours" bug that the 3.5.2 release seems to have. According to the "pveversion -v"...
  9. R

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

    > qm config VMID Some items below have been changed to retain anonymity bootdisk: virtio0 cores: 4 memory: 16384 name: test01 net0: virtio=01:02:03:04:05:06,bridge=vmbr1 net1: virtio=07:08:09:10:11:12,bridge=vmbr2 onboot: 1 ostype: l26 sockets: 1 virtio0...
  10. 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 -...
  11. R

    Upgrading to V4 from much earlier versions

    I couldn't even upgrade a 3.X node to 4.X following the official guide in the Wiki - lots of interactive choices during the upgrade that the Wiki never mentioned and quite a lot of warning messages throughout. I managed to bork the upgrade badly enough, that I ended up doing a clean install of...
  12. R

    [SOLVED] Upgrading Proxmox 4.0 from 3.4 - Web Interface "Connection Refused"

    I *always* backup /etc regularly for all my Proxmox servers - it should be made very clear that all Proxmox sysadmins need to do at least this. Yes, backup the disk images too, though I use iSCSI for my images because I run a clustered Proxmox. If you upgrade and /etc/pve/qemu-server has been...
  13. R

    recreate vm.conf

    You don't say what sort of configuration you typically use in general terms - local storage, iSCSI, multiple network interfaces, version of Proxmox etc. The network interface info could be retrieved from your running VMs (e.g. get the MAC address, but you may also be using bridges/VLANs which...
  14. 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...
  15. R

    Backup in Large VM Environment

    We use Amanda 3 ourselves and it's great for backing up Linux guest VMs. However, the Windows Amanda client is frankly so bad (full of bugs, ludicrously installs and uses MySQL on the *client*, times out, produces a ZIP64 image that *only* PKWare's Zip Reader can read, no client fixes for over 3...
  16. R

    Proxmox v4 Estimate for first beta

    Can I please suggest that live migration between two Proxmox servers - one running 3.4 and one running 4.0 - is tested and shown to work (ideally in both directions, but at least in the 3.4 -> 4.0 direction)? Sadly, such testing didn't take place for 3.1 -> Proxmox 3.3+ versions, completely...
  17. R

    Moving/Copying from PVE 1.9 to PVE 3.4

    Assuming your 3.4 server is ready to go, shut down your VM102 first on the 1.9 machine, then copy all your local .raw files from your 1.9 machine to the same location on your 3.4 machine (e.g. probably /var/lib/vz/images/102). Without some sort of shared filestore (e.g. iSCSI) between the...
  18. 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...


The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get your own in 60 seconds.

Buy now!