running
>>
>> - data_p shut off
>>
>>
>>
>> How could this vm persist over reboots and reinstalls? And how would I
>> remove this ?
>>
>>
>>
>>
>>
>> *Von:* Michal Skriv
gt;
>
> How could this vm persist over reboots and reinstalls? And how would I
> remove this ?
>
>
>
>
>
> *Von:* Michal Skrivanek [mailto:michal.skriva...@redhat.com]
> *Gesendet:* Donnerstag, 23. Februar 2017 17:35
> *An:* Sven Achtelik ; Martin Sivak <
> msi
How could this vm persist over reboots and reinstalls? And how would I remove
this ?
Von: Michal Skrivanek [mailto:michal.skriva...@redhat.com]
Gesendet: Donnerstag, 23. Februar 2017 17:35
An: Sven Achtelik ; Martin Sivak
Cc: Arman Khalatyan ; users
Betreff: Re: [ovirt-users] Mirgration issues
Von: Arman Khalatyan [mailto:arm2...@gmail.com <mailto:arm2...@gmail.com>]
> Gesendet: Donnerstag, 23. Februar 2017 13:45
>
> An: Sven Achtelik mailto:sven.achte...@eps.aero>>
> Cc: Yanir Quinn mailto:yqu...@redhat.com>>; users
> mailto:users@ovirt.org>
Did that twice and it didn’t change anything.
Von: Arman Khalatyan [mailto:arm2...@gmail.com]
Gesendet: Donnerstag, 23. Februar 2017 15:02
An: Sven Achtelik
Cc: Yanir Quinn ; users
Betreff: Re: [ovirt-users] Mirgration issues
engine gui.
On Thu, Feb 23, 2017 at 1:46 PM, Sven Achtelik
13:45
>
> *An:* Sven Achtelik
> *Cc:* Yanir Quinn ; users
> *Betreff:* Re: [ovirt-users] Mirgration issues
>
>
>
> Just random thought: try to reinstall the "bad" host:)
>
>
>
> On Thu, Feb 23, 2017 at 1:32 PM, Sven Achtelik
> wrote:
>
> Yes, a
Do you mean just reinstalling from the Engine gui or reinstalling it completely
including the OS?
Von: Arman Khalatyan [mailto:arm2...@gmail.com]
Gesendet: Donnerstag, 23. Februar 2017 13:45
An: Sven Achtelik
Cc: Yanir Quinn ; users
Betreff: Re: [ovirt-users] Mirgration issues
Just random
ted eof
>
> Feb 23 06:30:10 ovirt-node03.mgmt.lan.company.lan vdsm[3788]: vdsm
> vds.dispatcher ERROR SSL error receiving from
> connected ('::1', 39914, 0, 0) at 0x37772d8>: unexpected eof
>
> Feb 23 06:30:11 ovirt-node03.mgmt.lan.company.lan vdsm[3788]: vdsm
&
about it and that it’s not fixed yet.
Von: Arman Khalatyan [mailto:arm2...@gmail.com]
Gesendet: Donnerstag, 23. Februar 2017 13:22
An: Sven Achtelik
Cc: Yanir Quinn ; users
Betreff: Re: [ovirt-users] Mirgration issues
if you check the hosts capabilities are they same??
what about systemctl status
m]
> *Gesendet:* Donnerstag, 23. Februar 2017 11:59
> *An:* Sven Achtelik
> *Cc:* Yanir Quinn ; users
>
> *Betreff:* Re: [ovirt-users] Mirgration issues
>
>
>
> Did you disable selinux? this can be a reason.
>
>
>
> On Thu, Feb 23, 2017 at 10:31 AM, Sven Acht
with nothing running on host 02.
Von: Arman Khalatyan [mailto:arm2...@gmail.com]
Gesendet: Donnerstag, 23. Februar 2017 11:59
An: Sven Achtelik
Cc: Yanir Quinn ; users
Betreff: Re: [ovirt-users] Mirgration issues
Did you disable selinux? this can be a reason.
On Thu, Feb 23, 2017 at 10:31 AM
ted Engine Information is also showing good on all hosts.
>
>
>
> *Von:* Yanir Quinn [mailto:yqu...@redhat.com]
> *Gesendet:* Mittwoch, 22. Februar 2017 11:21
> *An:* Sven Achtelik
> *Cc:* Fred Rolland ; users
>
> *Betreff:* Re: [ovirt-users] Mirgration issues
>
>
>
Achtelik
Cc: Fred Rolland ; users
Betreff: Re: [ovirt-users] Mirgration issues
I can spot in engine.log that ovirt-node03.mgmt.lan.company.lan (if it is your
host 3) is being filtered out when trying to migrate the VM :
2017-02-21 04:32:33,618-06 INFO [org.ovirt.engine.core.bll.MigrateVmCommand
f11-f1297d149be3 14551 NAME
> Up 10.6.0.181
>
>
>
> I even tried that after restarting host 2 and at this point I’m sure there
> were no VMs running.
>
>
>
>
>
> *Von:* Fred Rolland [mailto:froll...@redhat.com]
> *Gesendet:* Diensta
.
Von: Fred Rolland [mailto:froll...@redhat.com]
Gesendet: Dienstag, 21. Februar 2017 13:59
An: Sven Achtelik
Cc: users
Betreff: Re: [ovirt-users] Mirgration issues
I see the following in the source VDSM log :
2017-02-21 05:53:28,067 INFO (migsrc/8733d4a6) [virt.vm]
(vmId='8733d4a6-0844-4955
I see the following in the source VDSM log :
2017-02-21 05:53:28,067 INFO (migsrc/8733d4a6) [virt.vm]
(vmId='8733d4a6-0844-4955-804f-6b919e93e076') starting migration to
qemu+tls://ovirt-node02.mgmt.lan.company.lan/system with miguri tcp://
172.16.4.19 (migration:453)
2017-02-21 05:53:28,262 ERRO
16 matches
Mail list logo
