Getting to know oVirt
by Alexandre Aguirre
I'm new to ovirt, I'm coming from Proxmox and VMware, so I had some doubts that I couldn't find myself;
- Via terminal, where are the VMs created in oVirt?
- What are the most used commands on a daily basis in the terminal?
- Can I use the host's local disk as storage for the VMs?
- Is glusterfs configuration native in ovirt, or do I need to install the part?
Thanks in advance for your attention!!
2 years, 3 months
Adding a new cluster is in doubt
by ziyi Liu
ovirt version 4.5.1
I didn't see the tutorial on the ovirt official website, but I found the tutorial of Red Hat Hyperconverged Infrastructure for Virtualization. Should I follow this tutorial to execute, or through Cockpit, first pass the three machines of the second cluster through glusterfs ansible to form a cluster of storage Add to the new cluster in the engine web interface
2 years, 3 months
oVirt node 4.4 repository missing package
by kenneth.hau@hactl.com
Hi there, I saw that there has new package of ovirt-node-ng-image-update-placeholder-4.4.10.3-1.el8.noarch.rpm has released on 2022-06-24. However, I would like to know if there has any plan to release new package of ovirt-node-ng-image-update-4.4.10.3-1.el8.noarch.rpm as the the package is still retain at 4.4.10.2-1. Many thanks.
2 years, 3 months
Cannot start VM after upgrade - certificate issue
by LAMARC
Hello,
after running a PoC oVirt setup for more than a year, I ran into the "expiring certificate issue". Done an full upgrade for 4.4, engine-setup, and "Enroll certificates" to all hosts, all hosts are now green, and the certificates are renewed:
- /etc/pki/vdsm/certs/vdsmcert.pem
- /etc/pki/vdsm/libvirt-spice/server-cert.pem
- /etc/pki/libvirt/clientcert.pem
- /etc/pki/vdsm/libvirt-migrate/server-cert.pem
But: I cannot start any VM any more. Getting:
engine.log:2022-08-16 16:34:36,209+02 ERROR [org.ovirt.engine.core.bll.RunVmCommand] (EE-ManagedThreadFactory-engine-Thread-213) [60c5f661-6231-4e03-87a5-f6e6f2c63ad1] Command 'org.ovirt.engine.core.bll.RunVmCommand' failed: EngineException: (Failed with error NotAfter: Mon Aug 15 09:15:42 CEST 2022 and code 5050)
Any ideas?
Cheers Marcus
2 years, 3 months
VM (live) migrate after update ovirt 4.2 -> 4.4
by Fabian Mohren
Hi,
we have upgrade the Cluster (and all Hosts) to oVirt 4.4 and Oracle Linux 8.5
After the Upgrade, we cannot migrate VMs from one Host to another (same Cluster).
oVirt stock, and on Hosts Tab we see the message (one the vm):
"VM-CPU dosent match the Cluster-CPU".
We checked the xml config from kvm
We checked the DB for Cluster-CPU and VM-CPU - its the same (Cascadelake-Server-noTSX,-mpx).
select name, cpu_name, cpu_flags from cluster;
name | cpu_name | cpu_flags
--------------------------+----------------------------------------+------------------------------------
TestMigrationCluster | Intel Haswell Family | vmx,nx,model_Haswell-noTSX
select vm_guid, vm_name, cpu_name from vms where vm_name='oVirtTest';
vm_guid | vm_name | cpu_name
--------------------------------------+-----------+---------------
421ade0f-4d76-941d-3de2-13b1df54c89d | oVirtTest | Haswell-noTSX
We create a new "TestMigrationCluster" with two Hosts for better testing.
We reinstall the Hosts (OS + ovirt) = failed
We reset the manager to an older State = failed
We have no idea where the "Cluster-CPU check" is running?
We search for a ansible role or play but nothing found
Have anybody a idea where the Cluster CPU check is?
Thanks & Regards
Fabian
2 years, 3 months
Server patching on the oVirt node
by kenneth.hau@hactl.com
Server patching on the oVirt node
Hi there, we have some oVirt node running on 4.4 and found vulnerabilities after performed TVM scan on the server. Please advise how can we fix the below vulnerabilities.
Python Unsupported Version Detection
CentOS 8 : cockpit (CESA-2022:2008)
CentOS 8 : container-tools:3.0 (CESA-2022:1793)
CentOS 8 : container-tools:3.0 (CESA-2022:2143)
CentOS 8 : samba (CESA-2022:2074)
CentOS 8 : maven:3.6 (CESA-2022:1860)
2 years, 3 months
Changing Cluster Compatibility Version from 4.6 to 4.7 issue
by Alexandr Mikhailov
Hi!
Just uprgaded from 4.4. to 4.5. Had all the problems with this update, such as postgresql-jdbc version and with stripeCount in cli.y . But I managed it, everything works more or less.
Now I cannot raise the Cluster compatibility level. The problem is that increasing the level tries to change something in the HE configuration but cannot.
This is error massage:
Error while executing action: Cannot update cluster because the update triggered update of the VMs/Templates and it failed for the following: HostedEngine. "There was an attempt to change Hosted Engine VM values that are locked." is one of the error(s).
To fix the issue, please go to each VM/Template, edit, change the Custom Compatibility Version (or other fields changed previously in the cluster dialog) and press OK. If the save does not pass, fix the dialog validation. After successful cluster update, you can revert your Custom Compatibility Version change (or other changes). If the problem still persists, you may refer to the engine.log file for further details.
If i trying to edit HE machine without changing anything i se next error: There was an attempt to change Hosted Engine VM values that are locked/ I think this is linked issues.
Log from engine log when i trying to update Cluster version:
2022-05-27 14:20:54,410+06 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-212) [1b8b6b78] EVENT_ID: CLUSTER_CANNOT_UPDATE_VM_COMPATIBILITY_VERSION(12,005), Ca
nnot update compatibility version of Vm/Template: [HostedEngine], Message: There was an attempt to change Hosted Engine VM values that are locked.
Log from engine log when i trying to save HE configuration without any changing:
2022-05-27 14:34:10,965+06 INFO [org.ovirt.engine.core.bll.UpdateVmCommand] (default task-220) [9cdfe99b-b7a1-46a4-ab3f-fc110b939f08] Lock Acquired to object 'EngineLock:{exclusiveLocks='[HostedEngine=
VM_NAME]', sharedLocks='[4d6a0ffb-a221-4ef8-9846-6ada7690e74a=VM]'}'
2022-05-27 14:34:10,968+06 WARN [org.ovirt.engine.core.bll.UpdateVmCommand] (default task-220) [9cdfe99b-b7a1-46a4-ab3f-fc110b939f08] Validation of action 'UpdateVm' failed for user admin@internal-auth
z. Reasons: VAR__ACTION__UPDATE,VAR__TYPE__VM,VM_CANNOT_UPDATE_HOSTED_ENGINE_FIELD
2022-05-27 14:34:10,969+06 INFO [org.ovirt.engine.core.bll.UpdateVmCommand] (default task-220) [9cdfe99b-b7a1-46a4-ab3f-fc110b939f08] Lock freed to object 'EngineLock:{exclusiveLocks='[HostedEngine=VM_
NAME]', sharedLocks='[4d6a0ffb-a221-4ef8-9846-6ada7690e74a=VM]'}'
It is not clear what is happening and what changes to the configuration are trying to be saved and what to do about it. Help please.
2 years, 3 months