June 2019 - Users - oVirt List Archives

Re: New to oVirt - Cluster questions
by ccox＠endlessnow.com 15 Jun '19

15 Jun '19

It is my opinion that you never want fewer than 3. Somebody else may want to comment on what is actually possible.------ Original message------From: adam.fasnacht(a)gmail.comDate: Sat, Jun 15, 2019 1:41 PMTo: users(a)ovirt.org;Cc: Subject:[ovirt-users] New to oVirt - Cluster questionsHello, I just discovered oVirt, and before installing, I'm already a fan. I have a question regarding the number of nodes needed for a cluster. My main end goal, is to have HA, where I can have live migrations. I currently have 2 nodes (2 Dell R630s) that have a ton of local SSD storage on them. Is it possible to setup oVirt with just 2 nodes, and have an HA "hyper converged" style cluster? I can't seem to find a solid answer for this question. I've read the documentation, as well as consulted Google. I seem to get mixed answers. Is this possible? Thank you! _______________________________________________ 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/YRKWAAHN4EGPU…

1 0

New to oVirt - Cluster questions
by adam.fasnacht＠gmail.com 15 Jun '19

15 Jun '19

Hello, I just discovered oVirt, and before installing, I'm already a fan. I have a question regarding the number of nodes needed for a cluster. My main end goal, is to have HA, where I can have live migrations. I currently have 2 nodes (2 Dell R630s) that have a ton of local SSD storage on them. Is it possible to setup oVirt with just 2 nodes, and have an HA "hyper converged" style cluster? I can't seem to find a solid answer for this question. I've read the documentation, as well as consulted Google. I seem to get mixed answers. Is this possible? Thank you!

1 0

4.3 live migration creates wrong image permissions.
by Alex McWhirter 15 Jun '19

15 Jun '19

after upgrading from 4.2 to 4.3, after a vm live migrates it's disk images are become owned by root:root. Live migration succeeds and the vm stays up, but after shutting down the VM from this point, starting it up again will cause it to fail. At this point i have to go in and change the permissions back to vdsm:kvm on the images, and the VM will boot again.

6 13

Re: Replace bad Host from a 9 Node hyperconverged setup 4.3.3
by Strahil 14 Jun '19

14 Jun '19

Hi Adrian, Please keep in mind that when a server dies, the easiest way to recover is to get another freshly installed server with different IP/FQDN . Then you will need to use 'replace-brick' and once gluster replaces that node - you should be able to remove the old entry in oVirt. Once the old entry is gone, you can add the new installation in oVirt via the UI. Another approach is to have the same IP/FQDN for the fresh install.In this situation, you need to have the same gluster ID (which should be a text file) and the peer IDs. Most probably you can create them on your own , based on data on the other gluster peers. Once the fresh install is available in 'gluster peer' , you can initiate a reset-brick' (don't forget to set the SELINUX , firewall and repos) and a full heal. From there you can reinstall the machine from the UI and it should be available for usage. P.S.: I know that the whole procedure is not so easy :) Best Regards, Strahil NikolovOn Jun 12, 2019 19:02, Adrian Quintero <adrianquintero(a)gmail.com> wrote: > > Strahil, I dont use the GUI that much, in this case I need to understand how all is tied together if I want to move to production. As far as Gluster goes, I can get do the administration thru CLI, however when my test environment was set up it was setup using geodeploy for Hyperconverged setup under oVirt. > The initial setup was 3 servers with the same amount of physical disks: sdb, sdc, sdc, sdd, sde(this last one used for caching as it is an SSD) > > vmm10.mydomain.com:/gluster_bricks/brick1(/dev/sdb) engine > vmm10.mydomain.com:/gluster_bricks/brick2(/dev/sdb) vmstore1 > vmm10.mydomain.com:/gluster_bricks/brick3(/dev/sdc) data1 > vmm10.mydomain.com:/gluster_bricks/brick4(/dev/sdd) data2 > > vmm11.mydomain.com:/gluster_bricks/brick1(/dev/sdb) engine > vmm11.mydomain.com:/gluster_bricks/brick2(/dev/sdb) vmstore1 > vmm11.mydomain.com:/gluster_bricks/brick3(/dev/sdc) data1 > vmm11.mydomain.com:/gluster_bricks/brick4(/dev/sdd) data2 > > vmm12.mydomain.com:/gluster_bricks/brick1(/dev/sdb) engine > vmm12.mydomain.com:/gluster_bricks/brick2(/dev/sdb) vmstore1 > vmm12.mydomain.com:/gluster_bricks/brick3(/dev/sdc) data1 > vmm12.mydomain.com:/gluster_bricks/brick4(/dev/sdd) data2 > > As you can see from the above the the engine volume is conformed of hosts vmm10 (Initiating cluster server but now dead sever), vmm11 and vmm12 and on block device /dev/sdb (100Gb LV), also the vmstore1 volume is also on /dev/sdb (2600Gb LV). > /dev/mapper/gluster_vg_sdb-gluster_lv_engine xfs 100G 2.0G 98G 2% /gluster_bricks/engine > /dev/mapper/gluster_vg_sdb-gluster_lv_vmstore1 xfs 2.6T 35M 2.6T 1% /gluster_bricks/vmstore1 > /dev/mapper/gluster_vg_sdc-gluster_lv_data1 xfs 2.7T 4.6G 2.7T 1% /gluster_bricks/data1 > /dev/mapper/gluster_vg_sdd-gluster_lv_data2 xfs 2.7T 9.5G 2.7T 1% /gluster_bricks/data2 > vmm10.mydomain.com:/engine fuse.glusterfs 300G 9.2G 291G 4% /rhev/data-center/mnt/glusterSD/vmm10.virt.iad3p:_engine > vmm10.mydomain.com:/vmstore1 fuse.glusterfs 5.1T 53G 5.1T 2% /rhev/data-center/mnt/glusterSD/vmm10.virt.iad3p:_vmstore1 > vmm10.mydomain.com:/data1 fuse.glusterfs 8.0T 95G 7.9T 2% /rhev/data-center/mnt/glusterSD/vmm10.virt.iad3p:_data1 > vmm10.mydomain.com:/data2 fuse.glusterfs 8.0T 112G 7.8T 2% /rhev/data-center/mnt/glusterSD/vmm10.virt.iad3p:_data2 > > > > before any issues I increased the size of the cluster and the gluster cluster with the following, creating 4 distributed replicated volumes (engine, vmstore1, data1, data2) > > vmm13.mydomain.com:/gluster_bricks/brick1(/dev/sdb) engine > vmm13.mydomain.com:/gluster_bricks/brick2(/dev/sdb) vmstore1 > vmm13.mydomain.com:/gluster_bricks/brick3(/dev/sdc) data1 > vmm13.mydomain.com:/gluster_bricks/brick4(/dev/sdd) data2 > > vmm14.mydomain.com:/gluster_bricks/brick1(/dev/sdb) engine > vmm14.mydomain.com:/gluster_bricks/brick2(/dev/sdb) vmstore1 > vmm14.mydomain.com:/gluster_bricks/brick3(/dev/sdc) data1 > vmm14.mydomain.com:/gluster_bricks/brick4(/dev/sdd) data2 > > vmm15.mydomain.com:/gluster_bricks/brick1(/dev/sdb) engine > vmm15.mydomain.com:/gluster_bricks/brick2(/dev/sdb) vmstore1 > vmm15.mydomain.com:/gluster_bricks/brick3(/dev/sdc) data1 > vmm15.mydomain.com:/gluster_bricks/brick4(/dev/sdd) data2 > > vmm16.mydomain.com:/gluster_bricks/brick1(/dev/sdb) engine > vmm16.mydomain.com:/gluster_bricks/brick2(/dev/sdb) vmstore1 > vmm16.mydomain.com:/gluster_bricks/brick3(/dev/sdc) data1 > vmm16.mydomain.com:/gluster_bricks/brick4(/dev/sdd) data2 > > vmm17.mydomain.com:/gluster_bricks/brick1(/dev/sdb) engine > vmm17.mydomain.com:/gluster_bricks/brick2(/dev/sdb) vmstore1 > vmm17.mydomain.com:/gluster_bricks/brick3(/dev/sdc) data1 > vmm17.mydomain.com:/gluster_bricks/brick4(/dev/sdd) data2 > > vmm18.mydomain.com:/gluster_bricks/brick1(/dev/sdb) engine > vmm18.mydomain.com:/gluster_bricks/brick2(/dev/sdb) vmstore1 > vmm18.mydomain.com:/gluster_bricks/brick3(/dev/sdc) data1 > vmm18.mydomain.com:/gluster_bricks/brick4(/dev/sdd) data > > with your first suggestion I dont think it is possible to recover as I will lose the engine if I stop the "engine" volume, It might be doable for vmstore1, data1 and data2 but not the engine. > A) If you have space on another gluster volume (or volumes) or on NFS-based storage, you can migrate all VMs live . Once you do it, the simple way will be to stop and remove the storage domain (from UI) and gluster volume that correspond to the problematic brick. Once gone, you can remove the entry in oVirt for the old host and add the newly built one. Then you can recreate your volume and migrate the data back. > > I tried removing the brick using CLI but get the following error: > volume remove-brick start: failed: Host node of the brick vmm10.mydomain.com:/gluster_bricks/engine/engine is down > > So I used the force command: > gluster vol remove-brick engine vmm10.mydomain.com:/gluster_bricks/engine/engine vmm11.mydomain.com:/gluster_bricks/engine/engine vmm12.mydomain.com:/gluster_bricks/engine/engine force > Remove-brick force will not migrate files from the removed bricks, so they will no longer be available on the volume. > Do you want to continue? (y/n) y > volume remove-brick commit force: success > > so I lost my engine: > Please enter your authentication name: vdsm@ovirt > Please enter your password: > Id Name State > ---------------------------------------------------- > 3 HostedEngine paused > > hosted-engine --vm-start > The hosted engine configuration has not been retrieved from shared storage. Please ensure that ovirt-ha-agent is running and the storage server is reachable. > > I guess this fail scenario is more complex than I thought, hosted engine should of survived, as far as gluster I am able to get around command line, the issue is the engine, though it was running on vmm18 and not running on any bricks belonging to vmm10, 11, or 12 (original setup) it still failed... > virsh list --all > Please enter your authentication name: vdsm@ovirt > Please enter your password: > Id Name State > ---------------------------------------------------- > - HostedEngine shut off > > Now I cant get it to start: > hosted-engine --vm-start > The hosted engine configuration has not been retrieved from shared storage. Please ensure that ovirt-ha-agent is running and the storage server is reachable. > df -hT still showing mounts from old hosts bricks, could the problem be that this was the initiating host of the hyperconverged setup? > vmm10.mydomain.com:/engine fuse.glusterfs 200G 6.2G 194G 4% /rhev/data-center/mnt/glusterSD/vmm10.mydomain.com:_engine > > > I will re-create everything from scratch and simulate this again, and see why is it too complex to recover ovirt's engine with gluster when a server dies completely. Maybe it is my lack of understanding with regards how ovirt integrates with gluster though I have a decent understanding of Gluster to work with it... > > I will let you know once I have the cluster recreated and will kill the same server and see if I missed anything from the recommendations your provided. > > Thanks, > > -- > Adrian. > > > > > > > > On Tue, Jun 11, 2019 at 4:13 PM Strahil Nikolov <hunter86_bg(a)yahoo.com> wrote: >> >> Do you have empty space to store the VMs ? If yes, you can always script the migration of the disks via the API . Even a bash script and curl can do the trick. >> >> About the /dev/sdb , I still don't get it . A pure "df -hT" from a node will make it way clear. I guess '/dev/sdb' is a PV and you got 2 LVs ontop of it. >> >> Note: I should admit that as an admin - I don't use UI for gluster management. >> >> For now do not try to remove the brick. The approach is either to migrate the qemu disks to another storage or to reset-brick/replace-brick in order to restore the replica count. >> I will check the file and I will try to figure it out. >> >> Redeployment never fixes the issue, it just speeds up the recovery. If you can afford the time to spent on fixing the issue - then do not redeploy. >> >> I would be able to take a look next week , but keep in mind that I'm not so in deep with oVirt - I have started playing with it when I deployed my lab. >> >> Best Regards, >> Strahil Nikolov >> >> Strahil, >> >> Looking at your suggestions I think I need to provide a bit more info on my current setup. >> >> >> I have 9 hosts in total >> >> I have 5 storage domains: >> >> hosted_storage (Data Master) >> >> vmstore1 (Data) >> >> data1 (Data) >> >> data2 (Data) >> >> ISO (NFS) //had to create this one because oVirt 4.3.3.1 would not let me upload disk images to a data domain without an ISO (I think this is due to a bug) >> >> Each volume is of the type “Distributed Replicate” and each one is composed of 9 bricks. >> I started with 3 bricks per volume due to the initial Hyperconverged setup, then I expanded the cluster and the gluster cluster by 3 hosts at a time until I got to a total of 9 hosts. >> >> Disks, bricks and sizes used per volume >> / dev/sdb engine 100GB >> / dev/sdb vmstore1 2600GB >> / dev/sdc data1 2600GB >> / dev/sdd data2 2600GB >> / dev/sde -------- 400GB SSD Used for caching purposes >> >> From the above layout a few questions came up: >> >> Using the web UI, How can I create a 100GB brick and a 2600GB brick to replace the bad bricks for “engine” and “vmstore1” within the same block device (sdb) ? >> >> What about / dev/sde (caching disk), When I tried creating a new brick thru the UI I saw that I could use / dev/sde for caching but only for 1 brick (i.e. vmstore1) so if I try to create another brick how would I specify it is the same / dev/sde device to be used for caching? >> >> >> If I want to remove a brick and it being a replica 3, I go to storage > Volumes > select the volume > bricks once in there I can select the 3 servers that compose the replicated bricks and click remove, this gives a pop-up window with the following info: >> >> Are you sure you want to remove the following Brick(s)? >> - vmm11:/gluster_bricks/vmstore1/vmstore1 >> - vmm12.virt.iad3p:/gluster_bricks/vmstore1/vmstore1 >> - 192.168.0.100:/gluster-bricks/vmstore1/vmstore1 >> - Migrate Data from the bricks? >> >> If I proceed with this that means I will have to do this for all the 4 volumes, that is just not very efficient, but if that is the only way, then I am hesitant to put this into a real production environment as there is no way I can take that kind of a hit for +500 vms :) and also I wont have that much storage or extra volumes to play with in a real sceneario. >> >> After modifying yesterday / etc/vdsm/vdsm.id by following (https://stijn.tintel.eu/blog/2013/03/02/ovirt-problem-duplicate-uuids) I was able to add the server back to the cluster using a new fqdn and a new IP, and tested replacing one of the bricks and this is my mistake as mentioned in #3 above I used / dev/sdb entirely for 1 brick because thru the UI I could not separate the block device and be used for 2 bricks (one for the engine and one for vmstore1). So in the “gluster vol info” you might see vmm102.mydomain.com but in reality it is myhost1.mydomain.com >> >> I am also attaching gluster_peer_status.txt and in the last 2 entries of that file you will see and entry vmm10.mydomain.com (old/bad entry) and vmm102.mydomain.com (new entry, same server vmm10, but renamed to vmm102). Also please find gluster_vol_info.txt file. >> >> I am ready to redeploy this environment if needed, but I am also ready to test any other suggestion. If I can get a good understanding on how to recover from this I will be ready to move to production. >> >> Wondering if you’d be willing to have a look at my setup through a shared screen? >> >> >> Thanks >> >> >> Adrian >> >> >> On Mon, Jun 10, 2019 at 11:41 PM Strahil <hunter86_bg(a)yahoo.com> wrote: >>> >>> Hi Adrian, >>> >>> You have several options: >>> A) If you have space on another gluster volume (or volumes) or on NFS-based storage, you can migrate all VMs live . Once you do it, the simple way will be to stop and remove the storage domain (from UI) and gluster volume that correspond to the problematic brick. Once gone, you can remove the entry in oVirt for the old host and add the newly built one.Then you can recreate your volume and migrate the data back. >>> >>> B) If you don't have space you have to use a more riskier approach (usually it shouldn't be risky, but I had bad experience in gluster v3): >>> - New server has same IP and hostname: >>> Use command line and run the 'gluster volume reset-brick VOLNAME HOSTNAME:BRICKPATH HOSTNAME:BRICKPATH commit' >>> Replace VOLNAME with your volume name. >>> A more practical example would be: >>> 'gluster volume reset-brick data ovirt3:/gluster_bricks/data/brick ovirt3:/gluster_ ricks/data/brick commit' >>> >>> If it refuses, then you have to cleanup '/gluster_bricks/data' (which should be empty). >>> Also check if the new peer has been probed via 'gluster peer status'.Check the firewall is allowing gluster communication (you can compare it to the firewalls on another gluster host). >>> >>> The automatic healing will kick in 10 minutes (if it succeeds) and will stress the other 2 replicas, so pick your time properly. >>> Note: I'm not recommending you to use the 'force' option in the previous command ... for now :) >>> >>> - The new server has a different IP/hostname: >>> Instead of 'reset-brick' you can use 'replace-brick': >>> It should be like this: >>> gluster volume replace-brick data old-server:/path/to/brick new-server:/new/path/to/brick commit force >>> >>> In both cases check the status via: >>> gluster volume info VOLNAME >>> >>> If your cluster is in production , I really recommend you the first option as it is less risky and the chance for unplanned downtime will be minimal. >>> >>> The 'reset-brick' in your previous e-mail shows that one of the servers is not connected. Check peer status on all servers, if they are less than they should check for network and/or firewall issues. >>> On the new node check if glusterd is enabled and running. >>> >>> In order to debug - you should provide more info like 'gluster volume info' and the peer status from each node. >>> >>> Best Regards, >>> Strahil Nikolov >>> >>> On Jun 10, 2019 20:10, Adrian Quintero <adrianquintero(a)gmail.com> wrote: >>>> >>>> > >>>> > Can you let me know how to fix the gluster and missing brick?, >>>> > I tried removing it by going to "storage > Volumes > vmstore > bricks > selected the brick >>>> > However it is showing as an unknown status (which is expected because the server was completely wiped) so if I try to "remove", "replace brick" or "reset brick" it wont work >>>> > If i do remove brick: Incorrect bricks selected for removal in Distributed Replicate volume. Either all the selected bricks should be from the same sub volume or one brick each for every sub volume! >>>> > If I try "replace brick" I cant because I dont have another server with extra bricks/disks >>>> > And if I try "reset brick": Error while executing action Start Gluster Volume Reset Brick: Volume reset brick commit force failed: rc=-1 out=() err=['Host myhost1_mydomain_com not connected'] >>>> > >>>> > Are you suggesting to try and fix the gluster using command line? >>>> > >>>> > Note that I cant "peer detach" the sever , so if I force the removal of the bricks would I need to force downgrade to replica 2 instead of 3? what would happen to oVirt as it only supports replica 3? >>>> > >>>> > thanks again. >>>> > >>>> > On Mon, Jun 10, 2019 at 12:52 PM Strahil <hunter86_bg(a)yahoo.com> wrote: >>>>> >>>>> >> >>>>> >> Hi Adrian, >>>>> >> Did you fix the issue with the gluster and the missing brick? >>>>> >> If yes, try to set the 'old' host in maintenance an >> >> >> >> -- >> Adrian Quintero > > > > -- > Adrian Quintero

3 3

Re: Memory ballon question
by Strahil 14 Jun '19

14 Jun '19

Hi Martin, Thanks for clarifying that. Best Regards, Strahil NikolovOn Jun 14, 2019 13:02, Martin Sivak <msivak(a)redhat.com> wrote: > > Hi, > > > 2019-06-13 07:11:40,973 - mom.Controllers.Balloon - INFO - Ballooning guest:node1 from 695648 to 660865 > > 2019-06-13 07:12:51,437 - mom.GuestMonitor.Thread - INFO - GuestMonitor-node1 ending > > > > Can someone clarify what exactly does this (from xxxx to yyyy) mean ? > > It is the ballooning operation log: > > - From - how much memory was left in the VM before the action > - To - how much after (could be both lower and higher) > > I do not remember the units, but I think it was in KiB. > > Martin > > > On Thu, Jun 13, 2019 at 9:26 PM Strahil Nikolov <hunter86_bg(a)yahoo.com> wrote: > > > > Hi Martin,Darrell, > > > > thanks for your feedback. > > > > I have checked the /var/log/vdsm/mom.log and it seems that MOM was actually working: > > > > 2019-06-13 07:08:47,690 - mom.GuestMonitor.Thread - INFO - GuestMonitor-node1 starting > > 2019-06-13 07:09:39,490 - mom.Controllers.Balloon - INFO - Ballooning guest:node1 from 1048576 to 996147 > > 2019-06-13 07:09:54,658 - mom.Controllers.Balloon - INFO - Ballooning guest:node1 from 996148 to 946340 > > 2019-06-13 07:10:09,853 - mom.Controllers.Balloon - INFO - Ballooning guest:node1 from 946340 to 899023 > > 2019-06-13 07:10:25,053 - mom.Controllers.Balloon - INFO - Ballooning guest:node1 from 899024 to 854072 > > 2019-06-13 07:10:40,233 - mom.Controllers.Balloon - INFO - Ballooning guest:node1 from 854072 to 811368 > > 2019-06-13 07:10:55,428 - mom.Controllers.Balloon - INFO - Ballooning guest:node1 from 811368 to 770799 > > 2019-06-13 07:11:10,621 - mom.Controllers.Balloon - INFO - Ballooning guest:node1 from 770800 to 732260 > > 2019-06-13 07:11:25,827 - mom.Controllers.Balloon - INFO - Ballooning guest:node1 from 732260 to 695647 > > 2019-06-13 07:11:40,973 - mom.Controllers.Balloon - INFO - Ballooning guest:node1 from 695648 to 660865 > > 2019-06-13 07:12:51,437 - mom.GuestMonitor.Thread - INFO - GuestMonitor-node1 ending > > > > Can someone clarify what exactly does this (from xxxx to yyyy) mean ? > > > > Best Regards, > > Strahil Nikolov > > > > В четвъртък, 13 юни 2019 г., 17:27:01 ч. Гринуич+3, Martin Sivak <msivak(a)redhat.com> написа: > > > > > > Hi, > > > > iirc the guest agent is not needed anymore as we get almost the same > > stats from the balloon driver directly. > > > > Ballooning has to be enabled on cluster level though. So that is one > > thing to check. If that is fine then I guess a more detailed > > description is needed. > > > > oVirt generally starts ballooning when the memory load gets over 80% > > of available memory. > > > > The host agent that handles ballooning is called mom and the logs are > > located in /var/log/vdsm/mom* iirc. It might be a good idea to check > > whether the virtual machines were declared ready (meaning all data > > sources we collect provided data). > > > > -- > > Martin Sivak > > used to be maintainer of mom > > > > On Thu, Jun 13, 2019 at 12:26 AM Darrell Budic <budic(a)onholyground.com> wrote: > > > > > > Do you have the overt-guest-agent running on your VMs? It’s required for ballooning to control allocations on the guest side. > > > > > > On Jun 12, 2019, at 11:32 AM, Strahil <hunter86_bg(a)yahoo.com> wrote: > > > > > > Hello All, > > > > > > as a KVM user I know how usefull is the memory balloon and how you can both increase - and also decrease memory live (both Linux & Windows). > > > I have noticed that I cannot decrease the memory in oVirt. > > > > > > Does anyone got a clue why the situation is like that ? > > > > > > I was expecting that the guaranteed memory is the minimum to which the balloon driver will not go bellow, but when I put my host under pressure - the host just started to swap instead of reducing some of the VM memory (and my VMs had plenty of free space). > > > > > > It will be great if oVirt can decrease the memory (if the VM has unallocated memory) when the host is under pressure and the VM cannot be relocated. > > > > > > Best Regards, > > > Strahil Nikolov > > > > > > _______________________________________________ > > > 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/LUWCN2MLNTDJU… > > > > > > > > > _______________________________________________ > > > 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/22XYJD7XAYZLV… > > > > _______________________________________________ > > Users mailing list -- users(a)ovirt.org > > To unsubscribe send an email to users-l

1 0

Memory ballon question
by Strahil 14 Jun '19

14 Jun '19

Hello All, as a KVM user I know how usefull is the memory balloon and how you can both increase - and also decrease memory live (both Linux & Windows). I have noticed that I cannot decrease the memory in oVirt. Does anyone got a clue why the situation is like that ? I was expecting that the guaranteed memory is the minimum to which the balloon driver will not go bellow, but when I put my host under pressure - the host just started to swap instead of reducing some of the VM memory (and my VMs had plenty of free space). It will be great if oVirt can decrease the memory (if the VM has unallocated memory) when the host is under pressure and the VM cannot be relocated. Best Regards, Strahil Nikolov

4 4

Re: High Performance VM: trouble using vNUMA and hugepages
by Andrej Krejcir 14 Jun '19

14 Jun '19

Hi, this is probably a bug. Can you open a new ticket in Bugzilla? https://bugzilla.redhat.com/enter_bug.cgi?product=ovirt-engine As a workaround, if you are sure that the VM's NUMA configuration is compatible with the host's NUMA configuration, you could create a custom cluster scheduling policy and disable the "NUMA" filter. In Administration -> Configure -> Scheduling Policies. Regards, Andrej On Thu, 13 Jun 2019 at 12:49, Matthias Leopold < matthias.leopold(a)meduniwien.ac.at> wrote: > Hi, > > I'm having trouble using vNUMA and hugepages at the same time: > > - hypervisor host hast 2 CPU and 768G RAM > - hypervisor host is configured to allocate 512 1G hugepages > - VM configuration > * 2 virtual sockets, vCPUs are evenly pinned to 2 physical CPUs > * 512G RAM > * 2 vNUMA nodes that are pinned to the 2 host NUMA nodes > * custom property "hugepages=1048576" > - VM is the only VM on hypervisor host > > when I want to start the VM I'm getting the error message > "The host foo did not satisfy internal filter NUMA because cannot > accommodate memory of VM's pinned virtual NUMA nodes within host's > physical NUMA nodes" > VM start only works when VM memory is shrunk so that it fits in (host > memory - allocated huge pages) > > I don't understand why this happens. Can someone explain to me how this > is supposed to work? > > oVirt engine is 4.3.3 > oVirt host is 4.3.4 > > thanks > matthias

2 2

Ovirt engine setup Err'or
by PS Kazi 14 Jun '19

14 Jun '19

I am getting following error while ovirt engine setup. I am using ovirt node 4.3.4 please help ___________________________________ [ ERROR ] fatal: [localhost]: FAILED! => {"attempts": 90, "changed": true, "cmd": "virsh -r net-dhcp-leases default | grep -i 00:16:3e:5f:0e:ea | awk '{ print $5 }' | cut -f1 -d'/'", "delta": "0:00:00.086952", "end": "2019-06-14 12:05:37.249240", "rc": 0, "start": "2019-06-14 12:05:37.162288", "stderr": "", "stderr_lines": [], "stdout": "", "stdout_lines": []} [ INFO ] TASK [ovirt.hosted_engine_setup : include_tasks] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Remove local vm dir] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Remove temporary entry in /etc/hosts for the local VM] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Notify the user about a failure] [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "The system may not be provisioned according to the playbook results: please check the logs for the issue, fix accordingly or re-deploy from scratch.\n"}

1 0

Ovirt hiperconverged setup error
by PS Kazi 14 Jun '19

14 Jun '19

ovirt Node version 4.3.3.1 I am trying to configure 3 node Gluster storage and oVirt hosted engine but gettng following error: TASK [gluster.features/roles/gluster_hci : Check if valid FQDN is provided] **** failed: [ov-node-2 -> localhost] (item=ov-node-2) => {"changed": true, "cmd": ["dig", "ov-node-2", "+short"], "delta": "0:00:00.041003", "end": "2019-06-12 12:52:34.158688", "failed_when_result": true, "item": "ov-node-2", "rc": 0, "start": "2019-06-12 12:52:34.117685", "stderr": "", "stderr_lines": [], "stdout": "", "stdout_lines": []} failed: [ov-node-2 -> localhost] (item=ov-node-3) => {"changed": true, "cmd": ["dig", "ov-node-3", "+short"], "delta": "0:00:00.038688", "end": "2019-06-12 12:52:34.459176", "failed_when_result": true, "item": "ov-node-3", "rc": 0, "start": "2019-06-12 12:52:34.420488", "stderr": "", "stderr_lines": [], "stdout": "", "stdout_lines": []} failed: [ov-node-2 -> localhost] (item=ov-node-1) => {"changed": true, "cmd": ["dig", "ov-node-1", "+short"], "delta": "0:00:00.047938", "end": "2019-06-12 12:52:34.768149", "failed_when_result": true, "item": "ov-node-1", "rc": 0, "start": "2019-06-12 12:52:34.720211", "stderr": "", "stderr_lines": [], "stdout": "", "stdout_lines": []} Please help

4 5

Re: The CPU type of the cluster is unknown. Its possible to change the cluster cpu or set a different one per VM.
by Strahil 14 Jun '19

14 Jun '19

In the docs, the proper order to update is: 1. update ovirt-setup packages on the engine yum update ovirt\*setup\* 2. update the engine engine-setup 3. update the OS on the engine yum update 4. reboot the engine if kernel/glibc/systemd got updated 5 upgrade hosts 1 by 1 Best Regards, Strahil NikolovOn Jun 13, 2019 16:27, sandeepkumar86k(a)gmail.com wrote: > > Thank you. > > I upgraded all three hosts one by one to oVirt-4.3 and then HE. After the upgrade, I was able to change the CPU Type. > _______________________________________________ > 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/NGUEEF4DVLBXL…

1 0

Re: Hosted Engine Abruptly Stopped Responding - Unexpected Shutdown
by Strahil 14 Jun '19

14 Jun '19

Hi Maria, I guess the memory usage is very specidic to the environment. My setup includes 2 VDOs, 8 gluster volumes , 2 clusters, 12 VMs and only 1 user - the built-in admin . In result my engine is using 4GB of RAM. How many users/storages/clusters/VMs do you have ? When you login on the engine, what is the process eating most of the RAM? My suspicion is the DB. If so, maybe someone else can advise if performing vacuum on DB during upgrade will be beneficial. Best Regards, Strahil NikolovOn Jun 13, 2019 15:55, souvaliotimaria(a)mail.com wrote: > > Hello and thank you very much for your reply. > > I'm terribly sorry for being so late to respond. > > I thought the same, that dropping the cache was more of a workaround and not a real solution but truthfully I was stuck and can't think of anything more than how much I need to upgrade the memory on the nodes. I try to find info about other ovirt virtualization set-ups and the amount of memory allocated so I can get an idea of what my set-up needs. The only thing that I found was that one admin had set ovirt up with 128GB and still needed more because of the growing needs of the system and its users and was about to upgrade its memory too. I'm just worried that ovirt is very memory consuming and no matter how much I will "feed" it, it will still ask for more. Also, I'm worried that there one, two or even more tweaks in the configurations that I still miss and they'd be able to solve the memory problem. > > Anyway, KSM is enabled. Sar shows that the committed memory when a Windows 10 VM is active too (alongside Hosted Engine of course, and two Linux VMs - 1 CentOS, 1 Debian) is around 89% in the specific host that it runs (together with the Debian VM) and has reached up to 98%. > > You are correct about the monitoring system too. I have set up a PRTG environment and there's Nagios running but they can't yet see ovirt. I will set them up correctly the next few days. > > I haven't made any changes to my tuned profile. it's the default from ovirt. Specifically, the active profile says it's set to virtual-host. > > Again I'm very sorry for taking me so long to reply and thank you very much for your response. > > Best Regards, > Maria Souvalioti > _______________________________________________ > 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/G4YELWF5L4AKU…

1 0

oVirt engine/engine-setup with other port than default HTTPS 443 possible?
by Dirk Rydvan 13 Jun '19

13 Jun '19

Hello, in a home lab with only one puplic IPv4-Adress is the Port 443 a very precious one. The installation of oVirt 4.3 on a single node/host with bare metal installed CentOS works well. (oVirt Cockpit and local installed engine added after installation of Centos 7.6). But it is more difficult to change the port from 443 to maybe 4443 the save the port 443. The change in: - /etc/httpd/conf/conf.d/ssl.conf - /var/lib/ovirt-engine/jboss_runtime/config/ovirt-engine.xml and - disable selinux - add 4443 to public with firewall-cmd It does not work... now I see is more difficult than I think before... A port redirection at the edge route from <public-IPv4>:4443 to <private-IPv4>:443 does also not work, because the links points all to the standard https adress without a port number. Is there a way to change the default port 443 of oVirt engine to a other port? Many Thanks in advance!

2 2

Re: 4.3.4 caching disk error during hyperconverged deployment
by Strahil 13 Jun '19

13 Jun '19

Better raise a bug in bugilla.redhat.com and mention the working 4.3.3 Best Regards, Strahil NikolovOn Jun 13, 2019 04:30, adrianquintero(a)gmail.com wrote: > > While trying to do a hyperconverged setup and trying to use "configure LV Cache" /dev/sdf the deployment fails. If I dont use the LV cache SSD Disk the setup succeds, thought you mighg want to know, for now I retested with 4.3.3 and all worked fine, so reverting to 4.3.3 unless you know of a workaround? > > Error: > TASK [gluster.infra/roles/backend_setup : Extend volume group] ***************** > failed: [vmm11.mydomain.com] (item={u'vgname': u'gluster_vg_sdb', u'cachethinpoolname': u'gluster_thinpool_gluster_vg_sdb', u'cachelvname': u'cachelv_gluster_thinpool_gluster_vg_sdb', u'cachedisk': u'/dev/sdf', u'cachemetalvname': u'cache_gluster_thinpool_gluster_vg_sdb', u'cachemode': u'writethrough', u'cachemetalvsize': u'0.1G', u'cachelvsize': u'0.9G'}) => {"ansible_loop_var": "item", "changed": false, "err": " Physical volume \"/dev/sdb\" still in use\n", "item": {"cachedisk": "/dev/sdf", "cachelvname": "cachelv_gluster_thinpool_gluster_vg_sdb", "cachelvsize": "0.9G", "cachemetalvname": "cache_gluster_thinpool_gluster_vg_sdb", "cachemetalvsize": "0.1G", "cachemode": "writethrough", "cachethinpoolname": "gluster_thinpool_gluster_vg_sdb", "vgname": "gluster_vg_sdb"}, "msg": "Unable to reduce gluster_vg_sdb by /dev/sdb.", "rc": 5} > > failed: [vmm12.mydomain.com] (item={u'vgname': u'gluster_vg_sdb', u'cachethinpoolname': u'gluster_thinpool_gluster_vg_sdb', u'cachelvname': u'cachelv_gluster_thinpool_gluster_vg_sdb', u'cachedisk': u'/dev/sdf', u'cachemetalvname': u'cache_gluster_thinpool_gluster_vg_sdb', u'cachemode': u'writethrough', u'cachemetalvsize': u'0.1G', u'cachelvsize': u'0.9G'}) => {"ansible_loop_var": "item", "changed": false, "err": " Physical volume \"/dev/sdb\" still in use\n", "item": {"cachedisk": "/dev/sdf", "cachelvname": "cachelv_gluster_thinpool_gluster_vg_sdb", "cachelvsize": "0.9G", "cachemetalvname": "cache_gluster_thinpool_gluster_vg_sdb", "cachemetalvsize": "0.1G", "cachemode": "writethrough", "cachethinpoolname": "gluster_thinpool_gluster_vg_sdb", "vgname": "gluster_vg_sdb"}, "msg": "Unable to reduce gluster_vg_sdb by /dev/sdb.", "rc": 5} > > failed: [vmm10.mydomain.com] (item={u'vgname': u'gluster_vg_sdb', u'cachethinpoolname': u'gluster_thinpool_gluster_vg_sdb', u'cachelvname': u'cachelv_gluster_thinpool_gluster_vg_sdb', u'cachedisk': u'/dev/sdf', u'cachemetalvname': u'cache_gluster_thinpool_gluster_vg_sdb', u'cachemode': u'writethrough', u'cachemetalvsize': u'30G', u'cachelvsize': u'270G'}) => {"ansible_loop_var": "item", "changed": false, "err": " Physical volume \"/dev/sdb\" still in use\n", "item": {"cachedisk": "/dev/sdf", "cachelvname": "cachelv_gluster_thinpool_gluster_vg_sdb", "cachelvsize": "270G", "cachemetalvname": "cache_gluster_thinpool_gluster_vg_sdb", "cachemetalvsize": "30G", "cachemode": "writethrough", "cachethinpoolname": "gluster_thinpool_gluster_vg_sdb", "vgname": "gluster_vg_sdb"}, "msg": "Unable to reduce gluster_vg_sdb by /dev/sdb.", "rc": 5} > > PLAY RECAP ********************************************************************* > vmm10.mydomain.com : ok=13 changed=4 unreachable=0 failed=1 skipped=10 rescued=0 ignored=0 > vmm11.mydomain.com : ok=13 changed=4 unreachable=0 failed=1 skipped=10 rescued=0 ignored=0 > vmm12.mydomain.com : ok=13 changed=4 unreachable=0 failed=1 skipped=10 rescued=0 ignored=0 > > > > --------------------------------------------------------------------------------------------------------------------- > #cat /etc/ansible/hc_wizard_inventory.yml > --------------------------------------------------------------------------------------------------------------------- > hc_nodes: > hosts: > vmm10.mydomain.com: > gluster_infra_volume_gro

2 1

The CPU type of the cluster is unknown. Its possible to change the cluster cpu or set a different one per VM.
by sandeepkumar86k＠gmail.com 13 Jun '19

13 Jun '19

Hi, I am having trouble in fixing the CPU type of my oVirt cluster. I have AMD EPYC 7551P 32-Core Processor hosts(x3) in a gluster cluster. The HE and cluster by default had the: AMD Opteron 23xx (Gen 3 Class Opteron). I tried changing it with this method(https://lists.ovirt.org/archives/list/users@ovirt.org/thread/XYY2WAG…, it didn't work as I can't move the Host to another cluster it complains (Error while executing action: *******: Cannot edit Host. Server having Gluster volume.) Then I tried updating the cpu_name manually in DB by following: https://www.mail-archive.com/users@ovirt.org/msg33177.html After the Update, the web UI shows it changed to AMD EPYC but if I click on Edit cluster it shows the "Intel Conroe Family" and again doesn't allow to modify. I am now stuck with unusable oVirt setup, my existing VMs won't start and throw: Error while executing action: ******: The CPU type of the cluster is unknown. Its possible to change the cluster cpu or set a different one per VM.) Please help or suggest to fix this issue. HE: cat /proc/cpuinfo |grep "model name" model name : AMD Opteron 23xx (Gen 3 Class Opteron) model name : AMD Opteron 23xx (Gen 3 Class Opteron) model name : AMD Opteron 23xx (Gen 3 Class Opteron) model name : AMD Opteron 23xx (Gen 3 Class Opteron) rpm -qa |grep -i ovirt ovirt-ansible-image-template-1.1.9-1.el7.noarch ovirt-engine-dwh-setup-4.2.4.3-1.el7.noarch ovirt-engine-backend-4.2.8.2-1.el7.noarch ovirt-engine-extension-aaa-ldap-1.3.8-1.el7.noarch ovirt-engine-extension-aaa-jdbc-1.1.7-1.el7.centos.noarch ovirt-engine-wildfly-overlay-14.0.1-3.el7.noarch ovirt-ansible-hosted-engine-setup-1.0.2-1.el7.noarch ovirt-host-deploy-java-1.7.4-1.el7.noarch ovirt-engine-setup-plugin-websocket-proxy-4.2.8.2-1.el7.noarch ovirt-engine-setup-plugin-vmconsole-proxy-helper-4.2.8.2-1.el7.noarch ovirt-ansible-engine-setup-1.1.6-1.el7.noarch ovirt-ansible-cluster-upgrade-1.1.10-1.el7.noarch ovirt-ansible-roles-1.1.6-1.el7.noarch ovirt-release42-4.2.8-1.el7.noarch ovirt-engine-setup-plugin-ovirt-engine-common-4.2.8.2-1.el7.noarch ovirt-engine-tools-backup-4.2.8.2-1.el7.noarch ovirt-provider-ovn-1.2.18-1.el7.noarch ovirt-imageio-common-1.4.6-1.el7.x86_64 ovirt-js-dependencies-1.2.0-3.1.el7.centos.noarch ovirt-cockpit-sso-0.0.4-1.el7.noarch ovirt-engine-restapi-4.2.8.2-1.el7.noarch ovirt-engine-vmconsole-proxy-helper-4.2.8.2-1.el7.noarch ovirt-engine-api-explorer-0.0.2-1.el7.centos.noarch ovirt-engine-lib-4.2.8.2-1.el7.noarch ovirt-engine-setup-base-4.2.8.2-1.el7.noarch ovirt-engine-metrics-1.1.8.1-1.el7.noarch ovirt-ansible-repositories-1.1.3-1.el7.noarch ovirt-ansible-disaster-recovery-1.1.4-1.el7.noarch ovirt-ansible-infra-1.1.10-1.el7.noarch ovirt-ansible-shutdown-env-1.0.0-1.el7.noarch ovirt-engine-dwh-4.2.4.3-1.el7.noarch ovirt-iso-uploader-4.2.0-1.el7.centos.noarch ovirt-engine-webadmin-portal-4.2.8.2-1.el7.noarch ovirt-engine-dbscripts-4.2.8.2-1.el7.noarch ovirt-engine-setup-plugin-ovirt-engine-4.2.8.2-1.el7.noarch ovirt-engine-extension-aaa-ldap-setup-1.3.8-1.el7.noarch ovirt-engine-extensions-api-impl-4.2.8.2-1.el7.noarch ovirt-host-deploy-1.7.4-1.el7.noarch ovirt-vmconsole-1.0.6-2.el7.noarch python-ovirt-engine-sdk4-4.2.9-2.el7.x86_64 ovirt-engine-wildfly-14.0.1-3.el7.x86_64 ovirt-guest-agent-common-1.0.16-1.el7.noarch ovirt-ansible-v2v-conversion-host-1.9.0-1.el7.noarch ovirt-ansible-manageiq-1.1.13-1.el7.noarch ovirt-setup-lib-1.1.5-1.el7.noarch ovirt-engine-websocket-proxy-4.2.8.2-1.el7.noarch ovirt-engine-dashboard-1.2.4-1.el7.noarch ovirt-engine-setup-4.2.8.2-1.el7.noarch ovirt-engine-sdk-python-3.6.9.1-1.el7.noarch ovirt-vmconsole-proxy-1.0.6-2.el7.noarch ovirt-web-ui-1.4.5-1.el7.noarch ovirt-ansible-vm-infra-1.1.12-1.el7.noarch ovirt-imageio-proxy-setup-1.4.6-1.el7.noarch ovirt-imageio-proxy-1.4.6-1.el7.noarch ovirt-engine-tools-4.2.8.2-1.el7.noarch ovirt-engine-4.2.8.2-1.el7.noarch ovirt-engine-cli-3.6.9.2-1.el7.centos.noarch 3xHosts: cat /proc/cpuinfo |grep "model name" model name : AMD EPYC 7551P 32-Core Processor model name : AMD EPYC 7551P 32-Core Processor model name : AMD EPYC 7551P 32-Core Processor rpm -qa |grep -i ovirt ovirt-release42-4.2.8-1.el7.noarch cockpit-ovirt-dashboard-0.11.38-1.el7.noarch ovirt-vmconsole-1.0.6-2.el7.noarch python-ovirt-engine-sdk4-4.2.9-2.el7.x86_64 cockpit-machines-ovirt-193-2.el7.noarch ovirt-imageio-daemon-1.4.6-1.el7.noarch ovirt-hosted-engine-setup-2.2.33-1.el7.noarch ovirt-engine-appliance-4.2-20190121.1.el7.noarch ovirt-vmconsole-host-1.0.6-2.el7.noarch ovirt-engine-sdk-python-3.6.9.1-1.el7.noarch ovirt-setup-lib-1.1.5-1.el7.noarch ovirt-host-deploy-1.7.4-1.el7.noarch ovirt-host-dependencies-4.2.3-1.el7.x86_64 ovirt-hosted-engine-ha-2.2.19-1.el7.noarch ovirt-provider-ovn-driver-1.2.18-1.el7.noarch ovirt-imageio-common-1.4.6-1.el7.x86_64 ovirt-host-4.2.3-1.el7.x86_64 Thanks,

2 2

Info about soft fencing mechanism
by Gianluca Cecchi 13 Jun '19

13 Jun '19

Hello, I would like to know in better detail how soft fencing works in 4.3. In particular, with "soft fencing" we "only" mean vdsmd restart attempt, correct? Who is responsible for issuing the command? Manager or host itself? Because in case of Manager, if the host has already lost connection, how could the manager be able to do it? Thanks in advance for clarifications and eventually documentation pointers Gianluca

1 0

Re: Hosted Engine Abruptly Stopped Responding - Unexpected Shutdown
by Strahil 13 Jun '19

13 Jun '19

On Jun 6, 2019 12:52, souvaliotimaria(a)mail.com wrote: > > Hello, > > I came upon a problem the previous month that I figured it would be good to discuss here. I'm sorry I didn't post here earlier but time slipped me. > > I have set up a glustered, hyperconverged oVirt environment for experimental use as a means to see its behaviour and get used to its management and performance before setting it up as a production environment for use in our organization. The environment is up and running since 2018 October. The three nodes are HP ProLiant DL380 G7 and have the following characteristics: > > Mem: 22GB > CPU: 2x Hexa Core - Intel Xeon Hexa Core E56xx > HDD: 5x 300GB > Network: BCM5709C with dual-port Gigabit > OS: Linux RedHat 7.5.1804(Core 3.10.0-862.3.2.el7.x86_64 x86_64) - Ovirt Node 4.2.3.1 > > As I was working on the environment, the engine stopped working. > Not long before the time the HE stopped, I was in the web interface managing my VMs, when the browser froze and the HE was also not responding to ICMP requests. > > The first thing I did was to connect via ssh to all nodes and run the command > #hosted-engine --vm-status > which showed that the HE was down in nodes 1 and 2 and up on the 3rd node. > > After executing > #virsh -r list > the VM list that was shown contained two of the VMs I had previously created and were up; the HE was nowhere. > > I tried to restart the HE with the > #hosted-engine --vm-start > but it didn't work. > > I then put all nodes in maintenance mode with the command > #hosted-engine --set-maintenance --mode=global > (I guess I should have done that earlier) and re-run > #hosted-engine --vm-start > that had the same result as it previously did. > > After checking the mails the system sent to the root user, I saw there were several mails on the 3rd node (where the HE had been), informing of the HE's state. The messages were changing between EngineDown-EngineStart, EngineStart-EngineStarting, EngineStarting-EngineMaybeAway, EngineMaybeAway-EngineUnexpectedlyDown, EngineUnexpectedlyDown-EngineDown, EngineDown-EngineStart and so forth. > > I continued by searching the following logs in all nodes : > /var/log/libvirt/qemu/HostedEngine.log > /var/log/libvirt/qemu/win10.log > /var/log/libvirt/qemu/DNStest.log > /var/log/vdsm/vdsm.log > /var/log/ovirt-hosted-engine-ha/agent.log > > After that I spotted and error that had started appearing almost a month ago in node #2: > ERROR Internal server error Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/yajsonrpc/__init__.py", line 606, in _handle_request res = method(**params) File "/usr/lib/python2.7/site-packages/vdsm/rpc/Bridge.py", line 197, in _dynamicMethod result = fn(*methodArgs) File "/usr/lib/python2.7/site-packages/vdsm/gluster/apiwrapper.py", line 85, in logicalVolumeList return self._gluster.logicalVolumeList() File "/usr/lib/python2.7/site-packages/vdsm/gluster/api.py", line 90, in wrapper rv = func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/gluster/api.py", line 808, in logicalVolumeList status = self.svdsmProxy.glusterLogicalVolumeList() File "/usr/lib/python2.7/site-packages/vdsm/common/supervdsm.py", line 55, in __call__ return callMethod() File "/usr/lib/python2.7/site-packages/vdsm/common/supervdsm.py", line 52, in <lambda> getattr(self._supervdsmProxy._svdsm, self._funcName)(*args, AttributeError: 'AutoProxy[instance]' object has no attribute 'glusterLogicalVolumeList' > > > The outputs of the following commands were also checked as a way to see if there was a mandatory process missing/killed, a memory problem or even disk space shortage that led to the sudden death of a process > #ps -A > #top > #free -h > #df -hT > > Finally, after some time delving in the logs, the output of the > #journalctl --dmesg > showed the following message > "Out of memory: Kill process 5422 (qemu-kvm) score 514 or sacrifice child. > Killed process 5422 (qemu-kvm) total-vm:17526548kB, anon-rss:9310396kB, > file-rss:2336kB, shmem-rss:12kB" > which after that the ovirtmgmt started not responding. If you run out of memory, you should take that serious.Droping the cache seems like a workaround and not a fix. Check if KSM is enabled - this will merge your VM's memory pages for an exchange for CPU cycles - still better than getting a VM killed. Also, you can protect the HostedEngine from OOM killer. > I tried to restart the vhostd by executing > #/etc/rc.d/init.d/vhostmd start > but it didn't work. > > Finally, I decided to run the HE restart command on the other nodes as well (I'd figured that since the HE was last running on the node #3, that's where I should try to restart it). So, I run > #hosted-engine --vm-start > and the output was > "Command VM.getStats with args {'vmID':'...<το ID της HE>....'} failed: > (code=1,message=Virtual machine does not exist: {'vmID':'...<το ID της > HE>....'})" > And then I run the command again and the output was > "VM exists and its status is Powering Up." > > After that I executed > #virsh -r list > and the output was the following: > Id Name State > ---------------------------------------------------- > 2 HostedEngine running > > After the HE's restart two mails came that stated: ReinitializeFSMEngineStarting and EngineStarting-EngineUp > > After that and after checking that we had access to the web interface again, we executed > hosted-engine --set-maintenance --mode=none > to get out of the maintenance mode. > > The thing is, I still am not 1000% sure what the problem was that led to the shutdown of the hosted engine and I think that maybe some of the steps I took were not needed. I believe it was because the process qemu-kvm was killed after there was not enough memory for it but is this the real cause? I wasn't doing anything unusual before the shutdown to believe it was because of the new VM that was still in shutdown mode or anything of the sort. Also, I believe it may be because of memory shortage because I hadn't executed the > #sync ; echo 3 > /proc/sys/vm/drop_caches > command for a couple of weeks. > > What are your thoughts on this? Could you point me to where to search for more information on the topic or tell me what is the right process to follow when something like this happens? Check the sar (there is a graphical util called 'ksar' and check cpu , memory, swap, context switches , I/O and network usage). Crreate simple systemd service to monitor your nodes, or even better put a real monitoring software so you can proactively take any actions. > Also, I have set up a few VMs but only three are Up and they have no users yet, even so the buffers fill almost to the brim when the usage is almost non-existant. If you have an environment that has some users or you use the VMs as virtual servers of some sort, what is the consumption of the memory? What's the optimal size for the memory? What is your tuned profile ? Any customizations there ? Best Regards, Strahil Nikolov > Thank you all very much. > _______________________________________________ > 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/PKRB26GSDQ5JV…

2 1

Re: 4.3 live migration creates wrong image permissions.
by Strahil 13 Jun '19

13 Jun '19

Hi Alex, Did you migrate from gluster v3 to v5 ? If yes, then it could be the issue with v5.3 where permissions go wrong. If so, pick ovirt 4.3.4 as it uses a newer (fixed ) version of gluster -> v5.6 Best Regards, Strahil NikolovOn Jun 13, 2019 09:46, Alex McWhirter <alex(a)triadic.us> wrote: > > after upgrading from 4.2 to 4.3, after a vm live migrates it's disk > images are become owned by root:root. Live migration succeeds and the vm > stays up, but after shutting down the VM from this point, starting it up > again will cause it to fail. At this point i have to go in and change > the permissions back to vdsm:kvm on the images, and the VM will boot > 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/TSWRTC2E7XZSG…

2 1

High Performance VM: trouble using vNUMA and hugepages
by Matthias Leopold 13 Jun '19

13 Jun '19

Hi, I'm having trouble using vNUMA and hugepages at the same time: - hypervisor host hast 2 CPU and 768G RAM - hypervisor host is configured to allocate 512 1G hugepages - VM configuration * 2 virtual sockets, vCPUs are evenly pinned to 2 physical CPUs * 512G RAM * 2 vNUMA nodes that are pinned to the 2 host NUMA nodes * custom property "hugepages=1048576" - VM is the only VM on hypervisor host when I want to start the VM I'm getting the error message "The host foo did not satisfy internal filter NUMA because cannot accommodate memory of VM's pinned virtual NUMA nodes within host's physical NUMA nodes" VM start only works when VM memory is shrunk so that it fits in (host memory - allocated huge pages) I don't understand why this happens. Can someone explain to me how this is supposed to work? oVirt engine is 4.3.3 oVirt host is 4.3.4 thanks matthias

1 0

[ANN] oVirt 4.3.5 First Release Candidate is now available
by Sandro Bonazzola 13 Jun '19

13 Jun '19

The oVirt Project is pleased to announce the availability of the oVirt 4.3.5 First Release Candidate, as of June 13th, 2019. This update is a release candidate of the fifth in a series of stabilization updates to the 4.3 series. This is pre-release software. This pre-release should not to be used in production. 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) See the release notes [1] for installation / upgrade instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is already available - oVirt Node is already available[2] Additional Resources: * Read more about the oVirt 4.3.5 release highlights: http://www.ovirt.org/release/4.3.5/ * 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.5/ [2] http://resources.ovirt.org/pub/ovirt-4.3-pre/iso/ -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/>

1 0

Re: Memory ballon question
by Strahil 13 Jun '19

13 Jun '19

Hi Darrell, Yes , all VMs (both openSUSE and RedHat/CentOS 7) have the ovirt-guest-agent up and running. Best Regards, Strahil NikolovOn Jun 12, 2019 22:07, Darrell Budic <budic(a)onholyground.com> wrote: > > Do you have the overt-guest-agent running on your VMs? It’s required for ballooning to control allocations on the guest side. > >> On Jun 12, 2019, at 11:32 AM, Strahil <hunter86_bg(a)yahoo.com> wrote: >> >> Hello All, >> >> as a KVM user I know how usefull is the memory balloon and how you can both increase - and also decrease memory live (both Linux & Windows). >> I have noticed that I cannot decrease the memory in oVirt. >> >> Does anyone got a clue why the situation is like that ? >> >> I was expecting that the guaranteed memory is the minimum to which the balloon driver will not go bellow, but when I put my host under pressure - the host just started to swap instead of reducing some of the VM memory (and my VMs had plenty of free space). >> >> It will be great if oVirt can decrease the memory (if the VM has unallocated memory) when the host is under pressure and the VM cannot be relocated. >> >> Best Regards, >> Strahil Nikolov >> >> _______________________________________________ >> 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/LUWCN2MLNTDJU… > >

2 1

Re: Ovirt hiperconverged setup error
by Strahil 13 Jun '19

13 Jun '19

Simone has provided you a workaround, so check his e-mail. The ansible is actually running: dig ov-node2 +short As dig is quarrying your DNS server, you need to bypass this check if you use /etc/host entries. Best Regards, Strahil NikolovOn Jun 12, 2019 21:57, PS Kazi <faruk.apsara(a)gmail.com> wrote: > > Hi, > How to check my DNS settings is ok or not for ovirt? > > On Wed, 12 Jun 2019, 6:55 pm Strahil Nikolov, <hunter86_bg(a)yahoo.com> wrote: >> >> Command run is "dig' which tries to resolve the hostname of each server. >> Do you have a DNS resolver properly configured ? >> >> Best Regards, >> Strahil Nikolov >> >> В сряда, 12 юни 2019 г., 3:59:14 ч. Гринуич-4, PS Kazi <faruk.apsara(a)gmail.com> написа: >> >> >> ovirt Node version 4.3.3.1 >> I am trying to configure 3 node Gluster storage and oVirt hosted engine but gettng following error: >> >> TASK [gluster.features/roles/gluster_hci : Check if valid FQDN is provided] **** >> failed: [ov-node-2 -> localhost] (item=ov-node-2) => {"changed": true, "cmd": ["dig", "ov-node-2", "+short"], "delta": "0:00:00.041003", "end": "2019-06-12 12:52:34.158688", "failed_when_result": true, "item": "ov-node-2", "rc": 0, "start": "2019-06-12 12:52:34.117685", "stderr": "", "stderr_lines": [], "stdout": "", "stdout_lines": []} >> failed: [ov-node-2 -> localhost] (item=ov-node-3) => {"changed": true, "cmd": ["dig", "ov-node-3", "+short"], "delta": "0:00:00.038688", "end": "2019-06-12 12:52:34.459176", "failed_when_result": true, "item": "ov-node-3", "rc": 0, "start": "2019-06-12 12:52:34.420488", "stderr": "", "stderr_lines": [], "stdout": "", "stdout_lines": []} >> failed: [ov-node-2 -> localhost] (item=ov-node-1) => {"changed": true, "cmd": ["dig", "ov-node-1", "+short"], "delta": "0:00:00.047938", "end": "2019-06-12 12:52:34.768149", "failed_when_result": true, "item": "ov-node-1", "rc": 0, "start": "2019-06-12 12:52:34.720211", "stderr": "", "stderr_lines": [], "stdout": "", "stdout_lines": []} >> >> >> Please help >> _______________________________________________ >> 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/BXMOTKHGI5TNP…

1 0

Re: Replace bad Host from a 9 Node hyperconverged setup 4.3.3
by Strahil 12 Jun '19

12 Jun '19

Hi Adrian, You have several options: A) If you have space on another gluster volume (or volumes) or on NFS-based storage, you can migrate all VMs live . Once you do it, the simple way will be to stop and remove the storage domain (from UI) and gluster volume that correspond to the problematic brick. Once gone, you can remove the entry in oVirt for the old host and add the newly built one.Then you can recreate your volume and migrate the data back. B) If you don't have space you have to use a more riskier approach (usually it shouldn't be risky, but I had bad experience in gluster v3): - New server has same IP and hostname: Use command line and run the 'gluster volume reset-brick VOLNAME HOSTNAME:BRICKPATH HOSTNAME:BRICKPATH commit' Replace VOLNAME with your volume name. A more practical example would be: 'gluster volume reset-brick data ovirt3:/gluster_bricks/data/brick ovirt3:/gluster_ ricks/data/brick commit' If it refuses, then you have to cleanup '/gluster_bricks/data' (which should be empty). Also check if the new peer has been probed via 'gluster peer status'.Check the firewall is allowing gluster communication (you can compare it to the firewalls on another gluster host). The automatic healing will kick in 10 minutes (if it succeeds) and will stress the other 2 replicas, so pick your time properly. Note: I'm not recommending you to use the 'force' option in the previous command ... for now :) - The new server has a different IP/hostname: Instead of 'reset-brick' you can use 'replace-brick': It should be like this: gluster volume replace-brick data old-server:/path/to/brick new-server:/new/path/to/brick commit force In both cases check the status via: gluster volume info VOLNAME If your cluster is in production , I really recommend you the first option as it is less risky and the chance for unplanned downtime will be minimal. The 'reset-brick' in your previous e-mail shows that one of the servers is not connected. Check peer status on all servers, if they are less than they should check for network and/or firewall issues. On the new node check if glusterd is enabled and running. In order to debug - you should provide more info like 'gluster volume info' and the peer status from each node. Best Regards, Strahil Nikolov On Jun 10, 2019 20:10, Adrian Quintero <adrianquintero(a)gmail.com> wrote: > > Can you let me know how to fix the gluster and missing brick?, > I tried removing it by going to "storage > Volumes > vmstore > bricks > selected the brick > However it is showing as an unknown status (which is expected because the server was completely wiped) so if I try to "remove", "replace brick" or "reset brick" it wont work > If i do remove brick: Incorrect bricks selected for removal in Distributed Replicate volume. Either all the selected bricks should be from the same sub volume or one brick each for every sub volume! > If I try "replace brick" I cant because I dont have another server with extra bricks/disks > And if I try "reset brick": Error while executing action Start Gluster Volume Reset Brick: Volume reset brick commit force failed: rc=-1 out=() err=['Host myhost1_mydomain_com not connected'] > > Are you suggesting to try and fix the gluster using command line? > > Note that I cant "peer detach" the sever , so if I force the removal of the bricks would I need to force downgrade to replica 2 instead of 3? what would happen to oVirt as it only supports replica 3? > > thanks again. > > On Mon, Jun 10, 2019 at 12:52 PM Strahil <hunter86_bg(a)yahoo.com> wrote: >> >> Hi Adrian, >> Did you fix the issue with the gluster and the missing brick? >> If yes, try to set the 'old' host in maintenance an

3 4

oVirt engine/engine-setup with other port than default HTTPS 443 possible?
by Dirk Rydvan 12 Jun '19

12 Jun '19

Hello, in a home lab with only one puplic IPv4-Adress is the Port 443 a very precious one. The installation of oVirt 4.3 on a single node/host with bare metal installed CentOS works well. (oVirt Cockpit and local installed engine added after installation of Centos 7.6). But it is more difficult to change the port from 443 to maybe 4443 the save the port 443. The change in: - /etc/httpd/conf/conf.d/ssl.conf - /var/lib/ovirt-engine/jboss_runtime/config/ovirt-engine.xml and - disable selinux - add 4443 to public with firewall-cmd It does not work... now I see is more difficult than I think before... A port redirection at the edge route from <public-IPv4>:4443 to <private-IPv4>:443 does also not work, because the links points all to the standard https adress without a port number. Is there a way to change the default port 443 of oVirt engine to a other port? Many Thanks in advance!

1 0

RFE: HostedEngine to use boom by default
by Strahil Nikolov 12 Jun '19

12 Jun '19

Hello All, I have seen a lot of cases where the HostedEngine gets corrupted/broken and beyond repair. I think that BOOM is a good option for our HostedEngine appliances due to the fact that it supports booting from LVM snapshots and thus being able to easily recover after upgrades or other outstanding situations. Sadly, BOOM has 1 drawback - that everything should be under a single snapshot - thus no separation of /var /log or /audit. Do you think that changing the appliance layout is worth it ? Note: I might have an unsupported layout that could cause my confusion.Is your layout a single root LV ? Best Regards,Strahil Nikolov

2 2

4K Sector Hard drive Support - oVirt 4.3.4
by nico.kruger＠darkmatter.ae 12 Jun '19

12 Jun '19

Hi Guys, Does anyone have any idea if/when 4K Sector drives will be supported? My understanding is that this was one of the features for 4.3.4 Thanks Nico Kruger

2 1