December 2024 - Users - Ovirt List Archives

Curl error (7): Couldn't connect to server for https://mirrorlist.ovirt.org/mirrorlist-ovirt-4.5-el8

by eyup ustaoglu

Hello. I keep getting this error during the ovirt PREPARE VM phase. Is there a site where I can get the current repositories under /etc/yum.repos.d? Also, have ovirt updates stopped? Why are repo addresses that have been unreachable for a long time still in the ovirt node?

5 months, 3 weeks

1
0
0 / 0

Cannot prepare internal mirrorlist: Curl error (6): Couldn't resolve host name for http://mirrorlist.centos.org/?release=8-stream&arch=x86_64&repo=virt-ovirt-45 [Could not resolve host: mirrorlist.centos.org]

by onr onr

I am in the Prepare VM step in ovirt installation. and I keep getting the above error. Why is the unused repo address defined even though I downloaded the latest ovirt-node? Where can I find repo addresses for el8 that can be accessed for installation? Is ovirt a discontinued system?

5 months, 4 weeks

1
0
0 / 0

How to stop backup operation on vm

by marco.pegoraro＠univr.it

Hi, I have the following problem. In the db engine I have the following backups: engine=# select * from vm_backups; backup_id | from_checkpoint_id | to_checkpoint_id | vm_id | phase | _create_date | host_id | description | _update_date | backup_type | snapshot_id | is_stopped --------------------------------------+--------------------+--------------------------------------+------------------------------------ --+-------+----------------------------+---------+------------------------------------------------------------------------------------- -----------------------------------+----------------------------+-------------+--------------------------------------+------------ 864beee4-c87d-447c-a249-83a38fd1d4e7 | | 0ecf0a56-e7bb-4133-9ac7-441aa0d84545 | e1465242-3724-405b-9750-250d1eeb974 2 | Ready | 2024-12-18 16:42:54.717+01 | | {"type":"veeam","job_uuid":"0c3a6b0a-b46e-4ca2-8ed1-3d29c4b221ab","session_id":"4706 6400-4f1f-456e-ab94-6c3af7043809"} | 2024-12-18 16:43:06.736+01 | hybrid | 234de52d-8739-499a-8031-b8d6f6db0422 | f ace9cdf3-ad51-45b9-af6f-1728b3941187 | | e5b1ed24-4781-43dc-a1fd-b71173fd1602 | f2e2a274-71f7-4e4a-87ae-942ce0b78dd 2 | Ready | 2024-12-19 11:35:16.67+01 | | {"type":"veeam","job_uuid":"0c3a6b0a-b46e-4ca2-8ed1-3d29c4b221ab","session_id":"8d89 018d-ad81-4857-a4e3-42cf0b38a41d"} | 2024-12-19 11:35:40.907+01 | hybrid | c9108e74-8bdc-401a-b27d-adab99f28682 | f (2 rows) I want to stop the backups and delete them. I ran the following commands on the KVM nodes to stop the backups: #vdsm-client VM stop_backup vmID=e1465242-3724-405b-9750-250d1eeb9742 backup_id=864beee4-c87d-447c-a249-83a38fd1d4e7 { "code": 0, "message": "Done" } #vdsm-client VM stop_backup vmID=e1465242-3724-405b-9750-250d1eeb9742 backup_id=864beee4-c87d-447c-a249-83a38fd1d4e7 { "code": 0, "message": "Done" } but in the db there are still: engine=# select * from vm_backups; backup_id | from_checkpoint_id | to_checkpoint_id | vm_id | phase | _create_date | host_id | description | _update_date | backup_type | snapshot_id | is_stopped --------------------------------------+--------------------+--------------------------------------+------------------------------------ --+-------+----------------------------+---------+------------------------------------------------------------------------------------- -----------------------------------+----------------------------+-------------+--------------------------------------+------------ 864beee4-c87d-447c-a249-83a38fd1d4e7 | | 0ecf0a56-e7bb-4133-9ac7-441aa0d84545 | e1465242-3724-405b-9750-250d1eeb974 2 | Ready | 2024-12-18 16:42:54.717+01 | | {"type":"veeam","job_uuid":"0c3a6b0a-b46e-4ca2-8ed1-3d29c4b221ab","session_id":"4706 6400-4f1f-456e-ab94-6c3af7043809"} | 2024-12-18 16:43:06.736+01 | hybrid | 234de52d-8739-499a-8031-b8d6f6db0422 | f ace9cdf3-ad51-45b9-af6f-1728b3941187 | | e5b1ed24-4781-43dc-a1fd-b71173fd1602 | f2e2a274-71f7-4e4a-87ae-942ce0b78dd 2 | Ready | 2024-12-19 11:35:16.67+01 | | {"type":"veeam","job_uuid":"0c3a6b0a-b46e-4ca2-8ed1-3d29c4b221ab","session_id":"8d89 018d-ad81-4857-a4e3-42cf0b38a41d"} | 2024-12-19 11:35:40.907+01 | hybrid | c9108e74-8bdc-401a-b27d-adab99f28682 | f (2 rows) Do you have any idea how I can accomplish this? Thank you very much.

6 months

1
0
0 / 0

"Master" Storage Domain

by duparchy＠esrf.fr

Hi What is the role of the "Master Storage Domain" ? (and what consequences if it is unresponsive for a while)

6 months

2
1
0 / 0

Re: Problems when add storagedomain "master"

by Erik＠deerlickgroup.com

I think you can onoy have one master. Have you tried just promoting a domain vs. trying to add a new one? Erik Sent from my iPad

6 months

1
0
0 / 0

Migrate from Centos8 to Centos9

by suporte＠logicworks.pt

Hi, I need to migrate from Centos8 to Centos9, engine+ 2 nodes, iSCSI storage, My idea is backup Engine on Centos8: engine-backup --scope=all --mode=backup --file=/root/backup Then install a new engine machine with Centos9 and restore: engine-backup --mode=restore --file=backup --log=backup_restore.log engine-setup Now Engine on Centos9 is controlling the 2 nodes on Centos8 Than, I migrate all VMs from node2 to node1. Install node2 with Centos9 Migrate all VMs from node1 to node2 Install node1 with Centos9 Do you think it will work? Thanks -- Jose Ferradeira http://www.logicworks.pt

6 months

4
8
0 / 0

Re: [External] : Adding ISO doesn't work

by Stanley Ang

Hi Marcos Is the problem fixed on 4.5.5-1.28 already? Is the repLacement of olvm45-security-fixes supposed to be a workaround?? I have already changed olvm45-security-fixes.conf to the one that you attached in the mail but the problem still persisted. Stan

6 months

2
1
0 / 0

CentOS 9 Stream Ovirt 4;5

by eevans＠digitaldatatechs.com

My setup: 1 Seperate physical ovirt engine with 3 Centos 9 nodes; I have imported ova's from Ovirt 4.3 and that will not launch. They stay in waiting to launch for bout 15 seconds then shutdown. ALso, the node networks will not sync. I turned off firewalls to make sure it wasn't blocked with the same result. I also disabled selinux with the same result. Any help would be appereciated.

6 months, 1 week

1
0
0 / 0

Uploading .iso image with REST API creates <id>.meta with wrong DISKTYPE value

by markul11＠protonmail.com

When creating file (.iso image) with the web GUI the .meta file has DISKTYPE=ISOF, but when using REST, DISKTYPE=DATA and the file is not listed on the "Attach CD" drop down when creating a new vm. Using API is the only way for me cos I can't find a fix to a connection problem from Firefox/Fedora 39 to the web GUI, so all transfers end up as "suspended by the system". I am using the following POST to crate the file: curl -k -u "admin@internal:secretpw" -X POST \ -H "Content-Type: application/xml" \ -d '<disk><name>Rocky-9-latest-x86_64-boot.iso</name><alias>Rocky-9-latest-x86_64-boot.iso</alias>\ <description>Rocky-9-latest-x86_64-boot.iso</description>\ <provisioned_size>1068498944</provisioned_size><format>raw</format>\ <storage_domains><storage_domain><name>isos</name>\ </storage_domain></storage_domains></disk>' \ https://ovirtsvc.adm.cnt.uksw.edu.pl/ovirt-engine/api/disks The resulting <id>.meta is: CAP=1068498944 CTIME=1732282300 DESCRIPTION={"DiskAlias":"Rocky-9-latest-x86_64-boot.iso","DiskDescription":"Rocky-9-latest-x86_64-boot.iso"} DISKTYPE=DATA [...] FORMAT=RAW [...]TYPE=SPARSE VOLTYPE=LEAF EOF

6 months, 1 week

2
2
0 / 0

oVirt New version?

by ecsi＠ecsi.hu

There hasn't been a new version for over a year, and not long ago, you asked for help with the release of a new version. What is the current status of the project?

6 months, 1 week

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Users December 2024