Bug 1234394 - [RFE] VM Pools allow stateful VMs
Summary: [RFE] VM Pools allow stateful VMs
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: RFEs
Version: 3.5.0
Hardware: x86_64
OS: All
Target Milestone: ovirt-4.0.0-beta
: 4.0.0
Assignee: Shmuel Melamud
QA Contact: sefi litmanovich
Depends On: 1343672
TreeView+ depends on / blocked
Reported: 2015-06-22 13:05 UTC by Olimp Bockowski
Modified: 2019-12-16 04:51 UTC (History)
15 users (show)

Fixed In Version: 4.0.0-12
Doc Type: Enhancement
Doc Text:
Virtual machines from a stateful virtual machine pool are now always started in stateful mode. The state of the virtual machine is preserved even when the virtual machine is passed to a different user.
Clone Of:
Last Closed: 2016-08-23 20:24:15 UTC
oVirt Team: Virt
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2016:1743 0 normal SHIPPED_LIVE Red Hat Virtualization Manager 4.0 GA Enhancement (ovirt-engine) 2016-09-02 21:54:01 UTC
oVirt gerrit 55633 0 master MERGED core: Stateful VM Pools implementation 2016-05-16 15:15:58 UTC

Description Olimp Bockowski 2015-06-22 13:05:07 UTC
Using VM Pools enables to use only stateless virtual machines. There is no options for users to save non-volatile data as well for upgrade system, install or update software.

Comment 2 Omer Frenkel 2015-06-23 07:51:11 UTC
vm-pools are stateless by definition, making it statefull collides with the concept the vm is part of a pool and can be used by different users every time.

did you try to use 'manual' vm-pool? i think this can fit your use case:
in manual vm-pools, user take vm from pool, and the user owns the vm until manually removed by the administrator, the state of the vm is kept even if the vm is stopped, until this manual operation (admin need to remove the user permission from the specific vm).
once the admin removes the user permission from the vm, the state is cleared and the vm is returned to the pool.

this option available under "Type" tab in the new vm-pool dialog.
please update if this works for you.

Comment 3 Michal Skrivanek 2015-07-24 14:11:06 UTC

Comment 5 Sigbjorn Lie 2015-08-03 08:21:04 UTC
Sorry for the late reply, it's been vacation time around here.

Our Windows VDI template does not contain any data, just the VM config and an empty disk. When we deploy the pool, all the pool VM's disks are initially empty and they are all PXE booted off the SCCM server to install Windows in each individual pool VM.

We have tried the manual pool. Even installing these Windows machines in a manual pool failed. All the task sequences in SCCM did not complete for some reason. However using the same VM template for deploying a normal (non-pool) VM  works just fine. 

Never the less, there is personal data stored in the VM which should never be deleted, even if the machine is released from the user (users permission to the machine is removed). This is company policy.

Our RHEL VDI's on the other hand, are using (stateless) automatic pools, and for this use case stateless VM's are working just fine.

If we did manage to get a manual stateless pool for the Windows VDI's working, it would make the machine unusable when the machine was released, as the computer password would have been changed, the central database detailing installed software and patches would be out of sync. And the list goes on over system software that does not support reverting to a previous snapshot without further manual intervention.

Human error may also happen, where the helpdesk personnel may release (remove the permissions from) the incorrect user at the incorrect pool VM. This will cause this user to experience a data loss.

A side note: I'm sure we all agree that personal data should never be stored on the local OS disk, however in a Windows environment that is virtually impossible to achieve.  

Please consider making stateless VM's an option in a pool, not a requirement as it is today.

Comment 14 Tomas Jelinek 2015-12-02 09:05:20 UTC
OK, seems to be a good justification. The feature will be:

- it will be possible to decide to create a stateful pool (new pool dialog/REST API) and also to change the pool from stateful to stateless (edit pool dialog/REST)

- the pool will still be a set of VMs with homogeneous HW - only the content of the disks will be different

Comment 18 Yaniv Lavi 2016-05-09 11:03:00 UTC
oVirt 4.0 Alpha has been released, moving to oVirt 4.0 Beta target.

Comment 21 sefi litmanovich 2016-06-28 10:26:35 UTC
Verified with rhevm- according to test plan.
See test run results:


Comment 23 errata-xmlrpc 2016-08-23 20:24:15 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.