June 2022 - Users - oVirt List Archives

qemu-xhci + win7
by lizhijian＠fujitsu.com 02 Jun '22

02 Jun '22

Hi folks I'm trying to enable usb3.0 for all guest. Currently, win10 and linux guest work well with qemu-xhci device while win7sp1 doesn't I have googled usb3 drivers for win7, but none of them match qemu-xhci. So any body know where i can download this driver for win7 [cid:part1.0dnShC07.J0KywPNb@fujitsu.com] [cid:part2.5HjJSU84.6EjOQ0mv@fujitsu.com] Thanks Zhijian

3 2

4.4.10 -> 4.5.0 upgrade fails
by Sketch 02 Jun '22

02 Jun '22

Just tried to upgrade my engine from 4.4.10.6 -> 4.5.0 on CentOS Stream 8. I relized I missed the step of updating to the very latest version of 4.4.10 around the same time it failed and left things in somewhat of a bad state, so I just built a new Rocky 8.6 host and restored my backup there. Update from 4.4.10.6 to 4.4.10.7 there went fine. 4.4.10.7 -> 4.5.0 fails with the same error, however: [ ERROR ] schema.sh: FATAL: Cannot execute sql command: --file=/usr/share/ovirt-engine/dbscripts/upgrade/pre_upgrade/0000_config.sql [ ERROR ] Failed to execute stage 'Misc configuration': Engine schema refresh failed This appears to be the relevant section of the log: psql:/usr/share/ovirt-engine/dbscripts/upgrade/pre_upgrade/0000_config.sql:22: NOTICE: column "default_value" of relation "vdc_options" already exists, skipping psql:/usr/share/ovirt-engine/dbscripts/upgrade/pre_upgrade/0000_config.sql:1454: ERROR: column "default_value" contains null values CONTEXT: SQL statement "ALTER TABLE vdc_options ALTER COLUMN default_value SET NOT NULL" PL/pgSQL function fn_db_change_column_null(character varying,character varying,boolean) line 10 at EXECUTE FATAL: Cannot execute sql command: --file=/usr/share/ovirt-engine/dbscripts/upgrade/pre_upgrade/0000_config.sql 2022-06-01 01:10:03,015-0700 ERROR otopi.plugins.ovirt_engine_setup.ovirt_engine.db.schema schema._misc:530 schema.sh: FATAL: Cannot execute sql command: --file=/usr/share/ovirt-engine/dbscripts/upgrade/pre_upgrade/0000_config.sql 2022-06-01 01:10:03,016-0700 DEBUG otopi.context context._executeMethod:145 method exception Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/otopi/context.py", line 132, in _executeMethod method['method']() File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/db/schema.py", line 532, in _misc raise RuntimeError(_('Engine schema refresh failed')) RuntimeError: Engine schema refresh failed 2022-06-01 01:10:03,017-0700 ERROR otopi.context context._executeMethod:154 Failed to execute stage 'Misc configuration': Engine schema refresh failed Any ideas?

2 2

Updating oVirt Node
by Jonas 01 Jun '22

01 Jun '22

Hello all For Updates to the oVirt Node hosts I have seen two options in the documentation: - https://ovirt.org/documentation/administration_guide/index.html#Updating_al… - https://ovirt.org/documentation/administration_guide/index.html#Updating_In… Does anyone here have experiences with one or the other strategy or any recommendation of one over the other? I would like to update the hosts in intervals and not all at once, but as far as I understand it is only possible to update to the latest packages at the time of the update. Or is there a way to define something like a baseline for nodes using oVirt Engine? Thank you for your valuable input! Jonas

1 0

New Template dialog, clicking OK in one environment results in template creation, the other environment does nothing.
by mblecha＠flagshipbio.com 01 Jun '22

01 Jun '22

We have two oVirt environments configured, one for our Lab and one for Production. In the Lab, we can create templates. Clicking OK results in the New Template dialog disappearing and the VM's disk becomes locked and template creation begins. In the production environment, we cannot create templates. Clicking OK results in nothing, the dialog box remains. Nothing indicates missing/incorrect information. Both environments are on hosted engines, and oVirt Engine version 4.5. I have monitored the logs in the production environment and nothing comes up when the OK button is clicked. I have tested both environments in both Firefox and Chrome, and the behavior is also the same, our lab will progress, but production will simply not budge.

2 3