Search results

(I know too broad a question ... I'll try to narrow it down) I'm often migrating vm's but sometimes it fails. E.g. I migrate a vm from node 1 to node 2, and it failed after memory was transferred. (log below) A second attempt between the same hosts worked OK. node1: proxmox-ve: 6.2-1...

I've now migrated all vm's during a maintenance window ... no failures. So I'm all up to 6.x now.

I'd like to upgrade the last node in my cluster, but to do that I first want to migrate all vm's to another node. :( dependency loop... I've not been able to identify why some migrations worked and some others failed. (while migrating between the same nodes)

I think I'm seeing the same issue here. I'm upgrading my cluster from 5.x(latest) to 6.x(latest) and for that migrating all vm's to an already upgraded server. The failure occurs about when the memory transfer is finished. The VM then stops. And remains on the source server. I have to manually...

Thanks, had the same issue and this helped. It would be nice to add this to the wiki under Preconditions or Troubleshooting. The Jessie to stretch upgrade was apparently not affected by this, I found a kernel from before that upgrade. So I extended the command from the install wiki page where...

Thanks, I don't have a screenlog of the check output from before but must have interpreted it as related to having to do the corosync upgrade. Maybe extending the current "Corosync transport explicitly set to '$transport' instead of implicit default!" with "Change to 'knet' before upgrading...

I've upgraded corosync in my cluster in preparation of the upgrade to Proxmox 6.x. (followed https://pve.proxmox.com/wiki/Upgrade_from_5.x_to_6.0) I did have some difficulties ... but it worked. After upgrading the first node I got: # pvecm status Cannot initialize CMAP service Then it...

Thanks... now requested in https://bugzilla.proxmox.com/show_bug.cgi?id=2413

Any idea which component is setting this limit? A kernel module?

On a Proxmox host I noticed that memory ballooning kicks in when the host is reaching 80% capacity on it's RAM. This was confirmed in the docs. Is there a setting to tune that? On a 128GB machine it feels not ok to take memory from a guest when the host still has 25GB free. The 'free' space...

Q1: See https://bugzilla.proxmox.com/show_bug.cgi?id=438 Q2: I had the same thought and just created https://bugzilla.proxmox.com/show_bug.cgi?id=1822

I was also seeing this on a server, I'm fairly sure I "always" run dist-upgrade... It turned out I still had the linux-image-amd64 package installed. In the install docs removing that is an optional step... but maybe it needs a bit more emphasis. Here's the output of a dist upgrade with extra...

Single disk is OK, but with multiple disks I'm also having trouble. I recently opened a bugzilla issue for this in https://bugzilla.proxmox.com/show_bug.cgi?id=1664

I recently opened a bugzilla issue for this in https://bugzilla.proxmox.com/show_bug.cgi?id=1664

In NiSv's example 108 is the vm number from which the source can be derived, and server8 is the name of the destination server.

I'm not sure about the iso image, but local LVM disks can be live migrated. It's CLI only at the moment though, see https://forum.proxmox.com/threads/live-migration-with-local-directories.30443/

I just tried the live migration via cli with a single vm disk on LVM. TLDR: It works :) After initially failing it turned out my firewall should have tcp 60000 open. Maybe that's something to add to the 'Ports used by Proxmox VE' section on https://pve.proxmox.com/wiki/Firewall ? Some other...