On Wed, Aug 22, 2018 at 5:28 PM Daniel Renaud <daniel@djj-consultants.com> wrote:
No more VM in problem since I remove the CPU type , etc.  Theses values came back the same as they was but no more problem starting the VMs after 

I see.
That's a pity because we cannot figure out what actually lead to that NPE that I saw in the engine log.
But glad to see that it works for you now. Thanks.
 

2018-08-22 9:58 GMT-04:00 Arik Hadas <ahadas@redhat.com>:


On Wed, Aug 22, 2018 at 4:51 PM Daniel Renaud <daniel@djj-consultants.com> wrote:
I checked for the unmanaged interface and they was all ok in the 3 vm

And do you still have a VM that experieces such failures?
 

--
Daniel Renaud
Analyste Sécurité & Système
Téléphone : 418-907-9530, poste 200
GPG key : 0x7189C9D0

Le 22 août 2018 à 09:43, Arik Hadas <ahadas@redhat.com> a écrit :



On Wed, Aug 22, 2018 at 3:07 PM Daniel Renaud <daniel@djj-consultants.com> wrote:
Hi

I didn't upgrade and the run once didn't solve the issue but ..... When I use run once again, I remove (in the system tab) Custom emulate machine and Custom CPU type (leave it blank) and the run once worked.  After that, I can shutdown and but without any problem.  If I go back to look the emulate machine and CPU type, it is back to the same value but now I can boot.

Please reply to the list.
You said that you have 3 VMs in that state - could you please check if you have unmanaged interfaces for the other 2 before fixing them that way?
 

2018-08-22 7:44 GMT-04:00 Arik Hadas <ahadas@redhat.com>:
Do you remember to what version of oVirt you upgraded the 4.1/4.0/3.6 cluster?
It sounds like a bug we had (relatively long time ago) that lead to having duplicated unmanaged devices.
Can you please check in the VM devices tab if you have unmanaged network interfaces? if you do, it was reported that running the VM in run-once mode would clear those devices (but you can also remove them from the database as well).

On Wed, Aug 22, 2018 at 1:38 PM <daniel@djj-consultants.com> wrote:
I also tried to export (work) and re-import(work) the same VM and try to start the imported one with the same result that it didn't start
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/SVE77SQAO5BUC2YQSBWRL54DKYB5FE62/



--
Daniel Renaud
Analyste Sécurité & Système
DJJ Consultants, http://www.djj-consultants.com
Téléphone : 418-907-9530, poste 200
GPG key : 0x7189C9D0



--
Daniel Renaud
Analyste Sécurité & Système
DJJ Consultants, http://www.djj-consultants.com
Téléphone : 418-907-9530, poste 200
GPG key : 0x7189C9D0