[ovirt-users] Re: VDI management on top of Ovirt
Hi Samuel, how are you? I'm trying with OpenUDS (https://github.com/dkmstr/openuds). It's suffer from lack of documentation but at this time appears to be very good. Best regards, Vinicius. ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/YG6K26WGDSCWB3W6HIQIQ2YDK6SWVP5F/
[ovirt-users] Re: VDI and ovirt
Alex From your response it looks you were able to use spicehtml5 using a squid proxy. Do you mind sharing your setup or some howto ou followed. I have been wanting to deploy it in our setup. TIA Pascal ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/APOEDY7XEIVPJ6SDGLFMEVHRHE77KZO6/
[ovirt-users] Re: VDI and ovirt
On 2021-02-23 07:39, cpo cpo wrote: Is anyone using Ovirt for a Windows 10 VDI deployment? If so are you using a connection broker? If you are what are you using? Thanks for your time We use ovirt quite a lot for windows 10 vdi, 4.4 / EL8 is quite a bit nicer spice version wise. No broker needed, ovirt does that pretty well on it's own. We do use squid as a spice http proxy however. We just have pools of vms based on sysprep'd images. We also repurposed some HP thin clients, installed centos minimal + openbox, wrote a small application that accepts user credentials and gets a spice connection via the ovirt API. ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/COB73ASC5UIJIC5SZHG43BIULPUD7W4L/
[ovirt-users] Re: VDI
Alex, how to assign users (or groups) to a Pool? ___ 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/TZBFUX3RSYERV3XNMWJYOHC7Q6FC2VEU/
[ovirt-users] Re: VDI
Thank you very much for the informations. I'm am sorry for my lack of knowledge, but the vGPU / vm graphical performance part is a bit confusing for me at the moment. As far as i've understood, if some real decent graphical performance is needed for the vms, the only proper way is to install a grid supported gpu card on the hypervisor, and have the "slices" assigned to the vms. A rough look show that this will add at least 4k - 5k dollars per node... Just as a reference, its only about "office type" vdi's that only do web browsing and sometimes youtube videos / skype calls. Any thoughts for a more less expensive way to achieve this ? Again, thank you very much ! On Sun, Oct 6, 2019 at 12:22 PM Alex McWhirter wrote: > We use customized versions of spice / kvm. Same versions ovirt ships with > for compatibility reasons, with audio patches on the kvm side and spice > patches for vp8 encoding the video streams. We've been meaning to make the > repo for our custom patched versions public for a while, if you are > interested i can accelerate that. Note, you also need patched versions of > spice client if yours wasn't build with vp8 support, we have those too. > > On the experimental side we have another in-progress set of patches that > enable h264 encoding in spice, hardware accelerated with AMD W5100's, but > this requires a lot of new software to be installed and a new kernel, > CentOS 8 should fix most of that, so we'll probably re-base and release on > that when the time is right. > > The GPU's are not used for the guests at all, we only use them for the > h264 encoding. AMD was picked to avoid proprietary drivers and stream > limits. No RAM / SR-IOV needed, if you want 3d support you will be looking > more for Nvidia-GRID. > > > Anyways, with just the patched software installed and some custom > settings, video playback is about 95% the quality of native, takes about > 40mbit/s per client to stream it. Audio has the occasional stutter, but > it's not bad. > > > On 2019-10-06 05:09, Leo David wrote: > > Thank you for sharing the informations Alex, they are very helpfull. I am > now able to get sound from the vms, although performance is pretty poor > even with "adjust for performance" setting in Win10. Cannot even talk > about youtube video playing - freezing and crackling. > Could you please be so kind to share the following infos: > 1. Have you upgraded the "spice-server" installed on the hosts with a > newer version than 1.4.0 ? If so, could you provide me how could I get > these packages ? > 2. What graphic card have you used for getting better graphic performance > with the vms ? Im trying to understand what "accepted" card could I use > with my 1U chassis servers... > 3. Is it only needed to install the card and the platform will alocate > physical video memory to "desktop" vms ? ( Will the card RAM > be automatically shared across the desktop tyoe vms running on top of the > host ? ) > 4. Is it necesarilly to activate sr-iov in the hosts bios or any other > platform configurations ? > > I am really sorry for asking too many things, but im just trying to get > these vdi vms working at least decent... > Thank you so much ! > > Leo > > > -- Forwarded message - > From: > Date: Tue, Sep 24, 2019 at 7:50 PM > Subject: Re: [ovirt-users] Re: VDI > To: Leo David > > > Audio should just work as long as the VM is of the desktop type. > > On Sep 24, 2019 6:50 AM, Leo David wrote: > > Thank you Alex, > When you say "gpu backed" are you referring to sr-iov to share same gpu > to multiple vms ? > Any thoughts regarding passing audio form the vm to the client ? > Did you do any update of the spice-server on the hosts ? > > Thanks, > > Leo > > On Tue, Sep 24, 2019 at 12:01 PM wrote: > > I believe a lot of the package updates in CentOS 8 will solve some of the > issues. > > But for now we get around them by disabling all visual effects on our VMS. > If you are gpu backing the VMS with something like Nvidia grid the issues > are non existent, but for non gpu backed VMS currently disabling all the > effects is a must. > > We deploy the changes via gpo directly to the registry, so they take > effect on first VM boot. > > On Sep 24, 2019 2:03 AM, Leo David wrote: > > Thank you Alex from my side as well, very usefull information. I am the > middle of vdi implementation as well, and i'm having issues with the spice > console since 4.2, and it seems that latest 4.3 is still having the > problem. > What am i confrunting is: > - spice console is very slaggy and slow for Win10 vms ( not even talking > about running videos..) > - i
[ovirt-users] Re: VDI
Thank you Alex, If you could share the repos for server and client patches would be very helpful. ( also some install guidance info would it be very good ) I could try them on the actual 4.2.8 that i'm trying to enable vdi's on. Cheers, Leo On Sun, Oct 6, 2019 at 12:22 PM Alex McWhirter wrote: > We use customized versions of spice / kvm. Same versions ovirt ships with > for compatibility reasons, with audio patches on the kvm side and spice > patches for vp8 encoding the video streams. We've been meaning to make the > repo for our custom patched versions public for a while, if you are > interested i can accelerate that. Note, you also need patched versions of > spice client if yours wasn't build with vp8 support, we have those too. > > On the experimental side we have another in-progress set of patches that > enable h264 encoding in spice, hardware accelerated with AMD W5100's, but > this requires a lot of new software to be installed and a new kernel, > CentOS 8 should fix most of that, so we'll probably re-base and release on > that when the time is right. > > The GPU's are not used for the guests at all, we only use them for the > h264 encoding. AMD was picked to avoid proprietary drivers and stream > limits. No RAM / SR-IOV needed, if you want 3d support you will be looking > more for Nvidia-GRID. > > > Anyways, with just the patched software installed and some custom > settings, video playback is about 95% the quality of native, takes about > 40mbit/s per client to stream it. Audio has the occasional stutter, but > it's not bad. > > > On 2019-10-06 05:09, Leo David wrote: > > Thank you for sharing the informations Alex, they are very helpfull. I am > now able to get sound from the vms, although performance is pretty poor > even with "adjust for performance" setting in Win10. Cannot even talk > about youtube video playing - freezing and crackling. > Could you please be so kind to share the following infos: > 1. Have you upgraded the "spice-server" installed on the hosts with a > newer version than 1.4.0 ? If so, could you provide me how could I get > these packages ? > 2. What graphic card have you used for getting better graphic performance > with the vms ? Im trying to understand what "accepted" card could I use > with my 1U chassis servers... > 3. Is it only needed to install the card and the platform will alocate > physical video memory to "desktop" vms ? ( Will the card RAM > be automatically shared across the desktop tyoe vms running on top of the > host ? ) > 4. Is it necesarilly to activate sr-iov in the hosts bios or any other > platform configurations ? > > I am really sorry for asking too many things, but im just trying to get > these vdi vms working at least decent... > Thank you so much ! > > Leo > > > -- Forwarded message - > From: > Date: Tue, Sep 24, 2019 at 7:50 PM > Subject: Re: [ovirt-users] Re: VDI > To: Leo David > > > Audio should just work as long as the VM is of the desktop type. > > On Sep 24, 2019 6:50 AM, Leo David wrote: > > Thank you Alex, > When you say "gpu backed" are you referring to sr-iov to share same gpu > to multiple vms ? > Any thoughts regarding passing audio form the vm to the client ? > Did you do any update of the spice-server on the hosts ? > > Thanks, > > Leo > > On Tue, Sep 24, 2019 at 12:01 PM wrote: > > I believe a lot of the package updates in CentOS 8 will solve some of the > issues. > > But for now we get around them by disabling all visual effects on our VMS. > If you are gpu backing the VMS with something like Nvidia grid the issues > are non existent, but for non gpu backed VMS currently disabling all the > effects is a must. > > We deploy the changes via gpo directly to the registry, so they take > effect on first VM boot. > > On Sep 24, 2019 2:03 AM, Leo David wrote: > > Thank you Alex from my side as well, very usefull information. I am the > middle of vdi implementation as well, and i'm having issues with the spice > console since 4.2, and it seems that latest 4.3 is still having the > problem. > What am i confrunting is: > - spice console is very slaggy and slow for Win10 vms ( not even talking > about running videos..) > - i can't find a way to get audio from the vm > At the moment i am running 4.3, latest virt-viewer installed on the > client, and latest qxl-dod driver installed on the vm. > Any thoughts on solving video performance and audio redirection ? > Thank you again, > > Leo > > On Mon, Sep 23, 2019, 22:53 Alex McWhirter wrote: > > To achieve that all you need to do is create a template of the desktop > base vm, make sure the vm type
[ovirt-users] Re: VDI
We use customized versions of spice / kvm. Same versions ovirt ships with for compatibility reasons, with audio patches on the kvm side and spice patches for vp8 encoding the video streams. We've been meaning to make the repo for our custom patched versions public for a while, if you are interested i can accelerate that. Note, you also need patched versions of spice client if yours wasn't build with vp8 support, we have those too. On the experimental side we have another in-progress set of patches that enable h264 encoding in spice, hardware accelerated with AMD W5100's, but this requires a lot of new software to be installed and a new kernel, CentOS 8 should fix most of that, so we'll probably re-base and release on that when the time is right. The GPU's are not used for the guests at all, we only use them for the h264 encoding. AMD was picked to avoid proprietary drivers and stream limits. No RAM / SR-IOV needed, if you want 3d support you will be looking more for Nvidia-GRID. Anyways, with just the patched software installed and some custom settings, video playback is about 95% the quality of native, takes about 40mbit/s per client to stream it. Audio has the occasional stutter, but it's not bad. On 2019-10-06 05:09, Leo David wrote: Thank you for sharing the informations Alex, they are very helpfull. I am now able to get sound from the vms, although performance is pretty poor even with "adjust for performance" setting in Win10. Cannot even talk about youtube video playing - freezing and crackling. Could you please be so kind to share the following infos: 1. Have you upgraded the "spice-server" installed on the hosts with a newer version than 1.4.0 ? If so, could you provide me how could I get these packages ? 2. What graphic card have you used for getting better graphic performance with the vms ? Im trying to understand what "accepted" card could I use with my 1U chassis servers... 3. Is it only needed to install the card and the platform will alocate physical video memory to "desktop" vms ? ( Will the card RAM be automatically shared across the desktop tyoe vms running on top of the host ? ) 4. Is it necesarilly to activate sr-iov in the hosts bios or any other platform configurations ? I am really sorry for asking too many things, but im just trying to get these vdi vms working at least decent... Thank you so much ! Leo -- Forwarded message - From: Date: Tue, Sep 24, 2019 at 7:50 PM Subject: Re: [ovirt-users] Re: VDI To: Leo David Audio should just work as long as the VM is of the desktop type. On Sep 24, 2019 6:50 AM, Leo David wrote: Thank you Alex, When you say "gpu backed" are you referring to sr-iov to share same gpu to multiple vms ? Any thoughts regarding passing audio form the vm to the client ? Did you do any update of the spice-server on the hosts ? Thanks, Leo On Tue, Sep 24, 2019 at 12:01 PM wrote: I believe a lot of the package updates in CentOS 8 will solve some of the issues. But for now we get around them by disabling all visual effects on our VMS. If you are gpu backing the VMS with something like Nvidia grid the issues are non existent, but for non gpu backed VMS currently disabling all the effects is a must. We deploy the changes via gpo directly to the registry, so they take effect on first VM boot. On Sep 24, 2019 2:03 AM, Leo David wrote: Thank you Alex from my side as well, very usefull information. I am the middle of vdi implementation as well, and i'm having issues with the spice console since 4.2, and it seems that latest 4.3 is still having the problem. What am i confrunting is: - spice console is very slaggy and slow for Win10 vms ( not even talking about running videos..) - i can't find a way to get audio from the vm At the moment i am running 4.3, latest virt-viewer installed on the client, and latest qxl-dod driver installed on the vm. Any thoughts on solving video performance and audio redirection ? Thank you again, Leo On Mon, Sep 23, 2019, 22:53 Alex McWhirter wrote: 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
[ovirt-users] Re: VDI
Thank you for sharing the informations Alex, they are very helpfull. I am now able to get sound from the vms, although performance is pretty poor even with "adjust for performance" setting in Win10. Cannot even talk about youtube video playing - freezing and crackling. Could you please be so kind to share the following infos: 1. Have you upgraded the "spice-server" installed on the hosts with a newer version than 1.4.0 ? If so, could you provide me how could I get these packages ? 2. What graphic card have you used for getting better graphic performance with the vms ? Im trying to understand what "accepted" card could I use with my 1U chassis servers... 3. Is it only needed to install the card and the platform will alocate physical video memory to "desktop" vms ? ( Will the card RAM be automatically shared across the desktop tyoe vms running on top of the host ? ) 4. Is it necesarilly to activate sr-iov in the hosts bios or any other platform configurations ? I am really sorry for asking too many things, but im just trying to get these vdi vms working at least decent... Thank you so much ! Leo -- Forwarded message - From: Date: Tue, Sep 24, 2019 at 7:50 PM Subject: Re: [ovirt-users] Re: VDI To: Leo David Audio should just work as long as the VM is of the desktop type. On Sep 24, 2019 6:50 AM, Leo David wrote: Thank you Alex, When you say "gpu backed" are you referring to sr-iov to share same gpu to multiple vms ? Any thoughts regarding passing audio form the vm to the client ? Did you do any update of the spice-server on the hosts ? Thanks, Leo On Tue, Sep 24, 2019 at 12:01 PM wrote: I believe a lot of the package updates in CentOS 8 will solve some of the issues. But for now we get around them by disabling all visual effects on our VMS. If you are gpu backing the VMS with something like Nvidia grid the issues are non existent, but for non gpu backed VMS currently disabling all the effects is a must. We deploy the changes via gpo directly to the registry, so they take effect on first VM boot. On Sep 24, 2019 2:03 AM, Leo David wrote: Thank you Alex from my side as well, very usefull information. I am the middle of vdi implementation as well, and i'm having issues with the spice console since 4.2, and it seems that latest 4.3 is still having the problem. What am i confrunting is: - spice console is very slaggy and slow for Win10 vms ( not even talking about running videos..) - i can't find a way to get audio from the vm At the moment i am running 4.3, latest virt-viewer installed on the client, and latest qxl-dod driver installed on the vm. Any thoughts on solving video performance and audio redirection ? Thank you again, Leo On Mon, Sep 23, 2019, 22:53 Alex McWhirter wrote: 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 ru
[ovirt-users] Re: VDI
I believe a lot of the package updates in CentOS 8 will solve some of the issues.But for now we get around them by disabling all visual effects on our VMS. If you are gpu backing the VMS with something like Nvidia grid the issues are non existent, but for non gpu backed VMS currently disabling all the effects is a must.We deploy the changes via gpo directly to the registry, so they take effect on first VM boot.On Sep 24, 2019 2:03 AM, Leo David wrote:Thank you Alex from my side as well, very usefull information. I am the middle of vdi implementation as well, and i'm having issues with the spice console since 4.2, and it seems that latest 4.3 is still having the problem.What am i confrunting is:- spice console is very slaggy and slow for Win10 vms ( not even talking about running videos..)- i can't find a way to get audio from the vmAt the moment i am running 4.3, latest virt-viewer installed on the client, and latest qxl-dod driver installed on the vm.Any thoughts on solving video performance and audio redirection ?Thank you again,LeoOn Mon, Sep 23, 2019, 22:53 Alex McWhirterwrote: 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.orgTo unsubscribe send an email to users-le...@ovirt.orgPrivacy 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/DWY46KJGSYJGRXMRY7WWCINAW2Y5ETDI/ ___ 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/4ZYV6AXK3NA7WN7URALJJC7FBVCBBBL3/
[ovirt-users] Re: VDI
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/
[ovirt-users] Re: VDI
Thank you Alex from my side as well, very usefull information. I am the middle of vdi implementation as well, and i'm having issues with the spice console since 4.2, and it seems that latest 4.3 is still having the problem. What am i confrunting is: - spice console is very slaggy and slow for Win10 vms ( not even talking about running videos..) - i can't find a way to get audio from the vm At the moment i am running 4.3, latest virt-viewer installed on the client, and latest qxl-dod driver installed on the vm. Any thoughts on solving video performance and audio redirection ? Thank you again, Leo On Mon, Sep 23, 2019, 22:53 Alex McWhirter wrote: > 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/DWY46KJGSYJGRXMRY7WWCINAW2Y5ETDI/ > ___ 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/VUANDTA34W6XBQZMDZRFMZC7CSCNBYCK/
[ovirt-users] Re: VDI
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/DWY46KJGSYJGRXMRY7WWCINAW2Y5ETDI/
[ovirt-users] Re: VDI
I am trying to setup a full vdi environment w10 in domain Rgds harry Op ma 23 sep. 2019 om 19:47 schreef Fabio Marzocca > 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/ > -- Vriendelijke groeten, Harry Conings ICE bvba Liebroekstraat 43 3545 Halen BE0446888007 tel 32475464289 ___ 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/WSCQF36UWEETVHXRAQ2SL4FSRUU5YHK6/
[ovirt-users] Re: VDI broker and oVirt
Hi, I think you mean to ask about the connection broker to connect to your VDI infrastructure? Something like this: Or https://www.leostream.com/solution/remote-access-for-virtual-and-physical-workstations/ Ovirt has the VM user portal https://github.com/oVirt/ovirt-web-ui , but I have never used a third party connection broker myself so I'm not aware of any compatible with oVirt or RHEV... On 4/4/19 9:10 PM, oquerej...@gmail.com wrote: > I have Ovirt installed, with two hypervisor and Ovirt engine. I Want To mount > a VDI infrastructure, as cheap as possible, but robust and reliable. The > question is what broker I can use. Thank you. > ___ > 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/GLH7Y5HCOMBYL7QBPOGOPRTQY247GNUD/ Met vriendelijke groet, With kind regards, Jorick Astrego Netbulae Virtualization Experts Tel: 053 20 30 270 i...@netbulae.euStaalsteden 4-3A KvK 08198180 Fax: 053 20 30 271 www.netbulae.eu 7547 TA Enschede BTW NL821234584B01 ___ 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/EHSULIYRXUYFGDDFVQT7SAIKOBGVQASY/
[ovirt-users] Re: VDI broker and oVirt
I have Ovirt installed, with two hypervisor and Ovirt engine. I Want To mount a VDI infrastructure, as cheap as possible, but robust and reliable. The question is what broker I can use. Thank you. ___ 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/GLH7Y5HCOMBYL7QBPOGOPRTQY247GNUD/
[ovirt-users] Re: VDI broker and oVirt
> On 4 Apr 2019, at 14:14, oquerej...@gmail.com wrote: > > hello > What is the name of the broker that we can install in ovirt? What broker are you looking for? What is it supposed to do? > any documentation? > thanks !! > ___ > 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/SVUF3HEEATMX6HQEZGAWR4HW4N64KUBA/ ___ 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/DESF372OFNMILTZ3D34B36E5N46PDNLE/
[ovirt-users] Re: VDI - SPICE zero clients
We've been using IGEL thin clients for years in our RHEV environment. The Windows based ones suck and don't have a SPICE client pre-installed but the Linux ones work really well. CC On Thu, Jul 12, 2018 at 1:43 AM wrote: > Never mind, it looks like these don't the SPICE protocol. Will try an IGEL > thin client. > > Cam > ___ > 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/RPTZ56INAAP7FJCMMXJZWCD3JF7RQ652/ > ___ 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/J7CD3NXX23JKXAC2IX2JC4VY7HZ44LL5/
[ovirt-users] Re: VDI - SPICE zero clients
Never mind, it looks like these don't the SPICE protocol. Will try an IGEL thin client. Cam ___ 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/RPTZ56INAAP7FJCMMXJZWCD3JF7RQ652/