State of guest VMs when RHEV-Manager is down

Latest response

Hi,

What would happen to the state of guest VMs when RHEV-Manager (non-HA) which created/manages these VMs goes down due to user/host sever reboot.
Will there be any network outage w.r.t to the guest VMs, is communication between VMs affected and will the RHEV-Manager auto detect hanging guest VMs and further takes care of its status.

Responses

The guests continue to run. The hypervisors provide network access, so guest connectivity is not affected.

The manager provides the ability to manage guest lifecycle, guest configuration, and migrate guests to other hosts. So when the RHEV-M is down, you lose the ability to change those things.

When the RHEV-M comes back up, it will have an idea of the guest state in its database, and will communicate with the hypervisors to re-establish that state. You should not go changing things on the hypervisors manually while the RHEV-M is down.

Thanks Jamie. Just couple of more queries. 1) What would happen if guest VM (non-HA mode) goes down/reboots for some reason when RHEV-M is already down. Will it come up by itself or will it be brought back when the manager comes up. 2) How many total RHEL and RHV licenses are required in the below setup which i'm trying to bring up.

If the VM OS reboots, it's just a software reboot with no change in the VM lifecycle state.

If the VM OS shuts down, I believe the hypervisor should tell the RHEV-M about the state change with the manager comes back online. There is no (good, supported) way to start or restart a down guest without the manager.

The easiest way to license is to purchase the RHV entitlement with unlimited guests, your Hosted Engine then consumes one of those entitlements and you just add the manager channel to the Hosted Engine VM.

If you don't wish to purchase the unlimited licenses, then I am not sure of the current offerings. Sales or Customer Service or Tech Support should be able to confirm the licensing required for your specific needs.

Thanks again Jamie, sorry i missed out on the attachment, i have attached the snapshot to the main thread as i could not do the same to this reply. Please refer the same.

We are trying to do self-hosted engine deployment by following RHEL self-hosted document. So we installed RHEL 7.3 as Host OS and this server is registered. On top of that we subscribed to RHV 4.1 and enabled below repos. • subscription-manager repos --enable=rhel-7-server-rpms • subscription-manager repos --enable=rhel-7-server-rhv-4-mgmt-agent-rpms After enabling above repos we ran "hosted-engine --deploy" and spawned RHEV-Manager as a VM. Queries are: 1. When we subscribed to RHV 4.1 on host server to enable the above repos, will it use a RHV license? 2. RHEV-Manager VM contain thin layer of RHEL OS 7.3 as its guest OS. Do I need to register this RHEL also with a new license? 3. Can the license be reused by removing the RHEL subscription from Host OS and reattach to the VM to be used as manager. 4. Let us know how many total RHEL and RHV licenses are required in the below setup?

For specifics like this I am not sure sorry, you'd be best to open a support case for these questions.

Thanks Jamie, will open a support case for this one.

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.