On Sat, Sep 17, 2016 at 2:25 PM, wodel youchi <wodel.you...@gmail.com>
wrote:

> Hi,
>
> I am testing the deployment of oVirt using ovirt-node next-gen and ovirt
> appliance on a nested KVM environment.
>
> My base system (the physical machine) is a FC24 with 16Go of RAM and
> nested KVM enabled.
> I used NFS for storage.
>
> Test with oVirt 4.0.3:
> - I created two hypervisors 5Go of RAM each and 4vCpu.
> - I installed ovirt-node next-gen OS.
> - I downloaded ovirt appliance and started the engine deploy using
> generated configuration from cloud-init (I reserved 2Go of RAM for the
> VM-engine).
>
> Problems :
> - I couldn't add the second hypervisor from the engine's GUI, when I tried
> to do it, ovirt-engine crashed.
>

Can you please attach logs?


> - I tried with the command line, the process terminated with errors.
>

The same.


> - There is no create a new ISO or Export domain only Data domain in the
> select list.
>
> Unfortunately I deleted the two hypervisors.
>
> Test with oVirt 4.0.4 RC3 :
> - I created two hypervisors 5Go of RAM each and 4vCpu.
> - I installed ovirt-node next-gen OS.
> - I downloaded ovirt appliance and started the engine deploy using
> generated configuration from cloud-init (I reserved 2Go of RAM for the
> VM-engine).
>
> Problems:
> - I couldn't add the second hypervisor from the engine's GUI, when I tried
> to do it, ovirt-engine crashed.
> - After adding the Data domain, the hosted_storage was added successfully,
> but the VM engine was not imported successfully, it's does not appear on
> the VMs tab.
>

https://bugzilla.redhat.com/show_bug.cgi?id=1376751


> - There is no create a new ISO or Export domain only Data domain in the
> select list.
> - I added the second hypervisor from the command line successfully.
> - I tried to put the first hypervisor in maintenance mode, migration of
> the VM engine was started, from the command line I could see that the VM is
> running on the second hypervisor, but the migration process didn't
> terminate, I tried to reactivate the first hypervisor and put it in
> maintenance mode again, this time the ovirt-engine crashed.
>
> Regards.
>
>
> _______________________________________________
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Reply via email to