7:40 a.m.
Hi,
I am using these versions for my test :
- ovirt-engine-appliance-4.4-20200723102445.1.el8.x86_64.rpm
- ovirt-node-ng-installer-4.4.1-2020072310.el8.iso
A single HCI server using nested KVM.
The gluster part works now without error, but when I click the
hosted-engine deployment button I get :
*System data could not be retrieved!*
*No valid network interface has been found *
* If you are using Bonds or VLANs Use the following naming conventions: *
- VLAN interfaces: physical_device.VLAN_ID (for example, eth0.23, eth1.128,
enp3s0.50)
- Bond interfaces: bond*number* (for example, bond0, bond1)
- VLANs on bond interfaces: bond*number*.VLAN_ID (for example, bond0.50,
bond1.128)
* Supported bond modes: active-backup, balance-xor, broadcast, 802.3ad
* Networking teaming is not supported and will cause errors
From this log file I get :
cat ovirt-hosted-engine-setup-ansible-get_network_interfaces-xxxxxxxx.log
2020-07-29 15:27:09,246+0100 DEBUG var changed: host "localhost" var
"otopi_host_net" type "<class 'list'>" value: "[
"enp1s0",
"enp2s0"
]"
2020-07-29 15:27:09,246+0100 INFO ansible ok {'status': 'OK',
'ansible_type': 'task', 'ansible_playbook':
'/usr/share/ovirt-hosted-eng
ine-setup/ansible/trigger_role.yml', 'ansible_host': 'localhost',
'ansible_task': 'Filter unsupported interface types', 'task_duration
': 0}
2020-07-29 15:27:09,246+0100 DEBUG ansible on_any args
<ansible.executor.task_result.TaskResult object at 0x7fe804bc5940> kwargs
2020-07-29 15:27:09,514+0100 INFO ansible task start {'status': 'OK',
'ansible_type': 'task', 'ansible_playbook':
'/usr/share/ovirt-ho
sted-engine-setup/ansible/trigger_role.yml', 'ansible_task':
'ovirt.hosted_engine_setup : debug'}
2020-07-29 15:27:09,515+0100 DEBUG ansible on_any args TASK:
ovirt.hosted_engine_setup : debug kwargs is_conditional:False
2020-07-29 15:27:09,515+0100 DEBUG ansible on_any args localhostTASK:
ovirt.hosted_engine_setup : debug kwargs
2020-07-29 15:27:09,792+0100 INFO ansible ok {'status': 'OK',
'ansible_type': 'task', 'ansible_playbook':
'/usr/share/ovirt-hosted-eng
ine-setup/ansible/trigger_role.yml', 'ansible_host': 'localhost',
'ansible_task': '', 'task_duration': 0}
2020-07-29 15:27:09,793+0100 DEBUG ansible on_any args
<ansible.executor.task_result.TaskResult object at 0x7fe804cb45f8> kwargs
2020-07-29 15:27:10,059+0100 INFO ansible task start {'status': 'OK',
'ansible_type': 'task', 'ansible_playbook':
'/usr/share/ovirt-ho
sted-engine-setup/ansible/trigger_role.yml', 'ansible_task':
'ovirt.hosted_engine_setup : Failed if only teaming devices are availible
'}
2020-07-29 15:27:10,059+0100 DEBUG ansible on_any args TASK:
ovirt.hosted_engine_setup : Failed if only teaming devices are availible
kwargs is_conditional:False
2020-07-29 15:27:10,060+0100 DEBUG ansible on_any args localhostTASK:
ovirt.hosted_engine_setup : Failed if only teaming devices are a
vailible kwargs
2020-07-29 15:27:10,376+0100 DEBUG var changed: host "localhost" var
"ansible_play_hosts" type "<class 'list'>" value:
"[]"
2020-07-29 15:27:10,376+0100 DEBUG var changed: host "localhost" var
"ansible_play_batch" type "<class 'list'>" value:
"[]"
2020-07-29 15:27:10,376+0100 DEBUG var changed: host "localhost" var
"play_hosts" type "<class 'list'>" value:
"[]"
2020-07-29 15:27:10,376+0100 ERROR ansible failed {
"ansible_host": "localhost",
"ansible_playbook":
"/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml",
"ansible_result": {
"_ansible_no_log": false,
"msg": "The conditional check
*'(otopi_host_net.ansible_facts.otopi_host_net | length == 0)' failed. The
error was: error while evaluating conditional
((otopi_host_net.ansible_facts.otopi_host_net | length == 0)): 'list
object' has no attribute 'ansible_facts'\n\nThe error appears to be in
'/usr/share/ansible/roles/ovirt.hosted_engine_setup/tasks/filter_team_devices.yml':
line 29, column 13, *
but may\nbe elsewhere in the file depending on the exact syntax
problem.\n\nThe offending line appears to be:\n\n- debug: var=otopi_ho
st_net\n ^ here\n\nThere appears to be both 'k=v' shorthand
syntax and YAML in this task. Only one syntax may be used.\n"
},
"ansible_task": "Failed if only teaming devices are availible",
"ansible_type": "task",
"status": "FAILED",
"task_duration": 0
}
2020-07-29 15:27:10,377+0100 DEBUG ansible on_any args
<ansible.executor.task_result.TaskResult object at 0x7fe804c175c0> kwargs
ignor
e_errors:None
2020-07-29 15:27:10,378+0100 INFO ansible stats {
"ansible_playbook":
"/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml",
"ansible_playbook_duration": "00:15 Minutes",
"ansible_result": "type: <class 'dict'>\nstr:
{'localhost': {'ok': 16,
'failures': 1, 'unreachable': 0, 'changed': 1, 'skipped':
2
, 'rescued': 0, 'ignored': 0}}",
"ansible_type": "finish",
"status": "FAILED"
}
2020-07-29 15:27:10,378+0100 INFO SUMMARY:
Duration Task Name
-------- --------
[ < 1 sec ] Execute just a specific set of steps
[ 00:02 ] Force facts gathering
[ 00:01 ] Get all active network interfaces
[ < 1 sec ] Filter bonds with bad naming
[ < 1 sec ] Generate output list
[ 00:01 ] Collect interface types
[ < 1 sec ] Get list of Team devices
[ < 1 sec ] Filter unsupported interface types
[ FAILED ] Failed if only teaming devices are availible
2020-07-29 15:27:10,378+0100 DEBUG ansible on_any args
<ansible.executor.stats.AggregateStats object at 0x7fe8074bce80> kwargs
Regards.
1:33 p.m.
New subject: oVirt 4.4.1 HCI single server deployment failed nested-kvm
I tried using nested virtualization, too, a couple of weeks ago.
I was using a 3 node HCI CentOS 7.8 cluster and I got pretty far. Configuring KVM to work
with nested page tables isn't all that well documented but I got there, I even
installed some host extensions, that seem requried.
Even the actual nesting, that is a VM run inside a VM did work, the setup came to the
point where it ran the hosted engine on temporary local storage, before it's picked
up, fixed up to run on the Gluster storage and restarted there. But that process failed
eventually, evidently because the overlay network doesn't support nesting. Where the
initial hosted engine is using a local bridge with the (in this case virtual) host--and
that works--afterwards it's using the overlay network and that evidently doesn't.
It was only then when I ran across a very obscure message somewhere in this mailing list,
that oVirt on top of oVirt in fact does not work at all! Up to that point it just
wasn't "supported".
When a hypervisor producer speaks of nested virtualization support, I would understand it
to mean that you can run their product under their product, ideally also somebody
else's product. I've run ESX on VMware workstation and that was pretty cool.
In the case of oVirt from what I have gathered (and I'd love to be wrong), it is
supposed to only mean that you can run oVirt on top of KVM.
Not the other way around, nor in any other way most likely.
To me that looks much more like an internal Redhat development facility, than a product
feature.
Of course I mostly wish they'd find a way to make it work like it does on VMware.
But next on my wishlist would be an explicit description of what does and what doesn't
work.
This way it was almost a week of a me against the computer adventure where I lost.
6:41 a.m.
New subject: oVirt 4.4.1 HCI single server deployment failed nested-kvm
I've run KVM VMs ontop oVirt Guest. Are you sure that the Nested Virtualization
is your problem ?
Best Regards,
Strahil Nikolov
На 29 юли 2020 г. 23:33:48 GMT+03:00, thomas(a)hoberg.net написа:
>I tried using nested virtualization, too, a couple of weeks ago.
>
>I was using a 3 node HCI CentOS 7.8 cluster and I got pretty far.
>Configuring KVM to work with nested page tables isn't all that well
>documented but I got there, I even installed some host extensions, that
>seem requried.
>
>Even the actual nesting, that is a VM run inside a VM did work, the
>setup came to the point where it ran the hosted engine on temporary
>local storage, before it's picked up, fixed up to run on the Gluster
>storage and restarted there. But that process failed eventually,
>evidently because the overlay network doesn't support nesting. Where
>the initial hosted engine is using a local bridge with the (in this
>case virtual) host--and that works--afterwards it's using the overlay
>network and that evidently doesn't.
>
>It was only then when I ran across a very obscure message somewhere in
>this mailing list, that oVirt on top of oVirt in fact does not work at
>all! Up to that point it just wasn't "supported".
>
>When a hypervisor producer speaks of nested virtualization support, I
>would understand it to mean that you can run their product under their
>product, ideally also somebody else's product. I've run ESX on VMware
>workstation and that was pretty cool.
>
>In the case of oVirt from what I have gathered (and I'd love to be
>wrong), it is supposed to only mean that you can run oVirt on top of
>KVM.
>
>Not the other way around, nor in any other way most likely.
>
>To me that looks much more like an internal Redhat development
>facility, than a product feature.
>
>Of course I mostly wish they'd find a way to make it work like it does
>on VMware.
>But next on my wishlist would be an explicit description of what does
>and what doesn't work.
>
>This way it was almost a week of a me against the computer adventure
>where I lost.
>_______________________________________________
>Users mailing list -- users(a)ovirt.org
>To unsubscribe send an email to users-leave(a)ovirt.org
>Privacy Statement: https://www.ovirt.org/privacy-policy.html
>oVirt Code of Conduct:
>https://www.ovirt.org/community/about/community-guidelines/
>List Archives:
>https://lists.ovirt.org/archives/list/users@ovirt.org/message/7WHRDMXMAWW3DPS24X23X3GCY5S2MCZF/
7:22 a.m.
New subject: oVirt 4.4.1 HCI single server deployment failed nested-kvm
Hello,
I ve the same problem, I ve already set up glusterfs and like to deplay a self hosted
engine. I ve allready ovirt self hosted engine deployed, with no problems. But here I get
the same error with hosted-engine --deploy and in the web frontend.
[ INFO ] TASK [ovirt.hosted_engine_setup : Failed if only teaming devices are availible]
[ ERROR ] fatal: [localhost]: FAILED! => {"msg": "The conditional check
'(otopi_host_net.ansible_facts.otopi_host_net | length == 0)' failed. The error
was: error while evaluating conditional ((otopi_host_net.ansible_facts.otopi_host_net |
length == 0)): 'list object' has no attribute 'ansible_facts'\n\nThe error
appears to be in
'/usr/share/ansible/roles/ovirt.hosted_engine_setup/tasks/filter_team_devices.yml':
line 29, column 13, but may\nbe elsewhere in the file depending on the exact syntax
problem.\n\nThe offending line appears to be:\n\n- debug: var=otopi_host_net\n
^ here\n\nThere appears to be both 'k=v' shorthand syntax and YAML in this task.
Only one syntax may be used.\n"}
[ ERROR ] Failed to execute stage 'Environment customization': Failed executing
ansible-playbook
is there a solution or just use an older ovirt `node iso?
bye shb
7:22 a.m.
New subject: oVirt 4.4.1 HCI single server deployment failed nested-kvm
Hi,
This is not my first time, I have installed ovirt, ovirt-hci, rhv and
rhv-hci on top of a kvm host many times to test some functionality or to
test a new version til this latest version of ovirt 4.4.1
On my first test there was a problem with HCI deployment the gluster part.
Now that part works with the new ovirt-node version but not the vm manager
deployment part.
Regards.
Le jeu. 30 juil. 2020 14:56, Strahil Nikolov via Users <users(a)ovirt.org> a
écrit :
I've run KVM VMs ontop oVirt Guest. Are you sure that the
Nested
Virtualization is your problem ?
Best Regards,
Strahil Nikolov
На 29 юли 2020 г. 23:33:48 GMT+03:00, thomas(a)hoberg.net написа:
>I tried using nested virtualization, too, a couple of weeks ago.
>
>I was using a 3 node HCI CentOS 7.8 cluster and I got pretty far.
>Configuring KVM to work with nested page tables isn't all that well
>documented but I got there, I even installed some host extensions, that
>seem requried.
>
>Even the actual nesting, that is a VM run inside a VM did work, the
>setup came to the point where it ran the hosted engine on temporary
>local storage, before it's picked up, fixed up to run on the Gluster
>storage and restarted there. But that process failed eventually,
>evidently because the overlay network doesn't support nesting. Where
>the initial hosted engine is using a local bridge with the (in this
>case virtual) host--and that works--afterwards it's using the overlay
>network and that evidently doesn't.
>
>It was only then when I ran across a very obscure message somewhere in
>this mailing list, that oVirt on top of oVirt in fact does not work at
>all! Up to that point it just wasn't "supported".
>
>When a hypervisor producer speaks of nested virtualization support, I
>would understand it to mean that you can run their product under their
>product, ideally also somebody else's product. I've run ESX on VMware
>workstation and that was pretty cool.
>
>In the case of oVirt from what I have gathered (and I'd love to be
>wrong), it is supposed to only mean that you can run oVirt on top of
>KVM.
>
>Not the other way around, nor in any other way most likely.
>
>To me that looks much more like an internal Redhat development
>facility, than a product feature.
>
>Of course I mostly wish they'd find a way to make it work like it does
>on VMware.
>But next on my wishlist would be an explicit description of what does
>and what doesn't work.
>
>This way it was almost a week of a me against the computer adventure
>where I lost.
>_______________________________________________
>Users mailing list -- users(a)ovirt.org
>To unsubscribe send an email to users-leave(a)ovirt.org
>Privacy Statement: https://www.ovirt.org/privacy-policy.html
>oVirt Code of Conduct:
>https://www.ovirt.org/community/about/community-guidelines/
>List Archives:
>
https://lists.ovirt.org/archives/list/users@ovirt.org/message/7WHRDMXMAWW...
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/XI4G36UJLPK...
2:10 p.m.
New subject: oVirt 4.4.1 HCI single server deployment failed nested-kvm
the 4.4.1 72310 node-ng iso has a broken installer. It failed to find my
regular ethernet interfaces and gave the no networks error.
The 4.4.2-rc seems to be working fine hosted-engine installer wise, to an
nfs mount for the engine VM storage. I didn't try the gluster wizard.
On Thu, Jul 30, 2020 at 10:30 AM wodel youchi <wodel.youchi(a)gmail.com>
wrote:
Hi,
This is not my first time, I have installed ovirt, ovirt-hci, rhv and
rhv-hci on top of a kvm host many times to test some functionality or to
test a new version til this latest version of ovirt 4.4.1
On my first test there was a problem with HCI deployment the gluster part.
Now that part works with the new ovirt-node version but not the vm manager
deployment part.
Regards.
Le jeu. 30 juil. 2020 14:56, Strahil Nikolov via Users <users(a)ovirt.org>
a écrit :
> I've run KVM VMs ontop oVirt Guest. Are you sure that the Nested
> Virtualization is your problem ?
> Best Regards,
> Strahil Nikolov
>
> На 29 юли 2020 г. 23:33:48 GMT+03:00, thomas(a)hoberg.net написа:
> >I tried using nested virtualization, too, a couple of weeks ago.
> >
> >I was using a 3 node HCI CentOS 7.8 cluster and I got pretty far.
> >Configuring KVM to work with nested page tables isn't all that well
> >documented but I got there, I even installed some host extensions, that
> >seem requried.
> >
> >Even the actual nesting, that is a VM run inside a VM did work, the
> >setup came to the point where it ran the hosted engine on temporary
> >local storage, before it's picked up, fixed up to run on the Gluster
> >storage and restarted there. But that process failed eventually,
> >evidently because the overlay network doesn't support nesting. Where
> >the initial hosted engine is using a local bridge with the (in this
> >case virtual) host--and that works--afterwards it's using the overlay
> >network and that evidently doesn't.
> >
> >It was only then when I ran across a very obscure message somewhere in
> >this mailing list, that oVirt on top of oVirt in fact does not work at
> >all! Up to that point it just wasn't "supported".
> >
> >When a hypervisor producer speaks of nested virtualization support, I
> >would understand it to mean that you can run their product under their
> >product, ideally also somebody else's product. I've run ESX on VMware
> >workstation and that was pretty cool.
> >
> >In the case of oVirt from what I have gathered (and I'd love to be
> >wrong), it is supposed to only mean that you can run oVirt on top of
> >KVM.
> >
> >Not the other way around, nor in any other way most likely.
> >
> >To me that looks much more like an internal Redhat development
> >facility, than a product feature.
> >
> >Of course I mostly wish they'd find a way to make it work like it does
> >on VMware.
> >But next on my wishlist would be an explicit description of what does
> >and what doesn't work.
> >
> >This way it was almost a week of a me against the computer adventure
> >where I lost.
> >_______________________________________________
> >Users mailing list -- users(a)ovirt.org
> >To unsubscribe send an email to users-leave(a)ovirt.org
> >Privacy Statement: https://www.ovirt.org/privacy-policy.html
> >oVirt Code of Conduct:
> >https://www.ovirt.org/community/about/community-guidelines/
> >List Archives:
> >
>
https://lists.ovirt.org/archives/list/users@ovirt.org/message/7WHRDMXMAWW...
> _______________________________________________
> Users mailing list -- users(a)ovirt.org
> To unsubscribe send an email to users-leave(a)ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
>
https://lists.ovirt.org/archives/list/users@ovirt.org/message/XI4G36UJLPK...
>
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/JINUOPVOYLO...
8:01 a.m.
New subject: oVirt 4.4.1 HCI single server deployment failed nested-kvm
That's exactly the point: Running oVirt on top of a vanilla KVM seems to be the only
case supported, because the Redhat engineers use that themselves for development, testing
and demoing.
Running virtual machines nested inside an oVirt VM via KVM also works per se, as
HostedEngineLocal during the setup is working, can be talked to etc. from the host that is
running the setup, because it uses a local bridge. You can even reach everyone from within
that nested VM on the outside, but the VM itsself is only accessible from the host at the
point (normal in all cases).
But in the next stage of the installation that locally prepared VM is modified to run on
the cluster storage, gluster in the HCI case and use the overlay network and that's
where it loses network connectivity, I guess because overlay networks lack nesting (I
guess there is still a non-overlay way to run oVirt and then perhaps it even works...)
And while I admire that network overlay stuff, it's also black magic to me, and
evidently not trivial if not downright impossible to resolve, which is most likey why the
Redhat engineers don't seem to pursue that path. At least that's what I read from
this comment, which really should be somewhere right next to where "nested
virtualization" is ever mentioned, to ensure expectations are properly managed.
https://lists.ovirt.org/pipermail/users/2017-March/080219.html
8:13 a.m.
New subject: oVirt 4.4.1 HCI single server deployment failed nested-kvm
Just looking at the release notes, using anything 'older' in the case of 4.4 seems
very rough going...
Testing 4.4 was actually how I got into the nesting domain this time around, because I
didn't have physical hardware left for another HCI cluster.
Testing of oVirt 4.4 on top of oVirt 4.3 including migration scenarios is probably the
most sensible use of nesting overall....
Alas I had similarly bad luck during my first evaluation of oVirt about a year (or two?)
ago, when I tried nesting oVirt on top of a big windows workstation with VMware
Workstation: Everything seemed to work just fine, but nested VMs just stopped right at
boot, without any error, but also no progress.
I had a vSphere cluster run no problem on that setup...
12:46 a.m.
New subject: oVirt 4.4.1 HCI single server deployment failed nested-kvm
Hello, I also met the same problem, have you solved your problem?
I wonder if it's the configuration of the network card.
1358
days inactive
1367
days old
8 comments
6 participants
participants (6)
-
Edward Berger -
Stefan Wolf -
Strahil Nikolov -
thomas＠hoberg.net -
wodel youchi -
xilazz＠126.com