It looks clear and cool. Thank you.
- Sent from my mobile phone. Sorry for typos -
Il lun 23 set 2019, 21:46 Alex McWhirter ha scritto:
> To achieve that all you need to do is create a template of the desktop
> base vm, make sure the vm type is set to desktop. Afterwards just create
> new vms from that template. As long as the VM type is set to desktop each
> new VM will use a qcow overlay on top of the base image.
>
> Taking this a step further you can then create VM pools from said
> template, allowing users to dynamically be assigned a new VM on login.
> Granted pools are usually stateless, so you need to have network file
> storage. We use pools for windows 10 VDI instances, where we use sysprep to
> autojoin the new pool vm to the domain where redirected folders are already
> setup.
>
> For VDI only use spice protocol. By default we found spice to be semi
> lackluster, so we do apply custom settings and we have recompiled spice on
> both servers and clients with h264 support. This is not 100% necessary, but
> makes things like youtube much more usable. We have also backported some
> audio patches to KVM. CentOS 8 should resolve a lot of these customizations
> that we've had to do.
>
>
> As far as updating, pretty much. We create a VM from the template, update
> it, then push it back as a new version of the template. The pools are set
> to always use the latest template version. Users have to log out, then back
> in to the VDI system in order to get the new image as logging out will
> destroy the users current instance and create a new one on log in.
>
>
> On 2019-09-23 15:16, Fabio Marzocca wrote:
>
> Hi Alex, thanks for answering.
>
> I am approaching and studying oVirt in order to propose the solution to a
> customer as a replacement for a commercial solution they have now.
> They only need Desktop virtualization.
> Sorry for the silly question, but I can't find a way to deploy a VM
> (template) to users as a "linked-clone", meaning that the users' image
> still refers to the original image but modification are written (and
> afterwards read) from a new location. This technique is called
> Copy-on-write.
> Can this be achieved with oVirt?
>
>
> Then, what is the Best Practice to update WIndows OS for the all the
> users? Currently they simply "check-out" the Gold Image, update it and
> check-in, while all users are running...
>
> Fabio
>
> On Mon, Sep 23, 2019 at 8:04 PM Alex McWhirter wrote:
>
>> yes, we do. All spice, with some customizations done at source level for
>> spice / kvm packages.
>>
>>
>> On 2019-09-23 13:44, Fabio Marzocca wrote:
>>
>> Is there anyone who uses oVirt as a full VDI environment? I would have a
>> bunch of questions...
>>
>>
>>
>> ___
>> Users mailing list -- users@ovirt.org
>> To unsubscribe send an email to users-le...@ovirt.org
>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
>> oVirt Code of Conduct:
>> https://www.ovirt.org/community/about/community-guidelines/
>> List Archives:
>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/D44YB5VOKNBNCJSOMLKRAZBURFJLAOLM/
>>
>>
>>
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/TXWKRNSXAMP3T5TOBYCB5K7JHXL5YOK7/
