- Users - oVirt List Archives

VMs traffic cannot go outside host
by deyaa112006＠hotmail.com 28 Jun '21

28 Jun '21

Hi trying to get hands on ovirt virtualization. built a test environment on vmware workstation: - 2 VMs running centos7 as ovirt Hosts - 1 VM running centos 7 as ovirt-manager on ovirt Hosts: [root@ovirt-node1 ~]# rpm -q cockpit-ovirt-dashboard qemu-kvm-ev libvirt virt-install bridge-utils vdsm cockpit-ovirt-dashboard-0.13.10-1.el7.noarch qemu-kvm-ev-2.12.0-44.1.el7_8.1.x86_64 libvirt-4.5.0-36.el7_9.5.x86_64 virt-install-1.5.0-7.el7.noarch bridge-utils-1.5-9.el7.x86_64 vdsm-4.30.46-1.el7.x86_64 on ovirt-manager: [oVirt shell (connected)]# info backend version: 4.3.10 sdk version : 4.3.4 cli version : 3.6.9.2 python version : 2.7.5.final.0 entry point : https://ovirt-manager.home.lab/ovirt-engine/api I created two ovirt VMs, running ubuntu16, on the same VM Networks "vmnet-02" Both VMs' traffic cannot go outside hosts (i.e they can reach each others only if they run on the same host) need help fix this please! [d@dv6 ~]$ ovirt-node2 Last login: Mon Jun 28 15:25:12 2021 from 10.0.1.1 [root@ovirt-node2 ~]# ifconfig ens32: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether 00:0c:29:d2:71:10 txqueuelen 1000 (Ethernet) RX packets 5388529 bytes 7970598031 (7.4 GiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 287643 bytes 124694822 (118.9 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 ens34: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether 00:0c:29:d2:71:1a txqueuelen 1000 (Ethernet) RX packets 6574 bytes 637208 (622.2 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 3573 bytes 393479 (384.2 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 genev_sys_6081: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 65000 ether fe:66:e6:5e:51:f8 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 loop txqueuelen 1000 (Local Loopback) RX packets 15152 bytes 3732985 (3.5 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 15152 bytes 3732985 (3.5 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 ovirtmgmt: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 10.0.1.22 netmask 255.255.255.0 broadcast 10.0.1.255 ether 00:0c:29:d2:71:10 txqueuelen 1000 (Ethernet) RX packets 308773 bytes 7630918499 (7.1 GiB) RX errors 0 dropped 42 overruns 0 frame 0 TX packets 253627 bytes 92412626 (88.1 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 vmnet-02: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.57.146 netmask 255.255.255.0 broadcast 192.168.57.255 ether 00:0c:29:d2:71:1a txqueuelen 1000 (Ethernet) RX packets 9367 bytes 640524 (625.5 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1015 bytes 248111 (242.2 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 vnet0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether fe:6f:b4:ee:00:01 txqueuelen 1000 (Ethernet) RX packets 6483 bytes 289530 (282.7 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 5120 bytes 480414 (469.1 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 [root@ovirt-node2 ~]# [root@ovirt-node2 ~]# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 10.0.1.254 0.0.0.0 UG 0 0 0 ovirtmgmt 10.0.1.0 0.0.0.0 255.255.255.0 U 0 0 0 ovirtmgmt 169.254.0.0 0.0.0.0 255.255.0.0 U 1023 0 0 ovirtmgmt 192.168.57.0 0.0.0.0 255.255.255.0 U 0 0 0 vmnet-02 Here I can access the guest VM: [root@ovirt-node2 ~]# ssh sysadmin(a)10.0.1.44 sysadmin(a)10.0.1.44's password: sysadmin@ubuntu16-1:~$ ifconfig ens4 Link encap:Ethernet HWaddr 56:6f:b4:ee:00:01 inet addr:10.0.1.44 Bcast:10.0.1.255 Mask:255.255.255.0 inet6 addr: fe80::546f:b4ff:feee:1/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:312 errors:0 dropped:0 overruns:0 frame:0 TX packets:1834 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:75924 (75.9 KB) TX bytes:87332 (87.3 KB) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:1136 errors:0 dropped:0 overruns:0 frame:0 TX packets:1136 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1 RX bytes:105288 (105.2 KB) TX bytes:105288 (105.2 KB) sysadmin@ubuntu16-1:~$ route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 10.0.1.254 0.0.0.0 UG 0 0 0 ens4 10.0.1.0 0.0.0.0 255.255.255.0 U 0 0 0 ens4 but from the other host "node1" I cannot.

1 0

hosted-engine cannot can't communicate with vm
by Harry O 28 Jun '21

28 Jun '21

The VM is up and the ids match, but it fail when I try anything. hosted-engine --vm-shutdown Command VM.shutdown with args {'vmID': '350a168a-beb9-4417-9fbd-5a8121863a57', 'delay': '120', 'message': 'VM is shutting down!'} failed: (code=1, message=Virtual machine does not exist: {'vmId': '350a168a-beb9-4417-9fbd-5a8121863a57'}) virsh list Id Name State ------------------------------ 2 HostedEngine running virsh domuuid HostedEngine 350a168a-beb9-4417-9fbd-5a8121863a57 MainThread::ERROR::2021-06-17 09:58:54,537::hosted_engine::953::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_stop_engine_vm) Failed to stop engine VM: Command VM.destroy with args {'vmID': '350a168a-beb9-4417-9fbd-5a8121863a57'} failed: (code=1, message=Virtual machine does not exist: {'vmId': '350a168a-beb9-4417-9fbd-5a8121863a57'}) MainThread::INFO::2021-06-17 09:58:54,563::brokerlink::73::ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink::(notify) Success, was notification of state_transition (EngineForceStop-ReinitializeFSM) sent? ignored MainThread::INFO::2021-06-17 09:58:54,569::hosted_engine::517::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_monitoring_loop) Current state ReinitializeFSM (score: 0) MainThread::INFO::2021-06-17 09:59:04,654::brokerlink::73::ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink::(notify) Success, was notification of state_transition (ReinitializeFSM-EngineDown) sent? ignored MainThread::INFO::2021-06-17 09:59:04,738::hosted_engine::517::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_monitoring_loop) Current state EngineDown (score: 3400) MainThread::INFO::2021-06-17 09:59:13,759::states::472::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(consume) Engine down and local host has best score (3400), attempting to start engine VM MainThread::INFO::2021-06-17 09:59:13,796::brokerlink::73::ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink::(notify) Success, was notification of state_transition (EngineDown-EngineStart) sent? ignored MainThread::INFO::2021-06-17 09:59:13,888::hosted_engine::517::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_monitoring_loop) Current state EngineStart (score: 3400) MainThread::INFO::2021-06-17 09:59:13,903::hosted_engine::895::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_clean_vdsm_state) Ensuring VDSM state is clear for engine VM MainThread::INFO::2021-06-17 09:59:13,909::hosted_engine::907::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_clean_vdsm_state) Vdsm state for VM clean MainThread::INFO::2021-06-17 09:59:13,909::hosted_engine::853::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_start_engine_vm) Starting vm using `/usr/sbin/hosted-engine --vm-start` MainThread::INFO::2021-06-17 09:59:14,444::hosted_engine::862::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_start_engine_vm) stdout: VM in WaitForLaunch MainThread::INFO::2021-06-17 09:59:14,444::hosted_engine::863::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_start_engine_vm) stderr: Command VM.getStats with args {'vmID': '350a168a-beb9-4417-9fbd-5a8121863a57'} failed: (code=1, message=Virtual machine does not exist: {'vmId': '350a168a-beb9-4417-9fbd-5a8121863a57'}) MainThread::INFO::2021-06-17 09:59:14,444::hosted_engine::875::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_start_engine_vm) Engine VM started on localhost MainThread::INFO::2021-06-17 09:59:14,472::brokerlink::73::ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink::(notify) Success, was notification of state_transition (EngineStart-EngineStarting) sent? ignored MainThread::INFO::2021-06-17 09:59:14,479::hosted_engine::517::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_monitoring_loop) Current state EngineStarting (score: 3400)

3 4

[italian community] Geek talk and RH018 training
by Sandro Bonazzola 28 Jun '21

28 Jun '21

Hi, not relevant for everyone in the list but maybe interesting for the oVirt Italian community: I'll be in a live stream event today with Extraordy within the GeekTalk series[1]. There will also be a free Red Hat "RH018 - Virtualization and Infrastructure Migration Technical Overview" Training in Italian language on July 2nd where we'll talk also about oVirt[2]. See you there! [1] https://www.linkedin.com/feed/update/urn:li:activity:6815171728424087552/ [2] https://rh018.it/ -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/> *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

1 0

Inquiries regarding missing data in the calendar table created/inserted into the ovirt_engine_history DB.
by whoisjmh＠gmail.com 28 Jun '21

28 Jun '21

I recently discovered that the spark-line chart is not displayed in the dashboard of the ovirt admin page. As a result of looking up the code and query, the data of the calendar table in the ovirt_engine_history DB of ovirt-dwh was only available until 2021-01-01 00:00:00, so a query statement ( https://github.com/oVirt/ovirt-engine/blob/master/frontend/webadmin/modules…. RIGHT OUTER JOIN of properties) was not getting the correct data. First, the existing "generate_series('2011-01-01 00:00'::timestamp, '2021-01-01 00:00', '1 hours')" part was temporarily modified and applied until 2051. , it was confirmed that the spark-line chart was displayed normally. For this, is there a way I can directly edit the file (https://github.com/oVirt/ovirt-dwh/blob/master/packaging/dbscripts/upgrade/…) to commit or request a correction? I would like to know.

2 1

IPv6 Support
by David White 28 Jun '21

28 Jun '21

Hello, Reading https://www.ovirt.org/documentation/administration_guide/index.html#IPv6-ne…, I see this tidbit: - Dual-stack addressing, IPv4andIPv6, is not supported - Switching clusters from IPv4 to IPv6 is not supported. If I'm understanding this correctly... does that mean I cannot run some VMs with IPv4, and other VMs with IPv6, in the same cluster? If so, that's incredibly disappointing and frustrating. Is Dual-stack addressing a possible feature request? IPv4 addresses are expensive... and I have a couple of customers who only needs IPv6, so would really prefer to avoid having to pay for IPv4 addresses for them. Sent with ProtonMail Secure Email.

4 3

Re: CPU Compatibility Problem after Upgrading Centos 8 Stream Host
by Nur Imam Febrianto 27 Jun '21

27 Jun '21

Are this issue already fixed ? Do anybody already had try it again ? Regards, Nur Imam Febrianto From: Nur Imam Febrianto<mailto:nur_imam@outlook.com> Sent: 27 May 2021 13:01 To: Jeff Bailey<mailto:bailey@cs.kent.edu>; users(a)ovirt.org<mailto:users@ovirt.org> Subject: [ovirt-users] Re: CPU Compatibility Problem after Upgrading Centos 8 Stream Host Confirmed, excluding edk2-ovmf will solve the issue. Thanks for your info 😊 Regards, Nur Imam Febrianto From: Jeff Bailey<mailto:bailey@cs.kent.edu> Sent: 25 May 2021 23:16 To: users(a)ovirt.org<mailto:users@ovirt.org> Subject: [ovirt-users] Re: CPU Compatibility Problem after Upgrading Centos 8 Stream Host If it's the same problem that I ran into then it's the latest version of edk2-ovmf. I'm not sure why it was pushed into the repos without a fixed libvirt to go with it. On 5/25/2021 7:20 AM, Nur Imam Febrianto wrote: Hi, This morning I have a problem that suddenly my Host (Using Centos 8 Stream, not oVirt Node) showing error with Cpu Compatibility. It says my CPU doesn’t have Haswell-noTSX and spec_ctrl flag. After downgrading the kernel back from 4.18.0 – 305 to 4.18.0 – 301.1 and rollback yum update, it working again. Do anybody having same issue ? I’m using Xeon E5-2695v4 with cluster compatibility Secure Intel Haswell. Using oVirt 4.4.6 on CentOS Stream host. Thanks before. Sent from Mail<https://apac01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgo.micro…> for Windows 10 _______________________________________________ Users mailing list -- users(a)ovirt.org<mailto:users@ovirt.org> To unsubscribe send an email to users-leave(a)ovirt.org<mailto:users-leave@ovirt.org> Privacy Statement: https://www.ovirt.org/privacy-policy.html<https://apac01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovir…> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/<https://apac01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovir…> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/7R7SFBOPQL5S6…<https://apac01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.ov…>

1 0

Question about Template and Storage Domain
by Nur Imam Febrianto 27 Jun '21

27 Jun '21

Hi, Want to ask about template. For example I have a several template (with disk) stored in some Storage Domain. If I create a VM from the template, and when I change the parameter of cloned disk into another storage domain (different with where the template are stored). The VM always failed to be created. This only occurs in VM creation phase, if I create the VM at same storage domain where the templates are stored, it created successfully. Is this are “normal” behavior ? Thanks before. Regards, Nur Imam Febrianto

1 0

Re: oVirt and ARM
by Sandro Bonazzola 25 Jun '21

25 Jun '21

Il giorno gio 24 giu 2021 alle ore 16:34 Marko Vrgotic < M.Vrgotic(a)activevideo.com> ha scritto: > Hi oVirt, > > > > Where can I find if there are any information about oVirt supporting arm64 > CPU architecture? > Right now oVirt is not supporting arm64. There was an initiative about supporting it started some time ago from openEuler ovirt SIG. I didn't got any further updates on this topic, looping in those who I remember being looking into it. I think that if someone contributes arm64 support it would also be a feature worth a 4.5 release :-) > > > ----- > > kind regards/met vriendelijke groeten > > > > Marko Vrgotic > Sr. System Engineer @ System Administration > > > ActiveVideo > > *o: *+31 (35) 6774131 > > *m: +*31 (65) 5734174 > > *e:* m.vrgotic(a)activevideo.com > *w: *www.activevideo.com > > > > ActiveVideo Networks BV. Mediacentrum 3745 Joop van den Endeplein 1.1217 > WJ Hilversum, The Netherlands. The information contained in this message > may be legally privileged and confidential. It is intended to be read only > by the individual or entity to whom it is addressed or by their designee. > If the reader of this message is not the intended recipient, you are on > notice that any distribution of this message, in any form, is strictly > prohibited. If you have received this message in error, please immediately > notify the sender and/or ActiveVideo Networks, LLC by telephone at +1 > 408.931.9200 and delete or destroy any copy of this message. > > > > > _______________________________________________ > 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/MQ3XND2NKIL7V… > -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/> *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

2 1

Mount Export Domain only temporary
by jb 25 Jun '21

25 Jun '21

Hello community, We use a NFS export domain for full backups. Sometimes I have to restart the NFS file server, but when I just restart that server, without doing anything in oVirt (I guess normally I should put the domain in maintenance mode), it can happen that hosts and VMs a crashing. I had one time even the issue, that after a crash one XFS file system on one host got damage and I had to fix that. My though was now, because I make only one time a week a VM full backup, I only mount the export domain in this time. Is there an easy way to do this, with the API? Or would you have a other hint, how to solve this issue? Have a good day! Jonathan

4 5

oVirt 4.4.6 Gluster heal pending
by dlotarev＠yahoo.com 25 Jun '21

25 Jun '21

Hi there! I want to know what can i do with this trouble [root@ovirt-h2-new ~]# gluster volume heal data info Brick ovirt-h1-new.local:/gluster/ovirt_new/data / Status: Connected Number of entries: 1 Brick ovirt-h2-new.local:/gluster/ovirt_new/data / Status: Connected Number of entries: 1 [root@ovirt-h2-new ~]# [root@ovirt-h2-new ~]# [root@ovirt-h2-new ~]# [root@ovirt-h2-new ~]# gluster volume heal data info summary Brick ovirt-h1-new.local:/gluster/ovirt_new/data Status: Connected Total Number of entries: 2 Number of entries in heal pending: 2 Number of entries in split-brain: 0 Number of entries possibly healing: 0 Brick ovirt-h2-new.local:/gluster/ovirt_new/data Status: Connected Total Number of entries: 2 Number of entries in heal pending: 2 Number of entries in split-brain: 0 Number of entries possibly healing: 0 Entries not decreasing... Any help

2 1

Re: oVirt 4.2 how to upgrade
by Strahil Nikolov 24 Jun '21

24 Jun '21

Theoretically you most probably can, but you take the risk of being vulnerable to split-brain. Keep in mind that you can:- update gluster to the same version that is used on oVirt 4.4- update oVirt to 4.3.10 as this is the most tested migration scenario- reduce the volume and remove that 3rd node (don't forget to peer detach)- reinstall with EL8 and install gluster (same version) again. Add the brick and qait for the heal- create a new volume for the new HE- Stop the old HE and deploy the new one from the backup- Add the hosts to the new HE and migrate some of the VMs to free one of the old hosts- Reinstall the remaining hosts (one by one) to EL8 Best Regards,Strahil Nikolov On Thu, Jun 24, 2021 at 14:28, Fedele Stabile<fedele.stabile(a)fis.unical.it> wrote: I have a 3 node oVirt 4.2.1 cluster, i'm using a self-hosted engine architecture and storage-engine is on a glusterfs replica 3 of the cluster. The oldest CPU is SandyBridge family (E5-2609) and incidentally it has connectivity problems with IPMI NIC, but Hosted Engine HA is enabled and working. May I reduce the glusterfs replica to 2 and use one of the 3 nodes to begin the installation of ovirt 4.4 on that node? Fedele _______________________________________________ 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/6JWMAUPJQ5GLN…

1 1

[ANN] oVirt 4.4.7 Fifth Release Candidate is now available for testing
by Lev Veyde 24 Jun '21

24 Jun '21

oVirt 4.4.7 Fifth Release Candidate is now available for testing The oVirt Project is pleased to announce the availability of oVirt 4.4.7 Fifth Release Candidate for testing, as of June 24th, 2021. This update is the seventh 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.7 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.7 (redeploy in case of already being on 4.4.7). 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.4 or similar * CentOS Stream 8 This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 8.4 or similar will need the upcoming next batch update, providing an updated sanlock package. * CentOS Stream 8 * oVirt Node 4.4 based on CentOS Stream 8 (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 based on CentOS Stream 8 - oVirt Node NG is already available based on CentOS Stream 8 Additional Resources: * Read more about the oVirt 4.4.7 release highlights: http://www.ovirt.org/release/4.4.7/ * 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.7/ [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

oVirt and ARM
by Marko Vrgotic 24 Jun '21

24 Jun '21

Hi oVirt, Where can I find if there are any information about oVirt supporting arm64 CPU architecture? ----- kind regards/met vriendelijke groeten Marko Vrgotic Sr. System Engineer @ System Administration ActiveVideo o: +31 (35) 6774131 m: +31 (65) 5734174 e: m.vrgotic(a)activevideo.com<mailto:m.vrgotic@activevideo.com> w: www.activevideo.com<http://www.activevideo.com> ActiveVideo Networks BV. Mediacentrum 3745 Joop van den Endeplein 1.1217 WJ Hilversum, The Netherlands. The information contained in this message may be legally privileged and confidential. It is intended to be read only by the individual or entity to whom it is addressed or by their designee. If the reader of this message is not the intended recipient, you are on notice that any distribution of this message, in any form, is strictly prohibited. If you have received this message in error, please immediately notify the sender and/or ActiveVideo Networks, LLC by telephone at +1 408.931.9200 and delete or destroy any copy of this message.

1 0

Expected behavior when link of required VM networks down
by Gianluca Cecchi 24 Jun '21

24 Jun '21

Hello, suppose I have a cluster with required VM logical network setup. Suppose on hosts I have configured a bonding device with this logical network mapped on it. Suppose an active host for any reason loses the physical connectivity on this bond (both links down or problems with new network config impacting the bond, ecc) So from the VMs point of view, those having a vnic on this logical network will lose the connectivity, but I think they will not detect link down, correct? Is there any expected default action oVirt will take in respect of this scenario or not? Of course I expect to see events with messages about link down. But any automatic action such as live migration of impacted VMs for example? Any configurable one at oVirt level? Thanks, Gianluca

1 0

oVirt 4.2 how to upgrade
by Fedele Stabile 24 Jun '21

24 Jun '21

I have a 3 node oVirt 4.2.1 cluster, i'm using a self-hosted engine architecture and storage-engine is on a glusterfs replica 3 of the cluster. The oldest CPU is SandyBridge family (E5-2609) and incidentally it has connectivity problems with IPMI NIC, but Hosted Engine HA is enabled and working. May I reduce the glusterfs replica to 2 and use one of the 3 nodes to begin the installation of ovirt 4.4 on that node? Fedele

1 0

global ha maintenance status via rest api
by Markus Schaufler 24 Jun '21

24 Jun '21

Hello, I'd like to check the status of "global ha maintenance" via rest api. Can't find any hint on this in the api docs - only for enable/disable... any ideas? thanks!

1 0

[ANN] oVirt 4.4.7 Fourth Release Candidate is now available for testing
by Lev Veyde 24 Jun '21

24 Jun '21

oVirt 4.4.7 Fourth Release Candidate is now available for testing The oVirt Project is pleased to announce the availability of oVirt 4.4.7 Fourth Release Candidate for testing, as of June 18th, 2021. This update is the seventh 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.7 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.7 (redeploy in case of already being on 4.4.7). 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.4 or similar * CentOS Stream 8 This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 8.4 or similar * CentOS Stream 8 * oVirt Node 4.4 based on CentOS Stream 8 (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 based on CentOS Stream 8 - oVirt Node NG is already available based on CentOS Stream 8 Additional Resources: * Read more about the oVirt 4.4.7 release highlights: http://www.ovirt.org/release/4.4.7/ * 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.7/ [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>

3 4

ovirt4.4 vm with windows 2008r2 bsod19
by grig.4n＠gmail.com 24 Jun '21

24 Jun '21

after migrate from ovirt4.1 to ovirt4.4 virtual mashines with windows 2008r2 bsod 0x00000019.

1 1

oVirt 4.4.5 - Windows Server 2003 VM Reboot problems
by simon＠justconnect.ie 24 Jun '21

24 Jun '21

Hi All, I've had to migrate a Windows Server 2003 R2 VM from VMWare to oVirt which I have successfully managed to get running. The problem I have is if I try to reboot from the OS I receive the following message after the VM shuts down but doesn't reboot: "Exit message: Lost connection with qemu process." Also any attempt to either shutdown or reboot from oVirt Manager has no effect. I realize that this OS is not supported in the current oVirt version, but is there something I am missing to get it working 'unsupported' please? Regards Simon...

2 1

Disk (brick) failure on my stack
by Dominique D 24 Jun '21

24 Jun '21

yesterday I had a disk failure on my stack of 3 Ovirt 4.4.1 node on each server I have 3 Bricks (engine, data, vmstore) brick data 4X600Gig raid0. /dev/gluster_vg_sdb/gluster_lv_data mount /gluster_bricks/data brick engine 2X1TB raid1 /dev/gluster_vg_sdc/gluster_lv_engine mount /gluster_bricks/engine brick vmstore 2X1TB raid1 /dev/gluster_vg_sdc/gluster_lv_vmstore mount /gluster_bricks/vmstore Everything was configured by the gui (hyperconverge and hosted-engine) It is the raid0 of the 2nd server who broke. all VMs were automatically moved to the other two servers, I haven't lost any data. the host2 is now in maintenance mode. I am going to buy 4 new SSD disks to replace the 4 disks of the defective raid0. When I'm going to erase the faulty raid0 and create the new raid with the new disks on the raid controler, how do I add in ovirt so that they resynchronize with the other bricks data? Status of volume: data Gluster process TCP Port RDMA Port Online Pid ------------------------------------------------------------------------------ Brick 172.16.70.91:/gluster_bricks/data/dat a 49153 0 Y 79168 Brick 172.16.70.92:/gluster_bricks/data/dat a N/A N/A N N/A Brick 172.16.70.93:/gluster_bricks/data/dat a 49152 0 Y 3095 Self-heal Daemon on localhost N/A N/A Y 2528 Self-heal Daemon on 172.16.70.91 N/A N/A Y 225523 Self-heal Daemon on 172.16.70.93 N/A N/A Y 3121

5 5

Is there a slack channel for oVirt project?
by Jesse Hu 23 Jun '21

23 Jun '21

Hi folks, Is there a slack channel for oVirt project? and is the #ovirt channel on irc.oftc.net server still active? I'd like to learn how oVirt project can be used for building IaaS platform, and whether oVirt community is active to provide support for questions. Thanks a lot.

2 2

Problems moving vm & templates between oVirt 4.3 & 4.4
by Guillaume Pavese 23 Jun '21

23 Jun '21

On ovirt 4.4.6, I created a VM and made a template from it. I would like to copy them to oVirt 4.3.7 & 4.3.10 DCs - I saw that Export Domain is deprecated. I tried exporting the VM & template to an Export Domain anyway but, after attaching the Export DOmain on my ovirt 4.3.7 DC, both VM and Template imports failed. The Template import failed immediately without any errors visible in the UI, The VM import failed with the message "General command validation failure." - I tried to do it through a Data Domains as recommended, but: If created on oVirt 4.4.6, I get a Format V5 DataDomain that my oVirt 4.3.7 refuses to import. If created first on the oVirt 4.3 DC, I get a Format V4 Domain. But then importing it on the oVirt 4.4 DC, I get the message: "Approving this operation will upgrade the Storage Domain format from 'V4' to 'V5'. Note that you will not be able to attach it back to an older Data Center." In "Administration > Providers" everything seems supported, from XEN / KVM and even VMware (we have used all three with some success). However oVirt is the obvious missing option... I still have to try "Export as OVA", is that the only supported way? Guillaume Pavese Ingénieur Système et Réseau Interactiv-Group -- Ce message et toutes les pièces jointes (ci-après le “message”) sont établis à l’intention exclusive de ses destinataires et sont confidentiels. Si vous recevez ce message par erreur, merci de le détruire et d’en avertir immédiatement l’expéditeur. Toute utilisation de ce message non conforme a sa destination, toute diffusion ou toute publication, totale ou partielle, est interdite, sauf autorisation expresse. L’internet ne permettant pas d’assurer l’intégrité de ce message . Interactiv-group (et ses filiales) décline(nt) toute responsabilité au titre de ce message, dans l’hypothèse ou il aurait été modifié. IT, ES, UK. <https://interactiv-group.com/disclaimer.html>

3 6

Is there a way to find the creation date of a Virtual Machines from Ovirt Manager
by k.gunasekhar＠non.keysight.com 22 Jun '21

22 Jun '21

Is there a way to find the creation date of a Virtual Machines from Ovirt Manager command line or psql

7 9

Import Ge0-Replicated Storage Domain fails
by simon＠justconnect.ie 22 Jun '21

22 Jun '21

Hi All, I have 2 independent Hyperconverged Sites/Data Centers. Site A has a GlusterFS Replica 3 + Arbiter Volume that is Storage Domain data2 This Volume is Geo-Replicated to a Replica 3 + Arbiter Volume at Site B called data2_bdt I have simulated a DR event and now want to import the Ge0-Replicated volume data2_bdt as a Storage Domain on Site B. Once imported I need to import the VMs on this volume to run in Site B. The Geo-Replication now works perfectly (thanks Strahil) but I haven't been able to import the Storage Domain. Please can someone point me in the right direction or documentation on how this can be achieved. Kind Regards Shimme...

6 9

importing vm's from storage pool from 4.1.6.2-1 in to 4.4.6 fails due to lingering snapshot configuration in source
by Charles Kozler 22 Jun '21

22 Jun '21

I know the subject is a bit wordy but let me try to explain I have a 4.1 installation that I am migrating to 4.4. I placed the storage domain into maintenance and then rsync'ed it to the storage I am using for 4.4. In 4.4 I import the domain and it comes in fine, however, when trying to import some VM's it fails because it says it cannot find a disk. The disk ID's I cannot find anywhere in 4.1 or 4.4 so I opened OVF_STORE after upgrading the pool in 4.4 and look at the ovf file for some of the VM's that are failing to import I see this in the ovf configuration file - <Section xsi:type="ovf:SnapshotsSection_Type"> <Snapshot ovf:id="e300fa3b-eee4-4b96-9103-45115081db57"> <Type>ACTIVE</Type> <Description>Active VM</Description> <CreationDate>2019/12/19 16:47:48</CreationDate> <Memory>07d3447c-c640-4163-9cf1-74ce126d702a,59b5cfdf-015b-0333-004b-000000000397,8c48ea33-dc34-403a-90d2-a3e78776404c,1757809b-9685-4315-a92e-3ea82dc6d8a8,94a2c2b3-e02e-4b05-80eb-6f4b7a9701e7,248a9fd1-61f0-4c5a-b6ab-4630d433c6fa</Memory> </Snapshot> </Section> </Content> </ovf:Envelope> These are the disk ID's I can see failing to import in engine.log I am aware that importing a VM cannot support snapshots and have found multiple mailing list posts around this, however, I do not have any snapshots visible in 4.1 UI. I also tried modifying OVF_STORE by untar'ing it and editing the ovf files directly, however, this does not work as it ends up overwritten by ovirt with the previous configuration Any ideas? As noted, I cannot see any snapshots listed in 4.1 source pool so I therefore cannot remove this stale configuration from the source and upon importing in to 4.4 it fails because it cannot find the disks I tried import partial and that still fails which to me seems like a bug because the idea of the import partial is to still register the VM even if it cant find disks I also tried scanning domain for disks and update OVF's in the UI and it does not help anything -- *Notice to Recipient*: https://www.fixflyer.com/disclaimer <https://www.fixflyer.com/disclaimer>

2 1