- Users - oVirt List Archives

Need to register with oVirt community
by Manish Shukla 03 Oct '18

03 Oct '18

Dear Team, Please suggest me how to joined community. I would like to be an implementation of the oVirt infrastructure. Thanks & Regards, Manish SHUKLA

1 0

P2V Tools for oVirt
by Vinícius Ferrão 03 Oct '18

03 Oct '18

Hello, I’m looking for a P2V tool to migrate some physical machine to oVirt. I’m specifically worried about database servers that must be made virtual. What are the recommendations and tested tools? Thanks in advance,

1 0

[OT] transferring kvm raw mage from filesystem to lvm based
by Gianluca Cecchi 02 Oct '18

02 Oct '18

Hello, I have a windows 7 VM that is composed by a raw disk on filesystem on Fedora 28. I would like to transfer this VM to another environment, always based on same version of Fedora 28, but where the storage is configured in virt-manager as lvm based, so similar to what happens in oVirt block based storage domains. I'm trying to figure how to transfer the image. I presume I can create a new LV and then leave some bytes for the LVM header into the created LV and then make a sort of dd with offset? Anyone has any hint? Thanks in advance, Gianluca

3 3

iSCSI multipath with Dell Compellent
by Bernhard Dick 02 Oct '18

02 Oct '18

Hi, I'm trying to achieve iSCSI multipathing with an Dell Compellent SC4020 array. As the Dell Array does not work as an ALUA system it displays available LUNs only on the currently active system (here is a good description that I found: https://niktips.wordpress.com/2016/05/16/dell-compellent-is-not-an-alua-sto… ). As a result I cannot add the currently non-active controller to an iSCSI-Bond (as it does not present the LUNs to oVirt) and so the path to the second controller will not be up. Is there any way to solve this? Regards Bernhard

2 4

Change network interface for hosted engine iSCSI connection
by Bernhard Dick 02 Oct '18

02 Oct '18

Hi, after I changed the network configuration of one of my hosted engine hosts in oVirt I am no longer able to run the ha-daemon on the host. When I run hosted-engine --connect-storage on this host I get the following error: vdsm.client.TimeoutError: Request StoragePool.connectStorageServer with args {'connectionParams': [{'netIfaceName': 'ens1f1', 'port': '3260', 'connection': '192.168.1.1', 'iqn': 'iqn.2002-03.com.compellent:5000 d...', 'user': '', 'tpgt': '0', 'ifaceName': 'ens1f1', 'password': '', 'id': 'cd5fa13f-fbb7-4cc6-a094-4b280dc7b514'}], 'storagepoolID': '00000000-0000-0000-0000-000000000000', 'domainType': 3} timed out after 60 seconds ens1f1 is the network card that has been used earlier for iSCSI, now it should connect via ens1f0. Is there a way to update this configuration for the host? Regards Bernhard

2 2

oVirt Metrics Store installation
by Markus Schaufler 02 Oct '18

02 Oct '18

Hi! I'm having trouble installing the oVirt Metrics Store following this https://www.ovirt.org/develop/release-management/features/metrics/metrics-s… respectively this guide https://www.ovirt.org/develop/release-management/features/metrics/setting-u… When executing the test script ANSIBLE_LOG_PATH=/tmp/ansible-prereq.log ansible-playbook -vvv -e @/root/vars.yaml -i /root/ansible-inventory-origin-39-aio playbooks/prerequisites.yml following error occurs: Using module file /usr/lib/python2.7/site-packages/ansible/modules/packaging/os/yum.py <localhost> EXEC /bin/sh -c '/usr/bin/python && sleep 0' fatal: [localhost]: FAILED! => { "attempts": 3, "changed": false, "invocation": { "module_args": { "allow_downgrade": false, "bugfix": false, "conf_file": null, "disable_gpg_check": false, "disable_plugin": [], "disablerepo": null, "enable_plugin": [], "enablerepo": null, "exclude": null, "install_repoquery": true, "installroot": "/", "list": null, "name": [ "docker", "atomic", "skopeo" ], "security": false, "skip_broken": false, "state": "present", "update_cache": false, "update_only": false, "validate_certs": true } }, "msg": "Error: Package: 1:atomic-1.22.1-22.git5a342e3.el7.x86_64 (centosplus)\n Requires: python-docker-py >= 1.7.2-1\n Available: docker-python-1.4.0-115.el7.x86_64 (centosplus)\n python-docker-py = 1.4.0-115.el7\n Available: python-docker-py-1.10.6-3.el7.noarch (centosplus)\n python-docker-py = 1.10.6-3.el7\n Available: python-docker-py-1.10.6-4.el7.noarch (centosplus)\n python-docker-py = 1.10.6-4.el7\n Available: python2-docker-2.4.2-1.2.el7.noarch (centos-openshift-origin-testing-cbs)\n python-docker-py = 2.4.2-1.2.el7\n Installed: python2-docker-3.3.0-1.el7.noarch (@centos-openshift-origin-testing)\n Not found\n", "rc": 1, "results": [ "2:docker-1.13.1-74.git6e3bb8e.el7.centos.x86_64 providing docker is already installed", "Loaded plugins: fastestmirror\nLoading mirror speeds from cached hostfile\nResolving Dependencies\n--> Running transaction check\n---> Package atomic.x86_64 1:1.22.1-22.git5a342e3.el7 will be installed\n--> Processing Dependency: python-docker-py >= 1.7.2-1 for package: 1:atomic-1.22.1-22.git5a342e3.el7.x86_64\nPackage python-docker-py-1.10.6-4.el7.noarch is obsoleted by python2-docker-3.3.0-1.el7.noarch which is already installed\n--> Processing Dependency: runc for package: 1:atomic-1.22.1-22.git5a342e3.el7.x86_64\n--> Processing Dependency: python-dateutil for package: 1:atomic-1.22.1-22.git5a342e3.el7.x86_64\n--> Processing Dependency: ostree for package: 1:atomic-1.22.1-22.git5a342e3.el7.x86_64\n--> Processing Dependency: gomtree for package: 1:atomic-1.22.1-22.git5a342e3.el7.x86_64\n---> Package skopeo.x86_64 1:0.1.31-1.dev.gitae64ff7.el7.centos will be installed\n--> Running transaction check\n---> Package atomic.x86_64 1:1.22.1-22.git5a342e3.el7 will be installed\n-- > Processing Dependency: python-docker-py >= 1.7.2-1 for package: 1:atomic-1.22.1-22.git5a342e3.el7.x86_64\nPackage python-docker-py-1.10.6-4.el7.noarch is obsoleted by python2-docker-3.3.0-1.el7.noarch which is already installed\n---> Package gomtree.x86_64 0:0.5.0-0.2.git16da0f8.el7 will be installed\n---> Package ostree.x86_64 0:2018.5-1.el7 will be installed\n--> Processing Dependency: libarchive.so.13()(64bit) for package: ostree-2018.5-1.el7.x86_64\n---> Package python-dateutil.noarch 0:1.5-7.el7 will be installed\n---> Package runc.x86_64 0:1.0.0-37.rc5.dev.gitad0f525.el7 will be installed\n--> Processing Dependency: criu for package: runc-1.0.0-37.rc5.dev.gitad0f525.el7.x86_64\n--> Running transaction check\n---> Package atomic.x86_64 1:1.22.1-22.git5a342e3.el7 will be installed\n--> Processing Dependency: python-docker-py >= 1.7.2-1 for package: 1:atomic-1.22.1-22.git5a342e3.el7.x86_64\nPackage python-docker-py-1.10.6-4.el7.noarch is obsoleted by python2-docker-3.3.0-1.el7. noarch which is already installed\n---> Package criu.x86_64 0:3.5-4.el7 will be installed\n--> Processing Dependency: libprotobuf-c.so.1(LIBPROTOBUF_C_1.0.0)(64bit) for package: criu-3.5-4.el7.x86_64\n--> Processing Dependency: libprotobuf-c.so.1()(64bit) for package: criu-3.5-4.el7.x86_64\n--> Processing Dependency: libnet.so.1()(64bit) for package: criu-3.5-4.el7.x86_64\n---> Package libarchive.x86_64 0:3.1.2-10.el7_2 will be installed\n--> Running transaction check\n---> Package atomic.x86_64 1:1.22.1-22.git5a342e3.el7 will be installed\n--> Processing Dependency: python-docker-py >= 1.7.2-1 for package: 1:atomic-1.22.1-22.git5a342e3.el7.x86_64\nPackage python-docker-py-1.10.6-4.el7.noarch is obsoleted by python2-docker-3.3.0-1.el7.noarch which is already installed\n---> Package libnet.x86_64 0:1.1.6-7.el7 will be installed\n---> Package protobuf-c.x86_64 0:1.0.2-3.el7 will be installed\n--> Finished Dependency Resolution\n You could try using --skip-broken to work around the pro blem\n You could try running: rpm -Va --nofiles --nodigest\n" ] } PLAY RECAP ************************************************************************************************************************************************************ localhost : ok=75 changed=6 unreachable=0 failed=1 I already already found out that there might be a bug in some older versions of openshift/ansible but the recent versions should be fine. Thanks for any suggestions on this!

2 1

Trouble to update the ovirt hosts (and solution)
by Arman Khalatyan 02 Oct '18

02 Oct '18

Current cocpit packages are conflicting, which is preventing the host update: .... Transaction check error: file /usr/share/cockpit/networkmanager/manifest.json from install of cockpit-system-176-2.el7.centos.noarch conflicts with file from package cockpit-networkmanager-172-1.el7.noarch file /usr/share/cockpit/networkmanager/po.ca.js.gz from install of cockpit-system-176-2.el7.centos.noarch conflicts with file from package cockpit-networkmanager-172-1.el7.noarch .... Looks like a current packaging of cocpit is wrong, it doesn't upgrade existing version. To solve it simply: yum remove cockpit-networkmanager-172-1.el7.noarch yum clean ;yum update all fixed. arman.

1 0

clarification needed on power management options
by g.vasilopoulos＠uoc.gr 01 Oct '18

01 Oct '18

I would like some clarification on MinFreeMemoryForUnderUtilized and MaxFreeMemoryForOverUtilized. How does that work? it seems the names should be oposite ? so if I have hosts with 64GB ram and I want to consider them over utilized at 48GB used and under utilized at 12GB used, should I set MinFreeMemoryForUnderUtilized=12GB MaxFreeMemoryForOverUtilized=48GB ? is this correct ? Also If ihave hyperconverged setup with 3 hosts having a replica3 storage for the engine and I disable policy management on these hosts, will these hosts be part of the overall utilization regardless if the engine can shut them down ?

1 0

Proxmox - oVirt Migration
by Leo David 01 Oct '18

01 Oct '18

Hello everyone, I have this situation where I need to migrate about 20 vms from Proxmox to oVirt. In this case, its about qcow2 images running on Proxmox. I there a recomended way and procedure for doing this ? Thank you very much ! -- Best regards, Leo David

4 10

liveliness check fails on one host
by g.vasilopoulos＠uoc.gr 01 Oct '18

01 Oct '18

I have an ovirt installation (4.2.6), and I have come accross this issue: Hosted engine can migrate to a certain host say host5. Admin portal is working fine, everything is working fine AFAIK but hosted-engne --vm-status shows "failed livelines check", when engine is on that host, so after a while the engine migrates somewhere else, it not a terrible problem, but it is annoying and I would like to know why is this happening, and if there is a way to fix it On every other host in the cluster this problem does not exists. firewall rules are exactly the same on hosts (in fact they are copied) . Any places to look at? Thank you

2 2