- Users - oVirt List Archives

oVirt 4.4 new VM cannot be created in the datacenter other than Default?
by bjkelley＠us.ibm.com 16 May '20

16 May '20

So after setup of new DC and Storage and Host at 4.3 as the CPU technology is lower than the Hosted-Engine machine. when I try and create a VM the only DC choice is the Default one. Is this Normal or issue with 4.4? Thanks Bryan

2 1

Bridge not forwarding frames on node.
by s.danzi 15 May '20

15 May '20

Hi to all!I'm having an issue with networks bridges on ovirt node.It's look like this bug: https://bugzilla.redhat.com/show_bug.cgi?id=1279161On VM I have a bridge between a tap device and network interface. On node side the interface is bridged with bond0 vlan 128 (bond0.128 lacp).When I ping an host on the other side of tap device I can see this:Arp request goes from my lan to the tap device on vm. Arp reply return from tap vm and bridge forward this to vm networks interface. Using tcpdump on vm interface on node I can see the arp reply, using tcpdump on bond0.128 or on bridge I can't see the arp reply. Arp request is forwarded from bond0.128 to vm net but arp reply isn't forwarded from vm net to bond0.128. Very strange.....

5 11

Glance disk images credentials oVirt4.4
by bjkelley＠us.ibm.com 15 May '20

15 May '20

So if I use this to build a VM and I setup Cloud_init to set user id and passwords. should I not be able to login to the VM from Console? Bryan

2 1

[ANN] oVirt 4.4.0 Second Release Candidate is now available for testing
by Lev Veyde 15 May '20

15 May '20

oVirt 4.4.0 Second Release Candidate is now available for testing The oVirt Project is excited to announce the availability of oVirt 4.4.0 Second Release Candidate for testing, as of May 15th, 2020 This release unleashes an altogether more powerful and flexible open source virtualization solution that encompasses hundreds of individual changes and a wide range of enhancements across the engine, storage, network, user interface, and analytics on top of oVirt 4.3. Important notes before you try it Please note this is a pre-release build. The oVirt Project makes no guarantees as to its suitability or usefulness. This pre-release must not to be used in production. Some of the features included in oVirt 4.4.0 Release Candidate require content that will be available in CentOS Linux 8.2 but can’t be tested on RHEL 8.2 beta yet due to some incompatibility in openvswitch package shipped in CentOS Virt SIG which requires to rebuild openvswitch on top of CentOS 8.2. Installation instructions For the engine: either use appliance or: - Install CentOS Linux 8 minimal from http://centos.mirror.garr.it/centos/8.1.1911/isos/x86_64/CentOS-8.1.1911-x8… - dnf install https://resources.ovirt.org/pub/yum-repo/ovirt-release44-pre.rpm - dnf update (reboot if needed) - dnf module enable -y javapackages-tools pki-deps postgresql:12 389-ds - dnf install ovirt-engine - engine-setup For the nodes: Either use oVirt Node ISO or: - Install CentOS Linux 8 from http://centos.mirror.garr.it/centos/8.1.1911/isos/x86_64/CentOS-8.1.1911-x8… ; select minimal installation - dnf install https://resources.ovirt.org/pub/yum-repo/ovirt-release44-pre.rpm - dnf update (reboot if needed) - Attach the host to engine and let it be deployed. What’s new in oVirt 4.4.0? - Hypervisors based on CentOS Linux 8 (rebuilt from award winning RHEL8), for both oVirt Node and standalone CentOS Linux hosts - Easier network management and configuration flexibility with NetworkManager - VMs based on a more modern Q35 chipset with legacy seabios and UEFI firmware - Support for direct passthrough of local host disks to VMs - Live migration improvements for High Performance guests. - New Windows Guest tools installer based on WiX framework now moved to VirtioWin project - Dropped support for cluster level prior to 4.2 - Dropped SDK3 support - 4K disks support - Exporting a VM to a data domain - Editing of floating disks - Integrating ansible-runner into engine, which allows a more detailed monitoring of playbooks executed from engine - Adding/reinstalling hosts are now completely based on Ansible - The OpenStack Neutron Agent cannot be configured by oVirt anymore, it should be configured by TripleO instead This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 8.1 or newer * CentOS Linux (or similar) 8.1 or newer This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 8.1 or newer * CentOS Linux (or similar) 8.1 or newer * oVirt Node 4.4 based on CentOS Linux 8.1 (available for x86_64 only) See the release notes [1] for installation instructions and a list of new features and bugs fixed. If you manage more than one oVirt instance, OKD or RDO we also recommend to try ManageIQ <http://manageiq.org/>. In such a case, please be sure to take the qc2 image and not the ova image. Notes: - oVirt Appliance is already available for CentOS Linux 8 - oVirt Node NG is already available for CentOS Linux 8 Additional Resources: * Read more about the oVirt 4.4.0 release highlights: http://www.ovirt.org/release/4.4.0/ * 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.4.0/ [2] http://resources.ovirt.org/pub/ovirt-4.4-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>

1 0

POWER9 Support: VDSM requiring LVM2 package that's missing
by Vinícius Ferrão 15 May '20

15 May '20

Hello, I would like to know if this is a bug or not, if yes I will submit to Red Hat. I’m trying to add a ppc64le (POWER9) machine to the hosts pool, but there’s missing dependencies on VDSM: --> Processing Dependency: lvm2 >= 7:2.02.186-7.el7_8.1 for package: vdsm-4.30.44-1.el7ev.ppc64le --> Finished Dependency Resolution Error: Package: vdsm-4.30.44-1.el7ev.ppc64le (rhel-7-server-rhv-4-mgmt-agent-for-power-9-rpms) Requires: lvm2 >= 7:2.02.186-7.el7_8.1 Available: 7:lvm2-2.02.171-8.el7.ppc64le (rhel-7-for-power-9-rpms) lvm2 = 7:2.02.171-8.el7 Available: 7:lvm2-2.02.177-4.el7.ppc64le (rhel-7-for-power-9-rpms) lvm2 = 7:2.02.177-4.el7 Available: 7:lvm2-2.02.180-8.el7.ppc64le (rhel-7-for-power-9-rpms) lvm2 = 7:2.02.180-8.el7 Available: 7:lvm2-2.02.180-10.el7_6.1.ppc64le (rhel-7-for-power-9-rpms) lvm2 = 7:2.02.180-10.el7_6.1 Available: 7:lvm2-2.02.180-10.el7_6.2.ppc64le (rhel-7-for-power-9-rpms) lvm2 = 7:2.02.180-10.el7_6.2 Available: 7:lvm2-2.02.180-10.el7_6.3.ppc64le (rhel-7-for-power-9-rpms) lvm2 = 7:2.02.180-10.el7_6.3 Available: 7:lvm2-2.02.180-10.el7_6.7.ppc64le (rhel-7-for-power-9-rpms) lvm2 = 7:2.02.180-10.el7_6.7 Available: 7:lvm2-2.02.180-10.el7_6.8.ppc64le (rhel-7-for-power-9-rpms) lvm2 = 7:2.02.180-10.el7_6.8 Installing: 7:lvm2-2.02.180-10.el7_6.9.ppc64le (rhel-7-for-power-9-rpms) lvm2 = 7:2.02.180-10.el7_6.9 Thanks,

2 3

[ANN] oVirt 4.3.10 Fourth Release Candidate is now available for testing
by Lev Veyde 14 May '20

14 May '20

The oVirt Project is pleased to announce the availability of oVirt 4.3.10 Fourth Release Candidate for testing as of May 14th, 2020. This update is the tenth in a series of stabilization updates to the 4.3 series. 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) 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.10 release highlights: http://www.ovirt.org/release/4.3.10/ * 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.10/ [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>

1 0

Migrate hosted engine to standalone host
by Anton Louw 14 May '20

14 May '20

Hi All, So I have been playing around a bit, and I would just like some recommendations. I moved my HE from an oVirt node to my VMware environment, basically running as a standalone host now. Is there anything I should look out for? I can see there is a problem when configuring the HE after the move, where it says that global maintenance is not enabled. How will this work if the hosted engine is not sitting on a oVirt node anymore? Any feedback\suggestions will be greatly appreciated. Thanks Anton Louw Cloud Engineer: Storage and Virtualization ______________________________________ D: 087 805 1572 | M: N/A A: Rutherford Estate, 1 Scott Street, Waverley, Johannesburg anton.louw(a)voxtelecom.co.za www.vox.co.za

1 0

Unable to connect to cockpit
by Parth Dhanjal 14 May '20

14 May '20

Hey! I have a remote machine on which I have installed RHVH4.4 I'm unable to access the cockpit-plugin. journalctl -u cockpit returns this error cockpit-tls: gnutls_handshake failed: A TLS fatal alert has been received. Screenshot while trying to reach cockpit through the browser attached. Is anyone else facing this issue as well? And does anyone has a solution/workaround to this?

6 7

Networking documentation
by s.danzi 14 May '20

14 May '20

Hello!In this page https://www.ovirt.org/documentation/admin-guide/chap-Logical_Networks.html there are a link to https://www.ovirt.org/documentation/admin-guide/Marking_vNIC_as_Passthrough that does not work. Does anyone have the correct link?

2 1

Can't add freshly installed node.. host has no default route
by Giorgio Biacchi 13 May '20

13 May '20

Hi list, I've spent a couple of days trying to understand why this was happening... For the installation I have a well tested installation server with a custom kickstart file to setup ssh keys and custom hooks for infiniband and I'm installing Ovirt Node 4.3.9 via pxe, this is particularly useful when I have to install a bunch of blades at once.. In the past I had no issues and all was working like a charm until now when some hardware failed and I had to replace it. As expected I have no issues in the node installation process.. the troubles begins when I try to add the node, installation fails and in the UI I have an exclamation mark with the message "Host has no default route." but I can ping and do ssh to the host from the manager.. the problem is somewhere else in the communication between the engine and vdsmd preventing the engine to refresh the host capabilities. So from the engine I tried: [root@manager ~]# openssl s_client -connect 172.20.22.78:54321 CONNECTED(00000003) --- Certificate chain 0 s:/CN=cn128.lagrange.di.unimi.it/O=VDSM Certificate i:/CN=VDSM Certificate Authority 1 s:/CN=VDSM Certificate Authority i:/CN=VDSM Certificate Authority --- The host has still the self signed vdsm certificate.. and on the host in vdsm.log I find: 2020-05-11 09:52:25,433+0000 ERROR (Reactor thread) [ProtocolDetector.SSLHandshakeDispatcher] ssl handshake: SSLError, address: ::ffff:159.149.129.220 (sslutils:264) So I tried to enroll the certificate from the UI and from the events tab I sow the enrolling was successful but: [root@manager ~]# openssl s_client -connect 172.20.22.78:54321 140084336994192:error:140790E5:SSL routines:ssl23_write:ssl handshake failure:s23_lib.c:177: CONNECTED(00000003) --- no peer certificate available --- there's still some issue with the certificates.. so on the host again: [root@cn128 vdsm]# find /etc/pki/vdsm/ -type f -cmin -10| xargs ls -l -rw-------. 1 root kvm 1424 May 11 09:56 /etc/pki/vdsm/certs/cacert.pem -rw-------. 1 root kvm 5108 May 11 09:57 /etc/pki/vdsm/certs/vdsmcert.pem -r--r-----. 1 root kvm 1704 May 11 09:56 /etc/pki/vdsm/keys/vdsmkey.pem -rw-r--r--. 1 root root 1424 May 11 09:57 /etc/pki/vdsm/libvirt-spice/ca-cert.pem -rw-r--r--. 1 root root 5108 May 11 09:57 /etc/pki/vdsm/libvirt-spice/server-cert.pem -r--r-----. 1 root root 1704 May 11 09:56 /etc/pki/vdsm/libvirt-spice/server-key.pem It seems that cacert.pem and vdsmcert.pem have wrong permissions.. let's try to fix it.. [root@cn128 vdsm]# chown 36:36 /etc/pki/vdsm/certs/cacert.pem /etc/pki/vdsm/certs/vdsmcert.pem And now: [root@manager ~]# openssl s_client -connect 172.20.22.78:54321| less CONNECTED(00000003) --- Certificate chain 0 s:/O=lagrange.di.unimi.it/CN=172.20.22.78 i:/C=US/O=lagrange.di.unimi.it/CN=cn305.lagrange.di.unimi.it.35941 1 s:/C=US/O=lagrange.di.unimi.it/CN=cn305.lagrange.di.unimi.it.35941 i:/C=US/O=lagrange.di.unimi.it/CN=cn305.lagrange.di.unimi.it.35941 --- Now I can finally refresh the host capabilities and setup the host networks.. In attachment all the relevant logs, I don't know if I've found some bug.. this is the first time i had so many troubles adding a new host.. so I decided to share my experience with the list.. Cheers -- gb PGP Key: http://pgp.mit.edu/ Primary key fingerprint: C510 0765 943E EBED A4F2 69D3 16CC DC90 B9CB 0F34

5 12