Any tips about this error?
2023-08-10 18:24:57,544-03 INFO
[org.ovirt.engine.core.bll.MigrateVmToServerCommand] (default task-4)
[633be3a0-3afd-490c-b412-805d2b14e1c2] Lock Acquired to object
'EngineLock:{exclusiveLocks='[29032e83-cfaf-4d30-bcc2-df72c5358552=VM]',
sharedLocks=''}'
2023-08-10
This is the engine log (systemctl restart ovirt-engine)
2023-08-10 19:26:09,996-03 INFO [org.jboss.as.server.deployment] (MSC
service thread 1-7) WFLYSRV0207: Starting subdeployment (runtime-name:
"bll.jar")
2023-08-10 19:26:09,996-03 INFO [org.jboss.as.server.deployment] (MSC
service thread
Thank you for such a detailed answer. Also, reading this forum, I found options
with changing the Ansible code. But without clear instructions and any results.
The option of installing oVirt on a supported processor and then installing an
unsupported one is interesting, but time-consuming.
If
Is it possible to install oVirt 4.3/4.4 on ProLiant BL460c G1 with Intel Xeon
E5345 processor@2.33GHz ?
In case of a setup failure, [ERROR] is fatal:[localhost]:
FAILED!=>{"Changed":false,"message":"The host was inoperable, deployment
errors: code 156:Host host1.test.com disabled because the
I believe oVirt draws the line at Nehalem, which contained important
improvements to VM performance like extended page tables. Your Core 2 based
Xeon is below that line and you'd have to change the code to make it work.
Ultimately oVirt is just using KVM, so if KVM works, oVirt can be made to
5 matches
Mail list logo
