- Users - oVirt List Archives

Using Ansible ovirt_vm
by Matthew.Stier＠fujitsu.com 15 Jan '21

15 Jan '21

Over this weekend, I need to shutdown and restart 1500 VMs while I do work. Modifying an Ansible playbook I have, to accomplish that, seems easy enough. Last weekend I used the web gui and edited each Virtual Machine and changed the 'cluster' to the one I wanted to assign it too. Now I would like to automate this with Ansible. In between shutting them down and starting them up, I need to change the cluster registration of quite a few of the hosts, and I have concerns on how to do that. The Ansible ovirt_vm documentation on this is a bit fuzzy. I'm assuming it for assigning the cluster, but in some examples it appears to be used as a filter. Which changes the meaning. Is it "start the VM in this cluster" or "start this VM if it is in this cluster". The playbook I'm working from is straight forward and has three tasks. First, an ovirt_auth task to log into the SHE. Second, an ovirt_vm task which loops though the group of virtualmachines, defined in an 'ini' file. Third, an ovirt_auth task to logout from the SHE. For stopping, I assume I specify a name, and state to 'stopped' and that should initiate the shutdown. For starting, I assume I should set the state to 'running'. For changing the cluster a vm is assigned to, do I simply need to use the 'cluster' parameter with a value of new cluster? Are there other actions that need to be taken? The VM need to be un and re-registered for the change to take effect? I'd like to make the cluster change individual playbook, but could it be added to the start or stop playbook. (ie: stop and change cluster, start on new cluster) Waiting for the wisdom of the community.

1 0

Re: VM console does not work with new cluster.
by tommy 15 Jan '21

15 Jan '21

Cannot connect even closed firewalld service on hosts. -----Original Message----- From: users-bounces(a)ovirt.org <users-bounces(a)ovirt.org> On Behalf Of Matthew.Stier(a)fujitsu.com Sent: Thursday, January 14, 2021 11:20 PM To: Strahil Nikolov <hunter86_bg(a)yahoo.com>; tommy <sz_cuitao(a)163.com>; eevans(a)digitaldatatechs.com Cc: users(a)ovirt.org Subject: [ovirt-users] Re: VM console does not work with new cluster. Listed in firewalld service 'vdsm' -----Original Message----- From: Strahil Nikolov <hunter86_bg(a)yahoo.com> Sent: Wednesday, January 13, 2021 10:52 PM To: tommy <sz_cuitao(a)163.com>; Stier, Matthew <Matthew.Stier(a)fujitsu.com>; eevans(a)digitaldatatechs.com Cc: users(a)ovirt.org Subject: Re: [ovirt-users] Re: VM console does not work with new cluster. I don't see the VNC ports at all (5900 and above). Here is my firewall on oVirt 4.3.10: public (active) target: default icmp-block-inversion: no interfaces: enp4s0 enp5s0f0 enp5s0f1 enp7s5f0 enp7s5f1 enp7s6f0 enp7s6f1 ovirtmgmt team0 sources: services: cockpit ctdb dhcpv6-client glusterfs libvirt-tls nfs nfs3 nrpe ovirt-imageio ovirt-storageconsole ovirt-vmconsole rpc-bind samba snmp ssh vdsm ports: 111/tcp 2049/tcp 54321/tcp 5900/tcp 5900-6923/tcp 5666/tcp 16514/tcp 54322/tcp 22/tcp 6081/udp 8080/tcp 963/udp 965/tcp protocols: masquerade: no forward-ports: source-ports: icmp-blocks: rich rules: Best Regards, Strahil Nikolov В 05:25 +0800 на 13.01.2021 (ср), tommy написа: > I encountered the question too. > > The follow file is the connect file for vm that can connect using > remote viewer: > > [virt-viewer] > type=vnc > host=192.168.10.41 > port=5900 > password=rdXQA4zr/UAY > # Password is valid for 120 seconds. > delete-this-file=1 > fullscreen=0 > title=HostedEngine:%d > toggle-fullscreen=shift+f11 > release-cursor=shift+f12 > secure-attention=ctrl+alt+end > versions=rhev-win64:2.0-160;rhev-win32:2.0-160;rhel8:7.0-3;rhel7:2.0- > 6;rhel6:99.0-1 > newer-version-url= > http://www.ovirt.org/documentation/admin-guide/virt/console-client-res > ources > > [ovirt] > host=ooeng.tltd.com:443 > vm-guid=76f99df2-ef79-45d9-8eea-a32b168f9ef3 > sso-token=4Up7TfLLBjSuQgPkQvRz3D- > fUGZWZg4ynApe2Y7ylkARCFwQWsfEr3dU8FjlK8esctm3Im4tz80mE1DjrNT3XQ > admin=1 > ca=-----BEGIN CERTIFICATE----- > \nMIIDqDCCApCgAwIBAgICEAAwDQYJKoZIhvcNAQELBQAwPzELMAkGA1UEBhMCVVMxETA > PBgNVBAoM\nCHRsdGQuY29tMR0wGwYDVQQDDBRvb2VuZy50bHRkLmNvbS4xNzczMDAeFw > 0yMTAxMTAxNjE1NDda\nFw0zMTAxMDkxNjE1NDdaMD8xCzAJBgNVBAYTAlVTMREwDwYDV > QQKDAh0bHRkLmNvbTEdMBsGA1UE\nAwwUb29lbmcudGx0ZC5jb20uMTc3MzAwggEiMA0G > CSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCg\nYT9S7hWiXQUzAqFQKbg2nMjwyHDmb/J > mKeJAUVZqNKRg1q80IpWyoM12Zw0nX1eTwMnVY/JtJON4\n13PoEC3So8nniGt+wtHr44 > ysvCWfU0SBk/ZPnKmQ58o5MlSkidHwySChXfVPYLPWeUJ1JUrujna/\nCbi5bmmjx2pqw > LrZXX8Q5NO2MRKOTs0Dtg16Q6z+a3cXLIffVJfhPGS3AkIh6nznNaDeH5gFZZbd\nr3DK > E4xrpdw/7y6CgjmHe4vwGxOIyE+gElZ/lVtqznLMwohz7wgtgsDA36277mujNyMjMbrSF > heu\n5WfbIa9VVSZWEkISVq6eswLOQ1IRaFyJsFN9AgMBAAGjga0wgaowHQYDVR0OBBYE > FDYEqJOMqN8+\nQhCP7DAkqF3RZMFdMGgGA1UdIwRhMF+AFDYEqJOMqN8+QhCP7DAkqF3 > RZMFdoUOkQTA/MQswCQYD\nVQQGEwJVUzERMA8GA1UECgwIdGx0ZC5jb20xHTAbBgNVBA > MMFG9vZW5nLnRsdGQuY29tLjE3NzMw\nggIQADAPBgNVHRMBAf8EBTADAQH/MA4GA1UdD > wEB/wQEAwIBBjANBgkqhkiG9w0BAQsFAAOCAQEA\nAKs0/yQWkoOkGcL0PjF9ijekdMmj > rLZGyh5uLot7h9s/Y2+5l9n9IzEjjx9chi8xwt6MBsR6/nBT\n/skcciv2veM22HwNGjd > rHvhfbZFnZsGe2TU60kGzKjlv1En/8Pgd2aWBcwTlr+SErBXkehNEJRj9\n1saycPgwS4 > pHS04c2+4JMhpe+hxgsO2+N/SYkP95Lf7ZQynVsN/SKx7X3cWybErCqoB7G7McqaHN\nV > Ww+QNXo5islWUXqeDc3RcnW3kq0XUEzEtp6hoeRcLKO99QrAW31zqU/QY+EeZ6Fax1O/j > rDafZn\npTs0KJFNgeVnUhKanB29ONy+tmnUmTAgPMaKKw==\n-----END > CERTIFICATE-----\n > > the firewall list of the host 192.168.10.41 is: > > [root@ooengh1 ~]# firewall-cmd --list-all public (active) > target: default > icmp-block-inversion: no > interfaces: bond0 ovirtmgmt > sources: > services: cockpit dhcpv6-client libvirt-tls ovirt-imageio ovirt- > vmconsole snmp ssh vdsm > ports: 6900/tcp 22/tcp 6081/udp > protocols: > masquerade: no > forward-ports: > source-ports: > icmp-blocks: > rich rules: > > > > > > > > the follow file is the connect file that vm that cannot connect using > remote viewer: > > [virt-viewer] > type=vnc > host=ohost1.tltd.com > port=5900 > password=4/jWA+RLaSZe > # Password is valid for 120 seconds. > delete-this-file=1 > fullscreen=0 > title=testol:%d > toggle-fullscreen=shift+f11 > release-cursor=shift+f12 > secure-attention=ctrl+alt+end > versions=rhev-win64:2.0-160;rhev-win32:2.0-160;rhel8:7.0-3;rhel7:2.0- > 6;rhel6:99.0-1 > newer-version-url= > http://www.ovirt.org/documentation/admin-guide/virt/console-client-res > ources > > [ovirt] > host=ooeng.tltd.com:443 > vm-guid=2b0eeecf-e561-4f60-b16d-dccddfcc852a > sso-token=4Up7TfLLBjSuQgPkQvRz3D- > fUGZWZg4ynApe2Y7ylkARCFwQWsfEr3dU8FjlK8esctm3Im4tz80mE1DjrNT3XQ > admin=1 > ca=-----BEGIN CERTIFICATE----- > \nMIIDqDCCApCgAwIBAgICEAAwDQYJKoZIhvcNAQELBQAwPzELMAkGA1UEBhMCVVMxETA > PBgNVBAoM\nCHRsdGQuY29tMR0wGwYDVQQDDBRvb2VuZy50bHRkLmNvbS4xNzczMDAeFw > 0yMTAxMTAxNjE1NDda\nFw0zMTAxMDkxNjE1NDdaMD8xCzAJBgNVBAYTAlVTMREwDwYDV > QQKDAh0bHRkLmNvbTEdMBsGA1UE\nAwwUb29lbmcudGx0ZC5jb20uMTc3MzAwggEiMA0G > CSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCg\nYT9S7hWiXQUzAqFQKbg2nMjwyHDmb/J > mKeJAUVZqNKRg1q80IpWyoM12Zw0nX1eTwMnVY/JtJON4\n13PoEC3So8nniGt+wtHr44 > ysvCWfU0SBk/ZPnKmQ58o5MlSkidHwySChXfVPYLPWeUJ1JUrujna/\nCbi5bmmjx2pqw > LrZXX8Q5NO2MRKOTs0Dtg16Q6z+a3cXLIffVJfhPGS3AkIh6nznNaDeH5gFZZbd\nr3DK > E4xrpdw/7y6CgjmHe4vwGxOIyE+gElZ/lVtqznLMwohz7wgtgsDA36277mujNyMjMbrSF > heu\n5WfbIa9VVSZWEkISVq6eswLOQ1IRaFyJsFN9AgMBAAGjga0wgaowHQYDVR0OBBYE > FDYEqJOMqN8+\nQhCP7DAkqF3RZMFdMGgGA1UdIwRhMF+AFDYEqJOMqN8+QhCP7DAkqF3 > RZMFdoUOkQTA/MQswCQYD\nVQQGEwJVUzERMA8GA1UECgwIdGx0ZC5jb20xHTAbBgNVBA > MMFG9vZW5nLnRsdGQuY29tLjE3NzMw\nggIQADAPBgNVHRMBAf8EBTADAQH/MA4GA1UdD > wEB/wQEAwIBBjANBgkqhkiG9w0BAQsFAAOCAQEA\nAKs0/yQWkoOkGcL0PjF9ijekdMmj > rLZGyh5uLot7h9s/Y2+5l9n9IzEjjx9chi8xwt6MBsR6/nBT\n/skcciv2veM22HwNGjd > rHvhfbZFnZsGe2TU60kGzKjlv1En/8Pgd2aWBcwTlr+SErBXkehNEJRj9\n1saycPgwS4 > pHS04c2+4JMhpe+hxgsO2+N/SYkP95Lf7ZQynVsN/SKx7X3cWybErCqoB7G7McqaHN\nV > Ww+QNXo5islWUXqeDc3RcnW3kq0XUEzEtp6hoeRcLKO99QrAW31zqU/QY+EeZ6Fax1O/j > rDafZn\npTs0KJFNgeVnUhKanB29ONy+tmnUmTAgPMaKKw==\n-----END > CERTIFICATE-----\n > > > the firewall list of the host ohost1.tltd.com(192.168.10.160) is: > > [root@ohost1 ~]# firewall-cmd --list-all public (active) > target: default > icmp-block-inversion: no > interfaces: bond0 ovirtmgmt > sources: > services: cockpit dhcpv6-client libvirt-tls ovirt-imageio ovirt- > vmconsole snmp ssh vdsm > ports: 22/tcp 6081/udp > protocols: > masquerade: no > forward-ports: > source-ports: > icmp-blocks: > rich rules: > > > Please give me some advice,thanks. > > > > > > > > > > > > > > > > > > > > > > -----Original Message----- > From: users-bounces(a)ovirt.org <users-bounces(a)ovirt.org> On Behalf Of > Strahil Nikolov via Users > Sent: Wednesday, January 13, 2021 3:15 AM > To: Matthew.Stier(a)fujitsu.com; eevans(a)digitaldatatechs.com; > users(a)ovirt.org > Subject: [ovirt-users] Re: VM console does not work with new cluster. > > > > It’s just that once the VM has been moved to the new cluster, > > selecting console results in the same behavior, but that virt- > > viewer starts and stops within a second. > > In order to debug, you will need to compare the files provided when > you press the "console" button from both clusters and identify the > problem. > > Have you compared the firewalld ports on 2 nodes (old and new > cluster) ? > > 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/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/3U5ZIELT > USPKT6KZ7UZWWFCDRNCF5YLN/ > > _______________________________________________ Users mailing list -- users(a)ovirt.org To unsubscribe send an email to users-leave(a)ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/N7JRNNAJDZHA4…

1 0

Networking question on setting up self-hosting engine
by Kim Yuan Lee 14 Jan '21

14 Jan '21

Dear Ovirt list, I saw some failures in /var/log/ovirt-hosted-engine-setup such as: 1) Install oVirt Engine packages for restoring backup 2) Copy engine logs etc But I'm not sure what is the root cause for the setup to fail? Attached is the log file for your reference. Could you please advise? Thanks. > On Thursday, 14 January 1:45 a.m., <Yedidyah Bar David> wrote: >> Hi, >> >> On Wed, Jan 13, 2021 at 7:16 PM <netgoogling(a)gmail.com> wrote: ... <https://lists.ovirt.org/archives/list/users@ovirt.org/thread/X5WRCCSULCNW4B…> Dear list, I have tried setting up self-hosting engine on a host with ONE Nic (Ovirt 4.4 CentOS 8 Stream). I followed the Quick Start Guide, and tried the command line self-host setup, but ended up with the following error: {u'msg': u'There was a failure deploying the engine on the local engine VM. The system may not be provisioned according to the playbook results.... I tried on another host with TWO NICs (Ovirt 4.3 Oracle Linux 7 Update 9). This time I setup a bridge BR0 and disable EM1 (the first Ethernet interface on the host), and then created Bond0 on-top of BR0. Both Bond0 and EM2 (the second Ethernet interface on the host) were up. And then I tried again using Ovirt-Cockpit wizard, with the Engine VM set on BR0, and the deployment of Engine VM simply failed. The Engine and Host are using the same network numbers (192.168.2.0/24) and they resolved correctly. I read the logs in var/log/ovirt-engine/engine.log but there wasn't any error reported. I have already tried many times for the past few days and I'm at my wits-end. May I know: 1) Is it possible to install Self-hosted engine with just ONE NIC? >> Generally speaking, yes. ... <https://lists.ovirt.org/archives/list/users@ovirt.org/thread/X5WRCCSULCNW4B…> 2) Any suggestion how to troubleshoot these problems? And tested network configurations? >> >> Please check/share all relevant logs. If unsure, all of /var/log. >> Specifically, /var/log/ovirt-hosted-engine-setup/* (also engine-logs >> subdirs, if relevant) and /var/log/vdsm/* on the hosts. >> >> Good luck and best regards, Regards, Lee.

1 0

[ANN] oVirt 4.4.5 First Release Candidate is now available for testing
by Lev Veyde 14 Jan '21

14 Jan '21

oVirt 4.4.5 First Release Candidate is now available for testing The oVirt Project is pleased to announce the availability of oVirt 4.4.5 First Release Candidate for testing, as of January 14th, 2021. This update is the fifth in a series of stabilization updates to the 4.4 series. How to prevent hosts entering emergency mode after upgrade from oVirt 4.4.1 Note: Upgrading from 4.4.2 GA or later should not require re-doing these steps, if already performed while upgrading from 4.4.1 to 4.4.2 GA. These are only required to be done once. Due to Bug 1837864 <https://bugzilla.redhat.com/show_bug.cgi?id=1837864> - Host enter emergency mode after upgrading to latest build If you have your root file system on a multipath device on your hosts you should be aware that after upgrading from 4.4.1 to 4.4.5 you may get your host entering emergency mode. In order to prevent this be sure to upgrade oVirt Engine first, then on your hosts: 1. Remove the current lvm filter while still on 4.4.1, or in emergency mode (if rebooted). 2. Reboot. 3. Upgrade to 4.4.5 (redeploy in case of already being on 4.4.5). 4. Run vdsm-tool config-lvm-filter to confirm there is a new filter in place. 5. Only if not using oVirt Node: - run "dracut --force --add multipath” to rebuild initramfs with the correct filter configuration 6. Reboot. Documentation - If you want to try oVirt as quickly as possible, follow the instructions on the Download <https://ovirt.org/download/> page. - For complete installation, administration, and usage instructions, see the oVirt Documentation <https://ovirt.org/documentation/>. - For upgrading from a previous version, see the oVirt Upgrade Guide <https://ovirt.org/documentation/upgrade_guide/>. - For a general overview of oVirt, see About oVirt <https://ovirt.org/community/about.html>. 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 be used in production. Installation instructions For installation instructions and additional information please refer to: https://ovirt.org/documentation/ This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 8.3 or newer * CentOS Linux (or similar) 8.3 or newer This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 8.3 or newer * CentOS Linux (or similar) 8.3 or newer * oVirt Node 4.4 based on CentOS Linux 8.3 (available for x86_64 only) See the release notes [1] for installation instructions and a list of new features and bugs fixed. 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.5 release highlights: http://www.ovirt.org/release/4.4.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.4.5/ [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

Re: VM console does not work with new cluster.
by Strahil Nikolov 14 Jan '21

14 Jan '21

I don't see the VNC ports at all (5900 and above). Here is my firewall on oVirt 4.3.10: public (active) target: default icmp-block-inversion: no interfaces: enp4s0 enp5s0f0 enp5s0f1 enp7s5f0 enp7s5f1 enp7s6f0 enp7s6f1 ovirtmgmt team0 sources: services: cockpit ctdb dhcpv6-client glusterfs libvirt-tls nfs nfs3 nrpe ovirt-imageio ovirt-storageconsole ovirt-vmconsole rpc-bind samba snmp ssh vdsm ports: 111/tcp 2049/tcp 54321/tcp 5900/tcp 5900-6923/tcp 5666/tcp 16514/tcp 54322/tcp 22/tcp 6081/udp 8080/tcp 963/udp 965/tcp protocols: masquerade: no forward-ports: source-ports: icmp-blocks: rich rules: Best Regards, Strahil Nikolov В 05:25 +0800 на 13.01.2021 (ср), tommy написа: > I encountered the question too. > > The follow file is the connect file for vm that can connect using > remote viewer: > > [virt-viewer] > type=vnc > host=192.168.10.41 > port=5900 > password=rdXQA4zr/UAY > # Password is valid for 120 seconds. > delete-this-file=1 > fullscreen=0 > title=HostedEngine:%d > toggle-fullscreen=shift+f11 > release-cursor=shift+f12 > secure-attention=ctrl+alt+end > versions=rhev-win64:2.0-160;rhev-win32:2.0-160;rhel8:7.0-3;rhel7:2.0- > 6;rhel6:99.0-1 > newer-version-url= > http://www.ovirt.org/documentation/admin-guide/virt/console-client-resources > > [ovirt] > host=ooeng.tltd.com:443 > vm-guid=76f99df2-ef79-45d9-8eea-a32b168f9ef3 > sso-token=4Up7TfLLBjSuQgPkQvRz3D- > fUGZWZg4ynApe2Y7ylkARCFwQWsfEr3dU8FjlK8esctm3Im4tz80mE1DjrNT3XQ > admin=1 > ca=-----BEGIN CERTIFICATE----- > \nMIIDqDCCApCgAwIBAgICEAAwDQYJKoZIhvcNAQELBQAwPzELMAkGA1UEBhMCVVMxETA > PBgNVBAoM\nCHRsdGQuY29tMR0wGwYDVQQDDBRvb2VuZy50bHRkLmNvbS4xNzczMDAeFw > 0yMTAxMTAxNjE1NDda\nFw0zMTAxMDkxNjE1NDdaMD8xCzAJBgNVBAYTAlVTMREwDwYDV > QQKDAh0bHRkLmNvbTEdMBsGA1UE\nAwwUb29lbmcudGx0ZC5jb20uMTc3MzAwggEiMA0G > CSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCg\nYT9S7hWiXQUzAqFQKbg2nMjwyHDmb/J > mKeJAUVZqNKRg1q80IpWyoM12Zw0nX1eTwMnVY/JtJON4\n13PoEC3So8nniGt+wtHr44 > ysvCWfU0SBk/ZPnKmQ58o5MlSkidHwySChXfVPYLPWeUJ1JUrujna/\nCbi5bmmjx2pqw > LrZXX8Q5NO2MRKOTs0Dtg16Q6z+a3cXLIffVJfhPGS3AkIh6nznNaDeH5gFZZbd\nr3DK > E4xrpdw/7y6CgjmHe4vwGxOIyE+gElZ/lVtqznLMwohz7wgtgsDA36277mujNyMjMbrSF > heu\n5WfbIa9VVSZWEkISVq6eswLOQ1IRaFyJsFN9AgMBAAGjga0wgaowHQYDVR0OBBYE > FDYEqJOMqN8+\nQhCP7DAkqF3RZMFdMGgGA1UdIwRhMF+AFDYEqJOMqN8+QhCP7DAkqF3 > RZMFdoUOkQTA/MQswCQYD\nVQQGEwJVUzERMA8GA1UECgwIdGx0ZC5jb20xHTAbBgNVBA > MMFG9vZW5nLnRsdGQuY29tLjE3NzMw\nggIQADAPBgNVHRMBAf8EBTADAQH/MA4GA1UdD > wEB/wQEAwIBBjANBgkqhkiG9w0BAQsFAAOCAQEA\nAKs0/yQWkoOkGcL0PjF9ijekdMmj > rLZGyh5uLot7h9s/Y2+5l9n9IzEjjx9chi8xwt6MBsR6/nBT\n/skcciv2veM22HwNGjd > rHvhfbZFnZsGe2TU60kGzKjlv1En/8Pgd2aWBcwTlr+SErBXkehNEJRj9\n1saycPgwS4 > pHS04c2+4JMhpe+hxgsO2+N/SYkP95Lf7ZQynVsN/SKx7X3cWybErCqoB7G7McqaHN\nV > Ww+QNXo5islWUXqeDc3RcnW3kq0XUEzEtp6hoeRcLKO99QrAW31zqU/QY+EeZ6Fax1O/j > rDafZn\npTs0KJFNgeVnUhKanB29ONy+tmnUmTAgPMaKKw==\n-----END > CERTIFICATE-----\n > > the firewall list of the host 192.168.10.41 is: > > [root@ooengh1 ~]# firewall-cmd --list-all public (active) > target: default > icmp-block-inversion: no > interfaces: bond0 ovirtmgmt > sources: > services: cockpit dhcpv6-client libvirt-tls ovirt-imageio ovirt- > vmconsole snmp ssh vdsm > ports: 6900/tcp 22/tcp 6081/udp > protocols: > masquerade: no > forward-ports: > source-ports: > icmp-blocks: > rich rules: > > > > > > > > the follow file is the connect file that vm that cannot connect using > remote viewer: > > [virt-viewer] > type=vnc > host=ohost1.tltd.com > port=5900 > password=4/jWA+RLaSZe > # Password is valid for 120 seconds. > delete-this-file=1 > fullscreen=0 > title=testol:%d > toggle-fullscreen=shift+f11 > release-cursor=shift+f12 > secure-attention=ctrl+alt+end > versions=rhev-win64:2.0-160;rhev-win32:2.0-160;rhel8:7.0-3;rhel7:2.0- > 6;rhel6:99.0-1 > newer-version-url= > http://www.ovirt.org/documentation/admin-guide/virt/console-client-resources > > [ovirt] > host=ooeng.tltd.com:443 > vm-guid=2b0eeecf-e561-4f60-b16d-dccddfcc852a > sso-token=4Up7TfLLBjSuQgPkQvRz3D- > fUGZWZg4ynApe2Y7ylkARCFwQWsfEr3dU8FjlK8esctm3Im4tz80mE1DjrNT3XQ > admin=1 > ca=-----BEGIN CERTIFICATE----- > \nMIIDqDCCApCgAwIBAgICEAAwDQYJKoZIhvcNAQELBQAwPzELMAkGA1UEBhMCVVMxETA > PBgNVBAoM\nCHRsdGQuY29tMR0wGwYDVQQDDBRvb2VuZy50bHRkLmNvbS4xNzczMDAeFw > 0yMTAxMTAxNjE1NDda\nFw0zMTAxMDkxNjE1NDdaMD8xCzAJBgNVBAYTAlVTMREwDwYDV > QQKDAh0bHRkLmNvbTEdMBsGA1UE\nAwwUb29lbmcudGx0ZC5jb20uMTc3MzAwggEiMA0G > CSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCg\nYT9S7hWiXQUzAqFQKbg2nMjwyHDmb/J > mKeJAUVZqNKRg1q80IpWyoM12Zw0nX1eTwMnVY/JtJON4\n13PoEC3So8nniGt+wtHr44 > ysvCWfU0SBk/ZPnKmQ58o5MlSkidHwySChXfVPYLPWeUJ1JUrujna/\nCbi5bmmjx2pqw > LrZXX8Q5NO2MRKOTs0Dtg16Q6z+a3cXLIffVJfhPGS3AkIh6nznNaDeH5gFZZbd\nr3DK > E4xrpdw/7y6CgjmHe4vwGxOIyE+gElZ/lVtqznLMwohz7wgtgsDA36277mujNyMjMbrSF > heu\n5WfbIa9VVSZWEkISVq6eswLOQ1IRaFyJsFN9AgMBAAGjga0wgaowHQYDVR0OBBYE > FDYEqJOMqN8+\nQhCP7DAkqF3RZMFdMGgGA1UdIwRhMF+AFDYEqJOMqN8+QhCP7DAkqF3 > RZMFdoUOkQTA/MQswCQYD\nVQQGEwJVUzERMA8GA1UECgwIdGx0ZC5jb20xHTAbBgNVBA > MMFG9vZW5nLnRsdGQuY29tLjE3NzMw\nggIQADAPBgNVHRMBAf8EBTADAQH/MA4GA1UdD > wEB/wQEAwIBBjANBgkqhkiG9w0BAQsFAAOCAQEA\nAKs0/yQWkoOkGcL0PjF9ijekdMmj > rLZGyh5uLot7h9s/Y2+5l9n9IzEjjx9chi8xwt6MBsR6/nBT\n/skcciv2veM22HwNGjd > rHvhfbZFnZsGe2TU60kGzKjlv1En/8Pgd2aWBcwTlr+SErBXkehNEJRj9\n1saycPgwS4 > pHS04c2+4JMhpe+hxgsO2+N/SYkP95Lf7ZQynVsN/SKx7X3cWybErCqoB7G7McqaHN\nV > Ww+QNXo5islWUXqeDc3RcnW3kq0XUEzEtp6hoeRcLKO99QrAW31zqU/QY+EeZ6Fax1O/j > rDafZn\npTs0KJFNgeVnUhKanB29ONy+tmnUmTAgPMaKKw==\n-----END > CERTIFICATE-----\n > > > the firewall list of the host ohost1.tltd.com(192.168.10.160) is: > > [root@ohost1 ~]# firewall-cmd --list-all public (active) > target: default > icmp-block-inversion: no > interfaces: bond0 ovirtmgmt > sources: > services: cockpit dhcpv6-client libvirt-tls ovirt-imageio ovirt- > vmconsole snmp ssh vdsm > ports: 22/tcp 6081/udp > protocols: > masquerade: no > forward-ports: > source-ports: > icmp-blocks: > rich rules: > > > Please give me some advice,thanks. > > > > > > > > > > > > > > > > > > > > > > -----Original Message----- > From: users-bounces(a)ovirt.org <users-bounces(a)ovirt.org> On Behalf Of > Strahil Nikolov via Users > Sent: Wednesday, January 13, 2021 3:15 AM > To: Matthew.Stier(a)fujitsu.com; eevans(a)digitaldatatechs.com; > users(a)ovirt.org > Subject: [ovirt-users] Re: VM console does not work with new cluster. > > > > It’s just that once the VM has been moved to the new cluster, > > selecting console results in the same behavior, but that virt- > > viewer > > starts and stops within a second. > > In order to debug, you will need to compare the files provided when > you press the "console" button from both clusters and identify the > problem. > > Have you compared the firewalld ports on 2 nodes (old and new > cluster) ? > > 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/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/3U5ZIELTUSPKT… > >

3 2

Q: oVirt 4.4.4.7 Node settings on CentOS Stream
by Andrei Verovski 14 Jan '21

14 Jan '21

Hi ! I’m installing new oVirt 4.4.4 node on CentOS Stream and its seems there are some changes since older node on CentOS 7.x. 1) NFS shares for storage domain. In 7.x I used chown -Rv nfsnobody:nfsnobody /vmraid/nfs; chmod -Rv 755 /vmraid/nfs In Stream nfsnobody don’t exists, should I use: chown -Rv nobody:nobody /vmraid/nfs; chmod -Rv 777 /vmraid/nfs Is that correct settings? 2) SELinux seems to be more permissive now, looks like I don’t have to tweak it to have my custom cron and SNMP scripts running. Yes, SELinux is running, getenforce -> yields “Enforcing”. Will oVirt sw node installation change this behaviour? Thanks in advance Andrei

1 0

Networking question on setting up self-hosting engine
by netgoogling＠gmail.com 14 Jan '21

14 Jan '21

Dear list, I have tried setting up self-hosting engine on a host with ONE Nic (Ovirt 4.4 CentOS 8 Stream). I followed the Quick Start Guide, and tried the command line self-host setup, but ended up with the following error: {u'msg': u'There was a failure deploying the engine on the local engine VM. The system may not be provisioned according to the playbook results.... I tried on another host with TWO NICs (Ovirt 4.3 Oracle Linux 7 Update 9). This time I setup a bridge BR0 and disable EM1 (the first Ethernet interface on the host), and then created Bond0 on-top of BR0. Both Bond0 and EM2 (the second Ethernet interface on the host) were up. And then I tried again using Ovirt-Cockpit wizard, with the Engine VM set on BR0, and the deployment of Engine VM simply failed. The Engine and Host are using the same network numbers (192.168.2.0/24) and they resolved correctly. I read the logs in var/log/ovirt-engine/engine.log but there wasn't any error reported. I have already tried many times for the past few days and I'm at my wits-end. May I know: 1) Is it possible to install Self-hosted engine with just ONE NIC? 2) Any suggestion how to troubleshoot these problems? And tested network configurations? Hope to hear from you. Thanks.

2 1

Q: New oVirt Node - CentOS 8 or Stream ?
by Andrei Verovski 14 Jan '21

14 Jan '21

Hi, I’m currently adding new oVirt node to existing 4.4 setup. Which underlying OS version would you recommend for long-term deployment - CentOS 8 or Stream ? I don’t use pre-built node ISO since I have a number of custom scripts running on node host OS. Thanks in advance. Andrei

3 2

image upload on Managed Block Storage
by Henry lol 13 Jan '21

13 Jan '21

Hello, I've just checked I can't upload an image into the MBS block through either UI or restAPI. So, is there any method to do that?

2 4

2021 first ovirt network question
by ozmen62＠hotmail.com 13 Jan '21

13 Jan '21

Hi, We're using oVirt as VDI solution for awhile. Infrastacture is 2 HPE Gen10 server with 80x2 Core cpu, 2TB RAM, 16GBX2 HBA For getting performance i've splited the networks on physical layer 2X10GB LACP for VM network 2X10GB LACP for Display(Spice) network 1GB for management + Default Route After 40 VMs spice connections start to be laggy. We've found our SAN storage I/O is bad and we'll change it SSD But, on the other hand, RDP connections is flawless. Now, we have 70 VMs and i need to solve this problem. Do you thing this is a network problem? We've also checked dropping packages on the switches, but found nothing.

4 11