1 CPU 2 Users

[Battousai01]

Hi guys, I would like to ask for some tips or guide on how to set up a 2 users 1 CPU configuration with each user having their own dedicated operating system.

So basically, I would like to share one CPU to two users either simultaneously or for single user using his own operating system (the use case is one user for gaming and the other one for light task such as web browsing, office work or light CAD rendering).

My first option would be to use the free version of VM Ware Player or Virtual Box within Windows 10 but this seems this less efficient because I need to boot up the first host system for the other user to be able to use his own operating system using VM Ware or Virtual Box.

My second option would be to use KVM on Linux but I am not sure how exactly this should work?

I have checked Linus Tech Tips' video here but it looks quite complicated: https://www.youtube.com/watch?v=LuJYMCbIbPk

My hardware:

i7-7700
Intel on-board HD graphics
1pc. GTX-1070
8GB RAM (planning on upgrading to 16GB if needed)
1pc. EVO 750 SSD
1pc. m.2 SSD
on-board sound card
2pcs. monitor
2 set of keyboard and mouse

 

[Thunder 57]

That's an interesting use case for sure. My first guess would be to use VirtualBox and have the light user remote into that, unless you mean one computer and not one CPU. That probably isn't the most efficient way but it should work.

EDIT

Probably should have read your specs. So remote is out. You could still use Virtualbox and give each OS it's own screen, keyboard and mouse.

Honestly I would look into getting a cheap second system. I doubt you would be thrilled with the results of what you are trying to do.

 

[Elixer]

Sure, it is possible, and you can dedicate a vid card to each VM OS, same with keyboard / mouse...but, it is very resource demanding, and isn't a simple setup.

I wouldn't use anything less than a Ryzen 7 + 32GB RAM + 2 vid cards.
You are going to need all the cores you can get.

I would also go with another system, unless you become familiar with linux & use Xen or perhaps KVM.

 

[JackMDS]

Two heavy Users! No matter waht you do it will not work Well.

At least one low key user.

Get a sub $ 100 used LapTop or Core2Duo computer. Ebay is flooded with deals for those.

 

[PeterRoss]

I'll agree with people's opinions on this one. Not really doable for solid use. You would essentially get 2 systems that are subpar, without actually enjoying the experience. You need far greater specs. New Ryzen processors is a good start. A couple GPU's, a solid, capable motherboard would do wonders. Then I could maybe see it working out.

 

[PingSpike]

Unraid has the closest thing to a turnkey vga passthrough solution using KVM. They have a free trial, and its only $60 last time I checked. You can set it up under basically any linux distro but its perhaps more involved whereas the unraid guys have hidden much of it behind a web interface. I have it running using virt-manager/kvm on my machine just so I have a second windows VM for games...which I hardly ever use but that's another topic.

I use ESXi6 on my file server and pass through a GPU to my set top box VM. You could look into that, it was for a time the only way to do it and still works but its popularity is waning. ESXI6 is free but since its really not designed for this its setup can be troublesome and there are additional hardware considerations.

Important to note is that nvidia drivers try to detect if they're in a VM and then disable themselves. KVM has flags that can usually work around this. ESXi has some too but they are probably less reliable.

 

[Ketchup]

Due to the reasource demands you are describing for both, I don't see a good reason not to have two sepate systems. You wouldn't be saving much money, and I didn't see a space issue being avoided since we would be talking about two separate users with their own screen/mouse/kb.

 

[Ratman6161]

Microsoft actually makes a product that is exactly what you are looking for. Its called Windows Multipoint Service

https://docs.microsoft.com/en-us/wi...oint-services/introducing-multipoint-services

But...it's a role that can be installed and configured on Windows Server 2016. So that's the first problem. You need a windows server license. Then you need to install it in hardware capable of doing the job. For your purposes, it would be cheaper and easier to just build or buy 2 separate PC'S.

 

[LPCTech]

Get a thin client or a raspberry pi for the light user and let them RDP into a terminal session of their account. Have the gamer log into the actual PC. But you need to have at least win pro with some hacks or a windows server OS for multiple account simultaneous RDP. Like a terminal server.

Hacks for win pro 10
https://www.mysysadmintips.com/wind...ple-rdp-remote-desktop-sessions-in-windows-10

 

[XavierMace]

Gaming in an RDP session isn't going to work well (or at all) in most cases.

 

[Rifter]

You are going to need to spend enough on hardware for one high end/server system that you may as well just spend the same on two mid range systems instead and enjoy better results.

 

[Battousai01]

Hi guys! Thanks for the reply. Yes, I agree that it would be easier to just setup another workstation or desktop but it might take a few months before I can buy a new one. However, the Windows Multipoint Service seems interesting in the short term, I can see that Microsoft offers a few months trial of Windows Server 2016. I will check it out and explore what can Windows Multipoint Service can offer.

 

[thecoolnessrune]

My suggestion would be what you mentioned first. Have a primary Windows installation, followed by a second Windows installation. Install 16GB of RAM and give the light use VM in Virtualbox 4GB.

The reason I say this is that as soon as you try to pass through a GPU for gaming, you're talking a major step up in time investment, and the knowledge required to get it to work well. You need not only working Vt-d, but solid, well implemented IOMMU support on the Motherboard. IOMMU in a non-botched form is fairly rare on Consumer Intel Enthusiast boards and almost entirely absent on non-enthusiast boards.

Let the gamer have the main system and the other user have the VirtualBox window with his own screen / keyboard / mouse. He'll be at the whim of the Main User (every UAC request is going to stall the second user since it's still all just screens hosted on the main system), but the second user will have something.

Multipoint Services may, or may not work. Keep in mind that a lot of software, especially games, won't run on Server OS Installations because of OS Checks. For instance, NVIDIA and AMD don't validate their consumer GPUs anymore on Server OS's. Many games run rudimentary OS Checks and will also balk at a Windows Server operating system.

It's just a lot of extra hassle for not a lot of reward.

 

[LPCTech]

Gaming in an RDP session isn't going to work well (or at all) in most cases.

Correct, it will not, that's why no one has suggested it.

The gamer logs into the physical machine.

The light user uses RDP for a terminal session of their profile on a cheapo device. RasPi + keyboard + mouse = $50?

But some light hacks are required to have 2 sessions logged in at the same time on a non-server OS, otherwise the gamer will get logged out when the RDP user logs in. Also, the hacks will only work on windows pro, not home.

 

[XavierMace]

Correct, it will not, that's why no one has suggested it.

How do you think multipoint services works?

 

[PingSpike]

If you want to game on a passed through GPU VM without a monitor directly attached to the server, steam in home streaming is the next best thing. Its still not as good as the former.

 

[thecoolnessrune]

How do you think multipoint services works?

Through a variety of means actually. While you can RDP into your multipoint session like you always have, you can also connect directly off the system. The multipoint service assists you with slicing up services by monitor port, so you can connect your monitor or monitors, designate a keyboard, and designate a mouse, and assign them to a multipoint session. That's not RDP. That a direct connection to the session on the system in use.