Ok, it's going to be tomorrow before I can afford the time to down this machine and make those changes, but I'll give it a try.
The reason I don't think it will be that though is that I'm still using the guest video resources with this remote access - this isn't RDP remote access, it's a remote control program that connects me directly to the system. It's designed to allow me to take remote control of users workstations and see what is on their screen.
So I'm connecting directly to the screen that the VirtualBox GUI shows, and I'm also using this program to control the keyboard & mouse while the VirtualBox GUI is open. So the VirtualBox graphics are still being used.
I can even see that the VirtualBox graphics work fine if I use the remote keyboard and mouse to control the guest.
Intermittent console / graphic lock ups
-
Perryg
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: Intermittent console / graphic lock ups
Does this remote control program work via tcp/ip?
Re: Intermittent console / graphic lock ups
But I am using the video resource of the guest - I don't close the VirtualBox GUI at all - I still have it open and can see everything on there, watching the cursor move and my interacting with the system.
Re: Intermittent console / graphic lock ups
Drat, sorry, I got the 'new message' thing but didn't spot that we were on two pages now. Ignore that last post 
Yes, the remote program works over tcp/ip - it's Dameware Mini Remote control if you're interested.
Yes, the remote program works over tcp/ip - it's Dameware Mini Remote control if you're interested.
-
Perryg
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: Intermittent console / graphic lock ups
Then it is a remote desktop program, and as such does not actually use the VBox GUI or the remote systems resources. It samples the information and transmits it back and forth in a different way.
It will work much as any other remote desktop program unless you are actually plugging into the video, keyboard,and mouse ports with something like a KVM switch.
Typically by design these do not require the same amount of resources to work.
You have already proved this to some extent when you stopped Compiz and the performance improved somewhat.
It will work much as any other remote desktop program unless you are actually plugging into the video, keyboard,and mouse ports with something like a KVM switch.
Typically by design these do not require the same amount of resources to work.
You have already proved this to some extent when you stopped Compiz and the performance improved somewhat.
Re: Intermittent console / graphic lock ups
Yes, it's a remote desktop program and doesn't use the VBox GUI itself.
But I still have the VBox GUI open. I'm not closing the VBox GUI to use this, I have both active and on screen at the same time.
So if anything I'm using more resources when using this, and I'm still using exactly the same for the guest video because the VBox GUI is still running and still displaying everything that's going on.
But we're going round in circles here. I'll do the testing you asked for tomorrow and post up the results
But I still have the VBox GUI open. I'm not closing the VBox GUI to use this, I have both active and on screen at the same time.
So if anything I'm using more resources when using this, and I'm still using exactly the same for the guest video because the VBox GUI is still running and still displaying everything that's going on.
But we're going round in circles here. I'll do the testing you asked for tomorrow and post up the results
Re: Intermittent console / graphic lock ups
Hello again,
Sorry, it's taken a lot longer than expected to get around to testing this, but test I have and the problem seems to have gone away
I went to try your suggestion of increasing memory usage from 768MB to 1024MB, and decreasing my video ram from 24MB to 10MB, but I had some windows updates to install, so did that while shutting windows down.
When I booted back up, the problem was gone, so I thought the memory changes had fixed it. However the problem remains fixed when I revert to my original settings (or to any combination of settings), so I suspect that it's either an intermittent problem and I'm having problems reproducing it, or that one of the Microsoft updates I installed fixed the problem.
Either way, things are working smoothly again now, so thanks for the help
Sorry, it's taken a lot longer than expected to get around to testing this, but test I have and the problem seems to have gone away
I went to try your suggestion of increasing memory usage from 768MB to 1024MB, and decreasing my video ram from 24MB to 10MB, but I had some windows updates to install, so did that while shutting windows down.
When I booted back up, the problem was gone, so I thought the memory changes had fixed it. However the problem remains fixed when I revert to my original settings (or to any combination of settings), so I suspect that it's either an intermittent problem and I'm having problems reproducing it, or that one of the Microsoft updates I installed fixed the problem.
Either way, things are working smoothly again now, so thanks for the help