- Users - oVirt List Archives

Cannot start VM: Bad volume specification
by Alan G 04 Mar '19

04 Mar '19

Hi, I performed the following: - 1. Shutdown VM. 2. Take a snapshot 3. Create a clone from snapshot. 4. Start the clone. Clone starts fine. 5. Attempt to delete snapshot from original VM, fails. 6. Attempt to start original VM, fails with "Bad volume specification". This was logged in VDSM during the snapshot deletion attempt. 2019-02-26 13:27:10,907+0000 ERROR (tasks/3) [storage.TaskManager.Task] (Task='67577e64-f29d-4c47-a38f-e54b905cae03') Unexpected error (task:872) Traceback (most recent call last): File "/usr/share/vdsm/storage/task.py", line 879, in _run return fn(*args, **kargs) File "/usr/share/vdsm/storage/task.py", line 333, in run return self.cmd(*self.argslist, **self.argsdict) File "/usr/lib/python2.7/site-packages/vdsm/storage/securable.py", line 79, in wrapper return method(self, *args, **kwargs) File "/usr/share/vdsm/storage/sp.py", line 1892, in finalizeMerge merge.finalize(subchainInfo) File "/usr/share/vdsm/storage/merge.py", line 271, in finalize optimal_size = subchain.base_vol.optimal_size() File "/usr/share/vdsm/storage/blockVolume.py", line 440, in optimal_size check = qemuimg.check(self.getVolumePath(), qemuimg.FORMAT.QCOW2) File "/usr/lib/python2.7/site-packages/vdsm/qemuimg.py", line 157, in check out = _run_cmd(cmd) File "/usr/lib/python2.7/site-packages/vdsm/qemuimg.py", line 426, in _run_cmd raise QImgError(cmd, rc, out, err) QImgError: cmd=['/usr/bin/qemu-img', 'check', '--output', 'json', '-f', 'qcow2', '/rhev/data-center/mnt/blockSD/024109d5-ea84-47ed-87e5-1c8681fdd177/images/f7dea7bd-04 6c-4923-b5a5-d0c1201607fc/ac540314-989d-42c2-9e7e-3907eedbe27f'], ecode=3, stdout={ "image-end-offset": 52210892800, "total-clusters": 1638400, "check-errors": 0, "leaks": 323, "leaks-fixed": 0, "allocated-clusters": 795890, "filename": "/rhev/data-center/mnt/blockSD/024109d5-ea84-47ed-87e5-1c8681fdd177/images/f7dea7bd-046c-4923-b5a5-d0c1201607fc/ac540314-989d-42c2-9e7e-3907eedbe27f", "format": "qcow2", "fragmented-clusters": 692941 } , stderr=Leaked cluster 81919 refcount=1 reference=0 Leaked cluster 81920 refcount=1 reference=0 Leaked cluster 81921 refcount=1 reference=0 etc.. Is there any way to fix these leaked clusters? Running oVirt 4.1.9 with FC block storage. Thanks, Alan

4 12

Re: low power, low cost glusterfs storage
by Strahil 04 Mar '19

04 Mar '19

The problem is that anything on the budged doesn't have decent network + enough storage slots. Maybe a homemade workstation with AMD ryzen could do the trick - but this is way over the budged compared to raspberry Pi-s Best Regards, Strahil NikolovOn Mar 3, 2019 12:22, Jonathan Baecker <jonbae77(a)gmail.com> wrote: > > Hello everybody! > > Does anyone here have experience with a cheap, energy-saving glusterfs > storage solution? I'm thinking of something that has more power than a > rasbian Pi, 3 x 2 TB (SSD) storage, but doesn't cost much more and > doesn't consume much more power. > > Would that be possible? I know the "Red Hat Gluster Storage" > requirements, but are they generally so high? Only a few VM images would > have to be on it... > > Greetings > > Jonathan > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/NWOA24SHB2CV6…

3 2

Re: Advice around ovirt 4.3 / gluster 5.x
by Strahil 03 Mar '19

03 Mar '19

I think that there are updates via 4.3.1 . Have you checked for gluster updates? Best Regards, Strahil NikolovOn Mar 2, 2019 23:16, Endre Karlson <endre.karlson(a)gmail.com> wrote: > > Hi, should we downgrade / reinstall our cluster? we have a 4 node cluster that's breakin apart daily due to the issues with GlusterFS after upgrading from 4.2.8 that was rock solid. I am wondering why 4.3 was released as a stable version at all?? **FRUSTRATION** > > Endre

1 0

Cannot assign Network to Mellanox Interface
by cbop.mail＠gmail.com 02 Mar '19

02 Mar '19

Hello, I want to use my Infiniband Network for Storage Access, so I created a new network and tried to assign it to a host. When I do this, I get a success message but it's actually not assigned to my Infiniband NIC. I'm running the latest CentOS with the latest Mellanox OFED drivers and multiple Subnet Managers are running on the network. The NIC is a Mellanox ConnectX-2 VPI, set to Infiniband mode. I didnt't knew which logs to send, so when you need to look into a log, just tell me which one you need. I hope you can help me out. Roman Meusch

4 8

Re: Mounting CephFS
by Strahil 02 Mar '19

02 Mar '19

Hi Leo, Check libvirt's logs on the destination host. Maybe they can provide more information. Best Regards, Strahil NikolovOn Mar 2, 2019 15:40, Leo David <leoalex(a)gmail.com> wrote: > > Thank you, > I am trying to migrate a vm that has its disks on cephfs ( as posix domain - mounted on all hosts ), and it does not work. Not sure if this is normal, considering the vm disks being on this type of storage. The error logs in engine are: > > 2019-03-02 13:35:03,483Z ERROR [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-0) [] Migration of VM 'centos7-test' to host 'node1.internal' failed: VM destroyed during the startup. > 2019-03-02 13:35:03,505Z ERROR [org.ovirt.engine.core.vdsbroker.monitoring.VmsMonitoring] (ForkJoinPool-1-worker-14) [] Rerun VM 'bec1cd40-9d62-4f6d-a9df-d97a79584441'. Called from VDS 'node2.internal' > 2019-03-02 13:35:03,566Z ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-42967) [] EVENT_ID: VM_MIGRATION_TO_SERVER_FAILED(120), Migration failed (VM: centos7-test, Source: node2.internal, Destination: node1.internal). > > Any thoughts ? > > Thanks, > > Leo > > > On Sat, Mar 2, 2019 at 11:59 AM Strahil <hunter86_bg(a)yahoo.com> wrote: >> >> If you mean storage migration - could be possible. >> If it is about live migration between hosts - shouldn't happen. >> Anything in the logs ? >> >> Best Regards, >> Strahil Nikolov >> >> On Mar 2, 2019 09:23, Leo David <leoalex(a)gmail.com> wrote: >>> >>> Thank you Strahil, yes thought about that too, I'll give it a try. >>> Now ( to be a bit offtopic ), it seems that I can't live migrate the vm, even thought the cephfs mountpoint exists on all the hosts. >>> Could it be the fact that the storage type is "posix" and live migration not being possible ? >>> >>> Thank you ! >>> >>> On Sat, Mar 2, 2019, 04:05 Strahil <hunter86_bg(a)yahoo.com> wrote: >>>> >>>> Can you try to set the credentials in a file (don't recall where that was for ceph) , so you can mount without specifying user/pass ? >>>> >>>> Best Regards, >>>> Strahil Nikolov >>>> >>>> On Mar 1, 2019 13:46, Leo David <leoalex(a)gmail.com> wrote: >>>>> >>>>> Hi Everyone, >>>>> I am trying to mount cephfs as a posix storage domain and getting an error in vdsm.log, although the direct command run on the node " mount -t ceph 10.10.6.1:/sata/ovirt-data /cephfs-sata/ -o name=admin,secret=AQAzncZY0VyYHBAAoeeePdv8Rr5kZlW07EVhZZ== " works fine. I have configured: >>>>> Storage type: POSIX compliant FS >>>>> Path: 10.10.6.1:/sata/ovirt-data >>>>> VFS Type: ceph >>>>> Mount Options: name=admin,secret=AQAzncZY0VyYHBAAoeeePdv8Rr5kZlW07EVhZZ== >>>>> >>>>> >>>>> 2019-03-01 11:35:33,457+0000 INFO (jsonrpc/4) [storage.Mount] mounting 10.10.6.1:/sata/ovirt-data at /rhev/data-center/mnt/10.10.6.1:_sata_ovirt-data (mount:204) >>>>> 2019-03-01 11:35:33,464+0000 INFO (jsonrpc/0) [jsonrpc.JsonRpcServer] RPC call Host.ping2 succeeded in 0.00 seconds (__init__:312) >>>>> 2019-03-01 11:35:33,471+0000 ERROR (jsonrpc/4) [storage.HSM] Could not connect to storageServer (hsm:2414)

1 0

oVirt 4.3 and dual socket hosts : numad?
by Guillaume Pavese 02 Mar '19

02 Mar '19

Is it recommended to enable numad service for automatic NUMA memory optimization? I could not find any recommendation on that front for oVirt ; all benchmarks and documentation I could find are from around ~2015 I see that kernel autonuma balancing is on : cat /proc/sys/kernel/numa_balancing 1 Not sure which is better as of now. Guillaume Pavese Ingénieur Système et Réseau Interactiv-Group

1 0

Re: Cannot Increase Hosted Engine VM Memory
by Douglas Duckworth 02 Mar '19

02 Mar '19

Ok sounds good. I will upgrade then hope this goes away. On Thu, Jan 31, 2019, 12:09 PM Simone Tiraboschi <stirabos(a)redhat.com<mailto:stirabos@redhat.com> wrote: On Thu, Jan 31, 2019 at 4:20 PM Douglas Duckworth <dod2014(a)med.cornell.edu<mailto:dod2014@med.cornell.edu>> wrote: Hi Simone Thanks again for your help! Do you have some ideas on what I can try to resolve this issue? Honestly I'm not able to reproduce this issue. I can only suggest to try upgrading to 4.2.8 if still not there, and if still not working open a bug on bugzilla attaching engine.log. Thanks, Douglas Duckworth, MSc, LFCS HPC System Administrator Scientific Computing Unit<https://scu.med.cornell.edu> Weill Cornell Medicine 1300 York Avenue New York, NY 10065 E: doug(a)med.cornell.edu<mailto:doug@med.cornell.edu> O: 212-746-6305 F: 212-746-8690 On Fri, Jan 25, 2019 at 3:15 PM Douglas Duckworth <dod2014(a)med.cornell.edu<mailto:dod2014@med.cornell.edu>> wrote: Yes, I do. Gold crown indeed. It's the "HostedEngine" as seen attached! Thanks, Douglas Duckworth, MSc, LFCS HPC System Administrator Scientific Computing Unit<https://scu.med.cornell.edu> Weill Cornell Medicine 1300 York Avenue New York, NY 10065 E: doug(a)med.cornell.edu<mailto:doug@med.cornell.edu> O: 212-746-6305 F: 212-746-8690 On Wed, Jan 23, 2019 at 12:02 PM Simone Tiraboschi <stirabos(a)redhat.com<mailto:stirabos@redhat.com>> wrote: On Wed, Jan 23, 2019 at 5:51 PM Douglas Duckworth <dod2014(a)med.cornell.edu<mailto:dod2014@med.cornell.edu>> wrote: Hi Simone Can I get help with this issue? Still cannot increase memory for Hosted Engine. From the logs it seams that the engine is trying to hotplug memory to the engine VM which is something it should not happen. The engine should simply update engine VM configuration in the OVF_STORE and require a reboot of the engine VM. Quick question, in the VM panel do you see a gold crown symbol on the Engine VM? Thanks, Douglas Duckworth, MSc, LFCS HPC System Administrator Scientific Computing Unit<https://scu.med.cornell.edu> Weill Cornell Medicine 1300 York Avenue New York, NY 10065 E: doug(a)med.cornell.edu<mailto:doug@med.cornell.edu> O: 212-746-6305 F: 212-746-8690 On Thu, Jan 17, 2019 at 8:08 AM Douglas Duckworth <dod2014(a)med.cornell.edu<mailto:dod2014@med.cornell.edu>> wrote: Sure, they're attached. In "first attempt" the error seems to be: 2019-01-17 07:49:24,795-05 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-29) [680f82b3-7612-4d91-afdc-43937aa298a2] EVENT_ID: FAILED_HOT_SET_MEMORY_NOT_DIVIDABLE(2,048), Failed to hot plug memory to VM HostedEngine. Amount of added memory (4000MiB) is not dividable by 256MiB. Followed by: 2019-01-17 07:49:24,814-05 WARN [org.ovirt.engine.core.bll.UpdateRngDeviceCommand] (default task-29) [26f5f3ed] Validation of action 'UpdateRngDevice' failed for user admin@internal-authz. Reasons: ACTION_TYPE_FAILED_VM_IS_RUNNING 2019-01-17 07:49:24,815-05 ERROR [org.ovirt.engine.core.bll.UpdateVmCommand] (default task-29) [26f5f3ed] Updating RNG device of VM HostedEngine (adf14389-1563-4b1a-9af6-4b40370a825b) failed. Old RNG device = VmRngDevice:{id='VmDeviceId:{deviceId='6435b2b5-163c-4f0c-934e-7994da60dc89', vmId='adf14389-1563-4b1a-9af6-4b40370a825b'}', device='virtio', type='RNG', specParams='[source=urandom]', address='', managed='true', plugged='true', readOnly='false', deviceAlias='', customProperties='null', snapshotId='null', logicalName='null', hostDevice='null'}. New RNG device = VmRngDevice:{id='VmDeviceId:{deviceId='6435b2b5-163c-4f0c-934e-7994da60dc89', vmId='adf14389-1563-4b1a-9af6-4b40370a825b'}', device='virtio', type='RNG', specParams='[source=urandom]', address='', managed='true', plugged='true', readOnly='false', deviceAlias='', customProperties='null', snapshotId='null', logicalName='null', hostDevice='null'}. In "second attempt" I used values that are dividable by 256 MiB so that's no longer present. Though same error: 2019-01-17 07:56:59,795-05 INFO [org.ovirt.engine.core.vdsbroker.SetAmountOfMemoryVDSCommand] (default task-22) [7059a48f] START, SetAmountOfMemoryVDSCommand(HostName = ovirt-hv1.med.cornell.edu<http://ovirt-hv1.med.cornell.edu>, Params:{hostId='cdd5ffda-95c7-4ffa-ae40-be66f1d15c30', vmId='adf14389-1563-4b1a-9af6-4b40370a825b', memoryDevice='VmDevice:{id='VmDeviceId:{deviceId='7f7d97cc-c273-4033-af53-bc9033ea3abe', vmId='adf14389-1563-4b1a-9af6-4b40370a825b'}', device='memory', type='MEMORY', specParams='[node=0, size=2048]', address='', managed='true', plugged='true', readOnly='false', deviceAlias='', customProperties='null', snapshotId='null', logicalName='null', hostDevice='null'}', minAllocatedMem='6144'}), log id: 50873daa 2019-01-17 07:56:59,855-05 INFO [org.ovirt.engine.core.vdsbroker.SetAmountOfMemoryVDSCommand] (default task-22) [7059a48f] FINISH, SetAmountOfMemoryVDSCommand, log id: 50873daa 2019-01-17 07:56:59,862-05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-22) [7059a48f] EVENT_ID: HOT_SET_MEMORY(2,039), Hotset memory: changed the amount of memory on VM HostedEngine from 4096 to 4096 2019-01-17 07:56:59,881-05 WARN [org.ovirt.engine.core.bll.UpdateRngDeviceCommand] (default task-22) [28fd4c82] Validation of action 'UpdateRngDevice' failed for user admin@internal-authz. Reasons: ACTION_TYPE_FAILED_VM_IS_RUNNING 2019-01-17 07:56:59,882-05 ERROR [org.ovirt.engine.core.bll.UpdateVmCommand] (default task-22) [28fd4c82] Updating RNG device of VM HostedEngine (adf14389-1563-4b1a-9af6-4b40370a825b) failed. Old RNG device = VmRngDevice:{id='VmDeviceId:{deviceId='6435b2b5-163c-4f0c-934e-7994da60dc89', vmId='adf14389-1563-4b1a-9af6-4b40370a825b'}', device='virtio', type='RNG', specParams='[source=urandom]', address='', managed='true', plugged='true', readOnly='false', deviceAlias='', customProperties='null', snapshotId='null', logicalName='null', hostDevice='null'}. New RNG device = VmRngDevice:{id='VmDeviceId:{deviceId='6435b2b5-163c-4f0c-934e-7994da60dc89', vmId='adf14389-1563-4b1a-9af6-4b40370a825b'}', device='virtio', type='RNG', specParams='[source=urandom]', address='', managed='true', plugged='true', readOnly='false', deviceAlias='', customProperties='null', snapshotId='null', logicalName='null', hostDevice='null'}. This message repeats throughout engine.log: 2019-01-17 07:55:43,270-05 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-89) [] EVENT_ID: VM_MEMORY_UNDER_GUARANTEED_VALUE(148), VM HostedEngine on host ovirt-hv1.med.cornell.edu<http://ovirt-hv1.med.cornell.edu> was guaranteed 8192 MB but currently has 4224 MB As you can see attached the host has plenty of memory. Thank you Simone! Thanks, Douglas Duckworth, MSc, LFCS HPC System Administrator Scientific Computing Unit<https://scu.med.cornell.edu> Weill Cornell Medicine 1300 York Avenue New York, NY 10065 E: doug(a)med.cornell.edu<mailto:doug@med.cornell.edu> O: 212-746-6305 F: 212-746-8690 On Thu, Jan 17, 2019 at 5:09 AM Simone Tiraboschi <stirabos(a)redhat.com<mailto:stirabos@redhat.com>> wrote: On Wed, Jan 16, 2019 at 8:22 PM Douglas Duckworth <dod2014(a)med.cornell.edu<mailto:dod2014@med.cornell.edu>> wrote: Sorry for accidental send. Anyway I try to increase physical memory however it won't go above 4096MB. The hypervisor has 64GB. Do I need to modify this value with Hosted Engine offline? No, it's not required. Can you please attach your engine.log for the relevant time frame? Thanks, Douglas Duckworth, MSc, LFCS HPC System Administrator Scientific Computing Unit<https://scu.med.cornell.edu> Weill Cornell Medicine 1300 York Avenue New York, NY 10065 E: doug(a)med.cornell.edu<mailto:doug@med.cornell.edu> O: 212-746-6305 F: 212-746-8690 On Wed, Jan 16, 2019 at 1:58 PM Douglas Duckworth <dod2014(a)med.cornell.edu<mailto:dod2014@med.cornell.edu>> wrote: Hello I am trying to increase Hosted Engine physical memory above 4GB Thanks, Douglas Duckworth, MSc, LFCS HPC System Administrator Scientific Computing Unit<https://scu.med.cornell.edu> Weill Cornell Medicine 1300 York Avenue New York, NY 10065 E: doug(a)med.cornell.edu<mailto:doug@med.cornell.edu> O: 212-746-6305 F: 212-746-8690 _______________________________________________ Users mailing list -- users(a)ovirt.org<mailto:users@ovirt.org> To unsubscribe send an email to users-leave(a)ovirt.org<mailto:users-leave@ovirt.org> Privacy Statement: https://www.ovirt.org/site/privacy-policy/<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ovirt.org_site_pri…> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ovirt.org_communit…> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/WGSXQVVPJJ2CR…<https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.ovirt.org_archiv…>

1 1

Re: Mounting CephFS
by Strahil 02 Mar '19

02 Mar '19

If you mean storage migration - could be possible. If it is about live migration between hosts - shouldn't happen. Anything in the logs ? Best Regards, Strahil NikolovOn Mar 2, 2019 09:23, Leo David <leoalex(a)gmail.com> wrote: > > Thank you Strahil, yes thought about that too, I'll give it a try. > Now ( to be a bit offtopic ), it seems that I can't live migrate the vm, even thought the cephfs mountpoint exists on all the hosts. > Could it be the fact that the storage type is "posix" and live migration not being possible ? > > Thank you ! > > On Sat, Mar 2, 2019, 04:05 Strahil <hunter86_bg(a)yahoo.com> wrote: >> >> Can you try to set the credentials in a file (don't recall where that was for ceph) , so you can mount without specifying user/pass ? >> >> Best Regards, >> Strahil Nikolov >> >> On Mar 1, 2019 13:46, Leo David <leoalex(a)gmail.com> wrote: >>> >>> Hi Everyone, >>> I am trying to mount cephfs as a posix storage domain and getting an error in vdsm.log, although the direct command run on the node " mount -t ceph 10.10.6.1:/sata/ovirt-data /cephfs-sata/ -o name=admin,secret=AQAzncZY0VyYHBAAoeeePdv8Rr5kZlW07EVhZZ== " works fine. I have configured: >>> Storage type: POSIX compliant FS >>> Path: 10.10.6.1:/sata/ovirt-data >>> VFS Type: ceph >>> Mount Options: name=admin,secret=AQAzncZY0VyYHBAAoeeePdv8Rr5kZlW07EVhZZ== >>> >>> >>> 2019-03-01 11:35:33,457+0000 INFO (jsonrpc/4) [storage.Mount] mounting 10.10.6.1:/sata/ovirt-data at /rhev/data-center/mnt/10.10.6.1:_sata_ovirt-data (mount:204) >>> 2019-03-01 11:35:33,464+0000 INFO (jsonrpc/0) [jsonrpc.JsonRpcServer] RPC call Host.ping2 succeeded in 0.00 seconds (__init__:312) >>> 2019-03-01 11:35:33,471+0000 ERROR (jsonrpc/4) [storage.HSM] Could not connect to storageServer (hsm:2414) >>> Traceback (most recent call last): >>> File "/usr/lib/python2.7/site-packages/vdsm/storage/hsm.py", line 2411, in connectStorageServer >>> conObj.connect() >>> File "/usr/lib/python2.7/site-packages/vdsm/storage/storageServer.py", line 180, in connect >>> six.reraise(t, v, tb) >>> File "/usr/lib/python2.7/site-packages/vdsm/storage/storageServer.py", line 172, in connect >>> self._mount.mount(self.options, self._vfsType, cgroup=self.CGROUP) >>> File "/usr/lib/python2.7/site-packages/vdsm/storage/mount.py", line 207, in mount >>> cgroup=cgroup) >>> File "/usr/lib/python2.7/site-packages/vdsm/common/supervdsm.py", line 56, in __call__ >>> return callMethod() >>> File "/usr/lib/python2.7/site-packages/vdsm/common/supervdsm.py", line 54, in <lambda> >>> **kwargs) >>> File "<string>", line 2, in mount >>> File "/usr/lib64/python2.7/multiprocessing/managers.py", line 773, in _callmethod >>> raise convert_to_error(kind, result) >>> MountError: (1, ';mount: unsupported option format: name=admin,secret=AQAzncZY0VyYHBAAoeeePdv8Rr5kZlW07EVhZZ==\n') >>> Any thoughts on this, what could it be wrong with the options field ? >>> Using oVirt 4.3.1 >>> Thank you very much and have a great day ! >>> >>> Leo >>> >>> -- >>> Best regards, Leo David

2 1

Re: Mounting CephFS
by Strahil 02 Mar '19

02 Mar '19

Can you try to set the credentials in a file (don't recall where that was for ceph) , so you can mount without specifying user/pass ? Best Regards, Strahil NikolovOn Mar 1, 2019 13:46, Leo David <leoalex(a)gmail.com> wrote: > > Hi Everyone, > I am trying to mount cephfs as a posix storage domain and getting an error in vdsm.log, although the direct command run on the node " mount -t ceph 10.10.6.1:/sata/ovirt-data /cephfs-sata/ -o name=admin,secret=AQAzncZY0VyYHBAAoeeePdv8Rr5kZlW07EVhZZ== " works fine. I have configured: > Storage type: POSIX compliant FS > Path: 10.10.6.1:/sata/ovirt-data > VFS Type: ceph > Mount Options: name=admin,secret=AQAzncZY0VyYHBAAoeeePdv8Rr5kZlW07EVhZZ== > > > 2019-03-01 11:35:33,457+0000 INFO (jsonrpc/4) [storage.Mount] mounting 10.10.6.1:/sata/ovirt-data at /rhev/data-center/mnt/10.10.6.1:_sata_ovirt-data (mount:204) > 2019-03-01 11:35:33,464+0000 INFO (jsonrpc/0) [jsonrpc.JsonRpcServer] RPC call Host.ping2 succeeded in 0.00 seconds (__init__:312) > 2019-03-01 11:35:33,471+0000 ERROR (jsonrpc/4) [storage.HSM] Could not connect to storageServer (hsm:2414) > Traceback (most recent call last): > File "/usr/lib/python2.7/site-packages/vdsm/storage/hsm.py", line 2411, in connectStorageServer > conObj.connect() > File "/usr/lib/python2.7/site-packages/vdsm/storage/storageServer.py", line 180, in connect > six.reraise(t, v, tb) > File "/usr/lib/python2.7/site-packages/vdsm/storage/storageServer.py", line 172, in connect > self._mount.mount(self.options, self._vfsType, cgroup=self.CGROUP) > File "/usr/lib/python2.7/site-packages/vdsm/storage/mount.py", line 207, in mount > cgroup=cgroup) > File "/usr/lib/python2.7/site-packages/vdsm/common/supervdsm.py", line 56, in __call__ > return callMethod() > File "/usr/lib/python2.7/site-packages/vdsm/common/supervdsm.py", line 54, in <lambda> > **kwargs) > File "<string>", line 2, in mount > File "/usr/lib64/python2.7/multiprocessing/managers.py", line 773, in _callmethod > raise convert_to_error(kind, result) > MountError: (1, ';mount: unsupported option format: name=admin,secret=AQAzncZY0VyYHBAAoeeePdv8Rr5kZlW07EVhZZ==\n') > Any thoughts on this, what could it be wrong with the options field ? > Using oVirt 4.3.1 > Thank you very much and have a great day ! > > Leo > > -- > Best regards, Leo David

2 1

impact of --emulate512 setting for VDO volumes
by Guillaume Pavese 02 Mar '19

02 Mar '19

Hello, We are planning to deploy VDO with oVirt 4.3 on centos 7.6 (on SSD devices). As oVirt does not support 4K devices yet, VDO volumes are created with the parameter "--emulate512 enabled" What are the implications of this setting? Does it impact performance? If so, is it IOPS or throughput that is impacted? What about reliability (is that mode equally tested as standard mode)? As I saw on RH Bugzilla, support for 4K devices in oVirt will need to wait at least for Centos 7.7 Once that is supported, would it be possible to transition/upgrade an emulate512 vdo volume to a standard one? Thanks, Guillaume Pavese Ingénieur Système et Réseau Interactiv-Group

2 2

Re: oVirt Performance (Horrific)
by Strahil 02 Mar '19

02 Mar '19

Another option is to try nfs-ganesha - in my case I can reach 80MB/s sequential writes in the VM. Best Regards, Strahil NikolovOn Mar 1, 2019 00:15, Jayme <jaymef(a)gmail.com> wrote: > > Also one more thing, did you make sure to setup the 10Gb gluster network in ovirt and set migration and vm traffic to use the gluster network? > > On Thu, Feb 28, 2019 at 6:11 PM Jayme <jaymef(a)gmail.com> wrote: >> >> Check volumes in Ovirt admin and make sure the optimize volume for cm storage is selected >> >> I have a three node ovirt hci with ssd gluster backed storage and 10Gb storage network and I write at around 50-60 megabytes per second from within vms. Before I used the optimize for vm storage it was about 10x less. Iirc the optimize setting it suppose to get set by the installler by default but it wasn’t set in my case when I used cockpit to deploy (this was a little while ago on ovirt 4.2). Worth checking anyway. >> >> On Thu, Feb 28, 2019 at 4:51 PM Drew R <drew.rash(a)gmail.com> wrote: >>> >>> I expect VM's to be able to write at 200MB or 500MB to the hdd/ssd when using an NFS mount or gluster from inside a VM. >>> >>> But heck, it's not even 10% (20MB or 50MB), it's closer to 2.5%-5% of the speed of the drives. >>> >>> I expect windows services to not timeout due to slow hard drives while booting. >>> I expect a windows vm to boot in less than 6 minutes. >>> I expect to open chrome in less than 1 minute. >>> >>> :) I was hoping for like, at least half speed or quarter speed. I'd be ok with 50MBps or 100MBps. Writing. >>> >>> I think what I was expecting was out of the box it would perform. But there appears to be something we've done wrong, or a tweak we aren't doing. >>> >>> But we can't even run 1 windows vm at something anyone would remotely call "performs very well". >>> >>> Please guide me. Do you have any commands you want me to run? Or tests to do? Do you want a print out or a specific configuration you would like to try? >>> _______________________________________________ >>> Users mailing list -- users(a)ovirt.org >>> To unsubscribe send an email to users-leave(a)ovirt.org >>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ >>> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ >>> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/VLWJHKXBR3A4R…

1 0

Re: oVirt Performance (Horrific)
by Strahil 01 Mar '19

01 Mar '19

Can you try setting the viodiskcache custom property to write back ? Best Regards, Strahil

3 2

Upgrade 4.2.8 to 4.3.1 failed: Constraint violation found in vm_interface (vmt_guid) |1
by John Florian 01 Mar '19

01 Mar '19

I tried to upgrade my engine and was running engine-setup when: [ INFO ] Checking the Engine database consistency [ ERROR ] Failed to execute stage 'Setup validation': Failed checking Engine database: an exception occurred while validating the Engine database, please check the logs for getting more info: Constraint violation found in vm_interface (vmt_guid) |1 I found https://bugzilla.redhat.com/show_bug.cgi?id=1528316 but that looks to have been resolved already. How should I proceed?

2 2

Mounting CephFS
by Leo David 01 Mar '19

01 Mar '19

Hi Everyone, I am trying to mount cephfs as a posix storage domain and getting an error in vdsm.log, although the direct command run on the node " mount -t ceph 10.10.6.1:/sata/ovirt-data /cephfs-sata/ -o name=admin,secret=AQAzncZY0VyYHBAAoeeePdv8Rr5kZlW07EVhZZ== " works fine. I have configured: Storage type: POSIX compliant FS Path: 10.10.6.1:/sata/ovirt-data VFS Type: ceph Mount Options: name=admin,secret=AQAzncZY0VyYHBAAoeeePdv8Rr5kZlW07EVhZZ== 2019-03-01 11:35:33,457+0000 INFO (jsonrpc/4) [storage.Mount] mounting 10.10.6.1:/sata/ovirt-data at /rhev/data-center/mnt/10.10.6.1:_sata_ovirt-data (mount:204) 2019-03-01 11:35:33,464+0000 INFO (jsonrpc/0) [jsonrpc.JsonRpcServer] RPC call Host.ping2 succeeded in 0.00 seconds (__init__:312) 2019-03-01 11:35:33,471+0000 ERROR (jsonrpc/4) [storage.HSM] Could not connect to storageServer (hsm:2414) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/storage/hsm.py", line 2411, in connectStorageServer conObj.connect() File "/usr/lib/python2.7/site-packages/vdsm/storage/storageServer.py", line 180, in connect six.reraise(t, v, tb) File "/usr/lib/python2.7/site-packages/vdsm/storage/storageServer.py", line 172, in connect self._mount.mount(self.options, self._vfsType, cgroup=self.CGROUP) File "/usr/lib/python2.7/site-packages/vdsm/storage/mount.py", line 207, in mount cgroup=cgroup) File "/usr/lib/python2.7/site-packages/vdsm/common/supervdsm.py", line 56, in __call__ return callMethod() File "/usr/lib/python2.7/site-packages/vdsm/common/supervdsm.py", line 54, in <lambda> **kwargs) File "<string>", line 2, in mount File "/usr/lib64/python2.7/multiprocessing/managers.py", line 773, in _callmethod raise convert_to_error(kind, result) *MountError: (1, ';mount: unsupported option format: * name=admin,secret=AQAzncZY0VyYHBAAoeeePdv8Rr5kZlW07EVhZZ==\n') Any thoughts on this, what could it be wrong with the options field ? Using oVirt 4.3.1 Thank you very much and have a great day ! Leo -- Best regards, Leo David

1 1

Gluster messages after upgrade to 4.3.1
by Stefano Danzi 01 Mar '19

01 Mar '19

Hello, I've just upgrade to version 4.3.1 and I can see this message in gluster log of all my host (running oVirt Node): The message "E [MSGID: 101191] [event-epoll.c:671:event_dispatch_epoll_worker] 0-epoll: Failed to dispatch handler" repeated 59 times between [2019-03-01 10:21:42.099983] and [2019-03-01 10:23:38.340971 Another strange thing: A Vm was running. I shutted down it fo mistake. I was no more able to run this vm. The error was: "Bad volume specification ". After a little investigation I notice that disk image was no more owned by vdsm.kvm but root.root. I changed back to correct value and vm started fine.

3 2

Ovirt 4.3 RC missing glusterfs-gnfs
by Strahil 01 Mar '19

01 Mar '19

7 15

Ovirt 4.3.1 Install failed
by kiv＠intercom.pro 01 Mar '19

01 Mar '19

Hi all. Testing fresh install 4.3.1 Install Node 4.3 - ok Install Engine from Cockpit - not working. Install Engine from CLI - not working, we get error: [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "The resolved address doesn't resolve on the selected interface\n"} [ ERROR ] Failed to execute stage 'Closing up': Failed executing ansible-playbook Vlans are not used.

2 1

[oVirt 4.3.1-RC2 Test Day] Hyperconverged HE Deployment
by Guillaume Pavese 01 Mar '19

01 Mar '19

Hi, I tried again today to deploy HE on Gluster with oVirt 4.3.1 RC2 on a clean Nested environment (no precedent deploy attempts to clean before...). Gluster was deployed without problem from cockpit. I then snapshoted my vms before trying to deploy HE both from cockpit, then from cmdline. Both attempts failed at the same spot : [ INFO ] Creating Storage Domain [ INFO ] TASK [ovirt.hosted_engine_setup : Execute just a specific set of steps] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Force facts gathering] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Check local VM dir stat] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Enforce local VM dir existence] [ INFO ] skipping: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : include_tasks] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Obtain SSO token using username/password credentials] [ ERROR ] ConnectionError: Error while sending HTTP request: (7, 'Failed connect to vs-inf-int-ovt-fr-301-210.hostics.fr:443; No route to host') [ ERROR ] fatal: [localhost]: FAILED! => {"attempts": 50, "changed": false, "msg": "Error while sending HTTP request: (7, 'Failed connect to vs-inf-int-ovt-fr-301-210.hostics.fr:443; No route to host')"} Please specify the storage you would like to use (glusterfs, iscsi, fc, nfs)[nfs]: [root@vs-inf-int-kvm-fr-301-210 ~]# traceroute vs-inf-int-ovt-fr-301-210.hostics.fr traceroute to vs-inf-int-ovt-fr-301-210.hostics.fr (192.168.122.147), 30 hops max, 60 byte packets 1 vs-inf-int-kvm-fr-301-210.hostics.fr (192.168.122.1) 3006.344 ms !H 3006.290 ms !H 3006.275 ms !H Guillaume Pavese Ingénieur Système et Réseau Interactiv-Group

3 4

error: "cannot set lock, no free lockspace" (localized)
by Mike Lykov 01 Mar '19

01 Mar '19

Hi all. I have a HCI setup, glusterfs 3.12, ovirt 4.2.7, 4 nodes Yesterday I see 3 VMs detected by engine as "not responding" (it is marked as HA VMs) (it all located on ovirtnode1 server) Two of them are restarted by engine on other nodes successfully, but one are not. All get LOCALIZED message like 'cannot set lock: no free space on device' - what is this ? Why engine get that errors, and why some VMs can restart automatically, some not (but successfully restarted bu user via webui after some pause?) Who knows, what are you think? Full engine logs may be uploaded. from engine.log: start event --------------- 2019-02-26 17:04:05,308+04 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (EE-ManagedThreadFactory-engineScheduled-Thread-59) [] VM 'd546add1-126a-4490-bc83-469bab659854'(openfire.miac) moved from 'Up' --> 'NotResponding' 2019-02-26 17:04:05,865+04 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-59) [] EVENT_ID: VM_NOT_RESPONDING(126), VM openfire.miac is not responding. 2019-02-26 17:04:05,865+04 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (EE-ManagedThreadFactory-engineScheduled-Thread-59) [] VM '7a3af2e7-8296-4fe0-ac55-c52a4b1de93f'(e-l-k.miac) moved from 'Up' --> 'NotResponding' 2019-02-26 17:04:05,894+04 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-59) [] EVENT_ID: VM_NOT_RESPONDING(126), VM e-l-k.miac is not responding. 2019-02-26 17:04:05,895+04 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (EE-ManagedThreadFactory-engineScheduled-Thread-59) [] VM 'de76aa6c-a211-41de-8d85-7d2821c3980d'(tsgr-mon) moved from 'Up' --> 'NotResponding' 2019-02-26 17:04:05,926+04 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-59) [] EVENT_ID: VM_NOT_RESPONDING(126), VM tsgr-mon is not responding. --------------------------- 2019-02-26 17:04:22,237+04 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (ForkJoinPool-1-worker-9) [] EVENT_ID: VM_DOWN_ERROR(119), VM openfire.miac is down with error. Exit message: VM has been terminated on the host. .... 2019-02-26 17:04:22,374+04 INFO [org.ovirt.engine.core.bll.VdsEventListener] (ForkJoinPool-1-worker-9) [] Highly Available VM went down. Attempting to restart. VM Name 'openfire.miac', VM Id 'd546add1-126a-4490-bc83-469bab659854' ... 2019-02-26 17:04:27,737+04 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-5) [] EVENT_ID: VM_DOWN_ERROR(119), VM openfire.miac is down with error. Exit message: resource busy: Failed to acquire lock: Lease is held by another host. ... 2019-02-26 17:04:28,350+04 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-2886073) [] EVENT_ID: VDS_INITIATED_RUN_VM(506), Trying to restart VM openfire.miac on Host ovirtnode6.miac 2019-02-26 17:04:31,841+04 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (ForkJoinPool-1-worker-2) [] EVENT_ID: VM_DOWN_ERROR(119), VM openfire.miac is down with error. Exit message: resource busy: Failed to acquire lock: Lease is held by another host. 2019-02-26 17:04:31,877+04 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-2886082) [] EVENT_ID: VDS_INITIATED_RUN_VM_FAILED(507), Failed to restart VM openfire.miac on Host ovirtnode6.miac ... 2019-02-26 17:04:31,994+04 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-2886082) [] EVENT_ID: VDS_INITIATED_RUN_VM(506), Trying to restart VM openfire.miac on Host ovirtnode1.miac ..... 2019-02-26 17:04:36,054+04 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (ForkJoinPool-1-worker-9) [] EVENT_ID: VM_DOWN_ERROR(119), VM openfire.miac is down with error. Exit message: Не удалось установить блокировку: На устройстве не осталось свободного места. 2019-02-26 17:04:36,054+04 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-9) [] add VM 'd546add1-126a-4490-bc83-469bab659854'(openfire.miac) to rerun treatment 2019-02-26 17:04:36,091+04 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-2886083) [] EVENT_ID: VDS_INITIATED_RUN_VM_FAILED(507), Failed to restart VM openfire.miac on Host ovirtnode1.miac ------------------- No more attemtps for this VM were made (state now is 'Down') Engine tried restart this VM on some other nodes, get ' Lease is held by another host' (it is normal, because timeout for lock not expired?) and then got (LOCALIZED MESSAGE ?? Why it is localized while all other are not?) 'cannot set lock: no free space on device' Which 'device' it mean? How to see how many 'free space' in it? gluster volumes almost empty: ovirtstor1.miac:/engine 150G 7,5G 143G 5% /rhev/data-center/mnt/glusterSD/ovirtstor1.miac:_engine ovirtnode1.miac:/data 5,9T 42G 5,9T 1% /rhev/data-center/mnt/glusterSD/ovirtnode1.miac:_data ovirtnode1.miac:/vmstore 4,4T 194G 4,2T 5% /rhev/data-center/mnt/glusterSD/ovirtnode1.miac:_vmstore ovirtnode1.miac:/iso_storage 600G 1,3G 599G 1% /rhev/data-center/mnt/glusterSD/ovirtnode1.miac:_iso__storage ovirtnode1.miac:/export 5,1T 14G 5,1T 1% /rhev/data-center/mnt/glusterSD/ovirtnode1.miac:_export Other VMs also get this error about free space: ------------- 2019-02-26 17:05:05,142+04 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (ForkJoinPool-1-worker-11) [] EVENT_ID: VM_DOWN_ERROR(119), VM tsgr-mon is down with error. Exit message: Не удалось установить блокир овку: На устройстве не осталось свободного места. 2019-02-26 17:05:43,526+04 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-11) [] VM 'de76aa6c-a211-41de-8d85-7d2821c3980d'(tsgr-mon) moved from 'PoweringUp' --> 'Up' 2019-02-26 17:05:43,537+04 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (ForkJoinPool-1-worker-11) [] EVENT_ID: VDS_INITIATED_RUN_VM(506), Trying to restart VM tsgr-mon on Host ovirtnode6.miac ---------------- And it is last message about this VM, state now is 'Up' Therefore all VMs are migrated from this node ovirtnode1, and later in log are records about it unresponsiveness: 2019-02-26 17:07:43,584+04 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (DefaultQuartzScheduler9) [35e05907] EVENT_ID: VDS_BROKER_COMMAND_FAILURE(10,802), VDSM ovirtnode1.miac command GetGlusterVolumeHealIn foVDS failed: Message timeout which can be caused by communication issues 2019-02-26 17:07:43,592+04 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-2886194) [35e05907] EVENT_ID: VDS_HOST_NOT_RESPONDING_CONNECTING(9,008), Host ovirtnode1.miac i s not responding. It will stay in Connecting state for a grace period of 60 seconds and after that an attempt to fence the host will be issued. 2019-02-26 17:07:49,684+04 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-99) [4511cab1] EVENT_ID: FENCE_OPERATION_USING_AGENT_AND_PROXY_STARTED(9,020), Executing power management status on Host ovirtnode1.miac using Proxy Host ovirtnode5.miac and Fence Agent ipmilan:172.16.16.1. 2019-02-26 17:07:49,685+04 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.FenceVdsVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-99) [4511cab1] START, FenceVdsVDSCommand(HostName = ovirtnode5.miac, ... action='STATUS', agent='FenceAgent:{id='338cbdd9-aab6-484c-a906-21e747a96a84', ... type='ipmilan', ip='172.16.16.1', port='null', user='admin', password='***', encryptOptions='false', options=''}', policy='null'}), log id: 281e6c2019-02-26 17:07:49,942+04 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.FenceVdsVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-99) [4511cab1] FINISH, FenceVdsVDSCommand, return: FenceOperationResult:{status='SUCCESS', powerStatus='ON', message=''}, log id: 281e6c 2019-02-26 17:07:56,131+04 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-99) [317316e4] EVENT_ID: SYNC_STORAGE_DEVICES_IN_HOST(4,126), Manually synced the storage devices from host ovirtnode1.miac 2019-02-26 17:07:56,550+04 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-99) [3a88be4f] EVENT_ID: VDS_DETECTED(13), Status of host ovirtnode1.miac was set to Up. 2019-02-26 17:07:56,554+04 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-99) [3a88be4f] EVENT_ID: VDS_FENCE_STATUS(496), Host ovirtnode1.miac power managementwas verified successfully. ------------- After all, now I try to start VM that not restarted automatically: ------------- 2019-02-27 11:23:30,139+04 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-2921212) [8e405cb9-3a3a-42ab-ae05-5aaf40194b30] EVENT_ID: USER_STARTED_VM(153), VM openfire.miac was started by admin@internal-authz (Host: ovirtnode1.miac). ..... 2019-02-27 11:24:12,489+04 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-1) [] VM 'd546add1-126a-4490-bc83-469bab659854'(openfire.miac) moved from 'PoweringUp' --> 'Up' 2019-02-27 11:24:12,502+04 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (ForkJoinPool-1-worker-1) [] EVENT_ID: USER_RUN_VM(32), VM openfire.miac started on Host ovirtnode1.miac --------------- It started without problems on same host ovirtnode1. Strange. -- Mike

2 3

VM poor iops
by Leo David 01 Mar '19

01 Mar '19

Hi Everyone, I am encountering the following issue on a single instance hyper-converged 4.2 setup. The following fio test was done: fio --randrepeat=1 --ioengine=libaio --direct=1 --gtod_reduce=1 --name=test --filename=test --bs=4k --iodepth=64 --size=4G --readwrite=randwrite The results are very poor doing the test inside of a vm with a prealocated disk on the ssd store: ~2k IOPS Same test done on the oVirt node directly on the mounted ssd_lvm: ~30k IOPS Same test done, this time on the gluster mount path: ~20K IOPS What could be the issue that the vms have this slow hdd performance ( 2k on ssd !! )? Thank you very much ! -- Best regards, Leo David

4 11

oVirt - Unable to delete VM snapshots
by dean＠datacom.ca 28 Feb '19

28 Feb '19

Unable to delete VM snapshots. Error messages and log info below. Running oVirt VM 4.2.8.2-1.el7, I haven't been able to find good documentation on how to fix. Can someone point me in the right direction? Thank you, ... Dean Feb 28, 2019, 3:32:34 PM Failed to delete snapshot 'Centos7_20190120' for VM 'n2_Centos7'. Feb 28, 2019, 3:32:28 PM VDSM n1 command HSMGetAllTasksStatusesVDS failed: Volume does not exist: (u'b2391a0b-c9e5-4dfe-9551-1e1f25c5c622',) Feb 28, 2019, 3:32:22 PM VDSM n2 command MergeVDS failed: Merge failed The VM has snapshot(s) with disk(s) in illegal status. Please don't shutdown the vm before successfully retrying the snapshot delete. engine.log 2019-02-28 15:32:33,420-05 ERROR [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-39) [f702317d-87cc-41dd-bcb2-12c6a2a93f10] Merging o f snapshot '3ddab9e6-a6ce-40d6-9ec6-815251471c5f' images 'fb974fb8-99d3-4a69-9f4e-096e30b85749'..'b2391a0b-c9e5-4dfe-9551-1e1f25c5c622' 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. 2019-02-28 15:32:33,429-05 ERROR [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-39) [f702317d-87cc-41dd-bcb2-12c6a2a93f10] Ending co mmand 'org.ovirt.engine.core.bll.snapshots.RemoveSnapshotSingleDiskLiveCommand' with failure. 2019-02-28 15:32:33,578-05 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-39) [f702317d-87cc-41dd-bcb2-12c6a2a93f10] Command 'Remov eSnapshot' id: '2243e15a-2569-498c-b0f8-de345321ba2f' child commands '[2e8dccfe-1c17-40ec-9f98-84f61863e450]' executions were completed, status 'FAILED' 2019-02-28 15:32:34,773-05 ERROR [org.ovirt.engine.core.bll.snapshots.RemoveSnapshotCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-10) [f702317d-87cc-41dd-bcb2-12c6a2a93f10] Ending command 'org.ovi rt.engine.core.bll.snapshots.RemoveSnapshotCommand' with failure. 2019-02-28 15:32:35,023-05 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-10) [f702317d-87cc-41dd-bcb2-12c6a2a93f10] EVENT_ID: USER_REMOVE_SNAPSHOT_FINISHED_FAILURE(357), Failed to delete snapshot 'Centos7_20190120' for VM 'n2_Centos7'. vdsm.log 2019-02-28 15:32:22,251-0500 INFO (jsonrpc/7) [jsonrpc.JsonRpcServer] RPC call Host.getStats succeeded in 0.02 seconds (__init__:573) 2019-02-28 15:32:22,326-0500 INFO (jsonrpc/0) [root] /usr/libexec/vdsm/hooks/after_get_caps/50_openstacknet: rc=0 err= (hooks:110) 2019-02-28 15:32:22,449-0500 INFO (jsonrpc/6) [api.host] START getAllVmStats() from=::ffff:192.168.1.10,48074 (api:46) 2019-02-28 15:32:22,452-0500 INFO (jsonrpc/6) [api.host] FINISH getAllVmStats return={'status': {'message': 'Done', 'code': 0}, 'statsList': (suppressed)} from=::ffff:192.168.1.10,48074 (api:52) 2019-02-28 15:32:22,453-0500 INFO (jsonrpc/6) [jsonrpc.JsonRpcServer] RPC call Host.getAllVmStats succeeded in 0.00 seconds (__init__:573) 2019-02-28 15:32:22,669-0500 INFO (jsonrpc/4) [api.virt] START merge(drive={u'imageID': u'96fbec76-c518-4010-8988-46b3c3172f09', u'volumeID': u'f7f1a3ec-d936-4482-8ec9-af2b3990b111', u'domainID': u'34af4473 -0779-42a0-8b97-e1ccc725fd60', u'poolID': u'5a3025a3-005f-03d4-0333-000000000382'}, baseVolUUID=u'fb974fb8-99d3-4a69-9f4e-096e30b85749', topVolUUID=u'b2391a0b-c9e5-4dfe-9551-1e1f25c5c622', bandwidth=u'0', jo bUUID=u'0b551b37-a6ee-4ac7-a004-2d410eaa8304') from=::ffff:192.168.1.10,48074, flow_id=f702317d-87cc-41dd-bcb2-12c6a2a93f10, vmId=a9082c6d-038e-4eb5-8436-69f93839a2ec (api:46) 2019-02-28 15:32:22,693-0500 INFO (jsonrpc/0) [root] /usr/libexec/vdsm/hooks/after_get_caps/openstacknet_utils.py: rc=0 err= (hooks:110) 2019-02-28 15:32:22,730-0500 ERROR (jsonrpc/4) [virt.vm] (vmId='a9082c6d-038e-4eb5-8436-69f93839a2ec') merge: Cannot find volume b2391a0b-c9e5-4dfe-9551-1e1f25c5c622 in drive vda's volume chain (vm:5944) 2019-02-28 15:32:22,731-0500 INFO (jsonrpc/4) [api.virt] FINISH merge return={'status': {'message': 'Merge failed', 'code': 52}} from=::ffff:192.168.1.10,48074, flow_id=f702317d-87cc-41dd-bcb2-12c6a2a93f10, vmId=a9082c6d-038e-4eb5-8436-69f93839a2ec (api:52)

2 1

[ANN] oVirt 4.3.1 is now generally available
by Sandro Bonazzola 28 Feb '19

28 Feb '19

The oVirt Project is pleased to announce the general availability of oVirt 4.3.1, as of February 26th, 2019. This update is the first in a series of stabilization updates to the 4.3 series. This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 7.6 or later * CentOS Linux (or similar) 7.6 or later This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 7.6 or later * CentOS Linux (or similar) 7.6 or later * oVirt Node 4.3 (available for x86_64 only) Experimental tech preview for x86_64 and s390x architectures for Fedora 28 is also included. See the release notes [1] for installation / upgrade instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is available for EL7 only - oVirt Node is available for EL7 only [2] - Fedora 28 based appliance and node couldn't be built due to a bug in Lorax (the tool used to build the images) affecting Fedora 28 and still pending a build from Fedora project. oVirt Node has been updated including: - oVirt 4.3.1: http://www.ovirt.org/release/4.3.1/ - ansible-2.7.8: https://github.com/ansible/ansible/blob/stable-2.7/changelogs/CHANGELOG-v2.… Relevant EPEL Errata included: - FEDORA-EPEL-2019-5f2f93029f security update in Fedora EPEL 7 for ansible ( https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-5f2f93029f ) Relevant CentOS Errata included: - CESA-2019:0231 Important CentOS 7 spice Security Update ( https://lists.centos.org/pipermail/centos-announce/2019-February/023192.html ) - CESA-2019:0368 Important CentOS 7 systemd Security Update ( https://lists.centos.org/pipermail/centos-announce/2019-February/023202.html ) Additional Resources: * Read more about the oVirt 4.3.1 release highlights: http://www.ovirt.org/release/4.3.1/ * Get more oVirt Project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] http://www.ovirt.org/release/4.3.1/ [2] http://resources.ovirt.org/pub/ovirt-4.3/iso/ -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig>

1 0

non-redhat version of ovirt-host-deploy
by ivan.kabaivanov＠gmail.com 28 Feb '19

28 Feb '19

Hi, I'm trying to get ovirt working on Linux From Scratch. So far so good, I can build and install it, and engine-setup also works fine. Now, I'm at the last stage, configuring it. And this is where I hit serious trouble: ovirt-host-deploy requires dnf/yum/rpm. But since I'm not running a redhat-based distro, I have none of those. Short of reading the source code, what are the steps I need to manually perform to get a working host? Thanks, IvanK.

2 3

reinstall centos node (ovirt 4.2.7) fails due missing dependency on librbd1
by Mike Lykov 28 Feb '19

28 Feb '19

Hi All! I'm using ovirt-release42-4.2.7.1-1.el7.noarch centos-release-7-5.1804.5.el7.centos.x86_64 And HCI glusterfs deployment (no ceph). And yesterday I wanted an add hosted engine deploy on some node. It requires to enable maintenance mode, reinstall node with "hosted engine = deploy" config (in webui). I made it, but reinstall fails. In logs I see (not full list): ... Feb 27 16:35:39 Updated: libvirt-daemon-4.5.0-10.el7_6.4.x86_64 Feb 27 16:35:39 Updated: libvirt-daemon-driver-storage-core-4.5.0-10.el7_6.4.x86_64 Feb 27 16:36:04 Updated: libvirt-daemon-driver-storage-rbd-4.5.0-10.el7_6.4.x86_64 Feb 27 16:36:04 Updated: libvirt-daemon-driver-storage-disk-4.5.0-10.el7_6.4.x86_64 Feb 27 16:36:04 Updated: libvirt-daemon-driver-storage-4.5.0-10.el7_6.4.x86_64 After it # rpm -q librbd1 librbd1-0.94.5-2.el7.x86_64 фев 27 16:36:51 ovirtnode5.miac systemd[1]: Starting Virtualization daemon... фев 27 16:36:51 ovirtnode5.miac libvirtd[537]: 2019-02-27 12:36:51.338+0000: 537: info : libvirt version: 4.5.0, package: 10.el7_6.4 (CentOS BuildSystem <http://bugs.centos.org>, 2019-01-29-17:31:22, x86-01.bsys.centos.org) фев 27 16:36:51 ovirtnode5.miac libvirtd[537]: 2019-02-27 12:36:51.338+0000: 537: info : hostname: ovirtnode5.miac фев 27 16:36:51 ovirtnode5.miac libvirtd[537]: 2019-02-27 12:36:51.338+0000: 537: error : virModuleLoadFile:53 : внутренняя ошибка: Failed to load module '/usr/lib64/libvirt/storage-backend/libvirt_storage_backend_rbd.so': /usr/lib64/libv irt/storage-backend/libvirt_storage_backend_rbd.so: undefined symbol: rbd_diff_iterate2 фев 27 16:36:51 ovirtnode5.miac systemd[1]: libvirtd.service: main process exited, code=exited, status=3/NOTIMPLEMENTED фев 27 16:36:51 ovirtnode5.miac systemd[1]: Failed to start Virtualization daemon. There is a old bugs like https://bugzilla.redhat.com/show_bug.cgi?id=1316911 or new posts like http://dreamcloud.artark.ca/libvirtd-failure-after-latest-upgrade-in-rhel-c… Obviously, the libvirt* rpms are updated, but librbd* not. But why? Why libvirt packages are not strictly dependenced on all required package/lib versions? libvirt-daemon-driver-storage-rbd must require exactly that librbd version that can work with, i think. -- Mike

1 0

Deploying Self-Hosted Engine Using Cockpit 4.3 not working
by kiv＠intercom.pro 27 Feb '19

27 Feb '19

Hi all. Fresh install host node 4.3. Install ok. Open web ui, and start deploying Self-Hosted Engine. When i add ISCSI storage - i get error: Retrieval of iSCSI targets failed. My iscsi target up and work.

2 1