- Users - oVirt List Archives

oVirt + Proxmox Backup Server
by Diggy Mc 02 Feb '21

02 Feb '21

Is anyone using Proxmox Backup Server to backup VMs in an oVirt environment? Is it even possible? I'm looking for a free open-source solution for my backup needs (backup VMs as well as traditional file backups). Any guidance is appreciated.

6 6

move ovirt 4.3.9 to RHEL 8
by Paul Dyer 01 Feb '21

01 Feb '21

Hi, I am laying the groupwork for upgrade ovirt to 4.4. Since the standalone ovirt mgr is now running on RHEL 7, I have installed RHEL 8 to a new VM. Unfortunately, after installing ovirt-release43, I am not able to find documentation for the dnf modules required. All the current documentation point to ovirt-release44 and dnf modules not available for ovirt 4.3/RHEL 8. I have these repos enabled... Repo ID: ansible-2-for-rhel-8-x86_64-rpms Repo ID: rhel-8-for-x86_64-appstream-rpms Repo ID: rhel-8-for-x86_64-baseos-rpms I am looking setup docs for a standalone engine of ovirt 4.3 on RHEL 8. Thanks! -- Paul Dyer, Mercury Consulting Group, RHCE 504-338-8750

4 5

Re: AFFINITY GROUPS
by LS CHENG 01 Feb '21

01 Feb '21

ok thank you Is AFFINITY GROUPS extensively used? Cheers On Sun, Jan 31, 2021 at 10:42 AM Kim Kargaard <Kim.Kargaard(a)noroff.no> wrote: > You can select multiple hosts when selecting which host the VM can run on. > > Kim > ------------------------------ > *From:* LS CHENG <lsc.oraes(a)gmail.com> > *Sent:* Sunday, January 31, 2021 9:51 AM > *To:* Strahil Nikolov <hunter86_bg(a)yahoo.com> > *Cc:* users(a)ovirt.org <users(a)ovirt.org> > *Subject:* [ovirt-users] Re: AFFINITY GROUPS > > Hi > > Yes, that can be trick as well. I am using affinity rules because I am > trying to extend to more combinations. For examples 4 hosts and a vm can > run in 2 hosts only etc. > > Thanks > > On Sun, Jan 31, 2021 at 9:14 AM Strahil Nikolov <hunter86_bg(a)yahoo.com> > wrote: > > Why don't you go to VM settings and define that vm01 can run only on > host_x? > If the host is down, it won't start on host_y. > > Best Regards, > Strahil Nikolov > Sent from Yahoo Mail on Android > <https://go.onelink.me/107872968?pid=InProduct&c=Global_Internal_YGrowth_And…> > > On Sat, Jan 30, 2021 at 23:09, LS CHENG > <lsc.oraes(a)gmail.com> wrote: > Hi > > I would like to know how AFFINITY GROUPS works. > > I have 2 VM in 2 hosts, each VM runs in a host. Let's call > > HOST_X where vm01 runs > HOST_Y where vm02 runs > > I have set up an affinity group where it says vm01 relates to HOST_X, vm02 > relates to HOST_Y. VM affinity rule is set to negative and HOST affinity > rule set to positive. I need both vm01 and vm02 to run in their respective > physical host. > > I have a problem, when vm01 is stopped and HOST_Y is rebooted vm02 starts > in HOST_X, how can I avoid that? > > Thank you > > Luis Sanchez > > > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)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/users@ovirt.org/message/C74WDKK2SSFA3… > >

1 0

Custom Fence Agent
by Robert Tongue 31 Jan '21

31 Jan '21

Greetings everyone, I am having another problem that I was hoping to get some assistance with. I have created my own custom fence agent for some tasmota-flashed wifi smart plugs, that can control plug power input to ovirt nodes. This works great; however I am running into a problem getting it added to ovirt as a power manager. I got the custom fence agent added with engine-config -s, and it shows up in the webui to select as a power management agent, then I put in the details for the plug, IP address, login, password, and press the "test" button, which passes, and shows the status as power=on. Once I save the settings, however, it is logged in the engine.log file that fencing will fail, because there is no node available to proxy the operation. When I go back into the power management settings, and press "test" again, then I get the error: "Test failed: Failed to run fence status-check on host 'ovirt1'. No other host was available to serve as proxy for the operation." I have the agent script in /usr/sbin/ on all nodes, execute permissions set, and I can run it manually at the command line just fine, so I am really at a loss here as what to check. What am I missing here? Please help. Thank you for your time. Script: #!/usr/libexec/platform-python -tt from urllib.parse import quote import requests import sys import atexit sys.path.append("/usr/share/fence") from fencing import * def set_power_status(conn, options): if "on" in options["--action"]: response = requests.get(buildUrl(options, "on")) elif "off" in options["--action"]: response = requests.get(buildUrl(options, "off")) return def get_power_status(conn, options): response = requests.get(buildUrl(options, "status")) if "\"Power\":0" in response.text: return "off" elif "\"Power\":1" in response.text: return "on" def buildUrl(options, action): cmnd = { 'on' : 'Power On', 'off' : 'Power Off', 'status' : 'Status' } return "http://" + options["--ip"] + "/cm?user=" + quote(options["--username"]) + "&password=" + quote(options["--password"]) + "&cmnd=" + quote(cmnd.get(action, "Error")) def main(): device_opt = ["ipaddr", "login", "passwd", "web"] atexit.register(atexit_handler) all_opt["power_wait"]["default"] = 5 options = check_input(device_opt, process_input(device_opt)) docs = {} docs["shortdesc"] = "Fence agent for Tasmota-flashed Smarthome Plugs" docs["longdesc"] = "" docs["vendorurl"] = "" show_docs(options, docs) ## ## Fence operations #### result = fence_action(None, options, set_power_status, get_power_status) sys.exit(result) if __name__ == "__main__": main()

1 0

AFFINITY GROUPS
by LS CHENG 31 Jan '21

31 Jan '21

Hi I would like to know how AFFINITY GROUPS works. I have 2 VM in 2 hosts, each VM runs in a host. Let's call HOST_X where vm01 runs HOST_Y where vm02 runs I have set up an affinity group where it says vm01 relates to HOST_X, vm02 relates to HOST_Y. VM affinity rule is set to negative and HOST affinity rule set to positive. I need both vm01 and vm02 to run in their respective physical host. I have a problem, when vm01 is stopped and HOST_Y is rebooted vm02 starts in HOST_X, how can I avoid that? Thank you Luis Sanchez

3 3

recovering gluster volumes when moving hosts to a new datacenter
by Nathanaël Blanchet 30 Jan '21

30 Jan '21

Hi, I moved 3 hosts (for replica 3 volume) from a previous datacenter to a new datacenter. Those hosts had initially been configured in a gluster cluster and managed multiple gluster volume created with ovirt UI. These hosts are now apart of a new gluster cluster and they see each others with cli "gluster peer status" as well as the associated volumes "gluter volumes list". But I can't make gluster volumes visible in the usually "volume" tab, so ovirt doesn't seem to see them. Is there a way to import pre existing gluster volume so as to ovirt be able to manage them ? Thanks. -- Nathanaël Blanchet Supervision réseau SIRE 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 14 blanchet(a)abes.fr

2 2

Windows 10 on older CPUs
by Chris Adams 29 Jan '21

29 Jan '21

I have an oVirt cluster running 4.3.10 on older hardware with a cluster CPU type of Intel Nehalem. I needed to install a Windows 10 (latest release) VM, which oVirt rejected because of the CPU model. I remember there being issues with certain versions of Windows and this CPU model under oVirt (I don't do Windows very often and had forgotten). I instead told oVirt I was installing Windows 8 (which it accepted), and then installed - it installed and appears to be working just fine. I don't know if Microsoft changed whatever used to break or what... I remember the problem before not even getting through install, so it seems to be okay. Any issues I should be worried about? -- Chris Adams <cma(a)cmadams.net>

1 0

ovirt node ng 4.4 crash in anaconda when setting ntp
by Gianluca Cecchi 29 Jan '21

29 Jan '21

Hello, when installing ovirt node ng 4.4 on a Dell M620 I remember I had a crash in anaconda if I try to set up ntp. Using ovirt-node-ng-installer-4.4.4-2020122111.el8.iso As soon as I select it and try to type the hostname to use, all stops and then anaconda aborts. Just today I had the same with the latest RHVH 4.4 iso: RHVH-4.4-20201210.0-RHVH-x86_64-dvd1.iso on an R630. Quite disappointing because I also have to fight with iDRAC8 to install the OS: it is slow to die. In practice I waste about one hour.... Is anyone aware of it or able to reproduce on another platform so that eventually I'm going to open a bug/case for it? My config is default one in anaconda accepting default and creating a bonded connection (LACP). Then as the last step I go into the set time/date and click on the ntp button and I get the problem as soon as I try to type inside the text box. Thanks, Gianluca

1 1

LVM Filesystem not mount VMStore
by marcel＠deheureu.se 29 Jan '21

29 Jan '21

Hi, We got the following error message from our 3 Server Setup this morning. Two of the servers where switched off by a "User". Simply power off. One of the server startup well and the other one provide the following message. What should we do first, we can't mount the vmstore manual. The system takes a lot of minutes. Did anyone have an idea? Br Marcel

5 5

[ANN] oVirt 4.4.5 Third Release Candidate is now available for testing
by Sandro Bonazzola 29 Jan '21

29 Jan '21

oVirt 4.4.5 Third Release Candidate is now available for testing The oVirt Project is pleased to announce the availability of oVirt 4.4.5 Third Release Candidate for testing, as of January 29th, 2021. This update is the fifth in a series of stabilization updates to the 4.4 series. How to prevent hosts entering emergency mode after upgrade from oVirt 4.4.1 Note: Upgrading from 4.4.2 GA or later should not require re-doing these steps, if already performed while upgrading from 4.4.1 to 4.4.2 GA. These are only required to be done once. Due to Bug 1837864 <https://bugzilla.redhat.com/show_bug.cgi?id=1837864> - Host enter emergency mode after upgrading to latest build If you have your root file system on a multipath device on your hosts you should be aware that after upgrading from 4.4.1 to 4.4.5 you may get your host entering emergency mode. In order to prevent this be sure to upgrade oVirt Engine first, then on your hosts: 1. Remove the current lvm filter while still on 4.4.1, or in emergency mode (if rebooted). 2. Reboot. 3. Upgrade to 4.4.5 (redeploy in case of already being on 4.4.5). 4. Run vdsm-tool config-lvm-filter to confirm there is a new filter in place. 5. Only if not using oVirt Node: - run "dracut --force --add multipath” to rebuild initramfs with the correct filter configuration 6. Reboot. Documentation - If you want to try oVirt as quickly as possible, follow the instructions on the Download <https://ovirt.org/download/> page. - For complete installation, administration, and usage instructions, see the oVirt Documentation <https://ovirt.org/documentation/>. - For upgrading from a previous version, see the oVirt Upgrade Guide <https://ovirt.org/documentation/upgrade_guide/>. - For a general overview of oVirt, see About oVirt <https://ovirt.org/community/about.html>. Important notes before you try it Please note this is a pre-release build. The oVirt Project makes no guarantees as to its suitability or usefulness. This pre-release must not be used in production. Installation instructions For installation instructions and additional information please refer to: https://ovirt.org/documentation/ This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 8.3 or newer * CentOS Linux (or similar) 8.3 or newer This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 8.3 or newer * CentOS Linux (or similar) 8.3 or newer * oVirt Node 4.4 based on CentOS Linux 8.3 (available for x86_64 only) 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 - We found a few issues while testing on CentOS Stream so we are still basing oVirt 4.4.5 Node and Appliance on CentOS Linux. Additional Resources: * Read more about the oVirt 4.4.5 release highlights: http://www.ovirt.org/release/4.4.5/ * Get more oVirt project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] http://www.ovirt.org/release/4.4.5/ [2] http://resources.ovirt.org/pub/ovirt-4.4-pre/iso/ -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/> *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

1 0