[ovirt-users] Re: Help installing oVirt on single machine, without cockpit

2021-12-10 Thread cameronsplaze222
With this comment, I'm poking at getting the engine to run directly on the 
node. I figure worst case, I might try throwing it in a container if there's 
package conflicts. That'll at least give me the lighter-engine I'm looking for, 
along with not having to manage it's resources.

Looks like the powertools repo isn't enabled by default on the node, so 
following this guide let me enable all the different modules for the engine: 
https://computingforgeeks.com/enable-powertools-repository-on-centos-rhel-linux/

The engine-setup command is apart of "rpm install ovirt-engine-setup-base", 
which CentOS 8 can find, but not the node. It's inside the ovirt-4.4 repo too, 
so I have no idea why the node can't find it. To get the engine setup running 
on CentOS, I also needed to install 
ovirt-engine-setup-plugin-ovirt-engine-common (this bug here: 
https://bugzilla.redhat.com/show_bug.cgi?id=1114978), and the node couldn't 
find this package either.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/E5Z5RXJHWWESTOYSH546IN7CMO6LUAS3/


[ovirt-users] Re: Help installing oVirt on single machine, without cockpit

2021-12-10 Thread cameronsplaze222
Hi,

> ... You might want to check the list archives for previous discussions about 
> this ...

Thanks for those links! I have an idea for a path forward, but I'm not sure 
it's supported. It looks like oVirt used to have a "all-in-one" option, but the 
hosted engine replaced that.

> I'd like to clarify that a hosted-engine deployment isn't always the best 
> approach for a single machine setup.

The other path I can see is installing the vanilla "engine-setup" to an oVirt 
node directly. That way the engine isn't inside a VM (I just hate how much 
cpu/ram you have to dedicate to the VM, and it's not even dynamic). Is it in a 
VM for security? I'll never need to move it for my use case, so I can live 
without the adaptability VM's come with.

If installing the engine directly to the node IS supported, this was where I 
was hitting my problem:
```bash
yum upgrade -y
yum install https://resources.ovirt.org/pub/yum-repo/ovirt-release44.rpm
yum upgrade -y
yum install ovirt-engine # HERE, can't find it. I can still install 
ovirt-engine-appliance for the hosted-engine setup.
```
I was also hitting a problem at this step, with the machine not knowing the 
modules exist: 
https://www.ovirt.org/documentation/installing_ovirt_as_a_standalone_manager_with_remote_databases/#Enabling_the_Red_Hat_Virtualization_Manager_Repositories_install_RHVM
 (i.e `dnf module enable javapackages-tools` returns `missing groups or 
modules: javapackages-tools`)

If installing the engine directly to a node ISN'T supported, what other routes 
for a single host setup are there? The only replacement for the all-in-one I 
can find, is the hosted-engine route.

> I suppose most people do supply a name here, and the few that don't, just 
> retry without reporting a bug

I saw a lot of people using input files anyways to automate the install, so I 
think I'll go that route too, if hosted-engine still ends up taking the least 
resources of the possible options.

Thanks!
Cameron
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/Y7A6HDEJO5JL5OJ2QHWO2BQVX62UXWZX/


[ovirt-users] Re: Upgrading 4.3.7 -> 4.4.9 :: Can't migrate vm from old to new host

2021-12-10 Thread Nathanaël Blanchet

Hi,

Is your migration network provisionned by DHCP?

If so, there is a known bug that prevents NetworkManager to set ip rule 
table for your migration network, and it won't be fixed before 4.5 release.


As a workaround, you can set the protocol to static or manually assign 
rule table to 0 as folowing on all on your hosts:


nmcli connection mod migration ipv4.route-table 0 && nmcli con up migration

Le 10/12/2021 à 17:07, Niklas Larsson via Users a écrit :

Hi,

we are trying to upgrade 4.3.7 -> 4.4.9 (Ovirt-Node, hosted engine). 
And things looks good until we try to migrate VM from 4.3.7 host to 
the 4.4.9 host, it fails with an generic error - and in below is from 
the vsdm.log from the 4.3.7 host.


Migrating VM from 4.4.9 host -> 4.3.7 host works.

Upgraded the 4.3.7 to 4.3.10 - did not solve it

Log from the 4.3 host:
2021-12-10 16:18:22,829+0100 INFO  (jsonrpc/1) [api.virt] START 
migrate(params={u'incomingLimit': 2, u'src': 
u'kvm22.shg.mgn.weblink.se', u'dstqemu': u'10.1.2.111', 
u'autoConverge': u'true', u'tunneled': u'false', u'enableGuestEvents': T
rue, u'dst': u'kvm21.shg.mgn.weblink.se:54321', 
u'convergenceSchedule': {u'init': [{u'params': [u'100'], u'name': 
u'setDowntime'}], u'stalling': [{u'action': {u'params': [u'150'], 
u'name': u'setDowntime'}, u'limit': 1}, {u'action': {u'params': 
[u'200'], u'name': u'setDowntime'}, u'limit': 2}, {u'action': 
{u'params': [u'300'], u'name': u'setDowntime'}, u'limit': 3}, 
{u'action': {u'params': [u'400'], u'name': u'setDowntime'}, u'limit': 
4}, {u'action': {u'params': [u'500'], u'name': u'setDowntime'}, 
u'limit': 6}, {u'action': {u'params': [], u'name': u'abort'}, 
u'limit': -1}]}, u'vmId': u'11f3a2aa-7951-4064-92f9-bb8ab515373b', 
u'abortOnError': u'true', u'outgoingLimit': 2, u'compressed': 
u'false', u'maxBandwidth': 62, u'method': u'online'}) 
from=:::10.1.2.51,46546, 
flow_id=03aca28c-00c9-4b58-a1e8-3aa355e162c2, 
vmId=11f3a2aa-7951-4064-92f9-bb8ab515373b (api:48)
2021-12-10 16:18:22,831+0100 INFO  (jsonrpc/1) [api.virt] FINISH 
migrate return={'status': {'message': 'Migration in progress', 'code': 
0}, 'progress': 0} from=:::10.1.2.51,46546, 
flow_id=03aca28c-00c9-4b58-a1e8-3aa355e162c2, 
vmId=11f3a2aa-7951-4064-92f9-bb8ab515373b (api:54)
2021-12-10 16:18:22,831+0100 INFO  (jsonrpc/1) [jsonrpc.JsonRpcServer] 
RPC call VM.migrate succeeded in 0.01 seconds (__init__:312)
2021-12-10 16:18:22,873+0100 ERROR (migsrc/11f3a2aa) [virt.vm] 
(vmId='11f3a2aa-7951-4064-92f9-bb8ab515373b') [Errno -2] Name or 
service not known (migration:282)
2021-12-10 16:18:22,875+0100 ERROR (migsrc/11f3a2aa) [virt.vm] 
(vmId='11f3a2aa-7951-4064-92f9-bb8ab515373b') Failed to migrate 
(migration:450)

Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/vdsm/virt/migration.py", line 
402, in _regular_run

    self._setupVdsConnection()
  File "/usr/lib/python2.7/site-packages/vdsm/virt/migration.py", line 
239, in _setupVdsConnection

    client = self._createClient(port)
  File "/usr/lib/python2.7/site-packages/vdsm/virt/migration.py", line 
227, in _createClient
    client_socket = utils.create_connected_socket(host, int(port), 
sslctx)
  File "/usr/lib/python2.7/site-packages/vdsm/utils.py", line 435, in 
create_connected_socket

    socket.AF_UNSPEC, socket.SOCK_STREAM)
gaierror: [Errno -2] Name or service not known
2021-12-10 16:18:22,888+0100 INFO  (jsonrpc/7) [api.virt] START 
getMigrationStatus() from=:::10.1.2.51,46546, 
vmId=11f3a2aa-7951-4064-92f9-bb8ab515373b (api:48)
2021-12-10 16:18:22,888+0100 INFO  (jsonrpc/7) [api.virt] FINISH 
getMigrationStatus return={'status': {'message': 'Done', 'code': 0}, 
'migrationStats': {'status': {'message': 'Fatal error during 
migration', 'code': 12}, 'progress': 0}} from=:::10.1.2.51,46546, 
vmId=11f3a2aa-7951-4064-92f9-bb8ab515373b (api:54)
2021-12-10 16:18:22,889+0100 INFO  (jsonrpc/7) [jsonrpc.JsonRpcServer] 
RPC call VM.getMigrationStatus succeeded in 0.00 seconds (__init__:312)
2021-12-10 16:18:23,431+0100 INFO  (jsonrpc/3) [jsonrpc.JsonRpcServer] 
RPC call Host.ping2 succeeded in 0.00 seconds (__init__:312)


Any ideas?

/niklas
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/BWSVMZGNRNK5MBLJH3HSKZPRBCITL5XL/


--
Nathanaël Blanchet

Supervision réseau
SIRE
227 avenue Professeur-Jean-Louis-Viala
34193 MONTPELLIER CEDEX 5   
Tél. 33 (0)4 67 54 84 55
Fax  33 (0)4 67 54 84 14
blanc...@abes.fr
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 

[ovirt-users] Upgrading 4.3.7 -> 4.4.9 :: Can't migrate vm from old to new host

2021-12-10 Thread Niklas Larsson via Users

Hi,

we are trying to upgrade 4.3.7 -> 4.4.9 (Ovirt-Node, hosted engine). And 
things looks good until we try to migrate VM from 4.3.7 host to the 
4.4.9 host, it fails with an generic error - and in below is from the 
vsdm.log from the 4.3.7 host.


Migrating VM from 4.4.9 host -> 4.3.7 host works.

Upgraded the 4.3.7 to 4.3.10 - did not solve it

Log from the 4.3 host:
2021-12-10 16:18:22,829+0100 INFO  (jsonrpc/1) [api.virt] START 
migrate(params={u'incomingLimit': 2, u'src': 
u'kvm22.shg.mgn.weblink.se', u'dstqemu': u'10.1.2.111', u'autoConverge': 
u'true', u'tunneled': u'false', u'enableGuestEvents': T
rue, u'dst': u'kvm21.shg.mgn.weblink.se:54321', u'convergenceSchedule': 
{u'init': [{u'params': [u'100'], u'name': u'setDowntime'}], u'stalling': 
[{u'action': {u'params': [u'150'], u'name': u'setDowntime'}, u'limit': 
1}, {u'action': {u'params': [u'200'], u'name': u'setDowntime'}, 
u'limit': 2}, {u'action': {u'params': [u'300'], u'name': 
u'setDowntime'}, u'limit': 3}, {u'action': {u'params': [u'400'], 
u'name': u'setDowntime'}, u'limit': 4}, {u'action': {u'params': 
[u'500'], u'name': u'setDowntime'}, u'limit': 6}, {u'action': 
{u'params': [], u'name': u'abort'}, u'limit': -1}]}, u'vmId': 
u'11f3a2aa-7951-4064-92f9-bb8ab515373b', u'abortOnError': u'true', 
u'outgoingLimit': 2, u'compressed': u'false', u'maxBandwidth': 62, 
u'method': u'online'}) from=:::10.1.2.51,46546, 
flow_id=03aca28c-00c9-4b58-a1e8-3aa355e162c2, 
vmId=11f3a2aa-7951-4064-92f9-bb8ab515373b (api:48)
2021-12-10 16:18:22,831+0100 INFO  (jsonrpc/1) [api.virt] FINISH migrate 
return={'status': {'message': 'Migration in progress', 'code': 0}, 
'progress': 0} from=:::10.1.2.51,46546, 
flow_id=03aca28c-00c9-4b58-a1e8-3aa355e162c2, 
vmId=11f3a2aa-7951-4064-92f9-bb8ab515373b (api:54)
2021-12-10 16:18:22,831+0100 INFO  (jsonrpc/1) [jsonrpc.JsonRpcServer] 
RPC call VM.migrate succeeded in 0.01 seconds (__init__:312)
2021-12-10 16:18:22,873+0100 ERROR (migsrc/11f3a2aa) [virt.vm] 
(vmId='11f3a2aa-7951-4064-92f9-bb8ab515373b') [Errno -2] Name or service 
not known (migration:282)
2021-12-10 16:18:22,875+0100 ERROR (migsrc/11f3a2aa) [virt.vm] 
(vmId='11f3a2aa-7951-4064-92f9-bb8ab515373b') Failed to migrate 
(migration:450)

Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/vdsm/virt/migration.py", line 
402, in _regular_run

    self._setupVdsConnection()
  File "/usr/lib/python2.7/site-packages/vdsm/virt/migration.py", line 
239, in _setupVdsConnection

    client = self._createClient(port)
  File "/usr/lib/python2.7/site-packages/vdsm/virt/migration.py", line 
227, in _createClient

    client_socket = utils.create_connected_socket(host, int(port), sslctx)
  File "/usr/lib/python2.7/site-packages/vdsm/utils.py", line 435, in 
create_connected_socket

    socket.AF_UNSPEC, socket.SOCK_STREAM)
gaierror: [Errno -2] Name or service not known
2021-12-10 16:18:22,888+0100 INFO  (jsonrpc/7) [api.virt] START 
getMigrationStatus() from=:::10.1.2.51,46546, 
vmId=11f3a2aa-7951-4064-92f9-bb8ab515373b (api:48)
2021-12-10 16:18:22,888+0100 INFO  (jsonrpc/7) [api.virt] FINISH 
getMigrationStatus return={'status': {'message': 'Done', 'code': 0}, 
'migrationStats': {'status': {'message': 'Fatal error during migration', 
'code': 12}, 'progress': 0}} from=:::10.1.2.51,46546, 
vmId=11f3a2aa-7951-4064-92f9-bb8ab515373b (api:54)
2021-12-10 16:18:22,889+0100 INFO  (jsonrpc/7) [jsonrpc.JsonRpcServer] 
RPC call VM.getMigrationStatus succeeded in 0.00 seconds (__init__:312)
2021-12-10 16:18:23,431+0100 INFO  (jsonrpc/3) [jsonrpc.JsonRpcServer] 
RPC call Host.ping2 succeeded in 0.00 seconds (__init__:312)


Any ideas?

/niklas
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/BWSVMZGNRNK5MBLJH3HSKZPRBCITL5XL/


[ovirt-users] Re: Migrated a VM from VMware to Ovirt using import ova option. Task stuck and running for day 2 now.

2021-12-10 Thread Chris Heisler
I would like to add that I'm getting the same issue but the VM imports. I'm 
trying to import the VM from Veeam to enable RHEV native backups. I would LOVE 
to get this feature going!

___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/ZG3YVDYMCIM6TASZACID47ZH3NHE5FLC/