- Users - oVirt List Archives

Graphics performance and Windows VM
by Ciro Iriarte 26 Jun '19

26 Jun '19

Hello!, I'm wondering what would be a good fit for decent graphics performance on Windows 10/2016/2019 + oVirt/KVM. Is there some kind of offloading with SPICE?, should I use RDP instead?, will vGPU backed by Nvidia cards help somehow?. The idea is to build a VDI environment for Windows VM, probably using OpenThinClient or a custom Linux image at the endpoint. The clients will use office suites, Java IDE, AutoCAD and Sketchup. Comments? Regards, -- CI.- --

2 2

[ANN] oVirt 4.3.5 Third Release Candidate is now available for testing
by Sandro Bonazzola 26 Jun '19

26 Jun '19

The oVirt Project is pleased to announce the availability of the oVirt 4.3.5 Third Release Candidate for testing, as of June 26th, 2019. While testing this release candidate please consider deeper testing on gluster upgrade since with this release we are switching from Gluster 5 to Gluster 6. 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 has not been updated due to a regression in the tooling we use for building it.[3] - 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/ [3] https://bugzilla.redhat.com/show_bug.cgi?id=1724076 -- 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

Issues when Creating a Gluster Brick with Cache
by Robert Crawford 26 Jun '19

26 Jun '19

Hey Everyone, When in the server manager and creating a brick from the storage device the brick will fail whenever i attach a cache device to it. I'm not really sure why? It just says unknown.

3 7

HE on single oVirt node
by Mike Davis 26 Jun '19

26 Jun '19

I installed oVirt node for oVirt v4.3.4 on a single server (default partitioning). I know a single node is not best practice, but fits our current need. Now, I am trying to deploy the hosted engine, but getting the error "Device /dev/sdb not found" (full output below). /dev/sdb does not exist. Changing to /dev/sda fails (as I would expect) with "Creating physical volume '/dev/sda' failed". There is only one logical disk on this server (RAID), which is /dev/sda. The process does not seem correct to me. Why would the wizard try to build gluster volumes on bare partitions rather than in a file system like root? What do we need to do to deploy the HE? I used Cockpit and "Hyperconverged : Configure Gluster storage and oVirt hosted engine". Since it is a single node, I selected "Run Gluster Wizard For Single Node". Host1 set to the IP address of the eno1 Ethernet interface (10.0.0.11) No Packages, Update Hosts Volumes left at defaults (engine, data, and vmstore) Bricks left at defaults - (Raid 6 / 256 / 12) - Host 10.0.0.11 - device name /dev/sdb (all LVs) - engine 100GB, data 500GB, vmstore 500GB Output after "Deployment failed": PLAY [Setup backend] *********************************************************** TASK [Gathering Facts] ********************************************************* ok: [10.0.0.11] TASK [gluster.infra/roles/firewall_config : Start firewalld if not already started] *** ok: [10.0.0.11] TASK [gluster.infra/roles/firewall_config : check if required variables are set] *** skipping: [10.0.0.11] TASK [gluster.infra/roles/firewall_config : Open/Close firewalld ports] ******** ok: [10.0.0.11] => (item=2049/tcp) ok: [10.0.0.11] => (item=54321/tcp) ok: [10.0.0.11] => (item=5900/tcp) ok: [10.0.0.11] => (item=5900-6923/tcp) ok: [10.0.0.11] => (item=5666/tcp) ok: [10.0.0.11] => (item=16514/tcp) TASK [gluster.infra/roles/firewall_config : Add/Delete services to firewalld rules] *** ok: [10.0.0.11] => (item=glusterfs) TASK [gluster.infra/roles/backend_setup : Gather facts to determine the OS distribution] *** ok: [10.0.0.11] TASK [gluster.infra/roles/backend_setup : Change to Install lvm tools for debian systems.] *** skipping: [10.0.0.11] TASK [gluster.infra/roles/backend_setup : Change to Install lvm tools for RHEL systems.] *** ok: [10.0.0.11] TASK [gluster.infra/roles/backend_setup : Install python-yaml package for Debian systems] *** skipping: [10.0.0.11] TASK [gluster.infra/roles/backend_setup : Initialize vdo_devs array] *********** ok: [10.0.0.11] TASK [gluster.infra/roles/backend_setup : Record VDO devices (if any)] ********* skipping: [10.0.0.11] => (item={u'vgname': u'gluster_vg_sdb', u'pvname': u'/dev/sdb'}) TASK [gluster.infra/roles/backend_setup : Enable and start vdo service] ******** skipping: [10.0.0.11] TASK [gluster.infra/roles/backend_setup : Create VDO with specified size] ****** skipping: [10.0.0.11] TASK [gluster.infra/roles/backend_setup : Check if valid disktype is provided] *** skipping: [10.0.0.11] TASK [gluster.infra/roles/backend_setup : Set PV data alignment for JBOD] ****** skipping: [10.0.0.11] TASK [gluster.infra/roles/backend_setup : Set PV data alignment for RAID] ****** ok: [10.0.0.11] TASK [gluster.infra/roles/backend_setup : Set VG physical extent size for RAID] *** ok: [10.0.0.11] TASK [gluster.infra/roles/backend_setup : Create volume groups] **************** failed: [10.0.0.11] (item={u'vgname': u'gluster_vg_sdb', u'pvname': u'/dev/sdb'}) => {"ansible_loop_var": "item", "changed": false, "item": {"pvname": "/dev/sdb", "vgname": "gluster_vg_sdb"}, "msg": "Device /dev/sdb not found."} NO MORE HOSTS LEFT ************************************************************* NO MORE HOSTS LEFT ************************************************************* PLAY RECAP ********************************************************************* 10.0.0.11 : ok=9 changed=0 unreachable=0 failed=1 skipped=8 rescued=0 ignored=0 ---

3 3

Re: Unable to log into Administration Portal
by Strahil 26 Jun '19

26 Jun '19

Zachary, The version lock is used by oVirt devs to prevent the system to update too far ahead of the oVirt level. Don't remove that next time. You should access the engine only by https://FQDN .IP should not be used. If you have some kind of snapshot (for example gluster) - you can consider reverting. Even consider restore from backup. I'm pretty sure that almost every failiure is recorded somewhere there ... (I am still new to advise location). Bet Regards, Strahil Nikolov On Jun 23, 2019 04:41, zachary.winter(a)witsconsult.com wrote: > > I suppose I just keep striking out on recent oVirt updates. Today (22 June 2019, all previous updates have been installed successfully) I saw that an update was available for my Enterprise Linux Host (main oVirt engine, CentOS 7 x64), and I attempted to update it. The update failed, which had never happened before. I logged in via SSH and saw that the updates had been halted due to "yum versionlock." I cleared versionlock and proceeded with the update, which appeared to work successfully. I rebooted the system, which came up a-ok. However, I can no longer reach the Administration Portal page. The browser only hangs. I see the following: > > - type in the IP address to the server and get the https://<ip address>/ovirt-engine/sso/oauth/authorize page, which tells me: > > "The FQDN used to access the system is not a valid engine FQDN. You must access the system using the engine FQDN or one of the engine alternate FQDNs. > Click here to continue." > > When I click the provided link, I get the same hanging behavior and it never loads the login page. > > - I was able to connect via Cockpit to https://<IP Address>:9090 and log in successfully as root after SSH'ing in and restarting the engine. There are no major issues displayed, and I was able to create a Diagnostic Report. Under Hostname > oVirt Machines, it will actually redirect me to the login page at https://fqdn/ovirt-engine/sso/login.html. The page will actually load after the redirect, but when I enter my admin@internal credentials it just hangs and spins. > > When I return to "Virtual Machines" in Cockpit, I have Host/Cluster/Templates/VDSM options, I see "oVirt login in progress" with a continually spinning circle, never actually able to authenticate. > > > In /var/log/ovirt-engine/ui.log, I see: > > 2019-06-22 19:08:02,533-04 ERROR [org.ovirt.engine.ui.frontend.server.gwt.OvirtRemoteLoggingService] (default task-4) [] Permutation name: C92E6928986552EDD0E1C99CDC0CC8AB > 2019-06-22 19:08:02,533-04 ERROR [org.ovirt.engine.ui.frontend.server.gwt.OvirtRemoteLoggingService] (default task-4) [] Uncaught exception: com.google.gwt.core.client.JavaScriptException: (TypeError) : Cannot read property 'kh' of null > at org.ovirt.engine.ui.uicommonweb.dataprovider.AsyncDataProvider.$lambda$4(AsyncDataProvider.java:387) > at org.ovirt.engine.ui.uicommonweb.dataprovider.AsyncDataProvider$lambda$4$Type.executed(AsyncDataProvider.java:387) > at org.ovirt.engine.ui.frontend.Frontend$2.$onFailure(Frontend.java:329) [frontend.jar:] > at org.ovirt.engine.ui.frontend.Frontend$2.onFailure(Frontend.java:329) [frontend.jar:] > at org.ovirt.engine.ui.frontend.communication.OperationProcessor$2.$onFailure(OperationProcessor.java:184) [frontend.jar:] > at org.ovirt.engine.ui.frontend.communication.OperationProcessor$2.onFailure(OperationProcessor.java:184) [frontend.jar:] > at org.ovirt.engine.ui.frontend.communication.GWTRPCCommunicationProvider.$handleMultipleQueriesFailure(GWTRPCCommunicationProvider.java:305) [frontend.jar:] > at org.ovirt.engine.ui.frontend.communication.GWTRPCCommunicationProvider$5$1.onFailure(GWTRPCCommunicationProvider.java:263) [frontend.jar:] > at com.google.gwt.user.client.rpc.impl.RequestCallbackAdapter.onResponseReceived(RequestCallbackAdapter.java:198) [gwt-servlet.jar:] > at com.google.gwt.http.client.Request.$fireOnResponseReceived(Request.java:233) [gwt-servlet.jar:] > at com.google.gwt.http.client.RequestBuilder$1.onReadyStateChange(RequestBuilder.java:409) [gwt-servlet.jar:] > at Unknown.eval(webadmin-0.js) > at com.google.gwt.core.client.impl.Impl.apply(Impl.java:236) [gwt-servlet.jar:] > at com.google.gwt.cor

2 1

Error when upgrading Node
by zachary.winter＠witsconsult.com 26 Jun '19

26 Jun '19

I am receiving the following error when attempting to update a Node manually that will not update through the administration portal: error: %pre(ovirt-node-ng-image-update-4.3.4-1.el7.noarch) scriptlet failed, exit status 1 Error in PREIN scriptlet in rpm package ovirt-node-ng-image-update-4.3.4-1.el7.noarch Software OS Version: RHEL - 7 - 6.1810.2.el7.centos OS Description: oVirt Node 4.3.3.1 Kernel Version: 3.10.0 - 957.10.1.el7.x86_64 KVM Version: 2.12.0 - 18.el7_6.3.1 LIBVIRT Version: libvirt-4.5.0-10.el7_6.6 VDSM Version: vdsm-4.30.13-1.el7 SPICE Version: 0.14.0 - 6.el7_6.1 GlusterFS Version: glusterfs-5.5-1.el7 CEPH Version: librbd1-10.2.5-4.el7 Open vSwitch Version: openvswitch-2.10.1-3.el7 Kernel Features: PTI: 1, IBRS: 0, RETP: 1, SSBD: 3 VNC Encryption: Enabled Any advice?

2 3

Error virNetTLSContextLoadCertFromFile after upgrade from oVirt 4.2 to 4.3.4
by Stefano Danzi 26 Jun '19

26 Jun '19

I've just upgraded my test environment from ovirt 4.2 to 4.3.4. System has only one host (Centos 7.6.1810) and run a self hosted engine. After upgrade I'm not able to run vdsmd (and so hosted engine....) Above the error in log: journalctl -xe -- L'unità libvirtd.service ha iniziato la fase di avvio. giu 24 18:09:17 ovirt01.hawai.lan libvirtd[8176]: 2019-06-24 16:09:17.006+0000: 8176: info : libvirt version: 4.5.0, package: 10.el7_6.12 (CentOS BuildSystem <http://bugs.centos.org>, 2019-06-20-15:01:15, x86-01.bsys. giu 24 18:09:17 ovirt01.hawai.lan libvirtd[8176]: 2019-06-24 16:09:17.006+0000: 8176: info : hostname: ovirt01.hawai.lan giu 24 18:09:17 ovirt01.hawai.lan libvirtd[8176]: 2019-06-24 16:09:17.006+0000: 8176: error : virNetTLSContextLoadCertFromFile:513 : Unable to import server certificate /etc/pki/vdsm/certs/vdsmcert.pem giu 24 18:09:17 ovirt01.hawai.lan systemd[1]: libvirtd.service: main process exited, code=exited, status=6/NOTCONFIGURED giu 24 18:09:17 ovirt01.hawai.lan systemd[1]: Failed to start Virtualization daemon. -- Subject: L'unità libvirtd.service è fallita

2 10

oVirt hyerconverged more than 12 node
by wodel youchi 26 Jun '19

26 Jun '19

Hi, Could someone explain the 12 nodes limitation when installing oVirt Hyperconverged? Our client has 16 nodes, can we use them on a hyperconverged installation? for example creating two clusters, one with 9 nodes and the second with 6 nodes. Regards.

2 2

Can ovirt implement FT functions
by xilazz＠126.com 26 Jun '19

26 Jun '19

Hi, now that ovirt has implemented the HA functionality of Shared storage and virtual machines, that's great. In our daily use and maintenance, we sometimes need some functions of virtual machine FT. At present, VMware can realize FT functions based on VSAN. Once upon a time there was a colo project, using qemu virtualization, https://wiki.qemu.org/Features/COLO, is now no one is updated. I would like to consult ovirt about the project plan of FT.

1 0

SAN re-attachment error
by Kim Kargaard 26 Jun '19

26 Jun '19

Hi, I am running into an issue with my SAN storage on ovirt 4.3 I had an issue with the engine and re-installed and when I try to activate the SAN storage and DC (once linked) again, I get this errors: VDSM node2 command HSMGetTaskStatusVDS failed: Cannot acquire host id: ('fb14e013-15f1-49b6-b129-210517aca0da', SanlockException(22, 'Sanlock lockspace add failure', 'Invalid argument')) Invalid status on Data Center Default. Setting status to Non Responsive. The nodes can still all see the SAN and the LUNs. I have tried restarting sanlock on the nodes, but the error persists. I have a vm with a disk on the SAN that I do not want to lose. Any thoughts? Kind regards Kim

1 0