[ovirt-users] RBD Mirror support

2023-03-13 Thread Murilo Morais
Good evening everyone!

Guys, I managed to raise the RBD through Cinder without problem. Everything
works, including removing the Storage Domain (through postgres).

The initial objective was to go up with RBD Mirror but I'm not succeeding,
because Cinder is connecting the volume through KRBD, it doesn't support
Journaling which ends up breaking the Mirror...

Is there any way/configuration for Cinder to start the machine using librbd
instead of KRBD? Because in my scenario we have to use Mirror.

Thanks in advance.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/XT6MX3XX73AEB6TKGUOZNNVIZMW6KMZ2/


[ovirt-users] VM migration failed

2023-03-13 Thread dobrodej88
Hi, when i tried to migrate vm between hardwarehosts? i got an error like

 ERROR (migsrc/53accc0c) [virt.vm] 
(vmId='53accc0c-15c6-4917-a9c9-5237f7f358b1') Cannot access backing file 
'/rhev/data-center/mnt/blockSD/30b8a383-f390-405f-ac0c-4ef7a19207fe/images/ca67b349-5a51-43de-96f0-592db000de05/360f96d3-f63f-43c4-bfd5-3a8fb43bd007'
 of storage file 
'/rhev/data-center/mnt/blockSD/30b8a383-f390-405f-ac0c-4ef7a19207fe/images/ca67b349-5a51-43de-96f0-592db000de05/f3a72252-904c-48b1-8591-f2dabd343b8e'
 (as uid:107, gid:107): No such file or directory (migration:282)


but file are exist 

PROD [root@olvm1 vdsm]# ll 
/rhev/data-center/mnt/blockSD/30b8a383-f390-405f-ac0c-4ef7a19207fe/images/ca67b349-5a51-43de-96f0-592db000de05/360f96d3-f63f-43c4-bfd5-3a8fb43bd007
lrwxrwxrwx. 1 vdsm kvm 78 Mar 10 14:59 
/rhev/data-center/mnt/blockSD/30b8a383-f390-405f-ac0c-4ef7a19207fe/images/ca67b349-5a51-43de-96f0-592db000de05/360f96d3-f63f-43c4-bfd5-3a8fb43bd007
 -> 
/dev/30b8a383-f390-405f-ac0c-4ef7a19207fe/360f96d3-f63f-43c4-bfd5-3a8fb43bd007
PROD [root@olvm1 vdsm]# qemu-img check 
/rhev/data-center/mnt/blockSD/30b8a383-f390-405f-ac0c-4ef7a19207fe/images/ca67b349-5a51-43de-96f0-592db000de05/360f96d3-f63f-43c4-bfd5-3a8fb43bd007
No errors were found on the image.
14/1638400 = 0.00% allocated, 57.14% fragmented, 0.00% compressed clusters
Image end offset: 1310720
PROD [root@olvm1 vdsm]# qemu-img info 
/rhev/data-center/mnt/blockSD/30b8a383-f390-405f-ac0c-4ef7a19207fe/images/ca67b349-5a51-43de-96f0-592db000de05/360f96d3-f63f-43c4-bfd5-3a8fb43bd007
image: 
/rhev/data-center/mnt/blockSD/30b8a383-f390-405f-ac0c-4ef7a19207fe/images/ca67b349-5a51-43de-96f0-592db000de05/360f96d3-f63f-43c4-bfd5-3a8fb43bd007
file format: qcow2
virtual size: 100 GiB (107374182400 bytes)
disk size: 0 B
cluster_size: 65536
backing file: b7c03917-6fd4-4c88-98e3-e8fcdb3955bd (actual path: 
/rhev/data-center/mnt/blockSD/30b8a383-f390-405f-ac0c-4ef7a19207fe/images/ca67b349-5a51-43de-96f0-592db000de05/b7c03917-6fd4-4c88-98e3-e8fcdb3955bd)
backing file format: qcow2
Format specific information:
compat: 1.1
lazy refcounts: false
refcount bits: 16
corrupt: false


Please tell me what the reason could be, thank you
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/Z3ND3RUXHVDB4UIXXRCQC6P5LUMNI45S/


[ovirt-users] Re: Failed to remove MBS

2023-03-13 Thread Murilo Morais
Benny, it worked perfectly. Thank you very much!

Em seg., 13 de mar. de 2023 às 08:02, Murilo Morais 
escreveu:

> Hello Benny, good morning!
>
> I will test the solution, any news I'll update here.
>
> Thanks a lot for answering!
>
> Em dom., 12 de mar. de 2023 às 06:32, Benny Zlotnik 
> escreveu:
>
>> I think there are more tables, perhaps running the stored
>> procedure Force_Delete_storage_domain(v_storage_domain_id UUID) would be
>> enough
>>
>> On Sat, Mar 11, 2023 at 5:17 PM Murilo Morais 
>> wrote:
>>
>>> Good afternoon everybody!
>>>
>>> I have an MBD (Managed Block Storage) Storage Domain that we no longer
>>> use, we want to remove it. We are using version 4.4.10.
>>>
>>> When trying to put the Storage Domain in Maintenance, a message appears
>>> saying that it was not possible to remove it and that there is a Task being
>>> executed. I already looked for it but I didn't find it.
>>>
>>> Therefore, I cannot put the Storage Domain in Maintenance in the
>>> Datacenter, making it impossible to carry out the removal.
>>>
>>> According to a Bug Report [1] the problem has been fixed in version
>>> 4.5.0, the problem is that we cannot perform the update.
>>>
>>> In the DB I found two references to this Storage Domain, one in the
>>> `storage_domain_static` table and another in the `cinder_storage` table. Is
>>> removing these two references enough to remove this Storage Domain?
>>>
>>> Is there any other way to perform this process manually?
>>>
>>> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1959385
>>> ___
>>> Users mailing list -- users@ovirt.org
>>> To unsubscribe send an email to users-le...@ovirt.org
>>> Privacy Statement: https://www.ovirt.org/privacy-policy.html
>>> oVirt Code of Conduct:
>>> https://www.ovirt.org/community/about/community-guidelines/
>>> List Archives:
>>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/53CJYIAKUA2OCQ7XHX7SUAJSZRYEQFN2/
>>>
>>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/EI4YINICPWKQ5XIL4PNNGDJDIP2OWA5D/


[ovirt-users] Re: Failed to remove MBS

2023-03-13 Thread Murilo Morais
Hello Benny, good morning!

I will test the solution, any news I'll update here.

Thanks a lot for answering!

Em dom., 12 de mar. de 2023 às 06:32, Benny Zlotnik 
escreveu:

> I think there are more tables, perhaps running the stored
> procedure Force_Delete_storage_domain(v_storage_domain_id UUID) would be
> enough
>
> On Sat, Mar 11, 2023 at 5:17 PM Murilo Morais 
> wrote:
>
>> Good afternoon everybody!
>>
>> I have an MBD (Managed Block Storage) Storage Domain that we no longer
>> use, we want to remove it. We are using version 4.4.10.
>>
>> When trying to put the Storage Domain in Maintenance, a message appears
>> saying that it was not possible to remove it and that there is a Task being
>> executed. I already looked for it but I didn't find it.
>>
>> Therefore, I cannot put the Storage Domain in Maintenance in the
>> Datacenter, making it impossible to carry out the removal.
>>
>> According to a Bug Report [1] the problem has been fixed in version
>> 4.5.0, the problem is that we cannot perform the update.
>>
>> In the DB I found two references to this Storage Domain, one in the
>> `storage_domain_static` table and another in the `cinder_storage` table. Is
>> removing these two references enough to remove this Storage Domain?
>>
>> Is there any other way to perform this process manually?
>>
>> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1959385
>> ___
>> Users mailing list -- users@ovirt.org
>> To unsubscribe send an email to users-le...@ovirt.org
>> Privacy Statement: https://www.ovirt.org/privacy-policy.html
>> oVirt Code of Conduct:
>> https://www.ovirt.org/community/about/community-guidelines/
>> List Archives:
>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/53CJYIAKUA2OCQ7XHX7SUAJSZRYEQFN2/
>>
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/55KE5C4VPORKOZMQLNVNMH6IGEKUZGYS/


[ovirt-users] Re: virt-viewer - working alternative

2023-03-13 Thread Sandro Bonazzola
Reported an issue there to make the nightly builds available:
https://gitlab.com/virt-viewer/virt-viewer/-/issues/103

Il giorno lun 13 mar 2023 alle ore 11:12  ha scritto:

> i have my installation package from https://virt-manager.org
> The latest Windows MSI is 2021.
>
> The source you linked is more recent, but it seems to be source code only.
> I'm not able to compile windows programs so i'm still stuck with that old
> version.
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/DUMCOCRA2H45LVUZNKGO6PNHNWTFKICV/
>


-- 

Sandro Bonazzola

MANAGER, SOFTWARE ENGINEERING - Red Hat In-Vehicle Operating System

Red Hat EMEA 

sbona...@redhat.com


*Red Hat respects your work life balance. Therefore there is no need to
answer this email out of your office hours.*
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/A75G3PFMIVGYFMDKXERPRVAQAH2CS6H3/


[ovirt-users] Re: virt-viewer - working alternative

2023-03-13 Thread lars . stolpe
i have my installation package from https://virt-manager.org 
The latest Windows MSI is 2021.

The source you linked is more recent, but it seems to be source code only. I'm 
not able to compile windows programs so i'm still stuck with that old version.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/DUMCOCRA2H45LVUZNKGO6PNHNWTFKICV/


[ovirt-users] Re: Self Hosted Engine in unaligned state: node are

2023-03-13 Thread Diego Ercolani
Finally it seem that the problem was in the external nfs server, it failed 
rpc.gsssd and the nfs service become unresponsive... so the hosted-engine 
configuration domain wasn't reacheable
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/3QMB3R3QU2M73WNOEOU7GDTZSG6A4U3W/


[ovirt-users] Self Hosted Engine in unaligned state: node are

2023-03-13 Thread Diego Ercolani
Hello,
ovirt-release-host-node-4.5.4-1.el8.x86_64

Today I found my cluster in an unconsinstent state
I have three nodes: ovirt-node2 ovirt-node3 ovirt-node4 with self hosted engine 
deployed using external nfs storage

My first attempt was to launch hosted-engine --vm-statos on three nodes and I 
get three inconsinstent states:

[root@ovirt-node2 ~]# hosted-engine --vm-status
The hosted engine configuration has not been retrieved from shared storage yet,
please ensure that ovirt-ha-agent service is running.

--== Host ovirt-node3.ovirt (id: 1) status ==--

Host ID: 1
Host timestamp : 1942858
Score  : 3400
Engine status  : unknown stale-data
Hostname   : ovirt-node3.ovirt
Local maintenance  : False
stopped: False
crc32  : 37cf5256
conf_on_shared_storage : True
local_conf_timestamp   : 1942859
Status up-to-date  : False
Extra metadata (valid at timestamp):
metadata_parse_version=1
metadata_feature_version=1
timestamp=1942858 (Sun Mar 12 01:26:20 2023)
host-id=1
score=3400
vm_conf_refresh_time=1942859 (Sun Mar 12 01:26:22 2023)
conf_on_shared_storage=True
maintenance=False
state=EngineDown
stopped=False


--== Host ovirt-node2.ovirt (id: 2) status ==--

Host ID: 2
Host timestamp : 4425500
Score  : 3400
Engine status  : unknown stale-data
Hostname   : ovirt-node2.ovirt
Local maintenance  : False
stopped: False
crc32  : ab944a8a
conf_on_shared_storage : True
local_conf_timestamp   : 4425500
Status up-to-date  : False
Extra metadata (valid at timestamp):
metadata_parse_version=1
metadata_feature_version=1
timestamp=4425500 (Sun Mar 12 01:26:01 2023)
host-id=2
score=3400
vm_conf_refresh_time=4425500 (Sun Mar 12 01:26:01 2023)
conf_on_shared_storage=True
maintenance=False
state=EngineUp
stopped=False

[root@ovirt-node3 ~]# hosted-engine --vm-status
--== Host ovirt-node4.ovirt (id: 3) status ==--

Host ID: 3
Host timestamp : 4452814
Score  : 3400
Engine status  : unknown stale-data
Hostname   : ovirt-node4.ovirt
Local maintenance  : False
stopped: False
crc32  : 95890d21
conf_on_shared_storage : True
local_conf_timestamp   : 4452814
Status up-to-date  : False
Extra metadata (valid at timestamp):
metadata_parse_version=1
metadata_feature_version=1
timestamp=4452814 (Sun Mar 12 01:25:55 2023)
host-id=3
score=3400
vm_conf_refresh_time=4452814 (Sun Mar 12 01:25:55 2023)
conf_on_shared_storage=True
maintenance=False
state=EngineDown
stopped=False



[root@ovirt-node4 ~]# hosted-engine --vm-status


--== Host ovirt-node3.ovirt (id: 1) status ==--

Host ID: 1
Host timestamp : 1942848
Score  : 3400
Engine status  : unknown stale-data
Hostname   : ovirt-node3.ovirt
Local maintenance  : False
stopped: False
crc32  : 7f645fbc
conf_on_shared_storage : True
local_conf_timestamp   : 1942848
Status up-to-date  : False
Extra metadata (valid at timestamp):
metadata_parse_version=1
metadata_feature_version=1
timestamp=1942848 (Sun Mar 12 01:26:10 2023)
host-id=1
score=3400
vm_conf_refresh_time=1942848 (Sun Mar 12 01:26:10 2023)
conf_on_shared_storage=True
maintenance=False
state=EngineDown
stopped=False


--== Host ovirt-node2.ovirt (id: 2) status ==--

Host ID: 2
Host timestamp : 4428404
Score  : 3400
Engine status  : unknown stale-data
Hostname   : ovirt-node2.ovirt
Local maintenance  : False
stopped: False
crc32  : af938ff8
conf_on_shared_storage : True
local_conf_timestamp   : 4428404
Status up-to-date  : False
Extra metadata (valid at timestamp):
metadata_parse_version=1
metadata_feature_version=1
timestamp=4428404 (Sun Mar 12 02:14:45 2023)