yea, I understand(you're welcome,
). I've been using MD* since ~'99; they have changed some things so finding what one needs can be difficult sometimes. Other distros do the same thing. ...
I have plans on installing VirtualBox OSE on 2008.1x64 PWP and then WinXPx64 so I needed the info anyway ...just in case.
FYI:
"PID" can be found with
pidof [task_name]
One can also do
taskset [options] `pidof [task_name]`
Those are backquotes which basically means execute and substitute the result at that spot in the cmd line; for the bash shell -don't rem' how good it works for ksh, csh or others. BASH is the std shell(CMD line) for MDLinux.
(BTW, brackets are not used in the command. They are just there for clarity ...)
Finding the task_name for virtualbox is done several ways. One is use (KDE) ksysguard program and just look for it; another from the shell is to use the "
top" program. If the manual has the name of the task I have not seen it. ... could be vbox but it could be something totally different too. I cannot help with that since I don't have V'Box running in MD*; you will have to hunt it down.
Note that if you use
KSysGuard or
top the PID of the task is displayed too.
There is another way you might try without setting the processor affinity.
Quit the X11 desktop and login at the virtual terminal. then from there use the VBoxManage to create the vdi; IIRC, the command is
VBoxManage createdvi [options] [/path/to/name.vdi]
options are size, type, etc. They will display if you type
VBoxManage createdvi
at the CLI with no information(no options, target,...).
It is possible that the GUI is getting in the way so not running X11 will eliminate that problem ...IF that is the issue.