On Wed, Aug 22, 2018 at 3:07 PM Daniel Renaud <daniel(a)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(a)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(a)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(a)ovirt.org
>> To unsubscribe send an email to users-leave(a)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/SVE77SQAO5B...
>>
>
--
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