Best practices for running VBox on a headless Linux host?

[harisund]

Currently, I have a headless, no-GUI host running CentOS 7. It has VirtualBox installed.

I use a Windows laptop (on the same subnet, wired via GiGE ethernet), X forward to "control" it. I mainly use VBoxManage, but sometimes, clicking around just is more helpful.

I have tried executing both

Code: Select all

"ssh -YC vmhost VirtualBox"

as well as

Code: Select all

"ssh -Y vmhost VirtualBox" 

and in both cases, while it's responsive initially, it kinds of slows down after a few seconds or so.

I have also tried setting up a headless VNC server (through tigerVNC) on the vmhost itself, and access it with a VNC client on my Windows laptop. I see the same behavior. It starts out as responsive as my local install on my Windows laptop, but becomes sluggish.

Any ideas on how best to handle a remote VirtualBox installation?

(Also, yes, I am aware that there are better solutions for what I am trying to do, I should probably be using KVM / Proxmox / Ovirt or something, but let's assume I am only allowed to use VirtualBox currently.)

[Perryg]

Post the guests log file ( as an attachment ).

[harisund]

Post the guests log file ( as an attachment ).

There are no guest logs. Everything's involving the host. I am talking about sluggishness on the host before even launching a VM.

[Perryg]

Then I suspect this is a host or host app issue. Without some diagnostic information it would be impossible to know.
Could be network related as well.