Kernel series for VirtualBox installation

[sling-shot]

VirtualBox allows us to set the kernel series of guest. Options available are :

- 2.4 series
- 2.6 series
- Unknown / Other

For our current 32 bit KDE PCLinuxOS, what would be the best option to go for? (I understand our current default kernel is 3.2.x series)

[Just17]

I have used both 2.6 and unknown .......  but have no idea what VBox does differently for them ..... so no idea which *should* be used.

[pags]

I have used both 2.6 and unknown .......  but have no idea what VBox does differently for them ..... so no idea which *should* be used.

Yep.

Really, it's pretty forgiving...I've had VMs setup for Windows 7 that boot LiveCDs without issue (in fact, the mouse integration seems better, there, as well as access to an addition 128MB of Video memory -- 128MB max for Linux VMs, 256MB max for Win7 --  )

[Just17]

I have used both 2.6 and unknown .......  but have no idea what VBox does differently for them ..... so no idea which *should* be used.

Yep.

Really, it's pretty forgiving...I've had VMs setup for Windows 7 that boot LiveCDs without issue (in fact, the mouse integration seems better, there, as well as access to an addition 128MB of Video memory -- 128MB max for Linux VMs, 256MB max for Win7 --  )

I hadn't realised that .....  might be useful in some situations to use the Win settings ....

[agmg]

You can also "cheat" Virtualbox in this section.

Select "Windows 7 or 8" in General.
This will allow you to have more than 128MB of Video Memory.
Set it to whatever you want.
Return to General and select Linux.
Video memory will retain the setting.

I don't know if there is an obvious reason for VirtualBox not allowing more than 128MB of Video Memory on Linux VMs... 

[Just17]

You can also "cheat" Virtualbox in this section.

Select "Windows 7 or 8" in General.
This will allow you to have more than 128MB of Video Memory.
Set it to whatever you want.
Return to General and select Linux.
Video memory will retain the setting.

I don't know if there is an obvious reason for VirtualBox not allowing more than 128MB of Video Memory on Linux VMs... 

I tried that on an existing VBox entry and it did not work .....  changing to Win did not allow for more than the 128MB video ram.

[agmg]

Strange...

Try another cheat:

vbm showvminfo your-vm | grep VRAM

Change your-vm with the actual name of your machine.
This will show you the amount of VRAM.

Then type:

vbm modifyvm your-vm --vram 256

And check again with the first command.

[Just17]

All I get is 


bash: vbm: command not found   
 

[agmg]

For your previous post. Just created a new machine and checked, I can "cheat" VB that way...



Be sure to have 3D Acceleration enabled...

For my post... I made a mistake... seems my notes were for an older version of VB.
Or for a different distro, I'm not sure

Try replacing vbm with vboxmanage.

[Just17]

Maybe because I am using Vbox 4.1.18, but the max display ram, even with Win guest is 128MB ....  no more available here.

[pags]

Maybe because I am using Vbox 4.1.18, but the max display ram, even with Win guest is 128MB ....  no more available here.

Could very well be.  Running 4.2.6 here.

Also, the command is

Code: [Select]

VBoxManage

Case is important.

[dcwbis]

I am running 4.2.4 and the max display ram for both my XP and Win7 VMs is 128mb

[agmg]

Maybe because I am using Vbox 4.1.18, but the max display ram, even with Win guest is 128MB ....  no more available here.

Could very well be.  Running 4.2.6 here.

Also, the command is

Code: [Select]

VBoxManage

Case is important.

Try with vboxmanage. It works.

[pags]

Maybe because I am using Vbox 4.1.18, but the max display ram, even with Win guest is 128MB ....  no more available here.

Could very well be.  Running 4.2.6 here.

Also, the command is

Code: [Select]

VBoxManage

Case is important.

Try with vboxmanage. It works.

Ah.

That must be new in one of the last updates (I'm sure only the one worked before...)...looks like symlinks to accommodate this:

[jpaglia@paglia-e6500 ~]$ ls /usr/bin/VBox* -lh
lrwxrwxrwx 1 root root 23 Jan  5 23:48 /usr/bin/VBoxAutostart -> /opt/VirtualBox/VBox.sh*
lrwxrwxrwx 1 root root 23 Jan  5 23:48 /usr/bin/VBoxBalloonCtrl -> /opt/VirtualBox/VBox.sh*
lrwxrwxrwx 1 root root 23 Jan  5 23:48 /usr/bin/VBoxHeadless -> /opt/VirtualBox/VBox.sh*
lrwxrwxrwx 1 root root 23 Jan  5 23:48 /usr/bin/VBoxManage -> /opt/VirtualBox/VBox.sh*
lrwxrwxrwx 1 root root 23 Jan  5 23:48 /usr/bin/VBoxSDL -> /opt/VirtualBox/VBox.sh*
lrwxrwxrwx 1 root root 23 Jan  5 23:48 /usr/bin/VBoxVRDP -> /opt/VirtualBox/VBox.sh*
[jpaglia@paglia-e6500 ~]$ ls /usr/bin/vbox* -lh
lrwxrwxrwx 1 root root 12 Jan  5 23:48 /usr/bin/vboxheadless -> VBoxHeadless*
lrwxrwxrwx 1 root root 10 Jan  5 23:48 /usr/bin/vboxmanage -> VBoxManage*
lrwxrwxrwx 1 root root  7 Jan  5 23:48 /usr/bin/vboxsdl -> VBoxSDL*
lrwxrwxrwx 1 root root 23 Jan  5 23:48 /usr/bin/vboxwebsrv -> /opt/VirtualBox/VBox.sh*
[jpaglia@paglia-e6500 ~]$