- Users - oVirt List Archives

Windows 10 Pro 64 (1909) crashes when migrating
by Maton, Brett 11 Apr '20

11 Apr '20

I recently added a Windows 10 Pro 64 bit (release 1909) VM, and I'm seeing a lot of failures when oVirt tries to move the VM to another host (triggered by load balancing), These errors are showing up in the UI event log Migration failed (VM: <vm label>, Source: <host 1>, Destination: <host 2>). Followed by: VM <host> is down with error. Exit message: Lost connection with qemu process. Google returned some references to 'options kvm ignore_msrs=1' which I've added to /etc/modprobe/d/kvm.conf and restarted the hosts but that doesn't appear to have made a difference. Is this a known issue with Windows 10 guests?

3 7

Firewall GARP not reachable to VM
by k.betsis＠gmail.com 10 Apr '20

10 Apr '20

Hi all Does anyone know how i can allow my Firewall VM cluster act as the default gateway to VMs within the same network? I've configured the GARP functionality on the OPNSENSE firewalls (PFSENSE fork). VMs within the same network can ping the firewall IP addresses successfully but not the GARP IP. The ovirt network has been configured with the MAC Address Anti-spoofing to false. One firewall has been configured with virtio network drivers and the with e1000 both exhibiting the same behavior. Currently all VMs have been configured with a default gateway the primary firewall. Network workarounds using BGP and attributes can work, but are way to complicate to streamline for all VMs when a simple VRRP can do the job. Any ideas what i am missing?

2 1

Data domain down due to space crunch
by Crazy Ayansh 10 Apr '20

10 Apr '20

Hi Guys, I am using Ovirt 4.3.7 in my environment.I am using servers local storage for data domains. Today one of the servers data domain got full and due to this my VMs paused. [image: image.png] Now i am unable to export my VM as the storage in ovirt is down.....What should i do now.....any suggestions.....? Thanks

2 2

Ovirt and Dell Compellent in ISCSI
by dalmasso＠cines.fr 10 Apr '20

10 Apr '20

hi all, we use ovirt 4.3 on dell server r640 runing centos 7.7 and a storage bay Dell Compellent SCv3020 in ISCSI. We use two 10gb interfaces for iSCSI connection on each dell server. If we configure ISCSI connection directly from web IU, we can’t specify the two physical ethernet interface , and there are missing path . (only 4 path on 8) So, on the shell of hypervisor we use this commands for configure the connections : iscsiadm -m iface -I em1 --op=new # 1st ethernet interface iscsiadm -m iface -I p3p1 --op=new # 2d ethernet interface iscsiadm -m discovery -t sendtargets -p xx.xx.xx.xx iscsiadm -m node -o show iscsiadm -m node --login after this, on the web IU we can connect our LUN with all path. Also, I don’t understand how to configure multipath in the web UI . By defaut the configuration is in failover : multipath -ll : 36000d3100457e4000000000000000005 dm-3 COMPELNT,Compellent Vol size=500G features='1 queue_if_no_path' hwhandler='0' wp=rw `-+- policy='service-time 0' prio=1 status=active |- 23:0:0:1 sdb 8:16 active ready running |- 24:0:0:1 sdd 8:48 active ready running |- 25:0:0:1 sdc 8:32 active ready running |- 26:0:0:1 sde 8:64 active ready running |- 31:0:0:1 sdf 8:80 active ready running |- 32:0:0:1 sdg 8:96 active ready running |- 33:0:0:1 sdh 8:112 active ready running |- 34:0:0:1 sdi 8:128 active ready running I think round robind or another configuration will be more performent. So can we made this configuration , select physical interface and configure multipath in web UI ? for easyly maintenance and adding other server ? Thank you. Sylvain.

3 4

oVirt 4.4.0 Beta release refresh is now available for testing
by Sandro Bonazzola 09 Apr '20

09 Apr '20

oVirt 4.4.0 Beta release refresh is now available for testing The oVirt Project is excited to announce the availability of the beta release of oVirt 4.4.0 refresh for testing, as of April 9th, 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 Beta release. The oVirt Project makes no guarantees as to its suitability or usefulness. This pre-release must not to be used in production. In particular, please note that upgrades from 4.3 and future upgrades from this beta to the final 4.4 release from this version are not supported. Some of the features included in oVirt 4.4.0 Beta 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. Known Issues - ovirt-imageio development is still in progress. In this beta you can’t upload images to data domains using the engine web application. You can still copy iso images into the deprecated ISO domain for installing VMs or upload and download to/from data domains is fully functional via the REST API and SDK. For uploading and downloading via the SDK, please see: - https://github.com/oVirt/ovirt-engine-sdk/blob/master/sdk/examples/upload_d… - https://github.com/oVirt/ovirt-engine-sdk/blob/master/sdk/examples/download… Both scripts are standalone command line tool, try --help for more info. 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 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 Beta? - 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 only for file based storage. iSCSI/FC storage do not support 4k disks yet. - 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 * CentOS Linux (or similar) 8.1 This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 8.1 * CentOS Linux (or similar) 8.1 * 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/ -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/>* <https://www.redhat.com/en/summit?sc_cid=7013a000002D2QxAAK>* *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

2 1

access to QEMU monitor
by Matthias Leopold 09 Apr '20

09 Apr '20

Hi, for educational purposes I'm trying to access the QEMU monitor of oVirt VMs. Can someone tell me how this can be done? Connecting to the unix socket with socat doesn't work, probably because it's not started with "server,nowait". Can the QEMU monitor be reached with the SPICE console? thx Matthias

1 0

UI lockup
by Shareef Jalloq 08 Apr '20

08 Apr '20

Hi, when browsing to the admin portal of the Engine, I get a popup: Uncaught exception occurred. Please try reloading the page. Details: (NS_ERROR_STORAGE_BUSY). And the ui.log has the error at the end of the mail. What gives? Shareef. 2020-04-07 15:54:12,255Z ERROR [org.ovirt.engine.ui.frontend.server.gwt.OvirtRemoteLoggingService] (default task-66) [] Permutation name: 1AD871380C0F85A90CBF764A6CF6663F 2020-04-07 15:54:12,255Z ERROR [org.ovirt.engine.ui.frontend.server.gwt.OvirtRemoteLoggingService] (default task-66) [] Uncaught exception: com.google.gwt.core.client.JavaScriptException: (NS_ERROR_STORAGE_BUSY) : at Unknown.loadFromLocalStorage( https://ovirt-engine.phoelex.com/ovirt-engine/webadmin/theme/00-ovirt.brand… ) at Unknown.init( https://ovirt-engine.phoelex.com/ovirt-engine/webadmin/theme/00-ovirt.brand… ) at Unknown.fn.setupVerticalNavigation( https://ovirt-engine.phoelex.com/ovirt-engine/webadmin/theme/00-ovirt.brand… ) at org.ovirt.engine.ui.webadmin.section.main.view.MainSectionView$lambda$0$Type.execute(MainSectionView.java:48) at com.google.gwt.core.client.impl.SchedulerImpl.runScheduledTasks(SchedulerImpl.java:167) [gwt-servlet.jar:] at com.google.gwt.core.client.impl.SchedulerImpl.$flushPostEventPumpCommands(SchedulerImpl.java:338) [gwt-servlet.jar:] at com.google.gwt.core.client.impl.SchedulerImpl$Flusher.execute(SchedulerImpl.java:76) [gwt-servlet.jar:] at com.google.gwt.core.client.impl.SchedulerImpl.execute(SchedulerImpl.java:140) [gwt-servlet.jar:] at com.google.gwt.core.client.impl.Impl.apply(Impl.java:236) [gwt-servlet.jar:] at com.google.gwt.core.client.impl.Impl.entry0(Impl.java:275) [gwt-servlet.jar:] at Unknown.Tu/<( https://ovirt-engine.phoelex.com/ovirt-engine/webadmin/?locale=en_US line 9 > scriptElement) at Unknown.d( https://ovirt-engine.phoelex.com/ovirt-engine/webadmin/?locale=en_US line 9 > scriptElement) at Unknown.anonymous(Unknown)

2 2

Cluster Console Encryption
by Tommaso - Shellrent 08 Apr '20

08 Apr '20

Hi to all. We are tryng to manage the value of "Enable VNC Encryption" on the cluster via ansible[or any automatic mode]. Someone got any hint? Regards -- -- Shellrent - Il primo hosting italiano Security First *Tommaso De Marchi* /COO - Chief Operating Officer/ Shellrent Srl Via dell'Edilizia, 19 - 36100 Vicenza Tel. 0444321155 <tel:+390444321155> | Fax 04441492177

1 0

Cannot upload image
by Green, Jacob Allen /C 07 Apr '20

07 Apr '20

Hello, I am in a precarious situation where I need to upload an image to the storage domain, I understand that normally you would achieve this via the upload button on the storage domain > Disks tab. However I currently do not have the ability to import the certificate. Is there a way from command line either on the RHV manager or otherwise to upload a qcow2 without using the image upload through the GUI? Thank you.

3 4

Gluster problems with new disk and device name change and overlap
by Gianluca Cecchi 07 Apr '20

07 Apr '20

Hi, I have configured a single host HCI environment through the GUI wizard in 4.3.9. Initial setup has thai layout of disks, as seen by the operating system: /dev/sda -> for ovirt-node-ng OS /dev/nvme0n1 --> for gluster, engine and data volumes /dev/nvme1n1 --> for gluster, vmstore volume So far so good and all is ok. I notice that, even with single path internal disks, at the end oVirt configures the gluster disks as multipath devices and LVM2 PV structure on top of the multipath devices. Is this for "code optimization" at low level or what is the rationale for that, as with Gluster normally you do use local disks and so single path? Multipath structure generated: [root@ovirt ~]# multipath -l nvme.8086-50484b53373530353031325233373541474e-494e54454c205353 dm-5 NVME,INTEL SSDPED1K375GA size=349G features='1 queue_if_no_path' hwhandler='0' wp=rw `-+- policy='service-time 0' prio=0 status=active `- 0:0:1:0 nvme0n1 259:0 active undef running eui.01000000010000005cd2e4b5e7db4d51 dm-6 NVME,INTEL SSDPEDKX040T7 size=932G features='1 queue_if_no_path' hwhandler='0' wp=rw `-+- policy='service-time 0' prio=0 status=active `- 2:0:1:0 nvme1n1 259:2 active undef running [root@ovirt ~]# Anyway, on top of the multipah devices On /dev/nvme0n1: gluster_vg_nvme0n1 volume group with gluster_lv_data and gluster_lv_engine On /dev/nvme1n1 gluster_vg_nvme1n1 volume group with gluster_lv_vmstore logical volume The problem arises when I add another nvme disk, that, occupying a PCI slot, it seems has always higher priority of the previous /dev/nvme1n1 disk and so takes its name. After booting the node: old nvme0n1 --> unmodified name old nvme1n1 --> becomes nvme2n1 new disk --> gets name nvme1n1 From a funcional point of view I have no problems apart LVM warnings I send below and also because the xfs entries in fstab are with UUID: UUID=fa5dd3cb-aeef-470e-b982-432ac896d87a /gluster_bricks/engine xfs inode64,noatime,nodiratime 0 0 UUID=43bed7de-66b1-491d-8055-5b4ef9b0482f /gluster_bricks/data xfs inode64,noatime,nodiratime 0 0 UUID=b81a491c-0a4c-4c11-89d8-9db7fe82888e /gluster_bricks/vmstore xfs inode64,noatime,nodiratime 0 0 lvs commands get: [root@ovirt ~]# lvs WARNING: Not using device /dev/nvme0n1 for PV eYfuXw-yaPd-cMUE-0dnA-tVON-uZ9g-5x4BDp. WARNING: Not using device /dev/nvme2n1 for PV O43LFq-46Gc-RRgS-Sk1F-5mFZ-Qw4n-oxXgJl. WARNING: PV eYfuXw-yaPd-cMUE-0dnA-tVON-uZ9g-5x4BDp prefers device /dev/mapper/nvme.8086-50484b53373530353031325233373541474e-494e54454c20535344504544314b3337354741-00000001 because device is used by LV. WARNING: PV O43LFq-46Gc-RRgS-Sk1F-5mFZ-Qw4n-oxXgJl prefers device /dev/mapper/eui.01000000010000005cd2e4e359284f51 because device is used by LV. LV VG Attr LSize Pool Origin ... Or, for the old nvme1n1 disk, now nvme2n1 multipath device: [root@ovirt ~]# pvdisplay /dev/mapper/eui.01000000010000005cd2e4e359284f51 WARNING: Not using device /dev/nvme0n1 for PV eYfuXw-yaPd-cMUE-0dnA-tVON-uZ9g-5x4BDp. WARNING: Not using device /dev/nvme2n1 for PV O43LFq-46Gc-RRgS-Sk1F-5mFZ-Qw4n-oxXgJl. WARNING: PV eYfuXw-yaPd-cMUE-0dnA-tVON-uZ9g-5x4BDp prefers device /dev/mapper/nvme.8086-50484b53373530353031325233373541474e-494e54454c20535344504544314b3337354741-00000001 because device is used by LV. WARNING: PV O43LFq-46Gc-RRgS-Sk1F-5mFZ-Qw4n-oxXgJl prefers device /dev/mapper/eui.01000000010000005cd2e4e359284f51 because device is used by LV. --- Physical volume --- PV Name /dev/mapper/eui.01000000010000005cd2e4e359284f51 VG Name gluster_vg_nvme1n1 PV Size 931.51 GiB / not usable 1.71 MiB Allocatable yes (but full) PE Size 4.00 MiB Total PE 238467 Free PE 0 Allocated PE 238467 PV UUID O43LFq-46Gc-RRgS-Sk1F-5mFZ-Qw4n-oxXgJl [root@ovirt ~]# I'm able to create PV on top of the new multipath device detected by the system (see the nvme1n1 of the underlying disk): eui.01000000010000005cd2e4b5e7db4d51 dm-6 NVME,INTEL SSDPEDKX040T7 size=3.6T features='1 queue_if_no_path' hwhandler='0' wp=rw `-+- policy='service-time 0' prio=0 status=active `- 1:0:1:0 nvme1n1 259:1 active undef running [root@ovirt ~]# pvcreate --dataalignment 256K /dev/mapper/eui.01000000010000005cd2e4b5e7db4d51 WARNING: Not using device /dev/nvme0n1 for PV eYfuXw-yaPd-cMUE-0dnA-tVON-uZ9g-5x4BDp. WARNING: Not using device /dev/nvme2n1 for PV O43LFq-46Gc-RRgS-Sk1F-5mFZ-Qw4n-oxXgJl. WARNING: PV eYfuXw-yaPd-cMUE-0dnA-tVON-uZ9g-5x4BDp prefers device /dev/mapper/nvme.8086-50484b53373530353031325233373541474e-494e54454c20535344504544314b3337354741-00000001 because device is used by LV. WARNING: PV O43LFq-46Gc-RRgS-Sk1F-5mFZ-Qw4n-oxXgJl prefers device /dev/mapper/eui.01000000010000005cd2e4e359284f51 because device is used by LV. Physical volume "/dev/mapper/eui.01000000010000005cd2e4b5e7db4d51" successfully created. [root@ovirt ~]# But then I'm unable to create a VG on top of it: [root@ovirt ~]# vgcreate gluster_vg_4t /dev/mapper/eui.01000000010000005cd2e4b5e7db4d51 WARNING: Not using device /dev/nvme0n1 for PV eYfuXw-yaPd-cMUE-0dnA-tVON-uZ9g-5x4BDp. WARNING: Not using device /dev/nvme1n1 for PV 56ON99-hFFP-cGpZ-g4MX-GfjW-jXeE-fKZVG9. WARNING: Not using device /dev/nvme2n1 for PV O43LFq-46Gc-RRgS-Sk1F-5mFZ-Qw4n-oxXgJl. WARNING: PV eYfuXw-yaPd-cMUE-0dnA-tVON-uZ9g-5x4BDp prefers device /dev/mapper/nvme.8086-50484b53373530353031325233373541474e-494e54454c20535344504544314b3337354741-00000001 because device is used by LV. WARNING: PV 56ON99-hFFP-cGpZ-g4MX-GfjW-jXeE-fKZVG9 prefers device /dev/mapper/eui.01000000010000005cd2e4b5e7db4d51 because device is in dm subsystem. WARNING: PV O43LFq-46Gc-RRgS-Sk1F-5mFZ-Qw4n-oxXgJl prefers device /dev/mapper/eui.01000000010000005cd2e4e359284f51 because device is used by LV. WARNING: Not using device /dev/nvme0n1 for PV eYfuXw-yaPd-cMUE-0dnA-tVON-uZ9g-5x4BDp. WARNING: Not using device /dev/nvme1n1 for PV 56ON99-hFFP-cGpZ-g4MX-GfjW-jXeE-fKZVG9. WARNING: Not using device /dev/nvme2n1 for PV O43LFq-46Gc-RRgS-Sk1F-5mFZ-Qw4n-oxXgJl. WARNING: PV eYfuXw-yaPd-cMUE-0dnA-tVON-uZ9g-5x4BDp prefers device /dev/mapper/nvme.8086-50484b53373530353031325233373541474e-494e54454c20535344504544314b3337354741-00000001 because of previous preference. WARNING: PV 56ON99-hFFP-cGpZ-g4MX-GfjW-jXeE-fKZVG9 prefers device /dev/mapper/eui.01000000010000005cd2e4b5e7db4d51 because of previous preference. WARNING: PV O43LFq-46Gc-RRgS-Sk1F-5mFZ-Qw4n-oxXgJl prefers device /dev/mapper/eui.01000000010000005cd2e4e359284f51 because of previous preference. Cannot use device /dev/mapper/eui.01000000010000005cd2e4b5e7db4d51 with duplicates. [root@ovirt ~]# the same with the "-f" option. I suspect I can solve the problem filtering out /dev/nvme* devices in lvm.conf, but I'm not sure. The OS disk is seen as sda so it should not have problems with this Something like this: filter = [ "r|/dev/nvme|", "a|.*/|" ] And also I am not sure if I have to rebuild the initrd or not in this case and if so what would be the exact sequence of commands to execute. Any suggestions? Thanks in advance, Gianluca

2 2