> On Jun 17, 2016, at 12:12 PM, Fabrice Bacchella 
> <fabrice.bacche...@icloud.com> wrote:
> 
> 
>> Le 17 juin 2016 à 12:05, Vinzenz Feenstra <vfeen...@redhat.com 
>> <mailto:vfeen...@redhat.com>> a écrit :
>> 
>> Hi Fabrice,
>> 
>>> On Jun 17, 2016, at 11:41 AM, Fabrice Bacchella 
>>> <fabrice.bacche...@icloud.com <mailto:fabrice.bacche...@icloud.com>> wrote:
>>> 
>>> I'm running an up to date ovirt setup.
>>> 
>>> I tried to put an host in maintenance mode, with one VM running on it.
>>> 
>>> It failed with this message in vdsm.log:
>>> 
> 
>>> libvirtError: internal error: process exited while connecting to monitor: 
>>> 2016-06-17T09:30:04.429323Z qemu-kvm: -chardev 
>>> socket,id=charchannel0,path=/var/lib/libvirt/qemu/channels/b82209c9-42ff-457c-bb98-b6a2034833fc.com.redhat.rhevm.vdsm,server,nowait:
>>>  Failed to bind socket to 
>>> /var/lib/libvirt/qemu/channels/b82209c9-42ff-457c-bb98-b6a2034833fc.com.redhat.rhevm.vdsm:
>>>  Permission denied
>> 
>> This is pretty odd, could you please send me the out put of this:
>> 
>> # rpm -qa | grep vdsm
>> 
>> From the target and destination hosts. Thanks.
> 
> On the host I was trying to put on maintenance:
> vdsm-xmlrpc-4.17.28-0.el7.centos.noarch
> vdsm-4.17.28-0.el7.centos.noarch
> vdsm-infra-4.17.28-0.el7.centos.noarch
> vdsm-yajsonrpc-4.17.28-0.el7.centos.noarch
> vdsm-python-4.17.28-0.el7.centos.noarch
> vdsm-jsonrpc-4.17.28-0.el7.centos.noarch
> vdsm-hook-vmfex-dev-4.17.28-0.el7.centos.noarch
> vdsm-cli-4.17.28-0.el7.centos.noarch
> 
> And it was trying to send to an host with:
> vdsm-yajsonrpc-4.17.28-1.el7.noarch
> vdsm-cli-4.17.28-1.el7.noarch
> vdsm-python-4.17.28-1.el7.noarch
> vdsm-hook-vmfex-dev-4.17.28-1.el7.noarch
> vdsm-xmlrpc-4.17.28-1.el7.noarch
> vdsm-4.17.28-1.el7.noarch
> vdsm-infra-4.17.28-1.el7.noarch
> vdsm-jsonrpc-4.17.28-1.el7.noarch
> 
> And in the log about that:
> jsonrpc.Executor/1::DEBUG::2016-06-17 
> 11:39:57,233::__init__::503::jsonrpc.JsonRpcServer::(_serveRequest) Calling 
> 'VM.migrate' in bridge with {u'params': {u
> 'tunneled': u'false', u'dstqemu': u'XX.XX.XX.28', u'autoConverge': u'false', 
> u'src': u'nb0101.XXX', u'dst': u'nb0105.XXX:54321', u
> 'vmId': u'b82209c9-42ff-457c-bb98-b6a2034833fc', u'abortOnError': u'true', 
> u'compressed': u'false', u'method': u'online'}, u'vmID': 
> u'b82209c9-42ff-457c-bb9
> 8-b6a2034833fc'}
> jsonrpc.Executor/1::DEBUG::2016-06-17 11:39:57,234::API::547::vds::(migrate) 
> {u'tunneled': u'false', u'dstqemu': u'XX.XX.XX.28', u'autoConverge': 
> u'false', 
> u'src': u'nb0101.XXX', u'dst': u'nb0105.XXX:54321', u'vmId': 
> u'b82209c9-42ff-457c-bb98-b6a2034833fc', u'abortOnError': u'true', u'
> compressed': u'false', u'method': u'online’}

Thanks.

And on the destination server what are the access rights on 
/var/lib/libvirt/qemu/channels? 
And if you have SELinux enabled can you temporary set it to permissive on the 
destination and try to migrate?


> 

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

Reply via email to