- Users - oVirt List Archives

Re: iSCSI Domain Addition Fails
by Benny Zlotnik 23 Feb '20

23 Feb '20

anything in the vdsm or engine logs? On Sun, Feb 23, 2020 at 4:23 PM Robert Webb <rwebb(a)ropeguru.com> wrote: > > Also, I did do the “Login” to connect to the target without issue, from what I can tell. > > > > From: Robert Webb > Sent: Sunday, February 23, 2020 9:06 AM > To: users(a)ovirt.org > Subject: iSCSI Domain Addition Fails > > > > So I am messing around with FreeNAS and iSCSI. FreeNAS has a target configured, it is discoverable in oVirt, but then I click “OK” nothing happens. > > > > I have a name for the domain defined and have expanded the advanced features, but cannot find it anything showing an error. > > > > oVirt 4.3.8 > > _______________________________________________ > 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/FMAXFDMNHVGTM…

1 0

Re: iSCSI Domain Addition Fails
by Robert Webb 23 Feb '20

23 Feb '20

Also, I did do the "Login" to connect to the target without issue, from what I can tell. From: Robert Webb Sent: Sunday, February 23, 2020 9:06 AM To: users(a)ovirt.org Subject: iSCSI Domain Addition Fails So I am messing around with FreeNAS and iSCSI. FreeNAS has a target configured, it is discoverable in oVirt, but then I click "OK" nothing happens. I have a name for the domain defined and have expanded the advanced features, but cannot find it anything showing an error. oVirt 4.3.8

1 0

iSCSI Domain Addition Fails
by Robert Webb 23 Feb '20

23 Feb '20

So I am messing around with FreeNAS and iSCSI. FreeNAS has a target configured, it is discoverable in oVirt, but then I click "OK" nothing happens. I have a name for the domain defined and have expanded the advanced features, but cannot find it anything showing an error. oVirt 4.3.8

1 0

dashboard data empty
by Fabrizio 23 Feb '20

23 Feb '20

Hello everyone. I intalled 4 node with hosted engine, everything works fine exept the dashboard. it doesn't collect any data and is always empty of information. searching around I found out that the problem could be the dwh service, inside the log there is an error: ## log file 2020-02-19 17:46:14|ETL Service Started ovirtEngineDbDriverClass|org.postgresql.Driver ovirtEngineHistoryDbJdbcConnection|jdbc:postgresql://localhost:5432/ovirt_engine_history?sslfactory=org.postgresql.ssl.NonValidatingFactory hoursToKeepDaily|0 hoursToKeepHourly|720 ovirtEngineDbPassword|********************** runDeleteTime|3 ovirtEngineDbJdbcConnection|jdbc:postgresql://localhost:5432/engine?sslfactory=org.postgresql.ssl.NonValidatingFactory runInterleave|60 limitRows|limit 1000 ovirtEngineHistoryDbUser|ovirt_engine_history ovirtEngineDbUser|engine deleteIncrement|10 timeBetweenErrorEvents|300000 hoursToKeepSamples|24 deleteMultiplier|1000 lastErrorSent|2011-07-03 12:46:47.000000 etlVersion|4.3.8 dwhAggregationDebug|false dwhUuid|5c4ffc1b-928f-4d06-a40f-bb34ba11c7f2 ovirtEngineHistoryDbDriverClass|org.postgresql.Driver ovirtEngineHistoryDbPassword|********************** Exception in component tJDBCInput_2 org.postgresql.util.PSQLException: Bad value for type short : 201905 at org.postgresql.jdbc2.AbstractJdbc2ResultSet.getShort(AbstractJdbc2ResultSet.java:2098) at ovirt_engine_dwh.osenumupdate_4_3.OsEnumUpdate.tJDBCInput_2Process(OsEnumUpdate.java:2354) at ovirt_engine_dwh.osenumupdate_4_3.OsEnumUpdate.tRowGenerator_1Process(OsEnumUpdate.java:1921) at ovirt_engine_dwh.osenumupdate_4_3.OsEnumUpdate.tJDBCInput_4Process(OsEnumUpdate.java:1376) at ovirt_engine_dwh.osenumupdate_4_3.OsEnumUpdate.tJDBCConnection_1Process(OsEnumUpdate.java:873) at ovirt_engine_dwh.osenumupdate_4_3.OsEnumUpdate.tJDBCConnection_2Process(OsEnumUpdate.java:736) at ovirt_engine_dwh.osenumupdate_4_3.OsEnumUpdate.runJobInTOS(OsEnumUpdate.java:4396) at ovirt_engine_dwh.osenumupdate_4_3.OsEnumUpdate.runJob(OsEnumUpdate.java:4099) at ovirt_engine_dwh.samplerunjobs_4_3.SampleRunJobs.tRunJob_4Process(SampleRunJobs.java:947) at ovirt_engine_dwh.samplerunjobs_4_3.SampleRunJobs.tJDBCConnection_2Process(SampleRunJobs.java:767) at ovirt_engine_dwh.samplerunjobs_4_3.SampleRunJobs.tJDBCConnection_1Process(SampleRunJobs.java:642) at ovirt_engine_dwh.samplerunjobs_4_3.SampleRunJobs$2.run(SampleRunJobs.java:2683) ## SERVICE STATUS ● ovirt-engine-dwhd.service - oVirt Engine Data Warehouse Loaded: loaded (/usr/lib/systemd/system/ovirt-engine-dwhd.service; enabled; vendor preset: disabled) Active: active (running) since Wed 2020-02-19 17:46:14 CET; 16h ago Main PID: 6425 (ovirt-engine-dw) CGroup: /system.slice/ovirt-engine-dwhd.service ├─6425 /usr/bin/python /usr/share/ovirt-engine-dwh/services/ovirt-engine-dwhd/ovirt-engine-dwhd.py --redirect-output --systemd=notify start └─6512 ovirt-engine-dwhd -Dorg.ovirt.engine.dwh.settings=/tmp/tmparNn_x/settings.properties -Xms1g -Xmx1g -classpath /usr/share/ovirt-engine-dwh/lib/*::/usr/share/java/dom4j.jar:/usr/share/java/apache-commons-collections.jar:/usr/share/java/postgresql-jdbc.jar ovirt_engine_dwh.historyetl_4_3.HistoryETL --context=Default Feb 19 17:46:14 engine.ovirt.local systemd[1]: Starting oVirt Engine Data Warehouse... Feb 19 17:46:14 engine.ovirt.local systemd[1]: Started oVirt Engine Data Warehouse.

4 4

metrics-store installation
by Christoph Köhler 23 Feb '20

23 Feb '20

Hello! I have installed metrics store along this documentation: https://ovirt.org/documentation/metrics-install-guide/Installing_Metrics_St… Everything went fine without errors, so I have now the login page in my browser. The Problem is that the credentials for login seems to be not taken over. The user should be 'admin' and the password is given at the beginning in secure_vars.yaml. Does anyone have an idea what to do now? Greetings! Chris

2 1

paused vm's will not resume
by eevans＠digitaldatatechs.com 23 Feb '20

23 Feb '20

I have 2 vm's, which are the most important in my world, that paused and will not resume. I have googled this to death but no solution. It stated a lack of space but none of the drives on my hosts are using more than 30% or there space and these 2 have ran on kvm host for several years and always had at least 50% free space. I like ovirt and want to use it but I cannot tolerate the down time. If I cannot get this resolved, I'm going back to kvm hosts. I am pulling my hair out here. If anyone can help with this issue, please let me know.

6 10

Hugepages and running out of memory
by klaasdemter＠gmail.com 22 Feb '20

22 Feb '20

Hi, this e-mail is meant to caution people using hugepages and mixing those VMs with non-hugepages VMs on the same hypervisors. I ran into major trouble, the hypervisors ran out of memory because the VM scheduling disregards the hugepages in it's calculations. So if you have hugepages and non-hugepages VMs better check the memory commited on a hypervisor manually :) https://bugzilla.redhat.com/show_bug.cgi?id=1804037 https://bugzilla.redhat.com/show_bug.cgi?id=1804046 As for workarounds: so far it seems the only viable solution is splitting hugepages/nonhugepages VMs with affinity groups but at least for me that means wasting a lot of resources. Greetings Klaas

1 0

main channel: failed to connect HTTP proxy connection not allowed
by Jorick Astrego 21 Feb '20

21 Feb '20

Hi, Having a spice console issue on our new 4.3.8 cluster. The console stays blank and with the cli and debug on, I get the following error "main channel: failed to connect HTTP proxy connection not allowed" We have a userportal through haproxy so this is configured in ovirt engine engine-config -g SpiceProxyDefault SpiceProxyDefault: http://userportal.*.*:****/ version: general But the same setting works fine on our 4.2 cluster. I can telnet to the ports on the 4.3.8 hosts without issue. Non working console on newer cluster: remote-viewer -v --debug console.vv (remote-viewer:29267): virt-viewer-DEBUG: 16:24:24.697: Opening display to console.vv (remote-viewer:29267): virt-viewer-DEBUG: 16:24:24.700: Guest (null) has a spice display Guest (null) has a spice display (remote-viewer:29267): virt-viewer-DEBUG: 16:24:24.789: Spice foreign menu updated (remote-viewer:29267): virt-viewer-DEBUG: 16:24:24.790: After open connection callback fd=-1 (remote-viewer:29267): virt-viewer-DEBUG: 16:24:24.790: Opening connection to display at console.vv Opening connection to display at console.vv (remote-viewer:29267): virt-viewer-DEBUG: 16:24:24.791: fullscreen display 0: 0 (remote-viewer:29267): virt-viewer-DEBUG: 16:24:24.791: app is not in full screen (remote-viewer:29267): virt-viewer-DEBUG: 16:24:24.792: New spice channel 0x55704bf70d40 SpiceMainChannel 0 (remote-viewer:29267): virt-viewer-DEBUG: 16:24:24.793: notebook show status 0x55704b820280 (remote-viewer:29267): virt-viewer-DEBUG: 16:24:24.969: main channel: failed to connect HTTP proxy connection not allowed (remote-viewer:29267): virt-viewer-DEBUG: 16:24:24.969: Destroy SPICE channel SpiceMainChannel 0 (remote-viewer:29267): virt-viewer-DEBUG: 16:24:24.969: zap main channel (remote-viewer:29267): virt-viewer-WARNING **: 16:24:24.969: Channel error: HTTP proxy connection not allowed Working console on older cluster: remote-viewer -v --debug console.vv (remote-viewer:29334): virt-viewer-DEBUG: 16:25:59.111: Opening display to console.vv (remote-viewer:29334): virt-viewer-DEBUG: 16:25:59.111: Guest (null) has a spice display Guest (null) has a spice display (remote-viewer:29334): virt-viewer-DEBUG: 16:25:59.209: Spice foreign menu updated (remote-viewer:29334): virt-viewer-DEBUG: 16:25:59.209: After open connection callback fd=-1 (remote-viewer:29334): virt-viewer-DEBUG: 16:25:59.209: Opening connection to display at console.vv Opening connection to display at console.vv (remote-viewer:29334): virt-viewer-DEBUG: 16:25:59.211: fullscreen display 0: 0 (remote-viewer:29334): virt-viewer-DEBUG: 16:25:59.211: app is not in full screen (remote-viewer:29334): virt-viewer-DEBUG: 16:25:59.212: New spice channel 0x556a03f7e820 SpiceMainChannel 0 (remote-viewer:29334): virt-viewer-DEBUG: 16:25:59.212: notebook show status 0x556a03c7a280 (remote-viewer:29334): virt-viewer-DEBUG: 16:25:59.397: main channel: opened (remote-viewer:29334): virt-viewer-DEBUG: 16:25:59.397: notebook show status 0x556a03c7a280 (remote-viewer:29334): virt-viewer-DEBUG: 16:25:59.404: virt_viewer_app_set_uuid_string: UUID changed to a2d64ffe-7583-45b6-92f3-87661039388c (remote-viewer:29334): virt-viewer-DEBUG: 16:25:59.404: app is not in full screen (remote-viewer:29334): virt-viewer-DEBUG: 16:25:59.502: app is not in full screen (remote-viewer:29334): virt-viewer-DEBUG: 16:25:59.514: New spice channel 0x556a043bb660 SpiceDisplayChannel 0 (remote-viewer:29334): virt-viewer-DEBUG: 16:25:59.514: New spice channel 0x556a0422b570 SpiceCursorChannel 0 (remote-viewer:29334): virt-viewer-DEBUG: 16:25:59.515: New spice channel 0x556a0422c000 SpiceInputsChannel 0 (remote-viewer:29334): virt-viewer-DEBUG: 16:25:59.515: new inputs channel (remote-viewer:29334): virt-viewer-DEBUG: 16:25:59.661: creating spice display (#:0) (remote-viewer:29334): virt-viewer-DEBUG: 16:25:59.661: Insert display 0 0x556a03ca29e0 (remote-viewer:29334): virt-viewer-DEBUG: 16:25:59.699: creating spice display (#:1) (remote-viewer:29334): virt-viewer-DEBUG: 16:25:59.699: Insert display 1 0x556a03ca2830 (remote-viewer:29334): virt-viewer-DEBUG: 16:25:59.699: creating spice display (#:2) (remote-viewer:29334): virt-viewer-DEBUG: 16:25:59.700: Insert display 2 0x556a03ca2680 (remote-viewer:29334): virt-viewer-DEBUG: 16:25:59.700: creating spice display (#:3) (remote-viewer:29334): virt-viewer-DEBUG: 16:25:59.700: Insert display 3 0x556a03ca24d0 (remote-viewer:29334): virt-viewer-DEBUG: 16:25:59.701: Found a window without a display, reusing for display #0 (remote-viewer:29334): virt-viewer-DEBUG: 16:25:59.701: notebook show display 0x556a03c7a280 (remote-viewer:29334): virt-viewer-DEBUG: 16:26:00.074: Allocated 1024x768 (remote-viewer:29334): virt-viewer-DEBUG: 16:26:00.074: Child allocate 1024x768 (remote-viewer:29334): virt-viewer-DEBUG: 16:26:04.846: Allocated 1024x768 (remote-viewer:29334): virt-viewer-DEBUG: 16:26:04.846: Child allocate 1024x768 Met vriendelijke groet, With kind regards, Jorick Astrego Netbulae Virtualization Experts ---------------- Tel: 053 20 30 270 info(a)netbulae.eu Staalsteden 4-3A KvK 08198180 Fax: 053 20 30 271 www.netbulae.eu 7547 TA Enschede BTW NL821234584B01 ----------------

1 1

[ANN] oVirt 4.3.9 Second Release Candidate is now available for testing
by Lev Veyde 21 Feb '20

21 Feb '20

The oVirt Project is pleased to announce the availability of the oVirt 4.3.9 Second Release Candidate for testing, as of February 20th, 2020. This update is a release candidate of the ninth 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.7 or later (but <8) * CentOS Linux (or similar) 7.7 or later (but <8) This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 7.7 or later (but <8) * CentOS Linux (or similar) 7.7 or later (but <8) * oVirt Node 4.3 (available for x86_64 only) has been built consuming CentOS 7.7 Release See the release notes [1] for known issues, new features and bugs fixed. Notes: - oVirt Appliance is already available - oVirt Node is already available Additional Resources: * Read more about the oVirt 4.3.9 release highlights: http://www.ovirt.org/release/4.3.9/ * 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.9/ [2] http://resources.ovirt.org/pub/ovirt-4.3-pre/iso/ -- Lev Veyde Senior Software Engineer, RHCE | RHCVA | MCITP Red Hat Israel <https://www.redhat.com> lev(a)redhat.com | lveyde(a)redhat.com <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

3 2

Understanding dashboard memory data
by nux＠li.nux.ro 21 Feb '20

21 Feb '20

Hello, I'm having to deal with an oVirt installation, once I log in the dashboard says: Memory: "1.2 Available of 4.5 TiB" and "Virtual resources - Committed: 113%, Allocated: 114%". So, clearly there is RAM available, but what's with the committed and allocated numbers? Regards

1 0