You can not migrate VM with NUMA. They are pinned to host. Yaniv Dary Technical Product Manager Red Hat Israel Ltd. 34 Jerusalem Road Building A, 4th floor Ra'anana, Israel 4350109 Tel : +972 (9) 7692306 8272306 Email: ydary@redhat.com IRC : ydary On Mon, Feb 8, 2016 at 12:24 PM, Nathanaël Blanchet <blanchet@abes.fr> wrote:

Hi all,

I created a cluster of VM with the same CPu level, except that one of them only has one physical CPU. When trying to migrate, I get this message into engine.log :

3b-4810-b5a4-f415c90ffdca`::Failed to migrate Traceback (most recent call last): File "/usr/share/vdsm/virt/migration.py", line 294, in run self._startUnderlyingMigration(time.time()) File "/usr/share/vdsm/virt/migration.py", line 364, in _startUnderlyingMigration self._perform_migration(duri, muri) File "/usr/share/vdsm/virt/migration.py", line 403, in _perform_migration self._vm._dom.migrateToURI3(duri, params, flags) File "/usr/share/vdsm/virt/virdomain.py", line 68, in f ret = attr(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/libvirtconnection.py", line 124, in wrapper ret = f(*args, **kwargs) File "/usr/lib64/python2.7/site-packages/libvirt.py", line 1836, in migrateToURI3 if ret == -1: raise libvirtError ('virDomainMigrateToURI3() failed', dom=self) libvirtError: unsupported configuration: NUMA node 1 is unavailable

It seems that engine allows to mix multinode and mononode host into a same cluster whereas vms can't migrate between these nodes. I've never been using and configuring NUMA until now, so I don't understand why we are not allowed to migrate vms.* Thank you for your help

-- Nathanaël Blanchet

Supervision réseau Pôle Infrastrutures Informatiques 227 avenue Professeur-Jean-Louis-Viala 34193 MONTPELLIER CEDEX 5 Tél. 33 (0)4 67 54 84 55 Fax 33 (0)4 67 54 84 14 blanchet@abes.fr

_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users

Le 08/02/2016 11:24, Nathanaël Blanchet a écrit :

Hi all,

I created a cluster of VM with the same CPu level, except that one of them only has one physical CPU. When trying to migrate, I get this message into engine.log :

3b-4810-b5a4-f415c90ffdca`::Failed to migrate Traceback (most recent call last): File "/usr/share/vdsm/virt/migration.py", line 294, in run self._startUnderlyingMigration(time.time()) File "/usr/share/vdsm/virt/migration.py", line 364, in _startUnderlyingMigration self._perform_migration(duri, muri) File "/usr/share/vdsm/virt/migration.py", line 403, in _perform_migration self._vm._dom.migrateToURI3(duri, params, flags) File "/usr/share/vdsm/virt/virdomain.py", line 68, in f ret = attr(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/libvirtconnection.py", line 124, in wrapper ret = f(*args, **kwargs) File "/usr/lib64/python2.7/site-packages/libvirt.py", line 1836, in migrateToURI3 if ret == -1: raise libvirtError ('virDomainMigrateToURI3() failed', dom=self) libvirtError: unsupported configuration: NUMA node 1 is unavailable

It seems that engine allows to mix multinode and mononode host into a same cluster whereas vms can't migrate between these nodes. I've never been using and configuring NUMA until now, so I don't understand why we are not allowed to migrate vms.* Thank you for your help

Salut Nathanaël, https://bugzilla.redhat.com/show_bug.cgi?id=1303842 -- Nicolas ECARNOT