Re: [Users] oVirt 3.2 and 3.2.1: unable to attach cd
On 03/16/2013 01:22 AM, Gianluca Cecchi wrote: On Sat, Mar 16, 2013 at 12:02 AM, Gianluca Cecchi wrote: Hello, lastly with 3.2 and 3.2.1 on F18 hosts I'm not able to attach cd At the window, after selecting iso and click OK I get: Error while executing action Change CD: Drive image file could not be found In webadmin gui events list I get: Failed to change disk in VM winxp (Host: local_host, User: admin@internal). It happens with all iso files I already used before. ISO_DOMAIN is up and they are listed in IMAGES pane Putting into maintenance the iso domain and then activating it solved the problem... but I don't know why... please also attach the vdsm.log from the host here it is engine.log: https://docs.google.com/file/d/0BwoPbcrMv8mvUGRMb01VYkROUm8/edit?usp=sharing system started at 23:26 first attempt of attaching cd at 23:48 then maintenance + activate then successful attempt of attaching cd at 00:16 Gianluca ___ 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: [Users] oVirt 3.2.1 and reports update error
Hi Gianluca On Sat, Mar 16, 2013 at 12:35 AM, Gianluca Cecchi gianluca.cec...@gmail.com wrote: Hello, an all-in-one setup with oVirt 3.2 on Fedora 18. # yum update ovirt-engine-setup and then # engine-upgrade with this output ... During the upgrade process, oVirt Engine will not be accessible. All existing running virtual machines will continue but you will not be able to start or stop any new virtual machines during the process. Would you like to proceed? (yes|no): yes Stopping ovirt-engine service...[ DONE ] Stopping DB related services... [ DONE ] Pre-upgrade validations... [ DONE ] Backing Up Database... [ DONE ] Rename Database... [ DONE ] Updating rpms...[ DONE ] Updating Database...[ DONE ] Restore Database name...[ DONE ] Preparing CA... [ DONE ] Running post install configuration... [ DONE ] Starting ovirt-engine service...[ DONE ] oVirt Engine upgrade completed successfully! * Error: Can't start the ovirt-engine-dwhd service * Upgrade log available at /var/log/ovirt-engine/ovirt-engine-upgrade_2013_03_15_23_16_02.log * Perform the following steps to upgrade the history service or the reporting package: 1. Execute: yum update ovirt-engine-reports* 2. Execute: ovirt-engine-dwh-setup 3. Execute: ovirt-engine-reports-setup * DB Backup available at /var/lib/ovirt-engine/backups/ovirt-engine_db_backup_2013_03_15_23_16_03.sql [root@tekkaman ~]# yum update ovirt-engine-reports* Loaded plugins: fastestmirror, langpacks, presto, refresh-packagekit, versionlock Loading mirror speeds from cached hostfile * fedora: fedora.mirror.garr.it * livna: ftp-stud.fht-esslingen.de * rpmfusion-free: ftp.nluug.nl * rpmfusion-free-updates: ftp.nluug.nl * rpmfusion-nonfree: ftp.nluug.nl * rpmfusion-nonfree-updates: ftp.nluug.nl * updates: ftp.nluug.nl No Packages marked for Update Do I have to consider or not the error regarding reports? Sure, yes; this is being already handled and will be merged into master upstream for ovirt-engine-dwh. After a reboot webadmin is ok but reports appears as totally scrambled: - login page https://docs.google.com/file/d/0BwoPbcrMv8mvQ3piS2xCRnRZdzg/edit?usp=sharing - after login https://docs.google.com/file/d/0BwoPbcrMv8mvNm1VVnk4cDhDR0U/edit?usp=sharing these above are from Fedora 18 and firefox 19.0.2 It seems that something is wrong with CSS loading. Do you have any CSS/JS blocker addons installed in Firefox? Gianluca ___ 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: [Users] engine-setup fails to setup ports when SElinux is disabled
Hi Dennis, all On Fri, Mar 15, 2013 at 10:12 AM, Itamar Heim ih...@redhat.com wrote: On 02/25/2013 06:50 PM, Sandro Bonazzola wrote: Hi Dennis, the bug https://bugzilla.redhat.com/show_bug.cgi?id=893562 has a patch merged in the master tree, it's not included in oVirt 3.2. As a workaround, if you don't want selinux enforcing, enable selinux in permissive mode. Regards, did we backport this to 3.2.1? No, we didn't backport it to 3.2.1; but anyway the 'fix' is exactly the same as the workaround - to enable SELINUX at least in the permissive mode. The real problem lies in Fedora's security policies packages with breaks the functionality of the semanage utility. It is still not fixed in the Fedora repos, thus in our setup we just exit gracefully and ask to turn the selinux on. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users Alex. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] oVirt 3.2.1 Update
On Thu, Mar 14, 2013 at 10:49:28AM -0400, Mike Burns wrote: New RPMS are now uploaded for oVirt 3.2.1. The updates included: ovirt-engine-cli 3.2.0.11-1 ovirt-engine-sdk 3.2.0.10-1 ovirt-engine 3.2.1-1 oVirt Engine changes: 1. Fixed bug blocking firewalld configuration when selinux was in enforcing mode 2. Small change in All-In-One 3. Minor patches at rest-api Also included in the oVirt Engine update are patches to enable EL6 builds. These builds will be posted shortly. To upgrade, please run engine-upgrade. Few days ago (March 14) Federico has rebuilt vdsm for ovirt-3.2 (vdsm-4.10.3-10). It fixes a serious storage bug, and makes glusterfs integration work for el6. I think that it would be good to respin this vdsm build into ovirt-3.2.1, or into a very quick ovirt-3.2.2. Regards, Dan. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Progress on image operations (dd USR1 signal)
- Original Message - Hi, I am using ovirt 3.2 and noticed that during image operations (move, copy) the user has no progress report. This is painful, especially if the images are large or the storage is slow. Vdsm uses 'dd' to transfer images and dd provides a simple progress report, when it receives the USR1 signal. Could this be uses to provide the user with some kind of progress? Actually image operations many times occur with qemu-img command so a solution for dd alone would not suffice, however, this is exactly the reason why we got the qemu folks to add -USR1 support for qemu-img. So this is in general the plan. Unfortunately today as you said we do not yet support progress report for these operations. If you feel like jumping into the code, we'd be more than happy to help you understand where changes need to be made (although I'm not sure this specific change would be trivial). Right now i would do it with myself with strace and kill, but ovirt/vdsm detects an stderr output and reports a failure. Actually it only detects a non zero return code, it shouldn't fail on retcode = 0 even if stderr is nonzero (if you're interested look at execCmd in vdsm/storage/misc.py). What is the retcode of dd if USR1 is called? if it's none zero then I would say this is a bug in dd, if it is zero then it sounds like either something else is going on or that there is a bug in vdsm. You can see the retcode in the vdsm.log together with the stdout and stderr, can you paste those after calling -USR1? $ strace -ff -etrace=write -p `pidof dd` 21 | grep -v 'write(1' # then, in a second terminal I send the signal $ killall -USR1 dd Process 8706 attached - interrupt to quit --- SIGUSR1 (User defined signal 1) @ 0 (0) --- write(2, 14022+0 records in\n14021+0 recor..., 39) = 39 write(2, 14702084096 bytes (15 GB) copied, 32) = 32 write(2, , 2189.75 s, 6.7 MB/s\n, 22) = 22 -- Ernest Beinrohr, AXON PRO Ing http://www.beinrohr.sk/ing.php, RHCE http://www.beinrohr.sk/rhce.php, RHCVA http://www.beinrohr.sk/rhce.php, LPIC http://www.beinrohr.sk/lpic.php, +421-2--6241-0360 callto://+421-2--6241-0360, +421-903--482-603 callto://+421-903--482-603 icq:28153343, skype:oernii-work callto://oernii-work, jabber:oer...@jabber.org “The bureaucracy is expanding to meet the needs of the expanding bureaucracy.” ― Oscar Wilde ___ 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] High Availability
What should I need to configure to put HA working? I mean, when a host broke all the VM automatically move to another host. Do I need to have Power management enabled? Thanks ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] High Availability
Currently it only applies to server VMs Go to Add/Edit VM dialogue - High Availability tab - mark the check box. and you are done. If this interests you stay on the lookout for: http://www.ovirt.org/Features/Watchdog_engine_support Noam. - Original Message - From: supo...@logicworks.pt To: Users@ovirt.org Sent: Sunday, March 17, 2013 6:27:53 PM Subject: [Users] High Availability What should I need to configure to put HA working? I mean, when a host broke all the VM automatically move to another host. Do I need to have Power management enabled? Thanks ___ 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: [Users] High Availability
Hi, You have to configure power management to make high availability working and mark the vms high availability checkbox... Regards, René -Original message- From:supo...@logicworks.pt supo...@logicworks.pt Sent: Sunday 17th March 2013 17:28 To: Users@ovirt.org Subject: [Users] High Availability What should I need to configure to put HA working? I mean, when a host broke all the VM automatically move to another host. Do I need to have Power management enabled? Thanks ___ 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: [Users] High Availability
Is it Mandatory to have power manamement enabled? if yes what equipment do you recommend to use with it? Regards Jose - Mensagem original - De: René Koch r.k...@ovido.at Para: supo...@logicworks.pt, Users@ovirt.org Enviadas: Domingo, 17 Março, 2013 16:47:41 Assunto: RE: [Users] High Availability Hi, You have to configure power management to make high availability working and mark the vms high availability checkbox... Regards, René -Original message- From:supo...@logicworks.pt supo...@logicworks.pt Sent: Sunday 17th March 2013 17:28 To: Users@ovirt.org Subject: [Users] High Availability What should I need to configure to put HA working? I mean, when a host broke all the VM automatically move to another host. Do I need to have Power management enabled? Thanks ___ 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: [Users] High Availability
I think that there is some confusion here so I will explain what are the configurations for fail-over. power management will reboot your host if a connectivity issue is detected so all your vm's will be killed. resilience policy will allow you to choose vm migration policy during a host failure and its configured in the cluster level (clusters - select cluster - general sub tab - edit policy) High Availability is configured only for servers type vm's and what it does is re-run the vm in case the pid of the vm is killed (so most commonly, if you have power management configured, and the host is rebooted, the vm will start automatically on a different host). so it really depends what you want. if you want vm migration than look into cluster policy, if you want a specific vm to always be up and you don't care about the other vm's than configure power management and a HA vm. it really depends on what you need. On 03/17/2013 07:15 PM, supo...@logicworks.pt wrote: Is it Mandatory to have power manamement enabled? if yes what equipment do you recommend to use with it? Regards Jose - Mensagem original - De: René Koch r.k...@ovido.at Para: supo...@logicworks.pt, Users@ovirt.org Enviadas: Domingo, 17 Março, 2013 16:47:41 Assunto: RE: [Users] High Availability Hi, You have to configure power management to make high availability working and mark the vms high availability checkbox... Regards, René -Original message- From:supo...@logicworks.pt supo...@logicworks.pt Sent: Sunday 17th March 2013 17:28 To: Users@ovirt.org Subject: [Users] High Availability What should I need to configure to put HA working? I mean, when a host broke all the VM automatically move to another host. Do I need to have Power management enabled? Thanks ___ 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 -- Dafna Ron ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] host power managment failures
On 03/16/2013 04:43 PM, Joop wrote: Jorick Astrego wrote: Having the same problem here. I installed the 3 nodes from iso and registered them to oVirt. In ovirt I approved them and added the Power Management settings. The source list is empty and Test fails with the message there is no other host to test it from. 2 Installing the node from ovirt with ssh appears to work ok, there I see as source cluster and dc to test it. Just found out if I register the node and approve without power management, I can then edit the node and enable/test powermanagent. Approving the node and enabling power management at the same time fails. If you try to register the FIRST node and try to set powermanagment then it will fail. Reason is because the check is done from another host in the cluster en since there is none it will error. Have been bitten by this multiple times when adding a host and thinking I could start adding a second before the first was ready. Adding a second and third in parallel when the first is ready should be no problem. jorick - if your use case isn't for the first node, please open a bug with details. Joop - if you got bitten, worth opening a bug to fix this to warn others... please do. thanks, Itamar ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] how the default bridge network is created.
hi in network table, there is a type column , how many kinds of value of column type? thanks At 2013-03-17 14:27:49,Mike Kolesnik mkole...@redhat.com wrote: hi,all Hi, vdsmgmt network is created defaultly, i want to know how and where ? You probably mean 'ovirtmgmt' network. Currently, It is created during the host's installation/bootstrap - it is one of the steps. The is a plan to have it created from engine side instead of host side: http://www.ovirt.org/Features/Normalized_ovirtmgmt_Initialization i now need to add my own network, better to refer to ovirt'default network. 1.if i need to insert network info into DB 2.how to start up the default network , 1)just put a network xml in right place, let libvirt tak care of it. 2)when start agent or engine, call add network API to product a network dynamicly? 3.in network table, what is column type, how many of this type. thanks. I would advise that you add the network through one of the clients: WEB/REST API since there are more steps involved, and the clients already take care of it. The 3 steps are: 1. Add network under the data center of your choice. 2. Attach the network to the cluster of your choice (under the aforementioned data center). 3. Use Setup Networks command on the hosts in the cluster to put the network on a NIC. Regards, Mike ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] High Availability
You might also find this helpful: https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Virtualization/3.1/html/Administration_Guide/High_availability_considerations.html The topics before and after it explain a bit more about high availability. Tim Hildred, RHCE Content Author II - Engineering Content Services, Red Hat, Inc. Brisbane, Australia Email: thild...@redhat.com Internal: 8588287 Mobile: +61 4 666 25242 IRC: thildred - Original Message - From: Dafna Ron d...@redhat.com To: supo...@logicworks.pt Cc: Users@ovirt.org Sent: Monday, March 18, 2013 4:46:51 AM Subject: Re: [Users] High Availability I think that there is some confusion here so I will explain what are the configurations for fail-over. power management will reboot your host if a connectivity issue is detected so all your vm's will be killed. resilience policy will allow you to choose vm migration policy during a host failure and its configured in the cluster level (clusters - select cluster - general sub tab - edit policy) High Availability is configured only for servers type vm's and what it does is re-run the vm in case the pid of the vm is killed (so most commonly, if you have power management configured, and the host is rebooted, the vm will start automatically on a different host). so it really depends what you want. if you want vm migration than look into cluster policy, if you want a specific vm to always be up and you don't care about the other vm's than configure power management and a HA vm. it really depends on what you need. On 03/17/2013 07:15 PM, supo...@logicworks.pt wrote: Is it Mandatory to have power manamement enabled? if yes what equipment do you recommend to use with it? Regards Jose - Mensagem original - De: René Koch r.k...@ovido.at Para: supo...@logicworks.pt, Users@ovirt.org Enviadas: Domingo, 17 Março, 2013 16:47:41 Assunto: RE: [Users] High Availability Hi, You have to configure power management to make high availability working and mark the vms high availability checkbox... Regards, René -Original message- From:supo...@logicworks.pt supo...@logicworks.pt Sent: Sunday 17th March 2013 17:28 To: Users@ovirt.org Subject: [Users] High Availability What should I need to configure to put HA working? I mean, when a host broke all the VM automatically move to another host. Do I need to have Power management enabled? Thanks ___ 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 -- Dafna Ron ___ 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: [Users] High Availability
If one host is down because of network interrupt or power failure, the engine should know how many HA VMs are down and find out the VM images on the storage domain to start the VM instances on another host in the cluster. Why do we need power manager to be configured? Power management allows the Manager to start highly available virtual machines on new hosts without worrying that virtual machine hard disk images will be corrupted. Imagine a situation in which the Manager cannot communicate with the host a highly available virtual machine is running on. If the host is still running as expected, and the virtual machine is also still running, the virtual machine is writing to its hard disk image. If the Manager starts that virtual machine on another host in the cluster, then both virtual machine instances will try and write to the disk image, and cause hard disk corruption. Power management lets the Manager be sure that only one instance of the highly available virtual machine is running, because the instance on the host the Manager couldn't communicate cannot survive a host reboot. Tim Hildred, RHCE Content Author II - Engineering Content Services, Red Hat, Inc. Brisbane, Australia Email: thild...@redhat.com Internal: 8588287 Mobile: +61 4 666 25242 IRC: thildred - Original Message - From: Shu Ming shum...@linux.vnet.ibm.com To: Tim Hildred thild...@redhat.com Cc: d...@redhat.com, Users@ovirt.org Sent: Monday, March 18, 2013 1:31:12 PM Subject: Re: [Users] High Availability Tim, Thanks for your information. I am not sure why we need power management to be configured for the hosts running HA virtual machines. We only need a method to check the VM or host status and a method to restart the VM instances with existing VM images on another host. Is it required to force powering down the failing host forever to make sure the failing host will not come back to live again? * Power management must be configured for the hosts running the highly available virtual machines. * The host running the highly available virtual machine must be part of a cluster which has other available hosts. * The destination host must be running. * The source and destination host must have access to the data domain on which the virtual machine resides. * The source and destination host must have access to the same virtual networks and VLANs. * There must be enough CPUs on the destination host that are not in use to support the virtual machine's requirements. * There must be enough RAM on the destination host that is not in use to support the virtual machine's requirements. Tim Hildred: You might also find this helpful: https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Virtualization/3.1/html/Administration_Guide/High_availability_considerations.html The topics before and after it explain a bit more about high availability. Tim Hildred, RHCE Content Author II - Engineering Content Services, Red Hat, Inc. Brisbane, Australia Email: thild...@redhat.com Internal: 8588287 Mobile: +61 4 666 25242 IRC: thildred - Original Message - From: Dafna Ron d...@redhat.com To: supo...@logicworks.pt Cc: Users@ovirt.org Sent: Monday, March 18, 2013 4:46:51 AM Subject: Re: [Users] High Availability I think that there is some confusion here so I will explain what are the configurations for fail-over. power management will reboot your host if a connectivity issue is detected so all your vm's will be killed. resilience policy will allow you to choose vm migration policy during a host failure and its configured in the cluster level (clusters - select cluster - general sub tab - edit policy) High Availability is configured only for servers type vm's and what it does is re-run the vm in case the pid of the vm is killed (so most commonly, if you have power management configured, and the host is rebooted, the vm will start automatically on a different host). so it really depends what you want. if you want vm migration than look into cluster policy, if you want a specific vm to always be up and you don't care about the other vm's than configure power management and a HA vm. it really depends on what you need. On 03/17/2013 07:15 PM, supo...@logicworks.pt wrote: Is it Mandatory to have power manamement enabled? if yes what equipment do you recommend to use with it? Regards Jose - Mensagem original - De: René Koch r.k...@ovido.at Para: supo...@logicworks.pt , Users@ovirt.org Enviadas: Domingo, 17 Março, 2013 16:47:41 Assunto: RE: [Users] High Availability Hi, You have to configure power management to make high availability working and mark the vms high availability checkbox... Regards, René -Original message- From:supo...@logicworks.pt supo...@logicworks.pt Sent: Sunday 17th March 2013 17:28 To: Users@ovirt.org Subject:
Re: [Users] High Availability
Tim Hildred: If one host is down because of network interrupt or power failure, the engine should know how many HA VMs are down and find out the VM images on the storage domain to start the VM instances on another host in the cluster. Why do we need power manager to be configured? Power management allows the Manager to start highly available virtual machines on new hosts without worrying that virtual machine hard disk images will be corrupted. Imagine a situation in which the Manager cannot communicate with the host a highly available virtual machine is running on. If the host is still running as expected, and the virtual machine is also still running, the virtual machine is writing to its hard disk image. Tim, Thanks for clarification. That is what I expected. If the Manager starts that virtual machine on another host in the cluster, then both virtual machine instances will try and write to the disk image, and cause hard disk corruption. Power management lets the Manager be sure that only one instance of the highly available virtual machine is running, because the instance on the host the Manager couldn't communicate cannot survive a host reboot. Tim Hildred, RHCE Content Author II - Engineering Content Services, Red Hat, Inc. Brisbane, Australia Email: thild...@redhat.com Internal: 8588287 Mobile: +61 4 666 25242 IRC: thildred - Original Message - From: Shu Ming shum...@linux.vnet.ibm.com To: Tim Hildred thild...@redhat.com Cc: d...@redhat.com, Users@ovirt.org Sent: Monday, March 18, 2013 1:31:12 PM Subject: Re: [Users] High Availability Tim, Thanks for your information. I am not sure why we need power management to be configured for the hosts running HA virtual machines. We only need a method to check the VM or host status and a method to restart the VM instances with existing VM images on another host. Is it required to force powering down the failing host forever to make sure the failing host will not come back to live again? * Power management must be configured for the hosts running the highly available virtual machines. * The host running the highly available virtual machine must be part of a cluster which has other available hosts. * The destination host must be running. * The source and destination host must have access to the data domain on which the virtual machine resides. * The source and destination host must have access to the same virtual networks and VLANs. * There must be enough CPUs on the destination host that are not in use to support the virtual machine's requirements. * There must be enough RAM on the destination host that is not in use to support the virtual machine's requirements. Tim Hildred: You might also find this helpful: https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Virtualization/3.1/html/Administration_Guide/High_availability_considerations.html The topics before and after it explain a bit more about high availability. Tim Hildred, RHCE Content Author II - Engineering Content Services, Red Hat, Inc. Brisbane, Australia Email: thild...@redhat.com Internal: 8588287 Mobile: +61 4 666 25242 IRC: thildred - Original Message - From: Dafna Ron d...@redhat.com To: supo...@logicworks.pt Cc: Users@ovirt.org Sent: Monday, March 18, 2013 4:46:51 AM Subject: Re: [Users] High Availability I think that there is some confusion here so I will explain what are the configurations for fail-over. power management will reboot your host if a connectivity issue is detected so all your vm's will be killed. resilience policy will allow you to choose vm migration policy during a host failure and its configured in the cluster level (clusters - select cluster - general sub tab - edit policy) High Availability is configured only for servers type vm's and what it does is re-run the vm in case the pid of the vm is killed (so most commonly, if you have power management configured, and the host is rebooted, the vm will start automatically on a different host). so it really depends what you want. if you want vm migration than look into cluster policy, if you want a specific vm to always be up and you don't care about the other vm's than configure power management and a HA vm. it really depends on what you need. On 03/17/2013 07:15 PM, supo...@logicworks.pt wrote: Is it Mandatory to have power manamement enabled? if yes what equipment do you recommend to use with it? Regards Jose - Mensagem original - De: René Koch r.k...@ovido.at Para: supo...@logicworks.pt , Users@ovirt.org Enviadas: Domingo, 17 Março, 2013 16:47:41 Assunto: RE: [Users] High Availability Hi, You have to configure power management to make high availability working and mark the vms high availability checkbox... Regards, René -Original message- From:supo...@logicworks.pt supo...@logicworks.pt Sent: Sunday 17th March 2013 17:28 To: Users@ovirt.org Subject: [Users] High Availability What should I
