- Users - oVirt List Archives

Re: [ovirt-devel] cannot add host (oVirt 4.3.3.7)
by Nir Soffer 10 Jun '19

10 Jun '19

On Sun, Jun 9, 2019 at 9:15 PM Hetz Ben Hamo <hetz(a)hetz.biz> wrote: Moving to users list, devel list is for discussion about oVirt development, not troubleshooting. I'm trying to add a new host to oVirt. The main host is Xeon E5 while the > new host is AMD Ryzen 5. > > The main host is running oVirt 4.3.3 and the new node is a minimal install > of CentOS 7.6 (1810) with all the latest updates. > Which engine version? on which OS? I'm enclosing the log files. it complains that it cannot get the oVirt > packages, perhaps wrong channel(?). Looking at the log, it's trying to use > minidnf. I don't think CentOS 7 supports DNF.. > Did you install ovirt-release43 rpm before adding the host? https://ovirt.org/download/ Nir

3 4

Re: Clusters run virtual machines or Red Hat Gluster Storage Servers
by Strahil 10 Jun '19

10 Jun '19

OVirt + Gluster is called 'Hyperconverged' setup and it supports only replica3 or a 'replica3 arbiter1' volumes. Vmware VSAN is another popular Hyperconverged Setup but requires a lot of licenses. The CPU and Disk resources are plenty on virtualization Hosts and this setup allows you to save space by removal of the iSCSI/NFS/SAN dedicated system. The setup is quite popular and it works quite well, but requires a 10G network (as load balancing smaller NICs is very hard ) - if performance is required, while even a 1 gbit/s NIC is possible to be used. Note: 1gbit/s will provide no more than 87 MB/s on gluster level for all your VMs , which is very poor. If you have 4 hosts -> one of them will not be in the gluster setup, or you will have 2 separate gluster volumes like this: oVirt1- Replica for volume A oVirt2- Replica for volume A , arbiter for volume B oVirt3 - Replica for volume B,arbiter for volume A oVirt4 - Replica for volume B Then you add them as hosts in your oVirt setup. Best Regards, Strahil NikolovOn Jun 10, 2019 05:29, xilazz(a)126.com wrote: > > Hi, everybody. When I was looking at the administrator's manual, it prompted Clusters run virtual machines or Red Hat Gluster Storage Servers. These two purposes are mad exclusive: > Virtualization and storage hosts together. When I configured the cluster, I said that the glusterfs and virt I saw were alternatives to the two checkboxes. > I would like to ask what happens when glusterfs and virt are in the same cluster? > How can I use hosted engine when I have four nodes? > Thank you very much for your reply. > _______________________________________________ > 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/CZR73TNWNRE5L…

2 1

Clusters run virtual machines or Red Hat Gluster Storage Servers
by xilazz＠126.com 09 Jun '19

09 Jun '19

Hi, everybody. When I was looking at the administrator's manual, it prompted Clusters run virtual machines or Red Hat Gluster Storage Servers. These two purposes are mad exclusive: Virtualization and storage hosts together. When I configured the cluster, I said that the glusterfs and virt I saw were alternatives to the two checkboxes. I would like to ask what happens when glusterfs and virt are in the same cluster? How can I use hosted engine when I have four nodes? Thank you very much for your reply.

1 0

run ovirt without firewalld
by Chris Boon 08 Jun '19

08 Jun '19

Hello, When i deploy and use oVirt 4.3, is firewalld really needed on hypervisors or can oVirt 4.3 run and function with a disabled firewalld? Regards, Chris

1 0

oVirt hosted engine lost superblocks, need to recover data - 4.1
by marcushershberger＠locl.net 07 Jun '19

07 Jun '19

I have been working on this a few days now, though no solution seems to have emerged. I have an oVirt 4.1 hosted engine that is now failing to boot except into emergency mode. When xfs_repair is run, it gives an error saying that the primary and secondary superblocks are bad. Earlier this week, I was trying to install engine-backup because there were problems with the root partition being full. I was working on resolving dependencies for engine-backup when the hosted engine became unresponsive with an output about gov0 (which I believe is related to gluster), and I have not been able to boot it correctly since then. I am able to mount /var, and I have access to it, but that is not true for the root partition. What are some suggestions for recovering the data on the root partition? Thanks!

1 0

disk description
by Dmitry Filonov 07 Jun '19

07 Jun '19

Hi - Looks like Friday is right around the corner... Have a really stupid question. Is there a way to edit disk description (or extend it's size) without attaching that disk to some VM and editing disk there? Thanks! -- Dmitry Filonov Linux Administrator SBGrid Core | Harvard Medical School 250 Longwood Ave, SGM-114 Boston, MA 02115

2 2

ETL service sampling has encountered an error. Please consult the service log for more details.
by nicolas＠devels.es 07 Jun '19

07 Jun '19

Hi, We're running oVirt 4.1.9 (cannot upgrade yet until [1] is released). Since a few days ago our event list if full of lines like this: ETL service sampling has encountered an error. Please consult the service log for more details. Having a look at the log I see events like: 2019-06-06 13:37:11|NJ4C8T|TOlL8U|FdlWtU|OVIRT_ENGINE_DWH|StatisticsSync|Default|6|Java Exception|tJDBCOutput_7|org.postgresql.util.PSQLException:ERROR: current transaction is aborted, commands ignored until end of transaction block|1 2019-06-06 13:37:11|NJ4C8T|TOlL8U|FdlWtU|OVIRT_ENGINE_DWH|StatisticsSync|Default|6|Java Exception|tJDBCOutput_4|org.postgresql.util.PSQLException:ERROR: current transaction is aborted, commands ignored until end of transaction block|1 Exception in component tJDBCOutput_5 org.postgresql.util.PSQLException: ERROR: current transaction is aborted, commands ignored until end of transaction block at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2157) at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1886) at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:255) at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:555) at org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:417) at org.postgresql.jdbc2.AbstractJdbc2Statement.executeUpdate(AbstractJdbc2Statement.java:363) at ovirt_engine_dwh.statisticssync_4_1.StatisticsSync.tJDBCInput_10Process(StatisticsSync.java:9030) at ovirt_engine_dwh.statisticssync_4_1.StatisticsSync$5.run(StatisticsSync.java:16071) 2019-06-06 13:37:11|NJ4C8T|TOlL8U|FdlWtU|OVIRT_ENGINE_DWH|StatisticsSync|Default|6|Java Exception|tJDBCOutput_5|org.postgresql.util.PSQLException:ERROR: current transaction is aborted, commands ignored until end of transaction block|1 Exception in component tRunJob_5 java.lang.RuntimeException: Child job running failed at ovirt_engine_dwh.samplerunjobs_4_1.SampleRunJobs.tRunJob_5Process(SampleRunJobs.java:1654) at ovirt_engine_dwh.samplerunjobs_4_1.SampleRunJobs.tRunJob_6Process(SampleRunJobs.java:1456) at ovirt_engine_dwh.samplerunjobs_4_1.SampleRunJobs.tRunJob_1Process(SampleRunJobs.java:1228) at ovirt_engine_dwh.samplerunjobs_4_1.SampleRunJobs.tRunJob_4Process(SampleRunJobs.java:1000) at ovirt_engine_dwh.samplerunjobs_4_1.SampleRunJobs.tJDBCConnection_2Process(SampleRunJobs.java:767) at ovirt_engine_dwh.samplerunjobs_4_1.SampleRunJobs.tJDBCConnection_1Process(SampleRunJobs.java:642) at ovirt_engine_dwh.samplerunjobs_4_1.SampleRunJobs$2.run(SampleRunJobs.java:2683) 2019-06-06 13:37:11|FdlWtU|TOlL8U|KNLNa4|OVIRT_ENGINE_DWH|SampleRunJobs|Default|6|Java Exception|tRunJob_5|java.lang.RuntimeException:Child job running failed|1 Exception in component tRunJob_1 java.lang.RuntimeException: Child job running failed at ovirt_engine_dwh.sampletimekeepingjob_4_1.SampleTimeKeepingJob.tRunJob_1Process(SampleTimeKeepingJob.java:6067) at ovirt_engine_dwh.sampletimekeepingjob_4_1.SampleTimeKeepingJob.tJDBCInput_2Process(SampleTimeKeepingJob.java:5809) at ovirt_engine_dwh.sampletimekeepingjob_4_1.SampleTimeKeepingJob.tJDBCConnection_1Process(SampleTimeKeepingJob.java:4444) at ovirt_engine_dwh.sampletimekeepingjob_4_1.SampleTimeKeepingJob.tJDBCConnection_2Process(SampleTimeKeepingJob.java:4319) at ovirt_engine_dwh.sampletimekeepingjob_4_1.SampleTimeKeepingJob.tRowGenerator_2Process(SampleTimeKeepingJob.java:4188) at ovirt_engine_dwh.sampletimekeepingjob_4_1.SampleTimeKeepingJob.tJDBCInput_3Process(SampleTimeKeepingJob.java:3593) at ovirt_engine_dwh.sampletimekeepingjob_4_1.SampleTimeKeepingJob.tJDBCInput_5Process(SampleTimeKeepingJob.java:2977) at ovirt_engine_dwh.sampletimekeepingjob_4_1.SampleTimeKeepingJob.tJDBCInput_4Process(SampleTimeKeepingJob.java:2295) at ovirt_engine_dwh.sampletimekeepingjob_4_1.SampleTimeKeepingJob.tJDBCConnection_3Process(SampleTimeKeepingJob.java:1649) at ovirt_engine_dwh.sampletimekeepingjob_4_1.SampleTimeKeepingJob$2.run(SampleTimeKeepingJob.java:11363) Can someone tell me how to fix it? I already restarted ovirt-engine, ovirt-engine-dwhd, postgresql and the three at a time and still didn't fix the issue. Currently the DWHD data is empty in the Dashboard. Thanks! [1]: https://github.com/oVirt/ovirt-web-ui/issues/490

2 2

[ANN] oVirt 4.3.4 Fourth Release Candidate is now available
by Sandro Bonazzola 07 Jun '19

07 Jun '19

The oVirt Project is pleased to announce the availability of the oVirt 4.3.4 FourthRelease Candidate, as of June 6th, 2019. This update is a release candidate of the fourth in a series of stabilization updates to the 4.3 series. This is pre-release software. This pre-release should not to be used inproduction. 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 already available - oVirt Node is already available[2] - oVirt Windows Guest Tools iso is already available [2] Additional Resources: * Read more about the oVirt 4.3.4 release highlights: http://www.ovirt.org/release/4.3.4/ * 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.4/ [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://red.ht/sig> <https://redhat.com/summit>

2 2

high number of interface RX errors on ovirtmgmt network
by Jayme 06 Jun '19

06 Jun '19

I have a three node HCI setup on Dell R720s running the latest stable version of 4.3.3 Each hosts has a 1gig link and a 10gig link. The 1gig is used for ovirt management network and 10gig link is used for backend glusterFS traffic. I haven't noticed before but after installing ovirt metrics store I'm seeing that gig interface used for ovirtmgmt on all three hosts are showing high RX error rates. The 10gig interfaces for glusterFS on all three hosts appear to be fine. The 1gig ethernet controllers are: Broadcom Inc. and subsidiaries NetXtreme II BCM57800 1/10 Gigabit Ethernet (rev 10) Other physical servers on the same network/switches outside of oVirt have zero RX errors. Here is an example of what I'm seeing: host0: # ip -s link show em3 4: em3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master ovirtmgmt state UP mode DEFAULT group default qlen 1000 link/ether b0:83:fe:cc:9a:2d brd ff:ff:ff:ff:ff:ff RX: bytes packets errors dropped overrun mcast 51777532544474 36233202312 416993 0 0 2062421 TX: bytes packets errors dropped carrier collsns 7284362442704 18685883330 0 0 0 0 host1: # ip -s link show em3 4: em3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master ovirtmgmt state UP mode DEFAULT group default qlen 1000 link/ether b0:83:fe:cc:99:31 brd ff:ff:ff:ff:ff:ff RX: bytes packets errors dropped overrun mcast 9518766859330 14424644226 89638 0 0 2056578 TX: bytes packets errors dropped carrier collsns 27866585257227 22323979969 0 0 0 0 host2: # ip -s link show em3 4: em3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master ovirtmgmt state UP mode DEFAULT group default qlen 1000 link/ether b0:83:fe:cc:92:50 brd ff:ff:ff:ff:ff:ff RX: bytes packets errors dropped overrun mcast 6409138012195 13045254148 14825 0 0 2040655 TX: bytes packets errors dropped carrier collsns 31577745516683 23466818659 0 0 0 0 Anyone have any ideas why the RX error rate on the ovirtmgmt network could be so high?

1 1

Hosted Engine Abruptly Stopped Responding - Unexpected Shutdown
by souvaliotimaria＠mail.com 06 Jun '19

06 Jun '19

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. 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? 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? Thank you all very much.

2 1