Unable to MIgrate VDI when host is low on free memory
-
Hi,
Low how? can you provide some numbers? Thanks!
-
@olivierlambert Here is the amount of free RAM on the system.
But when I try to migrate a VDI to a new storage repo, I get this error:
HOST_NOT_ENOUGH_FREE_MEMORY(8663334912, 3104964608)
I can create a new VM on that SR without issue.
-
Do you have dynamic memory set for your VM?
-
You say you're trying to migrate a vdi, where are you trying to migrate it?
To a SR attached to your current host or to another host/pool?If you're trying to migrate it to another host/pool this is something that i've seen as well when dom0 is not assigned enough RAM, we usually gave them 16Gg which seemed to resolved these kind of issues back when we were running 8.2.0.
-
@olivierlambert I do not.
-
@nikade I am trying to move the VDI from one storage SR to another on the same host. This is not in a cluster. This is a standalone host.
-
@hitechhillbilly said in Unable to MIgrate VDI when host is low on free memory:
@nikade I am trying to move the VDI from one storage SR to another on the same host. This is not in a cluster. This is a standalone host.
Alright, check the /var/log/SMlog as well as /var/log/xensource to see whats going on, you'll find an error there.
-
@hitechhillbilly I'd say this is normal if you are low on RAM and you are doing a live VDI migration. XCP-ng requires some amount of free RAM on the host to be able to live migrate the VDI. The larger the VDI, the more RAM is needed but exact sizing is unknown to me. I've encountered this error numerous times so I consider it common.
The way around this is to shutdown the VM and then migrate the VDI. RAM requirements in that case are much much lower.
-
@bvitnik said in Unable to MIgrate VDI when host is low on free memory:
@hitechhillbilly I'd say this is normal if you are low on RAM and you are doing a live VDI migration. XCP-ng requires some amount of free RAM on the host to be able to live migrate the VDI. The larger the VDI, the more RAM is needed but exact sizing is unknown to me. I've encountered this error numerous times so I consider it common.
The way around this is to shutdown the VM and then migrate the VDI. RAM requirements in that case are much much lower.
Yea, I suggested giving dom0 16Gb. That was our standard sizing back in the days and it worked pretty well.
-
@nikade This is not related to Dom0 RAM. It's related to the host RAM.
