It is perfect, It creates new disk, uses the configuration of CPU and also
assigns separate memory.
Thanks, both of you.
On Wed, Nov 14, 2018 at 12:47 PM Rabin Yasharzadehe <rabin(a)rabin.io> wrote:
From a quick overview on the project, is seems like openuds will
create
new VMs based on another machine VM (a template)
so I don't see why a file on machine1 should be on machine2 unless you
using a shared storages with is mounted to both machines like a network
drive and you write the file there ...
please correct me if i misunderstood your question.
Regards, Rabin
On Tue, 13 Nov 2018 at 16:49, Hari Prasanth Loganathan <
hariprasanth.l(a)msystechnologies.com> wrote:
> Hi Team,
>
> I created a VM which has one disk.
> For this VM, I created two Virtual Desktop (VDI_1 and VDI_2) using
> open-UDS and it created successfully.
>
> *Consider the following scenario* :
>
> 1) I took a console for VDI_1 and created a file in it using the console
> 2) I took the console for VDI_2 and checked whether the file created in
> VDI_1 is available in it but as per the VDI concept it is not available
>
> Could someone clarify the below use case,
>
> Now when I looked at the Disk associated with the VDI, It seems the Disk
> of the VM is same for the VDI_1 and VDI_2, so How does the file created in
> VDI_1 is not reflecting in VDI_2?
>
> Thanks,
> Hari
>
>
>
>
> DISCLAIMER - *MSysTechnologies LLC*
>
> This email message, contents and its attachments may contain
> confidential, proprietary or legally privileged information and is intended
> solely for the use of the individual or entity to whom it is actually
> intended. If you have erroneously received this message, please permanently
> delete it immediately and notify the sender. If you are not the intended
> recipient of the email message,you are notified strictly not to
> disseminate,distribute or copy this e-mail.E-mail transmission cannot be
> guaranteed to be secure or error-free as Information could be intercepted,
> corrupted, lost, destroyed, incomplete or contain viruses and
> MSysTechnologies LLC accepts no liability for the contents and integrity of
> this mail or for any damage caused by the limitations of the e-mail
> transmission.
>
> _______________________________________________
> Users mailing list -- users(a)ovirt.org
> To unsubscribe send an email to users-leave(a)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/D3IL6EXK56F...
>
--
DISCLAIMER - *MSysTechnologies LLC*
This email message, contents and
its attachments may contain confidential, proprietary or legally privileged
information and is intended solely for the use of the individual or entity
to whom it is actually intended. If you have erroneously received this
message, please permanently delete it immediately and notify the sender. If
you are not the intended recipient of the email message,you are notified
strictly not to disseminate,distribute or copy this e-mail.E-mail
transmission cannot be guaranteed to be secure or error-free as Information
could be intercepted, corrupted, lost, destroyed, incomplete or contain
viruses and MSysTechnologies LLC accepts no liability for the contents and
integrity of this mail or for any damage caused by the limitations of the
e-mail transmission.