- Users - oVirt List Archives

Supporting comments on ovirt-site Blog section
by Roy Golan 22 May '19

22 May '19

It would be very useful to have a comment section on our ovirt site. It is quite standard to have that on every blog out there, and for a reason - you get feedback and conversation around the topic, without going somewhere else (users list, irc, etc...) What do we need to do to help the middle man with that? Regards, Roy

4 3

Re: Scale out ovirt 4.3 (from 3 to 6 or 9 nodes) with hyperconverged setup and Gluster
by Strahil 22 May '19

22 May '19

I have edited my multipath.conf to exclude local disks , but you need to set '#VDSM private' as per the comments in the header of the file. Otherwise, use the /dev/mapper/multipath-device notation - as you would do with any linux. Best Regards, Strahil NikolovOn Apr 23, 2019 01:07, adrianquintero(a)gmail.com wrote: > > Thanks Alex, that makes more sense now while trying to follow the instructions provided I see that all my disks /dev/sdb, /dev/sdc, /dev/sdd are locked and inidicating " multpath_member" hence not letting me create new bricks. And on the logs I see > > Device /dev/sdb excluded by a filter.\n", "item": {"pvname": "/dev/sdb", "vgname": "gluster_vg_sdb"}, "msg": "Creating physical volume '/dev/sdb' failed", "rc": 5} > Same thing for sdc, sdd > > Should I manually edit the filters inside the OS, what will be the impact? > > thanks again. > _______________________________________________ > 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/FW3IR3NMQTYZL…

7 19

Gluster rebuild: request suggestions (poor IO performance)
by Jim Kusznir 22 May '19

22 May '19

Hi: I've been having one heck of a time for nearly the entire time I've been running ovirt with disk IO performance. I've tried a variety of things, I've posted to this list for help several times, and it sounds like in most cases the problems are due to design decisions and such. My cluster has been devolving into nearly unusable performance, and I believe its mostly disk IO related. I'm currently using FreeNAS as my primary VM storage (via NFS), but now it too is performing slowly (it started out reasonable, but slowly devolved for unknown reasons). I'm ready to switch back to gluster if I can get specific recommendations as to what I need to do to make it work. I feel like I've been trying random things, and sinking money into this to try and make it work, but nothing has really fixed the problem. I have 3 Dell R610 servers with 750GB SSDs as their primary drive. I had used some Seagate SSHDs, but the internal Dell DRAC raid controller (which had been configured to pass them through as a single disk volume, but still wasn't really JBOD), but it started silently failing them, and causing major issues for gluster. I think the DRAC just doesn't like those HDDs. I can put some real spinning disks in; perhaps a RAID-1 pair of 2TB? These servers only take 2.5" hdd's, so that greatly limits my options. I'm sure others out there are using Dell R610 servers...what do you use for storage? How does it perform? What do I need to do to get this cluster actually usable again? Are PERC-6i storage controllers usable? I'm not even sure where to go troubleshooting now...everything is so sloooowwwww. BTW: I had a small data volume on the SSDs, and the gluster performance on those was pretty poor. performance of the hosted engine is pretty poor still, and it is still on the SSDs.

1 0

Re: Scale out ovirt 4.3 (from 3 to 6 or 9 nodes) with hyperconverged setup and Gluster
by Strahil 21 May '19

21 May '19

> EUREKA: After doing the above I was able to get past the filter issues, however I am still concerned if during a reboot the disks might come up differently. For example /dev/sdb might come up as /dev/sdx... Even if they change , you don't have to worry about as each PV contains LVM metadata (including VG configuration) which is read by LVM on boot (actually everything that is not in the LVM filter is being scanned like that). Once all PVs are available the VG is activated and then the LVs are also activated. > I am trying to make sure this setup is always the same as we want to move this to production, however seems I still don't have the full hang of it and the RHV 4.1 course is way to old :) > > Thanks again for helping out with this. It's a plain KVM with some management layer. Just a hint: Get your HostedEngine's configuration xml from the vdsm log (for emergencies) and another copy with reverse boot order where DVD is booting first. Also get the xml for the ovirtmgmt network. It helped me a lot of times when I wanted to recover my HostedEngine. I'm too lazy to rebuild it. Hint2: Vdsm logs contain each VM's configuration xml when the VMs are powered on. Hint3: Get regular backups of the HostedEngine and patch it from time to time. I would go in prod as follows: Let's say you are on 4.2.8 Next step would be to go to 4.3.latest and then to 4.4.latest . A test cluster (even in VMs ) is also benefitial. Despite the hiccups I have stumbled upon, I think that the project is great. Best Regards, Strahil Nikolov

2 1

Migrating self-HostedEngine from NFS to iSCSI
by Miha Verlic 21 May '19

21 May '19

Hello, I have a few questions regarding migration of HostedEngine. Currently I have a cluster of 3 oVirt 4.3.3 nodes, all three of them are capable of running HE and I can freely migrate HostedEngine and regular VMs between them. However I deployed HostedEngine storage on rather edgy NFS server and I would like to migrate it to iSCSI based storage with multipathing. Quite a few VMs are already running on cluster and are using iSCSI data storage. Documentation is rather chaotic and fragmented, but from what I gathered the path of migration is someting like: - place one host (#1), the "failover" host, into maintenance mode prior to backup - export configuration with engine-backup - set global maintenance mode on all hosts - install ovirt engine on that host (#1) (already installed, since this is HE capable host) - restore engine configuration using engine-backup - run engine-setup with new parameters regarding storage - after engine-setup, log into admin portal and remove old host (#1) - redeploy hosts #2 and #3 Last two steps are a bit confusing as I'm not sure how removing old failover host on which new HE is running would work. Also not understanding the part where hosts 2 and 3 are described as unrecoverable (but with running VMs, which I'd have to live migrate to other hosts - how, if they're not operational?). Few other things: - Should I first remove & re-add host #1 without HE already deployed on host? - Should I set global maintenance mode on all hosts before migration? I'm guessing this is required if I want to prevent HE being started on random host during transition... - Which host should be selected as SPM during the transition phase? - How can I configure iSCSI multipathing? Self-hosted engine documentation mentions Multipath Helper tool, however I cannot find any info about it. Is this tool freely available or only a part od RHEL subscription? - Can I configure existing iSCSI Domain which already hosts some VMs as HE storage? Or do I have to assign extra LUN/target exclusively for HE? Cheers -- Miha

2 1

Re: Scale out ovirt 4.3 (from 3 to 6 or 9 nodes) with hyperconverged setup and Gluster
by Strahil 21 May '19

21 May '19

Thanks for the clarification. It seems that my nvme (used by vdo) is not locked. I will check again before opening a bug. Best Regards, Strahil NikolovOn May 21, 2019 09:52, Sahina Bose <sabose(a)redhat.com> wrote: > > > > On Tue, May 21, 2019 at 2:36 AM Strahil Nikolov <hunter86_bg(a)yahoo.com> wrote: >> >> Hey Sahina, >> >> it seems that almost all of my devices are locked - just like Fred's. >> What exactly does it mean - I don't have any issues with my bricks/storage domains. > > > > If the devices show up as locked - it means the disk cannot be used to create a brick. This is when the disk either already has a filesystem or is in use. > But if the device is a clean device and it still shows up as locked - this could be a bug with how python-blivet/ vdsm reads this > > The code to check is implemented as > _canCreateBrick(device): > if not device or device.kids > 0 or device.format.type or \ > hasattr(device.format, 'mountpoint') or \ > device.type in ['cdrom', 'lvmvg', 'lvmthinpool', 'lvmlv', 'lvmthinlv']: > return False > return True > >> >> Best Regards, >> Strahil Nikolov >> >> В понеделник, 20 май 2019 г., 14:56:11 ч. Гринуич+3, Sahina Bose <sabose(a)redhat.com> написа: >> >> >> To scale existing volumes - you need to add bricks and run rebalance on the gluster volume so that data is correctly redistributed as Alex mentioned. >> We do support expanding existing volumes as the bug https://bugzilla.redhat.com/show_bug.cgi?id=1471031 has been fixed >> >> As to procedure to expand volumes: >> 1. Create bricks from UI - select Host -> Storage Device -> Storage device. Click on "Create Brick" >> If the device is shown as locked, make sure there's no signature on device. If multipath entries have been created for local devices, you can blacklist those devices in multipath.conf and restart multipath. >> (If you see device as locked even after you do this -please report back). >> 2. Expand volume using Volume -> Bricks -> Add Bricks, and select the 3 bricks created in previous step >> 3. Run Rebalance on the volume. Volume -> Rebalance. >> >> >> On Thu, May 16, 2019 at 2:48 PM Fred Rolland <frolland(a)redhat.com> wrote: >>> >>> Sahina, >>> Can someone from your team review the steps done by Adrian? >>> Thanks, >>> Freddy >>>

1 0

VM Windows on 4.2
by gpesoli＠it.iliad.com 21 May '19

21 May '19

Hi all, I still cannot install or migrate windows virtual machines (64bit and UEFI BIOS) on my oVirt platform (4.2.8.2-1), is it possible? On migration from ESXi, after converted them, VM doesn't want to start in anyway. Further I noticed that on new installation I can't install 64bit version of Windows, because seems that 64bit disk driver are not recognised.

5 6

Wrong disk size in UI after expanding iscsi direct LUN
by Bernhard Dick 21 May '19

21 May '19

Hi, I've extended the size of one of my direct iSCSI LUNs. The VM is seeing the new size but in the webinterface there is still the old size reported. Is there a way to update this information? I already took a look into the list but there are only reports regarding updating the size the VM sees. Best regards Bernhard

3 4

hosts becomes NonResponsive
by Jiří Sléžka 21 May '19

21 May '19

Hi, time to time one of our four ovirt hosts become NonResponsive. From engine point of view it looks this way (engine.log) 2019-05-21 13:10:30,261+02 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-95) [] EVENT_ID: VDS_BROKER_COMMAND_FAILURE(10,802), VDSM ovirt03.net.slu.cz command Get Host Capabilities failed: Message timeout which can be caused by communication issues 2019-05-21 13:10:30,261+02 ERROR [org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring] (EE-ManagedThreadFactory-engineScheduled-Thread-95) [] Unable to RefreshCapabilities: VDSNetworkException: VDSGenericException: VDSNetworkException: Message timeout which can be caused by communication issues from host (which is reachable) it looks like (vdsm.log) 2019-05-21 13:10:27,154+0200 INFO (vmrecovery) [vdsm.api] START getConnectedStoragePoolsList(options=None) from=internal, task_id=a1bebf2f-7070-4344-90b7-1d709ba94b5c (api:48) 2019-05-21 13:10:27,154+0200 INFO (vmrecovery) [vdsm.api] FINISH getConnectedStoragePoolsList return={'poollist': []} from=internal, task_id=a1bebf2f-7070-4344-90b7-1d709ba94b5c (api:54) 2019-05-21 13:10:27,155+0200 INFO (vmrecovery) [vds] recovery: waiting for storage pool to go up (clientIF:709) 2019-05-21 13:10:31,245+0200 INFO (jsonrpc/4) [api.host] START getAllVmStats() from=::1,39144 (api:48) 2019-05-21 13:10:31,247+0200 INFO (jsonrpc/4) [api.host] FINISH getAllVmStats return={'status': {'message': 'Done', 'code': 0}, 'statsList': (suppressed)} from=::1,39144 (api:54) 2019-05-21 13:10:31,249+0200 INFO (jsonrpc/4) [jsonrpc.JsonRpcServer] RPC call Host.getAllVmStats succeeded in 0.00 seconds (__init__:312) hosts are latest CentOS7 (but old AMD Opteron HW), oVirt is 4.3.3.7-1.el7 I cannot track it down to network layer. We have 4 other RHV hosts on the same infrastructure and it works well. Some clues what is happening? Thanks in advance, Jiri Slezka

1 0

RHEL 8 Template Seal failed
by Vinícius Ferrão 21 May '19

21 May '19

Hello, I’m trying to seal a RHEL8 template but the operation is failing. Here’s the relevant information from engine.log: 2019-05-17 01:30:31,153-03 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.GetHostJobsVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-58) [91e1acd6-efc5-411b-8c76-970def4ebbbe] FINISH, GetHostJobsVDSCommand, return: {b80c0bbd-25b8-4007-9b91-376cb0a18e30=HostJobInfo:{id='b80c0bbd-25b8-4007-9b91-376cb0a18e30', type='virt', description='seal_vm', status='failed', progress='null', error='VDSError:{code='GeneralException', message='General Exception: ('Command [\'/usr/bin/virt-sysprep\', \'-a\', u\'/rhev/data-center/mnt/192.168.10.6:_mnt_pool0_ovirt_vm/d19456e4-0051-456e-b33c-57348a78c2e0/images/1ecdfbfc-1c22-452f-9a53-2159701549c8/f9de3eae-f475-451b-b587-f6a1405036e8\'] failed with rc=1 out=\'[ 0.0] Examining the guest ...\\nvirt-sysprep: warning: mount_options: mount exited with status 32: mount: \\nwrong fs type, bad option, bad superblock on /dev/mapper/rhel_rhel8-root,\\n missing codepage or helper program, or other error\\n\\n In some cases useful info is found in syslog - try\\n dmesg | tail or so. (ignored)\\nvirt-sysprep: warning: mount_options: mount: /boot: mount point is not a \\ndirectory (ignored)\\nvirt-sysprep: warning: mount_options: mount: /boot/efi: mount point is not \\na directory (ignored)\\n[ 17.9] Performing "abrt-data" ...\\n\' err="virt-sysprep: error: libguestfs error: glob_expand: glob_expand_stub: you \\nmust call \'mount\' first to mount the root filesystem\\n\\nIf reporting bugs, run virt-sysprep with debugging enabled and include the \\ncomplete output:\\n\\n virt-sysprep -v -x [...]\\n"',)'}'}}, log id: 1bbb34bf I’m not shure what’s wrong or missing. The VM image is using UEFI with Secure Boot, so standard UEFI partition is in place. Ive found something on bugzilla but does not seem to be related: https://bugzilla.redhat.com/show_bug.cgi?id=1671895 Thanks,

2 1