Single CPU, Multiple users

[ryosuke25897]

So I am trying to experiment with something like mentioned video. Is there anywhere I can get the technical details apart from watching all the prior videos? My idea is something similar, but for gaming. Also, is it possible for different VMs to share a common gaming folder? Like steam has a Steam Library folder, Riot Client also creates one such folder. So is it feasible to have games in a single shared folder between all the VMs so that there is no redundant storage usage? 

 

[emosun]

The machine will be slower and more expensive than just dedicated machines. Is there a reason you need this to be a single machine?

[ryosuke25897]

7 minutes ago, emosun said:

The machine will be slower and more expensive than just dedicated machines. Is there a reason you need this to be a single machine?

Not particularly. I have a use-case where several users either use same system or different systems in the same network. I want them to be able to feel like they are using the same system everytime. Other idea I had was to have one virtual machine for every user. And when a user wants to use that vm, then download the vdi or qcow2 file over network and just run it. But it also has the issue of redundant storage. Before that I also tried if just backing up the `AppData/RiotClient` or similar folders for each users would suffice but that didn't work.

[BiotechBen]

11 minutes ago, ryosuke25897 said:

Not particularly. I have a use-case where several users either use same system or different systems in the same network. I want them to be able to feel like they are using the same system everytime. Other idea I had was to have one virtual machine for every user. And when a user wants to use that vm, then download the vdi or qcow2 file over network and just run it. But it also has the issue of redundant storage. Before that I also tried if just backing up the `AppData/RiotClient` or similar folders for each users would suffice but that didn't work.

VMs are going to be a nightmare when you get into this as shown with really every "multi user one machine" project LTT has done. Would be better to have dedicated servers for tasks and then essentially terminals.

[ryosuke25897]

4 minutes ago, BiotechBen said:

VMs are going to be a nightmare when you get into this as shown with really every "multi user one machine" project LTT has done. Would be better to have dedicated servers for tasks and then essentially terminals.

Okay maybe not "multi user one machine", but just one vm per system. Every user has his own vm, they set up this VM on system A, next time they sit on system B, they download their VM disk file from system A to system B, and just run. I know I can handle the networking and coding involved to make it straightforward, but do you think it is feasible? 

[BiotechBen]

Just now, ryosuke25897 said:

Okay maybe not "multi user one machine", but just one vm per system. Every user has his own vm, they set up this VM on system A, next time they sit on system B, they download their VM disk file from system A to system B, and just run. I know I can handle the networking and coding involved to make it straightforward, but do you think it is feasible? 

Unless you are going to be doing it with other tech literate people, I wouldn't. I'd suggest having it as terminals that go back to a main server and each login profile has their data on the main server. Think of it like how schools/universities work for keeping student data.

[ryosuke25897]

Just now, BiotechBen said:

Unless you are going to be doing it with other tech literate people, I wouldn't. I'd suggest having it as terminals that go back to a main server and each login profile has their data on the main server. Think of it like how schools/universities work for keeping student data.

I didn't think storing login profiles on servers is possible. If that is possible then that would surely be my first choice? Is there any technical term for this kind of setup so I can google or do you have any references to any good docs?

[BiotechBen]

10 minutes ago, ryosuke25897 said:

I didn't think storing login profiles on servers is possible. If that is possible then that would surely be my first choice? Is there any technical term for this kind of setup so I can google or do you have any references to any good docs?

Roaming user profiles sounds like the thing, I may be slightly off, but it's pretty darn close if not exact.

 

https://learn.microsoft.com/en-us/windows-server/storage/folder-redirection/folder-redirection-rup-overview

 

Roaming User Profiles. A roaming user profile is a copy of the local profile that is copied to, and stored on, a server share. This profile is downloaded to any computer that a user logs onto on a network. Changes made to a roaming user profile are synchronized with the server copy of the profile when the user logs off. The advantage of roaming user profiles is that users do not need to create a profile on each computer they use on a network.

 

 

The thing that always annoyed me going through grade school was that the sequence to rest your password was 123456....

 

[ryosuke25897]

2 minutes ago, BiotechBen said:

Roaming user profiles sounds like the thing, I may be slightly off, but it's pretty darn close if not exact.

 

https://learn.microsoft.com/en-us/windows-server/storage/folder-redirection/folder-redirection-rup-overview

 

Roaming User Profiles. A roaming user profile is a copy of the local profile that is copied to, and stored on, a server share. This profile is downloaded to any computer that a user logs onto on a network. Changes made to a roaming user profile are synchronized with the server copy of the profile when the user logs off. The advantage of roaming user profiles is that users do not need to create a profile on each computer they use on a network.

 

 

Oh sounds like I was trying to reinvent the wheel. This is exactly what I needed. Thanks.

[BiotechBen]

Just now, ryosuke25897 said:

Oh sounds like I was trying to reinvent the wheel. This is exactly what I needed. Thanks.

Always happy to help not reinvent the wheel.