- Users - oVirt List Archives

oVirt 4.4 Engine data migration & GUI notes
by Andrei Verovski 23 Jul '20

23 Jul '20

Hi ! I have installed new oVirt 4.4 Engine (as separate entity, not hosted engine) and migrated data from old 4.3 installation. Everything went smooth. Q: Which PostgreSQL password now active - new one I entered during install or old which could migrate with old data? I noticed GUI changes straight on dashboard. Icons on top (data centres, clusters, hosts, etc) are simply put, too huge. This serves no useful purpose whatsoever, and consumes screen real estate for no reason. Decreasing their size by 2/3 will help to make 1st page more informative at 1st sight without extra scrolling. with best regards Andrei

3 4

HostedEngine start error: could not find capabilities for arch=x86_64 domaintype=kvm
by Gianluca Cecchi 23 Jul '20

23 Jul '20

Hello, I'm importing a VM into a new oVirt environment that is in 4.3.10: the new host is the same as the previous one (only difference it is in 4.3.10 while the old one in 4.3.9). This VM acted as a single host HCI environment (with 4.3.9). I imported the storage domain containing the VM and its disks and the VM boots ok. Now its Hosted Engine VM (that is so a nested VM) doesn't start. I think it was good when I stopped/detached it... and so I would like to cross check and verify if I missed something configuring the new environment or something changed from 4.3.9 to 4.3.10 In vdsm.log I see this reason: 2020-07-23 14:38:20,489+0200 ERROR (vm/9233dc8b) [virt.vm] (vmId='9233dc8b-7a4d-4fac-8551-dc7407f36548') The vm start process failed (vm: 934) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 868, in _startUnderlyingVm self._run() File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 2892, in _run dom = self._connection.defineXML(self._domain.xml) File "/usr/lib/python2.7/site-packages/vdsm/common/libvirtconnection.py", line 131, in wrapper ret = f(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/common/function.py", line 94, in wrapper return func(inst, *args, **kwargs) File "/usr/lib64/python2.7/site-packages/libvirt.py", line 3743, in defineXML if ret is None:raise libvirtError('virDomainDefineXML() failed', conn=self) libvirtError: invalid argument: could not find capabilities for arch=x86_64 domaintype=kvm The relevant parts of the generated xml in vdsm.log seems: 2020-07-23 14:38:20,487+0200 INFO (vm/9233dc8b) [virt.vm] (vmId='9233dc8b-7a4d-4fac-8551-dc7407f36548') <?xml version="1.0" encoding="ut f-8"?><domain type="kvm" xmlns:ns0="http://ovirt.org/vm/tune/1.0" xmlns:ovirt-vm="http://ovirt.org/vm/1.0"> <name>HostedEngine</name> <uuid>9233dc8b-7a4d-4fac-8551-dc7407f36548</uuid> <memory>16777216</memory> <currentMemory>16777216</currentMemory> <iothreads>1</iothreads> <maxMemory slots="16">67108864</maxMemory> <vcpu current="2">32</vcpu> <sysinfo type="smbios"> <system> <entry name="manufacturer">oVirt</entry> <entry name="product">oVirt Node</entry> <entry name="version">7-7.1908.0.el7.centos</entry> <entry name="serial">704e1338-5dec-46f8-a186-8c2080dcefd8</entry> <entry name="uuid">9233dc8b-7a4d-4fac-8551-dc7407f36548</entry> </system> </sysinfo> <clock adjustment="0" offset="variable"> <timer name="rtc" tickpolicy="catchup"/> <timer name="pit" tickpolicy="delay"/> <timer name="hpet" present="no"/> </clock> <features> <acpi/> </features> <cpu match="exact"> <model>Skylake-Server</model> <feature name="spec-ctrl" policy="require"/> <feature name="ssbd" policy="require"/> <feature name="md-clear" policy="require"/> <topology cores="2" sockets="16" threads="1"/> <numa> <cell cpus="0,1" id="0" memory="16777216"/> </numa> </cpu> <cputune/> ... </metadata> <on_poweroff>destroy</on_poweroff><on_reboot>destroy</on_reboot><on_crash>destroy</on_crash></domain> (vm:2890) Any insights? The configuration of the new 4.3.10 physical oVirt environment that contains the VM has this cluster cpu type: Intel Skylake Server IBRS SSBD MDS Family Do I have to change it to anything else? I don't remember how it was set in 4.3.9 Thanks in advance, Gianluca

1 1

Re: [moVirt] New ovirt 4.4.0.3-1.el8 leaves disks in illegal state on all snapshot actions
by Tomas Jelinek 23 Jul '20

23 Jul '20

forwarding to the correct list On Wed, Jul 22, 2020 at 5:15 PM Henri Aanstoot <fash(a)fash.nu> wrote: > Hi all, > > I've got 2 two node setup, image based installs. > When doing ova exports or generic snapshots, things seem in order. > Removing snapshots shows warning 'disk in illegal state' > > Mouse hover shows .. please do not shutdown before succesfully remove > snapshot > > > ovirt-engine log > 2020-07-22 16:40:37,549+02 ERROR > [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] > (EE-ManagedExecutorService-commandCoordinator-Thread-2) > [264b0047-5aa6-4380-9d32-eb328fd6bed0] EVENT_ID: > VDS_BROKER_COMMAND_FAILURE(10,802), VDSM node2.lab command MergeVDS failed: > Merge failed > 2020-07-22 16:40:37,549+02 ERROR > [org.ovirt.engine.core.vdsbroker.vdsbroker.MergeVDSCommand] > (EE-ManagedExecutorService-commandCoordinator-Thread-2) > [264b0047-5aa6-4380-9d32-eb328fd6bed0] Command 'MergeVDSCommand(HostName = > node2.lab, > MergeVDSCommandParameters:{hostId='02df5213-1243-4671-a1c6-6489d7146319', > vmId='64c25543-bef7-4fdd-8204-6507046f5a34', > storagePoolId='5a4ea80c-b3b2-11ea-a890-00163e3cb866', > storageDomainId='9a12f1b2-5378-46cc-964d-3575695e823f', > imageGroupId='3f7ac8d8-f1ab-4c7a-91cc-f34d0b8a1cb8', > imageId='c757e740-9013-4ae0-901d-316932f4af0e', > baseImageId='ebe50730-dec3-4f29-8a38-9ae7c59f2aef', > topImageId='c757e740-9013-4ae0-901d-316932f4af0e', bandwidth='0'})' > execution failed: VDSGenericException: VDSErrorException: Failed to > MergeVDS, error = Merge failed, code = 52 > 2020-07-22 16:40:37,549+02 ERROR [org.ovirt.engine.core.bll.MergeCommand] > (EE-ManagedExecutorService-commandCoordinator-Thread-2) > [264b0047-5aa6-4380-9d32-eb328fd6bed0] Engine exception thrown while > sending merge command: org.ovirt.engine.core.common.errors.EngineException: > EngineException: > org.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException: > VDSGenericException: VDSErrorException: Failed to MergeVDS, error = Merge > failed, code = 52 (Failed with error mergeErr and code 52) > Caused by: org.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException: > VDSGenericException: VDSErrorException: Failed to MergeVDS, error = Merge > failed, code = 52 > <driver name='qemu' error_policy='report'/> > <driver name='qemu' type='qcow2' cache='none' error_policy='stop' > io='threads'/> > 2020-07-22 16:40:39,659+02 ERROR > [org.ovirt.engine.core.bll.MergeStatusCommand] > (EE-ManagedExecutorService-commandCoordinator-Thread-3) > [264b0047-5aa6-4380-9d32-eb328fd6bed0] Failed to live merge. Top volume > c757e740-9013-4ae0-901d-316932f4af0e is still in qemu chain > [ebe50730-dec3-4f29-8a38-9ae7c59f2aef, c757e740-9013-4ae0-901d-316932f4af0e] > 2020-07-22 16:40:41,524+02 ERROR > [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommand] > (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-58) > [264b0047-5aa6-4380-9d32-eb328fd6bed0] Command id: > 'e0b2bce7-afe0-4955-ae46-38bcb8719852 failed child command status for step > 'MERGE_STATUS' > 2020-07-22 16:40:42,597+02 ERROR > [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommand] > (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-53) > [264b0047-5aa6-4380-9d32-eb328fd6bed0] Merging of snapshot > 'ef8f7e06-e48c-4a8c-983c-64e3d4ebfcf9' images > 'ebe50730-dec3-4f29-8a38-9ae7c59f2aef'..'c757e740-9013-4ae0-901d-316932f4af0e' > failed. Images have been marked illegal and can no longer be previewed or > reverted to. Please retry Live Merge on the snapshot to complete the > operation. > 2020-07-22 16:40:42,603+02 ERROR > [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommand] > (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-53) > [264b0047-5aa6-4380-9d32-eb328fd6bed0] Ending command > 'org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommand' > with failure. > 2020-07-22 16:40:43,679+02 ERROR > [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotCommand] > (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-15) > [264b0047-5aa6-4380-9d32-eb328fd6bed0] Ending command > 'org.ovirt.engine.core.bll.snapshots.RemoveSnapshotCommand' with failure. > 2020-07-22 16:40:43,774+02 ERROR > [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] > (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-15) > [264b0047-5aa6-4380-9d32-eb328fd6bed0] EVENT_ID: > USER_REMOVE_SNAPSHOT_FINISHED_FAILURE(357), Failed to delete snapshot > 'Auto-generated for Export To OVA' for VM 'Adhoc'. > > > VDSM on hypervisor > 2020-07-22 14:14:30,220+0200 ERROR (jsonrpc/5) [virt.vm] > (vmId='14283e6d-c3f0-4011-b90f-a1272f0fbc10') Live merge failed (job: > e59c54d9-b8d3-44d0-9147-9dd40dff57b9) (vm:5381) > if ret == -1: raise libvirtError ('virDomainBlockCommit() failed', > dom=self) > libvirt.libvirtError: internal error: qemu block name 'json:{"backing": > {"driver": "qcow2", "file": {"driver": "file", "filename": > "/rhev/data-center/mnt/10.12.0.9:_exports_data/9a12f1b2-5378-46cc-964d-3575695e823f/images/3206de41-ccdc-4f2d-a968-5e4da6c2ca3e/bb3aed4b-fc41-456a-9c18-1409a9aa6d14"}}, > "driver": "qcow2", "file": {"driver": "file", "filename": > "/rhev/data-center/mnt/10.12.0.9:_exports_data/9a12f1b2-5378-46cc-964d-3575695e823f/images/3206de41-ccdc-4f2d-a968-5e4da6c2ca3e/3995b256-2afb-4853-9360-33d0c12e5fd1"}}' > doesn't match expected '/rhev/data-center/mnt/10.12.0.9: > _exports_data/9a12f1b2-5378-46cc-964d-3575695e823f/images/3206de41-ccdc-4f2d-a968-5e4da6c2ca3e/3995b256-2afb-4853-9360-33d0c12e5fd1' > 2020-07-22 14:14:30,234+0200 INFO (jsonrpc/5) [jsonrpc.JsonRpcServer] RPC > call VM.merge failed (error 52) in 0.17 seconds (__init__:312) > > 2020-07-22 14:17:28,798+0200 INFO (jsonrpc/2) [api] FINISH getStats > error=Virtual machine does not exist: {'vmId': > '698d486c-edbf-4e28-a199-31a2e27bd808'} (api:129) > 2020-07-22 14:17:28,798+0200 INFO (jsonrpc/2) [jsonrpc.JsonRpcServer] RPC > call VM.getStats failed (error 1) in 0.00 seconds (__init__:312) > > Also in log, > INFO (jsonrpc/1) [api.virt] FINISH getStats return={'status': {'code': 1, > 'message': "Virtual machine does not exist: > But is is there and accessible > > Any advice here? > Henri > > > ovirt 4.4.0.3-1.el8 > > OS Version: > RHEL - 8 - 1.1911.0.9.el8 > OS Description: > oVirt Node 4.4.0 > Kernel Version: > 4.18.0 - 147.8.1.el8_1.x86_64 > KVM Version: > 4.1.0 - 23.el8.1 > LIBVIRT Version: > libvirt-5.6.0-10.el8 > VDSM Version: > vdsm-4.40.16-1.el8 > SPICE Version: > 0.14.2 - 1.el8 > GlusterFS Version: > glusterfs-7.5-1.el8 > CEPH Version: > librbd1-12.2.7-9.el8 > Open vSwitch Version: > openvswitch-2.11.1-5.el8 > Nmstate Version: > nmstate-0.2.10-1.el8 > > _______________________________________________ > moVirt mailing list -- movirt(a)ovirt.org > To unsubscribe send an email to movirt-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/movirt@ovirt.org/message/3GXS3N77LEMQ… >

1 0

oVirt Network problem.
by Emil Dumitrache 22 Jul '20

22 Jul '20

Hello, I am new to oVirt. I have a problem and I don't know how to deal with it, i added another network besides the management network and after that the node did not respond to the oVIrt manager. I had to change the DNS to the new IP of the new network so that oVIrt manager can manage it. Now i have an error: Out-of-sync: Default route: host true, DC false. I checked on the node and the second network has DEFROUTE=NO and the management network to yes. I don't know why the manager is seeing that. Also the management IP does not respond to ping or anything. Please some advice for a newbie? The setup is: A standalone server with Centos7 and oVIrt manager installed and a node with ovirt node os. Thank you. [image: Tremend Logo] Emil Dumitrache IT Support Manager [image: Mobile] +40720450085 [image: Phone] +40-212-237-700 <0040212237700> [image: Email] emil.dumitrache(a)tremend.com [image: Website] www.tremend.com [image: Facebook] <https://www.facebook.com/TremendSoftware> [image: LinkedIN] [image: Skype] ------------------------------ Fastest growing Romanian company in Deloitte Fast 50 CE 2016

2 1

ovirt+SDN
by Marco Mangione 22 Jul '20

22 Jul '20

hello, anyone are using OVIRT with a SDN controller?

2 1

Re: Hosted Engine 4.4.1
by Vijay Sachdeva 22 Jul '20

22 Jul '20

Anyone please can help me out on this.? Vijay Sachdeva From: Vijay Sachdeva <vijay.sachdeva(a)indiqus.com> Date: Wednesday, 22 July 2020 at 8:24 PM To: Florian Schmid via Users <users(a)ovirt.org> Subject: Hosted Engine 4.4.1 Hello Everyone, Waiting for host to be up task is stuck for hours and when checked engine log found this below: 2020-07-22 16:50:35,717+02 ERROR [org.ovirt.engine.core.sso.utils.SsoUtils] (default task-1) [] OAuthException access_denied: Cannot authenticate user 'None@N/A': No valid profile found in credentials.. Has anyone faced such issue then please help me out..!! Thanks Vijay Sachdeva

1 0

Need help ovirt hosted engine storage in loked state
by Tarun Kushwaha 22 Jul '20

22 Jul '20

My ovirt hosted engine storage got in locked state. Now I am unable to perform any activity on this domain so guide me through how to unlock “hosted_storage” domain.

2 1

which cpu type should I chose ??
by tommy 22 Jul '20

22 Jul '20

Hi: 1.My server using as ovirt host is built on virtualbox and the cpu info is: vendor_id : GenuineIntel cpu family : 6 model : 142 model name : Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz stepping : 10 cpu MHz : 1992.002 cache size : 8192 KB physical id : 0 siblings : 3 core id : 2 cpu cores : 3 apicid : 2 initial apicid : 2 fpu : yes fpu_exception : yes cpuid level : 22 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx rdtscp lm constant_tsc rep_good nopl xtopology nonstop_tsc cpuid tsc_known_freq pni pclmulqdq vmx ssse3 cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt aes xsave avx rdrand hypervisor lahf_lm abm 3dnowprefetch invpcid_single pti tpr_shadow flexpriority fsgsbase avx2 invpcid rdseed clflushopt md_clear flush_l1d bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit srbds bogomips : 3984.00 clflush size : 64 cache_alignment : 64 address sizes : 39 bits physical, 48 bits virtual power management: 2.On the ovirt host page it appears that the host is unusable.The log info is: Host ohost3 moved to Non-Operational state as host does not meet the cluster's minimum CPU level. Missing CPU features : model_IvyBridge, ssbd, spec_ctrl 3.I think the problem is on cluster's cpu type setting, but which one should I chose to fit for the host?

3 2

invalid spf record for ovirt.org
by Jorick Astrego 22 Jul '20

22 Jul '20

Hi, During routine maintenance on our mailserver I noticed the following in the log: [22/Jul/2020 14:33:33] Error when parsing SPF TXT record for domain: ovirt.org, envelope-from=users-bounces(a)ovirt.org, message: Invalid character found near "" in "66.187.233.88" A check on MXtoolbox also gives an invalid systax error: v=spf1 a:mail.ovirt.org a:gerrit.ovirt.org 66.187.233.88 ~all Prefix Type Value PrefixDesc Description Error v spf1 The SPF record version + a mail.ovirt.org Pass Match if IP has a DNS 'A' record in given domain. + a gerrit.ovirt.org Pass Match if IP has a DNS 'A' record in given domain. + 66.187.233.88 Pass Unknown Unknown mechanisms are not allowed ~ all SoftFail Always matches. It goes at the end of your record. Test Result <https://mxtoolbox.com/problem/spf/spf-syntax-check?page=prob_spf&action=spf…> SPF Syntax Check Invalid syntax found Met vriendelijke groet, With kind regards, Jorick Astrego Netbulae Virtualization Experts ---------------- Tel: 053 20 30 270 info(a)netbulae.eu Staalsteden 4-3A KvK 08198180 Fax: 053 20 30 271 www.netbulae.eu 7547 TA Enschede BTW NL821234584B01 ----------------

3 2

4.4: Export as OVA always fails w/ ACTION_TYPE_FAILED_INVALID_OVA_DESTINATION_FOLDER
by Gilboa Davara 22 Jul '20

22 Jul '20

Hello all, I'm trying to export a VM as OVA on a single host hyper converged (over NFS) 4.4 installation, and no matter which host destination directory I set, with or without a trailing '/' (per bugzilla #1780424) the export fails with the same error (see below). Export into the export domain (on the same path) seems to work just fine. $ cat engine.log | grep WARN 2020-07-22 14:51:50,155+03 WARN [org.ovirt.engine.core.bll.exportimport.ExportVmToOvaCommand] (default task-158) [57c42e68-155e-4bd2-9dcd-bbc620088943] Validation of action 'ExportVmToOva' failed for user gilboa@internal-authz. Reasons: VAR__ACTION__EXPORT,VAR__TYPE__VM,ACTION_TYPE_FAILED_INVALID_OVA_DESTINATION_FOLDER,$vdsName gilboa-home-srv.localdomain,$directory /exports/export/kvm/gilboa-vmh-probe64 2020-07-22 14:52:22,077+03 WARN [org.ovirt.engine.core.bll.exportimport.ExportVmToOvaCommand] (default task-160) [092fb51d-1054-43ff-9161-69943c677512] Validation of action 'ExportVmToOva' failed for user gilboa@internal-authz. Reasons: VAR__ACTION__EXPORT,VAR__TYPE__VM,ACTION_TYPE_FAILED_INVALID_OVA_DESTINATION_FOLDER,$vdsName gilboa-home-srv.localdomain,$directory /tmp 2020-07-22 14:52:45,504+03 WARN [org.ovirt.engine.core.bll.exportimport.ExportVmToOvaCommand] (default task-160) [3c8ae09d-3d03-42dd-b2e8-b488052674f1] Validation of action 'ExportVmToOva' failed for user gilboa@internal-authz. Reasons: VAR__ACTION__EXPORT,VAR__TYPE__VM,ACTION_TYPE_FAILED_INVALID_OVA_DESTINATION_FOLDER,$vdsName gilboa-home-srv.localdomain,$directory /tmp 2020-07-22 15:04:32,393+03 WARN [org.ovirt.engine.core.bll.exportimport.ExportVmToOvaCommand] (default task-159) [7a234e5a-be10-4b0b-b817-eb682b846272] Validation of action 'ExportVmToOva' failed for user gilboa@internal-authz. Reasons: VAR__ACTION__EXPORT,VAR__TYPE__VM,ACTION_TYPE_FAILED_INVALID_OVA_DESTINATION_FOLDER,$vdsName gilboa-home-srv.localdomain,$directory /exports/export/kvm/temp 2020-07-22 15:10:07,066+03 WARN [org.ovirt.engine.core.bll.exportimport.ExportVmToOvaCommand] (default task-159) [75e66244-aa1c-4d40-8f9f-578cccb265a3] Validation of action 'ExportVmToOva' failed for user gilboa@internal-authz. Reasons: VAR__ACTION__EXPORT,VAR__TYPE__VM,ACTION_TYPE_FAILED_INVALID_OVA_DESTINATION_FOLDER,$vdsName gilboa-home-srv.localdomain,$directory /exports/export/kvm/temp/gilboa-vmh-probe64.ova 2020-07-22 15:10:46,480+03 WARN [org.ovirt.engine.core.bll.exportimport.ExportVmToOvaCommand] (default task-163) [6a6e9cae-b111-4f89-8dad-41a45a57c96c] Validation of action 'ExportVmToOva' failed for user gilboa@internal-authz. Reasons: VAR__ACTION__EXPORT,VAR__TYPE__VM,ACTION_TYPE_FAILED_INVALID_OVA_DESTINATION_FOLDER,$vdsName gilboa-home-srv.localdomain,$directory /exports/export/kvm/temp - Gilboa

1 0