2021년 1월 24일 (일) 오전 1:22, Nir Soffer 님이 작성:
> On Sat, Jan 23, 2021 at 5:18 PM Henry lol
> wrote:
> >
> > Hi,
> >
> > according to HA VM documentation, a paused VM may be started on another
> host and later resumed on the original host.
> > - https://www.ovirt.org/develop/ha-vms.html
> > here,
Hi Eli,
could you please take a look?
Thanks,
Martin
On Mon, Jan 18, 2021 at 9:32 AM tommy wrote:
> But on every KVM hosts, using fence_xvm command success.
>
>
>
> [root@ohost1 ~]# fence_xvm -o list
>
> 1.ovs1 7fd9b01e-236c-4d08-9c07-ad0b710139e2 off
>
> 1.ovs2
Hi Ori,
could you please take a look?
Thanks,
Martin
On Thu, Jan 21, 2021 at 9:52 PM wrote:
> I am using the rest api to create a VM, because the VM is cloned from the
> template and it takes a long time, I am also passing the async parameters
> hoping to receive back a job id, which I could
Thanks, Joop. I saw this solution on the list and tried it as well. It did
not work for me.
On Fri, Jan 22, 2021 at 3:48 AM Joop wrote:
> Hallo All,
>
> I'm not sure if this was mentioned but I had some problems with NFS,
> using Synology, a while back and the solution for me was to use a
>
On Sat, Jan 23, 2021 at 5:18 PM Henry lol wrote:
>
> Hi,
>
> according to HA VM documentation, a paused VM may be started on another host
> and later resumed on the original host.
> - https://www.ovirt.org/develop/ha-vms.html
> here, I'm assuming the HA VM was paused due to I/O error.
>
> but
I guess the name in the NIC can be used for that purpose.
Best Regards,Strahil Nikolov
and in order to assign IP using cloud-init, "In-guest Network Interface Name"
field should be filled but how to know that name in advance?
___
Users mailing list --
Hi,
I'm trying to use Cloud-Init for assigning static IP to the guest, is there
any other way commonly used?
and in order to assign IP using cloud-init, "In-guest Network Interface
Name" field should be filled but how to know that name in advance?
___
Hi,
according to HA VM documentation, a paused VM may be started on another
host and later resumed on the original host.
- https://www.ovirt.org/develop/ha-vms.html
here, I'm assuming the HA VM was paused due to I/O error.
but I'm wondering how it can happen because I guess the HA VM will be
В 14:41 + на 23.01.2021 (сб), Florian Schmid via Users написа:
> Hi Strahil,
>
> thank you very much for the information.
>
> Now the question is, will oVirt stay 100 % compatible to RH?
It should, but it it might have issues like we got with ovirt 4.4
(cluster compatibility 4.5) and CentOS
Hi Strahil,
thank you very much for the information.
Now the question is, will oVirt stay 100 % compatible to RH?
As I understood it, is that oVirt will be developed for CentOS Stream and will
be tested against it.
RH doesn't have the same application versions than CentOS Stream, because
For anyone interested ,
RH are extending the developer subscription for production use of up to 16
systems [1].
For me , it's completely enough to run my oVirt nodes on EL 8.
https://www.redhat.com/en/blog/new-year-new-red-hat-enterprise-linux-programs-easier-ways-access-rhel
Best Regards,
Try using the 'source /opt/rh/rh-postgresql95/enable'
Best Regards,Strahil Nikolov
В 19:53 + на 22.01.2021 (пт), José Ferradeira via Users написа:
> The postgres is older than 10:
> postgresql-jdbc-9.2.1002-6.el7_5.noarch
> postgresql-libs-9.2.23-3.el7_4.x86_64
>
It worked for me , but my HE is 4.3.10.
Best Regards,Strahil Nikolov
В 16:39 + на 22.01.2021 (пт), José Ferradeira via Users написа:
> Hello,
>
> # su - postgres
> -bash-4.2$ source /opt/rh/rh-postgresql10/enable
> -bash: /opt/rh/rh-postgresql10/enable: No such file or directory
> -bash-4.2$
> Then I enable the quorum on the server side:
>
> [root@gluster1 ~]# gluster volume set all cluster.server-quorum-ratio
> 51%
> volume set: success
> [root@gluster1 ~]#
> [root@gluster1 ~]# gluster volume set volume1 cluster.server-quorum-
> type server
> volume set: success
> [root@gluster1
I think it's easier to get the Vmware's CA certificate and import it on
all hosts + engine and trust it.By default you should put it at
/etc/pki/ca-trust/source/anchors/ and then use "update-ca-trust" to
make all certs signed by the Vmware vCenter's CA trusted.
Best Regards,Strahil Nikolov
В
15 matches
Mail list logo