[ovirt-users] Re: [ovirt-announce] [ANN] oVirt 4.4.4 is now generally available

[Bernardo Juanicó]

Hello, considering we want to do a new oVirt hyper-converged
deployment on CentOS for a production environment what should we do
regarding the OS?
Considering Centos Stream is on tech preview and Centos 8 is near EOL, what
is the correct path?
Install CentOS 8.3 and use it until EOL and then update the hosts to
centos stream when it becomes stable?
install CentOS Stream even though it is on tech preview?

Regards!
Bernardo
PGP Key 


On Mon, Dec 21, 2020 at 10:32 AM Sandro Bonazzola 
wrote:

> oVirt 4.4.4 is now generally available
>
> The oVirt project is excited to announce the general availability of oVirt
> 4.4.4 , as of December 21st, 2020.
>
> 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 engine, storage,
> network, user interface, and analytics, as compared to oVirt 4.3.
> Important notes before you install / upgrade
>
> Please note that oVirt 4.4 only supports clusters and data centers with
> compatibility version 4.2 and above. If clusters or data centers are
> running with an older compatibility version, you need to upgrade them to at
> least 4.2 (4.3 is recommended).
>
> Please note that in RHEL 8 / CentOS 8 several devices that worked on EL7
> are no longer supported.
>
> For example, the megaraid_sas driver is removed. If you use Enterprise
> Linux 8 hosts you can try to provide the necessary drivers for the
> deprecated hardware using the DUD method (See the users’ mailing list
> thread on this at
> https://lists.ovirt.org/archives/list/users@ovirt.org/thread/NDSVUZSESOXEFJNPHOXUH4HOOWRIRSB4/
> )
> Documentation
>
>-
>
>If you want to try oVirt as quickly as possible, follow the
>instructions on the Download  page.
>-
>
>For complete installation, administration, and usage instructions, see
>the oVirt Documentation .
>-
>
>For upgrading from a previous version, see the oVirt Upgrade Guide
>.
>-
>
>For a general overview of oVirt, see About oVirt
>.
>
> What’s new in oVirt 4.4.4 Release?
>
> This update is the fourth in a series of stabilization updates to the 4.4
> series.
>
> This release is available now on x86_64 architecture for:
>
>-
>
>Red Hat Enterprise Linux 8.3
>-
>
>CentOS Linux (or similar) 8.3
>-
>
>CentOS Stream (tech preview)
>
>
> This release supports Hypervisor Hosts on x86_64 and ppc64le architectures
> for:
>
>-
>
>Red Hat Enterprise Linux 8.3
>-
>
>CentOS Linux (or similar) 8.3
>-
>
>oVirt Node (based on CentOS Linux 8.3)
>-
>
>CentOS Stream (tech preview)
>
>
>
> oVirt Node and Appliance have been updated, including:
>
>-
>
>oVirt 4.4.4: https://www.ovirt.org/release/4.4.4/
>-
>
>Ansible 2.9.16:
>
> https://github.com/ansible/ansible/blob/stable-2.9/changelogs/CHANGELOG-v2.9.rst#v2-9-16
>
>-
>
>CentOS Linux 8 (2011):
>
> https://lists.centos.org/pipermail/centos-announce/2020-December/048207.html
>-
>
>Advanced Virtualization 8.3
>
>
>
> See the release notes [1] for installation instructions and a list of new
> features and bugs fixed.
>
> Notes:
>
>-
>
>oVirt Appliance is already available for CentOS Linux 8
>-
>
>oVirt Node NG is already available for CentOS Linux 8
>
>
> Additional resources:
>
>-
>
>Read more about the oVirt 4.4.4 release highlights:
>https://www.ovirt.org/release/4.4.4/
>-
>
>Get more oVirt project updates on Twitter: https://twitter.com/ovirt
>-
>
>Check out the latest project news on the oVirt blog:
>https://blogs.ovirt.org/
>
>
> [1] https://www.ovirt.org/release/4.4.4/
> [2] https://resources.ovirt.org/pub/ovirt-4.4/iso/
>
> --
>
> Sandro Bonazzola
>
> MANAGER, SOFTWARE ENGINEERING, EMEA R RHV
>
> 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.*
>
>
> ___
> Announce mailing list -- annou...@ovirt.org
> To unsubscribe send an email to announce-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/annou...@ovirt.org/message/KMYD2GAHZXWLE45SZWAMOXN4WYKV54MK/
>
___
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 

Re: [ovirt-users] How is everyone performing backups?

[Bernardo Juanicó]

Torsten:
That tool (oVirtBackup ) is
based on the old SDK (Version 3) which is deprecated and will be removed
(correct me if im wrong) on the 4.2 version.
Take this into account if you plan on updating.


Regards,

Bernardo

PGP Key 
Skype: mattraken

2017-10-30 13:01 GMT-03:00 Torsten Stolpmann :

> We are using https://github.com/wefixit-AT/oVirtBackup for backups.
>
> This works ok for us for nightly scheduled online backups of our vms
> managed by an oVirt 4.0.2.7 engine.
>
> Is this the script you have been using?
>
> Torsten
>
>
> On 27.10.2017 17:27, Wesley Stewart wrote:
>
>> Originally, I used a script I found on github, but since updating I can't
>> seem to get that to work again.
>>
>> I was just curious if there were any other more elegant type solutions?
>> I am currently running a single host and local storage, but I would love to
>> backup VM's automatically once a week or so to an NFS share.
>>
>> Just curious if anyone had tackled this issue.
>>
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] oVirt's VM backup

[Bernardo Juanicó]

I didnt know that, we may adapt it in the future, but at first we will
probably just write a basic set of scripts for minimal backup functionally
since our dev time is limited.

Ill keep you in mind when looking into it.

Regards,

Bernardo

PGP Key <http://pgp.mit.edu/pks/lookup?op=get=0x695E5BCE34263F5B>
Skype: mattraken

2017-09-21 13:08 GMT-03:00 Nathanaël Blanchet <blanc...@abes.fr>:

> Hi Bernardo,
>
> Thanks, I knew this tool, but it is based on sdk3 which will be removed in
> the next version 4.2, so I'm looking at sdk4 project.
>
> You may want to adapt it?
>
> Le 21/09/2017 à 17:08, Bernardo Juanicó a écrit :
>
> Hi Nathanael,
>
> You may want to take a look at this too:
>
> https://github.com/bjuanico/oVirtBackup
>
> Regards,
>
> Bernardo
>
> PGP Key <http://pgp.mit.edu/pks/lookup?op=get=0x695E5BCE34263F5B>
> Skype: mattraken
>
> 2017-09-21 11:00 GMT-03:00 Nathanaël Blanchet <blanc...@abes.fr>:
>
>> Hello Victor,
>>
>> I have some questions about your script
>>
>> Le 07/07/2017 à 23:40, Victor José Acosta Domínguez a écrit :
>>
>> Hello everyone, i created a python tool to backup and restore oVirt's VMs.
>>
>> Also i created a little "how to" on my blog:
>> http://blog.infratic.com/2017/07/create-ovirtrhevs-vm-backup/
>>
>>
>>- Backup step is okay, and I get a usable qcow2 image of the snapshot
>>vm in the backup vm. It seems to be compliant with the official backup 
>> API,
>>except on the step 2.
>>
>>
>>1. *Take a snapshot of the virtual machine to be backed up -
>>(existing oVirt REST API operation)*
>>2. *Back up the virtual machine configuration at the time of the
>>snapshot (the disk configuration can be backed up as well if needed) -
>>(added capability to oVirt as part of the Backup API)*
>>
>> I can't see any vm configuration anywhere but only the qcow2 disk itself
>>
>>1. *Attach the disk snapshots that were created in (1) to the virtual
>>appliance for data backup - (added capability to oVirt as part of the
>>Backup API)*
>>2.
>> 3. *Detach the disk snapshots that were attached in (4) from the virtual
>>appliance - (added capability to oVirt as part of the Backup API)*
>>
>> An other case is when the vm to backup has more than one disk. After I
>> tested it, I found that only one qcow2 disk is saved on the backup vm. This
>> is really a matter when the original vm has many disks part of lvm, it
>> makes the vm restoration unusable.
>>
>>- About vm restoration, it seems that you are using the upload_disk
>>api, so the disk is uploaded to the pre-defined storage domain, so it is
>>not a real vm restoration.
>>
>> Do you plan to backup and restore a full VM (disks + vm definition) in a
>> next release?
>>
>>
>> I hope it help someone else
>>
>> Regards
>>
>> Victor Acosta
>>
>>
>>
>>
>> ___
>> Users mailing 
>> listUsers@ovirt.orghttp://lists.ovirt.org/mailman/listinfo/users
>>
>>
>> --
>> Nathanaël Blanchet
>>
>> Supervision réseau
>> Pôle Infrastrutures Informatiques227 avenue Professeur-Jean-Louis-Viala 
>> <https://maps.google.com/?q=227+avenue+Professeur-Jean-Louis-Viala=gmail=g>
>> 34193 MONTPELLIER CEDEX 5
>> Tél. 33 (0)4 67 54 84 55
>> Fax  33 (0)4 67 54 84 14blanc...@abes.fr
>>
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
>
> --
> Nathanaël Blanchet
>
> Supervision réseau
> Pôle Infrastrutures Informatiques227 avenue Professeur-Jean-Louis-Viala 
> <https://maps.google.com/?q=227+avenue+Professeur-Jean-Louis-Viala=gmail=g>
> 34193 MONTPELLIER CEDEX 5 
> Tél. 33 (0)4 67 54 84 55
> Fax  33 (0)4 67 54 84 14blanc...@abes.fr
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] oVirt's VM backup

[Bernardo Juanicó]

Hi Nathanael,

You may want to take a look at this too:

https://github.com/bjuanico/oVirtBackup

Regards,

Bernardo

PGP Key 
Skype: mattraken

2017-09-21 11:00 GMT-03:00 Nathanaël Blanchet :

> Hello Victor,
>
> I have some questions about your script
>
> Le 07/07/2017 à 23:40, Victor José Acosta Domínguez a écrit :
>
> Hello everyone, i created a python tool to backup and restore oVirt's VMs.
>
> Also i created a little "how to" on my blog:
> http://blog.infratic.com/2017/07/create-ovirtrhevs-vm-backup/
>
>
>- Backup step is okay, and I get a usable qcow2 image of the snapshot
>vm in the backup vm. It seems to be compliant with the official backup API,
>except on the step 2.
>
>
>1. *Take a snapshot of the virtual machine to be backed up - (existing
>oVirt REST API operation)*
>2. *Back up the virtual machine configuration at the time of the
>snapshot (the disk configuration can be backed up as well if needed) -
>(added capability to oVirt as part of the Backup API)*
>
> I can't see any vm configuration anywhere but only the qcow2 disk itself
>
>1. *Attach the disk snapshots that were created in (1) to the virtual
>appliance for data backup - (added capability to oVirt as part of the
>Backup API)*
>2.
> 3. *Detach the disk snapshots that were attached in (4) from the virtual
>appliance - (added capability to oVirt as part of the Backup API)*
>
> An other case is when the vm to backup has more than one disk. After I
> tested it, I found that only one qcow2 disk is saved on the backup vm. This
> is really a matter when the original vm has many disks part of lvm, it
> makes the vm restoration unusable.
>
>- About vm restoration, it seems that you are using the upload_disk
>api, so the disk is uploaded to the pre-defined storage domain, so it is
>not a real vm restoration.
>
> Do you plan to backup and restore a full VM (disks + vm definition) in a
> next release?
>
>
> I hope it help someone else
>
> Regards
>
> Victor Acosta
>
>
>
>
> ___
> Users mailing listUsers@ovirt.orghttp://lists.ovirt.org/mailman/listinfo/users
>
>
> --
> Nathanaël Blanchet
>
> Supervision réseau
> Pôle Infrastrutures Informatiques
> 227 avenue Professeur-Jean-Louis-Viala
> 34193 MONTPELLIER CEDEX 5 
> Tél. 33 (0)4 67 54 84 55
> Fax  33 (0)4 67 54 84 14blanc...@abes.fr
>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Slow booting host - restart loop

[Bernardo Juanicó]

Hi, the same happens, maybe the password somehow changed, or the file is
wrong? Is there a way to reset the password?

[root@ovirt-engine ~]# PGPASSWORD=CKBKMiSQrrPdq0w9RrWDXw psql -U engine -c
"update vdc_options set option_value = '900' where option_name =
'FenceQuietTimeBetweenOperationsInSec';" engine
psql: FATAL:  Peer authentication failed for user "engine"

this is my 10-setup-database.conf file

[root@ovirt-engine ~]# cat
/etc/ovirt-engine/engine.conf.d/10-setup-database.conf
ENGINE_DB_HOST="localhost"
ENGINE_DB_PORT="5432"
ENGINE_DB_USER="engine"
ENGINE_DB_PASSWORD="CKBKMiSQrrPdq0w9RrWDXw"
ENGINE_DB_DATABASE="engine"
ENGINE_DB_SECURED="False"
ENGINE_DB_SECURED_VALIDATION="False"
ENGINE_DB_DRIVER="org.postgresql.Driver"
ENGINE_DB_URL="jdbc:postgresql://localhost:5432/engine?sslfactory=org.postgresql.ssl.NonValidatingFactory"

Regards,

Bernardo


PGP Key <http://pgp.mit.edu/pks/lookup?op=get=0x695E5BCE34263F5B>
Skype: mattraken

2017-09-06 4:32 GMT-03:00 Eli Mesika <emes...@redhat.com>:

> Hi
>
> try from shell prompt
>
> PGPASSWORD= psql -U engine -c "update vdc_options set
> option_value = '900' where option_name = 
> 'FenceQuietTimeBetweenOperationsInSec';"
> engine
>
> On Tue, Sep 5, 2017 at 6:34 PM, Bernardo Juanicó <bjuan...@gmail.com>
> wrote:
>
>> Hi Eli,
>>
>> I could not access the psql prompt, i tried with the credentials and
>> values on /etc/ovirt-engine/engine.conf.d/10-setup-database.conf.
>>
>> I tried interactively and also with a .pgpass file containing:
>> localhost:5432:engine:engine:PASSWORD
>>
>> And i get the following error:
>>
>> psql: FATAL:  Peer authentication failed for user "engine"
>>
>> Thanks!
>>
>> Bernardo
>>
>>
>> PGP Key <http://pgp.mit.edu/pks/lookup?op=get=0x695E5BCE34263F5B>
>> Skype: mattraken
>>
>> 2017-09-05 12:14 GMT-03:00 Eli Mesika <emes...@redhat.com>:
>>
>>> Hi Bernardo
>>>
>>> I would like to suggest a workaround to this problem , can you please
>>> check that :
>>>
>>> We have a configuration value named FenceQuietTimeBetweenOperation
>>> sInSec.
>>> It controls the minimal timeout to wait between fence operation (stop,
>>> start),
>>> currently, it is defaulted to 180 sec , The key is not exposed to
>>> engine-config, so, I would suggest to
>>>
>>> 1) Change this key value to 900 by running the following from psql
>>> prompt :
>>>
>>> update vdc_options set option_value = '900' where option_name =
>>> 'FenceQuietTimeBetweenOperationsInSec';
>>>
>>> 2) Restart the engine
>>>
>>> 3) Repeat the scenario
>>>
>>> Now, the engine will require 15 min between fencing operations and your
>>> host can be up again without being fenced again.
>>>
>>> Please let me know if this workaround is working for you
>>>
>>> Thanks
>>>
>>> Eli
>>>
>>> On Tue, Sep 5, 2017 at 4:20 PM, Bernardo Juanicó <bjuan...@gmail.com>
>>> wrote:
>>>
>>>> Martin, thanks for your reply, i was aware of the [1] BUG and the
>>>> implemented solution, changing ServerRebootTimeout to 1200 didnt change a
>>>> thing...
>>>> Now i know about [2] and ill test the fix once it gets released.
>>>>
>>>> Regards,
>>>>
>>>> Bernardo
>>>>
>>>> PGP Key
>>>> <http://pgp.mit.edu/pks/lookup?op=get=0x695E5BCE34263F5B>
>>>> Skype: mattraken
>>>>
>>>> 2017-09-05 8:23 GMT-03:00 Martin Perina <mper...@redhat.com>:
>>>>
>>>>> Hi Bernardo,
>>>>>
>>>>> we have added timeout to wait until host is booted [1] in oVirt 4.1.2.
>>>>> This timeout is by default 5 minutes, but it can be extended using
>>>>> following command:
>>>>>
>>>>>engine-config -s ServerRebootTimeout=NNN
>>>>>
>>>>> where NNN is number of seconds you want to wait until host is booted
>>>>> up.
>>>>>
>>>>> But be aware that you may be affected by [2], which we are currently
>>>>> trying to fix.
>>>>>
>>>>> Regards
>>>>>
>>>>> Martin Perina
>>>>>
>>>>>
>>>>> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1423657
>>>>>

Re: [ovirt-users] Slow booting host - restart loop

[Bernardo Juanicó]

Hi Eli,

I could not access the psql prompt, i tried with the credentials and values
on /etc/ovirt-engine/engine.conf.d/10-setup-database.conf.

I tried interactively and also with a .pgpass file containing:
localhost:5432:engine:engine:PASSWORD

And i get the following error:

psql: FATAL:  Peer authentication failed for user "engine"

Thanks!

Bernardo


PGP Key <http://pgp.mit.edu/pks/lookup?op=get=0x695E5BCE34263F5B>
Skype: mattraken

2017-09-05 12:14 GMT-03:00 Eli Mesika <emes...@redhat.com>:

> Hi Bernardo
>
> I would like to suggest a workaround to this problem , can you please
> check that :
>
> We have a configuration value named FenceQuietTimeBetweenOperationsInSec.
> It controls the minimal timeout to wait between fence operation (stop,
> start),
> currently, it is defaulted to 180 sec , The key is not exposed to
> engine-config, so, I would suggest to
>
> 1) Change this key value to 900 by running the following from psql prompt :
>
> update vdc_options set option_value = '900' where option_name = '
> FenceQuietTimeBetweenOperationsInSec';
>
> 2) Restart the engine
>
> 3) Repeat the scenario
>
> Now, the engine will require 15 min between fencing operations and your
> host can be up again without being fenced again.
>
> Please let me know if this workaround is working for you
>
> Thanks
>
> Eli
>
> On Tue, Sep 5, 2017 at 4:20 PM, Bernardo Juanicó <bjuan...@gmail.com>
> wrote:
>
>> Martin, thanks for your reply, i was aware of the [1] BUG and the
>> implemented solution, changing ServerRebootTimeout to 1200 didnt change a
>> thing...
>> Now i know about [2] and ill test the fix once it gets released.
>>
>> Regards,
>>
>> Bernardo
>>
>> PGP Key <http://pgp.mit.edu/pks/lookup?op=get=0x695E5BCE34263F5B>
>> Skype: mattraken
>>
>> 2017-09-05 8:23 GMT-03:00 Martin Perina <mper...@redhat.com>:
>>
>>> Hi Bernardo,
>>>
>>> we have added timeout to wait until host is booted [1] in oVirt 4.1.2.
>>> This timeout is by default 5 minutes, but it can be extended using
>>> following command:
>>>
>>>engine-config -s ServerRebootTimeout=NNN
>>>
>>> where NNN is number of seconds you want to wait until host is booted up.
>>>
>>> But be aware that you may be affected by [2], which we are currently
>>> trying to fix.
>>>
>>> Regards
>>>
>>> Martin Perina
>>>
>>>
>>> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1423657
>>> [2] https://bugzilla.redhat.com/show_bug.cgi?id=1477700
>>>
>>>
>>> On Fri, Sep 1, 2017 at 7:54 PM, Bernardo Juanicó <bjuan...@gmail.com>
>>> wrote:
>>>
>>>> Hi everyone,
>>>>
>>>> I installed 2 hosts on a new cluster and the servers take a really long
>>>> to boot up (about 8 minutes).
>>>>
>>>> When a host crashes or is powered off the ovirt-manager starts it via
>>>> power management, since the servers takes all that time to boot up the
>>>> ovirt-manager thinks it failed to start and proceeds to reboot it, several
>>>> times before giving up, when the server is finally started (about 20
>>>> minutes after the failure)
>>>>
>>>> I changed some engine variables with engine-config trying to set a
>>>> higher timeout, but the problem persists.
>>>>
>>>> Any ideas??
>>>>
>>>>
>>>> Regards,
>>>> Bernardo
>>>>
>>>>
>>>> PGP Key
>>>> <http://pgp.mit.edu/pks/lookup?op=get=0x695E5BCE34263F5B>
>>>> Skype: mattraken
>>>>
>>>> ___
>>>> Users mailing list
>>>> Users@ovirt.org
>>>> http://lists.ovirt.org/mailman/listinfo/users
>>>>
>>>>
>>>
>>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Slow booting host - restart loop

[Bernardo Juanicó]

Martin, thanks for your reply, i was aware of the [1] BUG and the
implemented solution, changing ServerRebootTimeout to 1200 didnt change a
thing...
Now i know about [2] and ill test the fix once it gets released.

Regards,

Bernardo

PGP Key <http://pgp.mit.edu/pks/lookup?op=get=0x695E5BCE34263F5B>
Skype: mattraken

2017-09-05 8:23 GMT-03:00 Martin Perina <mper...@redhat.com>:

> Hi Bernardo,
>
> we have added timeout to wait until host is booted [1] in oVirt 4.1.2.
> This timeout is by default 5 minutes, but it can be extended using
> following command:
>
>engine-config -s ServerRebootTimeout=NNN
>
> where NNN is number of seconds you want to wait until host is booted up.
>
> But be aware that you may be affected by [2], which we are currently
> trying to fix.
>
> Regards
>
> Martin Perina
>
>
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1423657
> [2] https://bugzilla.redhat.com/show_bug.cgi?id=1477700
>
>
> On Fri, Sep 1, 2017 at 7:54 PM, Bernardo Juanicó <bjuan...@gmail.com>
> wrote:
>
>> Hi everyone,
>>
>> I installed 2 hosts on a new cluster and the servers take a really long
>> to boot up (about 8 minutes).
>>
>> When a host crashes or is powered off the ovirt-manager starts it via
>> power management, since the servers takes all that time to boot up the
>> ovirt-manager thinks it failed to start and proceeds to reboot it, several
>> times before giving up, when the server is finally started (about 20
>> minutes after the failure)
>>
>> I changed some engine variables with engine-config trying to set a higher
>> timeout, but the problem persists.
>>
>> Any ideas??
>>
>>
>> Regards,
>> Bernardo
>>
>>
>> PGP Key <http://pgp.mit.edu/pks/lookup?op=get=0x695E5BCE34263F5B>
>> Skype: mattraken
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] Slow booting host - restart loop

[Bernardo Juanicó]

Hi everyone,

I installed 2 hosts on a new cluster and the servers take a really long to
boot up (about 8 minutes).

When a host crashes or is powered off the ovirt-manager starts it via power
management, since the servers takes all that time to boot up the
ovirt-manager thinks it failed to start and proceeds to reboot it, several
times before giving up, when the server is finally started (about 20
minutes after the failure)

I changed some engine variables with engine-config trying to set a higher
timeout, but the problem persists.

Any ideas??


Regards,
Bernardo


PGP Key 
Skype: mattraken
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users