Thanks for your response! I guess my path will be to migrate to el9 ovirt-node
then.
Am 25. April 2024 08:18:57 MESZ schrieb "Nathanaël Blanchet" :
>Hello,
>I already mentioned this issue, it is because of el8 4.5.5 embedded qemu
>version that is not compatible with 4.5.4 one. If all your hosts
This helped to resolve the issue. 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/communit
On Tue, Jan 25, 2022 at 10:36 AM Sandro Bonazzola
wrote:
> Hi, can you please provide versions of the non-upgraded hosts, of the
> upgraded hosts (I'm assuming you are using oVirt Node, if not, please
> provide the reports form `sos report -o rpm
> `) and of the engine?
>
> Il giorno mar 25 gen
Hi, can you please provide versions of the non-upgraded hosts, of the
upgraded hosts (I'm assuming you are using oVirt Node, if not, please
provide the reports form `sos report -o rpm
`) and of the engine?
Il giorno mar 25 gen 2022 alle ore 02:49 Gunasekhar Kothapalli via Users <
users@ovirt.org>
Thanks Sandro, wait for Eyal
k
Sent from my iPhone
> On 30 Apr 2021, at 10:03, Sandro Bonazzola wrote:
>
>
>
>> Il giorno ven 30 apr 2021 alle ore 08:48 Konstantin Shalygin
>> ha scritto:
>> Hi Sandro,
>>
>> The question is - will ovirt plan to provide database migration scripts from
>>
Hi
That is what I thought that as long as the storage domains belong to the
same cluster the VM can be migrated between Hosts in the Cluster because
HOST-A and HOST-B see the same Storage Domains.
Thanks for confirm it!
On Sun, Apr 25, 2021 at 2:01 PM Eyal Shenitzky wrote:
> Hi,
>
> I think
Hi,
I think you mixed between 2 different things.
the VM runs on host-A, if host-B is in the same cluster the VM can migrate
to it since all the hosts in the same cluster connected to all the storage
domains there.
Also, the VM's disk can move to a different storage domain in the same data
cente
Hi Nikolov,
I solved it, the error was in cpu virtualization.
Thanks for the support !!!
___
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 Co
Once the vm fails, you can check in the host's vdsm log the whole xml file.
Can you share that ?
Best Regards,
Strahil Nikolov
В сряда, 18 ноември 2020 г., 11:31:55 Гринуич+2, tiziano.paci...@par-tec.it
написа:
Hi,
I installed a new server, using the ovirt iso, with the target of mi
Hi,
It seems to be fixed now. I updated all the nodes to the last version as
well as hosted engine. I'll see to look at VDSM logs if it happens again.
Regards
El 16/8/20 a las 02:44, Strahil Nikolov escribió:
What is the output of 'hosted-engine --vm-status' on all nodes that are
supposed
What is the output of 'hosted-engine --vm-status' on all nodes that are
supposed to host the HostedEngine ?
Usually issues there can be debugged , when you check the ovirt-ha-broker and
ovirt-ha-agent logs (in /var/log on the affected Host).
Best Regards,
Strahil Nikolov
На 15 август 2020 г
On Fri, Aug 14, 2020, 16:16 Juan Pablo Lorier wrote:
> Hi,
>
> I'm having issues with migration to some hosts. I have a 4 node cluster
> and I tried updating to see if it fixes but it's still failing. The reason
> is nos clear in the engine log.
>
>
> 2020-08-14 09:45:32,322-03 INFO
> [org.ovirt.
Hi Erez,
would you like to use the backup tool to backup your self Hosted Engine from
iSCSI, then restore to the Gluster of NFS storage? In this way, you can
migration as you want.
If you are looking forward to a backup tool, maybe you can try Vinchin Backup &
Recovery, which provides the solut
As you will migrate from block-based storage to file-based storage, I think
that you should use the backup & restore procedure.
Best Regards,
Strahil Nikolov
На 25 юни 2020 г. 7:31:55 GMT+03:00, Erez Zarum написа:
>I was looking for a “complete” best practice to migrate a self-hosted
>engine r
On Sun, Jun 7, 2020 at 11:56 AM Strahil Nikolov via Users
wrote:
>
> Hi ,
>
> I know that you won't receive this e-mail directly, but you might see it in
> the web (kitty).
>
> I updated my 4.3 this friday and I never experienced any hiccups.
> Can you provide your 'rpm -qa'?
>
> Best Regards
Hi ,
I know that you won't receive this e-mail directly, but you might see it in the
web (kitty).
I updated my 4.3 this friday and I never experienced any hiccups.
Can you provide your 'rpm -qa'?
Best Regards,
Strahil Nikolov
На 6 юни 2020 г. 18:12:44 GMT+03:00, eev...@digitaldatatechs.com
Hello Dipak,
i didn't used export domains, but directly data domain, which avoided
me the long time of copying and importing back before powering on.
Luca
On Tue, Feb 19, 2019 at 8:59 AM Dipak D. Chaudhari wrote:
>
>
> Thanks
>
> Migrated in same way.
>
> 1] Created new nfs export domain on Loc
Hello Dipak,
we shut down all the vms in a storage domain, detached and then
imported on the new environment. Once imported we moved the vms to a
newer storage and the old one removed.
I don't know what can happen with local storage, but i think works
like shared storage.
Luca
On Sat, Feb 16, 2
> On 2 Jan 2019, at 03:02, 董青龙 wrote:
>
> Hi all,
> I have an ovirt4.2 environment of 3 hosts. Now all vms in this
> environment could not be migrated. But all the vms could be started on all 3
> hosts. Anyone can help? Thanks a lot!
can you add source and destination vdsm.log please
19 matches
Mail list logo