- Users - oVirt List Archives

oVirt 4.2 alpha upgrade failed
by Maton, Brett 29 Sep '17

29 Sep '17

Upgrading from oVirt 4.1.7 hosted-engine VM: 4GB RAM hosted-engine setup failed, setup log shows this error: Running upgrade sql script '/usr/share/ovirt-engine/dbscripts/upgrade/04_02_0140_add_max_memory_constraint.sql'... 2017-09-28 16:56:22,951+0100 DEBUG otopi.plugins.ovirt_engine_setup.ovirt_engine.db.schema plugin.execute:926 execute-output: ['/usr/share/ovirt-engine/dbscripts/schema.sh', '-s', 'localhost', '-p', '5432', '-u', 'engine', '-d', 'engine', '-l', '/var/log/ovirt-engine/setup/ovirt-engine-setup-20170928164338-0rkilb.log', '-c', 'apply'] stderr: psql:/usr/share/ovirt-engine/dbscripts/upgrade/04_02_0140_add_max_memory_constraint.sql:2: ERROR: check constraint "vm_static_max_memory_size_lower_bound" is violated by some row FATAL: Cannot execute sql command: --file=/usr/share/ovirt-engine/dbscripts/upgrade/04_02_0140_add_max_memory_constraint.sql 2017-09-28 16:56:22,951+0100 ERROR otopi.plugins.ovirt_engine_setup.ovirt_engine.db.schema schema._misc:374 schema.sh: FATAL: Cannot execute sql command: --file=/usr/share/ovirt-engine/dbscripts/upgrade/04_02_0140_add_max_memory_constraint.sql 2017-09-28 16:56:22,952+0100 DEBUG otopi.context context._executeMethod:143 method exception Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/otopi/context.py", line 133, in _executeMethod method['method']() File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/db/schema.py", line 376, in _misc raise RuntimeError(_('Engine schema refresh failed')) RuntimeError: Engine schema refresh failed What's the minimum RAM required now ? Regards, Brett

4 13

Failure while using ovirt-image-template role
by Marc Seward 29 Sep '17

29 Sep '17

Hi, I'm trying to use the ovirt-image-template role to import a Glance image as a template into ovirt and I'm running into this error with python-ovirt-engine-sdk4-4.1.6-1.el7ev.x86_64 I'd appreciate any pointers. TASK [ovirt.ovirt-ansible-roles/roles/ovirt-image-template : Find data domain] ************************************************************************************************************************************ task path: /etc/ansible/roles/ovirt.ovirt-ansible-roles/roles/ovirt-image-template/tasks/glance_image.yml:21 fatal: [localhost]: FAILED! => { "failed": true, "msg": "You need to install \"jmespath\" prior to running json_query filter" } TASK [ovirt.ovirt-ansible-roles/roles/ovirt-image-template : Logout from oVirt] ***********************************************

3 2

[ANN] oVirt 4.2.0 First Alpha Release is now available for testing
by Sandro Bonazzola 29 Sep '17

29 Sep '17

The oVirt Project is pleased to announce the availability of the First Alpha Release of oVirt 4.2.0, as of September 28th, 2017 This is pre-release software. This pre-release should not to be used in production. Please take a look at our community page[1] to learn how to ask questions and interact with developers and users. All issues or bugs should be reported via oVirt Bugzilla[2]. This update is the first alpha release of the 4.2.0 version. This release brings more than 120 enhancements and more than 670 bug fixes, including more than 260 high or urgent severity fixes, on top of oVirt 4.1 series. What's new in oVirt 4.2.0? - The Administration Portal has been completely redesigned using Patternfly, a widely adopted standard in web application design. It now features a cleaner, more intuitive design, for an improved user experience. - There is an all-new VM Portal for non-admin users. - A new High Performance virtual machine type has been added to the New VM dialog box in the Administration Portal. - Open Virtual Network (OVN) adds support for Open vSwitch software defined networking (SDN). - oVirt now supports Nvidia vGPU. - The ovirt-ansible-roles package helps users with common administration tasks. - Virt-v2v now supports Debian/Ubuntu based VMs. For more information about these and other features, check out the oVirt 4.2.0 blog post <https://ovirt.org/blog/2017/09/introducing-ovirt-4.2.0/>. This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 7.4 or later * CentOS Linux (or similar) 7.4 or later This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 7.4 or later * CentOS Linux (or similar) 7.4 or later * oVirt Node 4.2 (available for x86_64 only) See the release notes draft [3] for installation / upgrade instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is already available. - An async release of oVirt Node will follow soon. Additional Resources: * Read more about the oVirt 4.2.0 release highlights: http://www.ovirt.org/release/4.2.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] https://www.ovirt.org/community/ [2] https://bugzilla.redhat.com/enter_bug.cgi?classification=oVirt [3] http://www.ovirt.org/release/4.2.0/ [4] http://resources.ovirt.org/pub/ovirt-4.2-pre/iso/ -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> <http://www.teraplan.it/redhat-osd-2017/>

3 2

Performance of cloning
by Gianluca Cecchi 29 Sep '17

29 Sep '17

Hello, I'm on 4.1.5 and I'm cloning a snapshot of a VM with 3 disks for a total of about 200Gb to copy The target I choose is on a different domain than the source one. They are both FC storage domains, with the source on SSD disks and the target on SAS disks. The disks are preallocated Now I have 3 processes of kind: /usr/bin/qemu-img convert -p -t none -T none -f raw /rhev/data-center/59b7af54-0155-01c2-0248-000000000195/fad05d79-254d-4f40-8201-360757128ede/images/8f62600a-057d-4d59-9655-631f080a73f6/21a8812f-6a89-4015-a79e-150d7e202450 -O raw /rhev/data-center/mnt/blockSD/6911716c-aa99-4750-a7fe-f83675a2d676/images/c3973d1b-a168-4ec5-8c1a-630cfc4b66c4/27980581-5935-4b23-989a-4811f80956ca but despite capabilities it seems it is copying using very low system resources. I see this both using iotop and vmstat vmstat 3 gives: ----io---- -system-- ------cpu----- bi bo in cs us sy id wa st 2527 698 3771 29394 1 0 89 10 0 iotop -d 5 -k -o -P gives: Total DISK READ : 472.73 K/s | Total DISK WRITE : 17.05 K/s Actual DISK READ: 1113.23 K/s | Actual DISK WRITE: 55.86 K/s PID PRIO USER DISK READ> DISK WRITE SWAPIN IO COMMAND 2124 be/4 sanlock 401.39 K/s 0.20 K/s 0.00 % 0.00 % sanlock daemon 2146 be/4 vdsm 50.96 K/s 0.00 K/s 0.00 % 0.00 % python /usr/share/o~a-broker --no-daemon 30379 be/0 root 7.06 K/s 0.00 K/s 0.00 % 98.09 % lvm vgck --config ~50-a7fe-f83675a2d676 30380 be/0 root 4.70 K/s 0.00 K/s 0.00 % 98.09 % lvm lvchange --conf~59-b931-4eb61e43b56b 30381 be/0 root 4.70 K/s 0.00 K/s 0.00 % 98.09 % lvm lvchange --conf~83675a2d676/metadata 30631 be/0 root 3.92 K/s 0.00 K/s 0.00 % 98.09 % lvm vgs --config d~f6-9466-553849aba5e9 2052 be/3 root 0.00 K/s 2.35 K/s 0.00 % 0.00 % [jbd2/dm-34-8] 6458 be/4 qemu 0.00 K/s 4.70 K/s 0.00 % 0.00 % qemu-kvm -name gues~x7 -msg timestamp=on 2064 be/3 root 0.00 K/s 0.00 K/s 0.00 % 0.00 % [jbd2/dm-32-8] 2147 be/4 root 0.00 K/s 4.70 K/s 0.00 % 0.00 % rsyslogd -n 9145 idle vdsm 0.00 K/s 0.59 K/s 0.00 % 24.52 % qemu-img convert -p~23-989a-4811f80956ca 13313 be/4 root 0.00 K/s 0.00 K/s 0.00 % 0.00 % [kworker/u112:3] 9399 idle vdsm 0.00 K/s 0.59 K/s 0.00 % 24.52 % qemu-img convert -p~51-9c8c-8d9aaa7e8f58 1310 ?dif root 0.00 K/s 0.00 K/s 0.00 % 0.00 % multipathd 3996 be/4 vdsm 0.00 K/s 0.78 K/s 0.00 % 0.00 % python /usr/sbin/mo~c /etc/vdsm/mom.conf 6391 be/4 root 0.00 K/s 0.00 K/s 0.00 % 0.00 % [kworker/u112:0] 2059 be/3 root 0.00 K/s 3.14 K/s 0.00 % 0.00 % [jbd2/dm-33-8] Is it expected? Any way to speed up the process? Thanks, Gianluca

3 5

[ovirt-announce][ANN] oVirt 4.1.7 Second Release Candidate is now available
by Lev Veyde 28 Sep '17

28 Sep '17

The oVirt Project is pleased to announce the availability of the Second Release Candidate of oVirt 4.1.7, as of September 28th, 2017 This update is the seventh in a series of stabilization updates to the 4.1 series. Starting from 4.1.5 oVirt supports libgfapi [5]. Using libgfapi provides a real performance boost for ovirt when using GlusterFS . Due to a known issue [6], using this will break live storage migration. This is expected to be fixed soon. If you do not use live storage migration you can give it a try. Use [7] for more details on how to enable it. This release is available now for: * Red Hat Enterprise Linux 7.4 or later * CentOS Linux (or similar) 7.4 or later This release supports Hypervisor Hosts running: * Red Hat Enterprise Linux 7.4 or later * CentOS Linux (or similar) 7.4 or later * oVirt Node 4.1 See the release notes draft [3] for installation / upgrade instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is already available - oVirt Live is already available[4] - oVirt Node is already available[4] Additional Resources: * Read more about the oVirt 4.1.7 release highlights: http://www.ovirt.org/release/4.1. <http://www.ovirt.org/release/4.1.7/>7 <http://www.ovirt.org/release/4.1.7/>/ <http://www.ovirt.org/release/4.1.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] https://www.ovirt.org/community/ [2] https://bugzilla.redhat.com/enter_bug.cgi?classification=oVirt [3] http://www.ovirt.org/release/4.1. <http://www.ovirt.org/release/4.1.7/>7 <http://www.ovirt.org/release/4.1.7/>/ <http://www.ovirt.org/release/4.1.7/> [4] http://resources.ovirt.org/pub/ovirt-4.1-pre/iso/ [5] http://staged-gluster-docs.readthedocs.io/en/release3.7.0beta1/Features/lib… [6] https://bugzilla.redhat.com/show_bug.cgi?id=1306562 [7] http://www.ovirt.org/develop/release-management/features/storage/glusterfs-… Thanks in advance, -- Lev Veyde 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

Renaming or deleting ovirtmgmt
by Gianluca Cecchi 28 Sep '17

28 Sep '17

Hello, I notice that in a cluster I can create a new network and then select it as the Management network, but at the same time the default "ovirtmgmt" logical network in "Manage Networks" is always checked as both as "Assign" and "Required" and also grayed so that I cannot change anything of it... and any host in this cluster must have ovirtmgmt even if it doesn't use it at all.. Is there any RFE to change this model? So for example to be able to change its name or delete it after we have defined a new network as management one. It seems something similar to the concept of the"Default" DC that now we can finally rename and /or delete Gianluca

3 6

Huge pages in guest with newer oVirt versions
by Gianluca Cecchi 28 Sep '17

28 Sep '17

Hello, I would like to go again in deep with what preliminary tested and already discussed here: http://lists.ovirt.org/pipermail/users/2017-April/081320.html I'm testing an oVirt node in 4.1.6-pre I don't find the vdsm hook for huge pages; doing a search I get these: vdsm-hook-ethtool-options.noarch : Allow setting custom ethtool options for vdsm controlled nics vdsm-hook-fcoe.noarch : Hook to enable FCoE support vdsm-hook-openstacknet.noarch : OpenStack Network vNICs support for VDSM vdsm-hook-vfio-mdev.noarch : Hook to enable mdev-capable devices. vdsm-hook-vhostmd.noarch : VDSM hook set for interaction with vhostmd vdsm-hook-vmfex-dev.noarch : VM-FEX vNIC support for VDSM Did anything change between 4.1.1 and 4.1.5/4.1.6? I'm making preliminary tests with an Oracle RDBMS and HammerDB in both a physical server and a "big" VM inside another same hw server configured with oVirt. Results are not bad, but I would like to see having huge pages inside the guest how could change results. Just for reference: The 2 Physical server are blades with each one: 2 sockets, each one with 14 cores and ht enabled, so in total 56 computational threads 256Gb ram huge pages enabled VM configured with this virtual hw on one of them: 2 sockets, each one with 6 cores and ht so in total 24 computational threads 64Gb ram no huge pages at the moment Oracle SGA is 32Gb on both physical rdbms and virtual one. Thanks for any insight to test huge pages in guest Gianluca

3 3

oVirt Node update question
by Matthias Leopold 28 Sep '17

28 Sep '17

hi, i still don't completely understand the oVirt Node update process and the involved rpm packages. We have 4 nodes, all running oVirt Node 4.1.3. Three of them show as available updates 'ovirt-node-ng-image-update-4.1.6-0.1.rc1.20170823083853.gitd646d2f.el7.centos' (i don't want run release candidates), one of them shows 'ovirt-node-ng-image-update-4.1.5-1.el7.centos' (this is what i like). The node that doesn't want to upgrade to '4.1.6-0.1.rc1' lacks the rpm package 'ovirt-node-ng-image-update-4.1.3-1.el7.centos.noarch', only has 'ovirt-node-ng-image-update-placeholder-4.1.3-1.el7.centos.noarch'. Also the version of ovirt-node-ng-nodectl is '4.1.3-0.20170709.0.el7' instead of '4.1.3-0.20170705.0.el7'. This node was the last one i installed and never made a version update before. I only began using oVirt starting with 4.1, but already completed minor version upgrades of oVirt nodes. IIRC this 'mysterious' ovirt-node-ng-image-update package comes into place when updating a node for the first time after initial installation. Usually i wouldn't care about all of this, but now i have this RC update situation that i don't want. How is this supposed to work? How can i resolve it? thx matthias

2 8

Is this guide still valid?data-warehouse
by Arman Khalatyan 28 Sep '17

28 Sep '17

Dear Ovirt documents maintainers is this document still valid? https://www.ovirt.org/documentation/data-warehouse/Data_Warehouse_Guide/ When I go one level up it is bringing an empty page: https://www.ovirt.org/documentation/data-warehouse/ Thanks, Arman.

3 7

Qemu prevents vm from starting up properly
by M R 28 Sep '17

28 Sep '17

Hello! I have followed instructions in https://www.ovirt.org/ develop/developer-guide/vdsm/hook/qemucmdline/ After adding any command for qemu cmdline, vm will try to start, but will immediately shutdown. Is this a bug? or is the information in the link insufficient? If it would be possible to confirm this and if there's a way to fix, I would really like to have step by step guide of how to get this working. thank you, Mikko

2 5