[ovirt-users] migration failures - libvirtError - listen attribute must match address attribute of first listen element

We have a new 4.1.1 cluster setup. Migration of VM's that have a console / graphics setup is failing. Migration of VM's that run headless succeeds. The red flag in vdsm.log on the source is: libvirtError: unsupported configuration: graphics 'listen' attribute '192.168.55.82' must match

Re: [ovirt-users] migration failures

> On 23 Feb 2017, at 17:08, Michael Watters wrote: > > I canceled the migration and manually moved the VM to another host > running ovirt 4.0. The source node was then able to set itself to > maintenance mode without any errors. > > On 02/23/2017 10:46 AM, Michael

Re: [ovirt-users] migration failures

On 02/23/2017 10:28 AM, Francesco Romani wrote: > > The load/save state errors are most often found when the two sides of > the migration have different and incompatible version of QEMU. > In turn, this is quite often a bug, because forward migrations (e.g. > from 2.3.0 to 2.4.0) are always

Re: [ovirt-users] migration failures

On 02/23/2017 10:28 AM, Francesco Romani wrote: > On 02/23/2017 04:20 PM, Michael Watters wrote: >> I have an ovirt cluster running ovirt 4.0 and I am seeing several errors >> when I attempt to put one of our nodes into maintenance mode. The logs >> on the source server show errors as follows.

Re: [ovirt-users] migration failures

On 02/23/2017 04:20 PM, Michael Watters wrote: > I have an ovirt cluster running ovirt 4.0 and I am seeing several errors > when I attempt to put one of our nodes into maintenance mode. The logs > on the source server show errors as follows. > > Feb 23 10:15:08 ovirt-node-production3.example.com

[ovirt-users] migration failures

I have an ovirt cluster running ovirt 4.0 and I am seeing several errors when I attempt to put one of our nodes into maintenance mode. The logs on the source server show errors as follows. Feb 23 10:15:08 ovirt-node-production3.example.com libvirtd[18800]: operation aborted: migration job: