Jump to content

Mark Cassidy

Member
  • Posts

    5
  • Joined

  • Last visited

Awards

This user doesn't have any awards

Mark Cassidy's Achievements

  1. Ok. I'm hoping there are others here with actual experience in running VMs that may have insight. Looking for a second or third opinion here
  2. Steam Home Streaming can do many things. Run a Windows 10 Hyper-V machine is not one of them. Much less 2 or 3 at the same time ?
  3. Sure. But the remote system has no issues at all. It has a 1080 to help, if need be. I'm connected to it more or less directly, with just 1 switch between us running 1Gbps. The issue doesn't lie there - it's solely on client side.
  4. Well. What doesn't make sense to me is; I can run that very same VM I'm currently testing locally, and have NO issue at all. But connecting to it remotely causes my entire system to being suffering from sluggish/slow UI, noticeable delays in window dragging and so on. More or less the EXACT opposite of what I was trying to achieve ?
  5. Hoping someone here can help, since every Google I've thrown at this thinks my problem is something else. On my home network, I've repurposed my old PC as a Hyper-V server. I figured I might as well put that CPU and memory to good use, as I often run 2-3 Virtual Machines and my laptop resources were stretched thin. HOWEVER. When I connect to a Hyper-V machine on this new "server" now - I hit a different bottleneck. For some reason, Windows on my laptop uses the onboard GPU to drive the session - not my Geforce card. It's a dual GPU Dell laptop. So just connecting to this remote VM is now causing my system to stress. When I ran the very same VM locally, I never had any issue. Please note; this is NOT about getting RemoteFX to work or anything similar - this is where Google takes me whenever I try and search for this problem. It is strictly about getting my connection to the remote Hyper-V server to NOT use my underpowered onboard card, but instead the NVidia card. Any insights? :-)
×