Yes,/etc/ovirt-hosted-engine-ha/agent.conf should be enough.
Best Regards,Strahil Nikolov___
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
Please disregard the previous e-mail.
Best Regards,Strahil Nikolov
On Wed, May 5, 2021 at 1:06, Strahil Nikolov wrote:
Yes,/etc/ovirt-hosted-engine-ha/agent.conf should be enough.
Best Regards,Strahil Nikolov
___
Users mailing list --
Yes,/etc/ovirt-hosted-engine-ha/agent.conf should be enough.
Best Regards,Strahil Nikolov___
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
Below is my Add_host routine with reboot=False and my host will still
reboot on install. What am I doing wrong? It is not giving me errors.
def Add_host():
hosts_service = connection.system_service().hosts_service()
# Add the host:
host = hosts_service.add(
types.Host(
On Wed, May 5, 2021 at 8:32 AM marcel d'heureuse wrote:
>
> Hi,
>
> We shutdown the complete ovirt system, if a poweroutage occurs and we don't
> want to make an hard power off.
>
> So we stop all vms, put the storages in maintenance and shut down the engine,
> disconnect storages and shut down
Hi,
We shutdown the complete ovirt system, if a poweroutage occurs and we don't
want to make an hard power off.
So we stop all vms, put the storages in maintenance and shut down the engine,
disconnect storages and shut down the nodes.
On power up, sometimes it works fine but in some cases
Hello,
I have been trying to upgrade my self-hosted engine from 4.3 to 4.4 but running
into issue while performing hosted-engine deploy.
Old hypervisor hosts are all running Centos 8 and old ovirt-engine is also
running Centos 7.
I created a brand new baremental node running Centos 8, Kernel
On Wed, May 5, 2021 at 8:18 AM wrote:
>
> Hello,
>
> I have been trying to upgrade my self-hosted engine from 4.3 to 4.4 but
> running into issue while performing hosted-engine deploy.
> Old hypervisor hosts are all running Centos 8 and old ovirt-engine is also
> running Centos 7.
>
> I created
Hello,
welcome to ovirt, I hope you'll have a wonderful experience :)
Since you mentioned having (one) server I suppose you're deploying a
self-hosted ovirt engine. I haven't tried deploying everything on one node
but I believe this should be possible although not recommended, certainly
not for
It's quite interesting why the link is not created when it should ...Can you
paste the contents of the ha daemons' config where the shared storage should be
defined?
You can create the link if needed, but it won't solve the problem.
Best Regards,Strahil
does anyone have a solution for this.
Engine is failed continuously and try migrate between two hosts
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement:
Hi Strahil,
Creating link towards conf_image on shared storage, did help in regards to HE
migrating with donor not ending up with down_expected but simply down.
Regarding “Can you paste the contents of the ha daemons' config where the
shared storage should be defined?”, are you referring to
Hi all,
we are starting to work on oVirt 4.4.7 and as you probably noticed we are
slowly transitioning away from CentOS. We added CentOS Stream option for
regular hosts, and the current 4.4.6 Node and Appliance are already built from
Stream. We also have some initial patches for alternative
Ok –
These are the symlinks in place:
1. /var/run/vdsm/storage//
2. /var/run/vdsm/storage//
3. /var/run/vdsm/storage//
4. /var/run/vdsm/storage// -
this one exist only on the current Host
5. /var/run/vdsm/storage//
Migration issue – seem to be solved at part 3:
Part1:
*
Hi,
With last OLVM update installed, we are unable to delete snapshot without
stopping the vm (live merge error)
Vdsm.log:
2021-05-04 09:44:28,389+0200 ERROR (jsonrpc/6) [virt.vm]
(vmId='dba27e34-f8f3-4d9b-a6fd-95ba92c2970e') Live merge failed (job:
36f515b5-fb9e-4e29-b5f8-5b7c062cef5d)
Hi,
it’s a known regression due to updates on qemu/libvirt releases.
The easiest way to get it sorted out is to rollback to previous qemu-3.1.0-7
release on the KVM host.
Soon an update for qemu/libvirt will address the same.
Simon
On May 4, 2021, at 12:03 PM, Renevey Christian
The oVirt project is excited to announce the general availability of oVirt
4.4.6 , as of May 4th, 2021.
This release unleashes an altogether more powerful and flexible open source
virtualization solution that encompasses hundreds of individual changes and
a wide range of enhancements across the
17 matches
Mail list logo
