VirtualBox - how to increase video memory?
I have just installed Ubuntu 14.04 on VirtualBox, including the guest additions.
However, the display is really slow. Looking at the display settings I can see that the video memory is only 12MB but I can't move the slider to increase it. The checkboxes for extended features are greyed-out too. See screenshot.
.
How do I increase the amount of memory?
TIA
virtualbox guest-additions
asked Feb 18 '15 at 20:28
kslksl
3251413
add a comment |
I have just installed Ubuntu 14.04 on VirtualBox, including the guest additions.
However, the display is really slow. Looking at the display settings I can see that the video memory is only 12MB but I can't move the slider to increase it. The checkboxes for extended features are greyed-out too. See screenshot.
.
How do I increase the amount of memory?
TIA
virtualbox guest-additions
asked Feb 18 '15 at 20:28
kslksl
3251413
add a comment |
I have just installed Ubuntu 14.04 on VirtualBox, including the guest additions.
However, the display is really slow. Looking at the display settings I can see that the video memory is only 12MB but I can't move the slider to increase it. The checkboxes for extended features are greyed-out too. See screenshot.
.
How do I increase the amount of memory?
TIA
virtualbox guest-additions
asked Feb 18 '15 at 20:28
kslksl
3251413
I have just installed Ubuntu 14.04 on VirtualBox, including the guest additions.
However, the display is really slow. Looking at the display settings I can see that the video memory is only 12MB but I can't move the slider to increase it. The checkboxes for extended features are greyed-out too. See screenshot.
.
How do I increase the amount of memory?
TIA
virtualbox guest-additions
virtualbox guest-additions
asked Feb 18 '15 at 20:28
kslksl
3251413
asked Feb 18 '15 at 20:28
kslksl
3251413
asked Feb 18 '15 at 20:28
kslksl
3251413
asked Feb 18 '15 at 20:28
kslksl
3251413
asked Feb 18 '15 at 20:28
kslksl
3251413
3251413
add a comment |
add a comment |
7 Answers
7
active
oldest
votes
You need to shut down the virtual OS before you can edit settings.
edited Aug 8 '16 at 18:21
JetCrusherTorpedo
33
answered Feb 18 '15 at 20:35
Marvin MicekMarvin Micek
572416
Just an addition, you need to properly shutdown the virtual OS. Saving the state won't work.
– Reeshabh Ranjan
Mar 3 at 17:18
add a comment |
Virtual Box supports up to 256 MB of video RAM. This can not be set using the slider of the Virtual Box Manager.
To make full use of all supported memory we can issue the following command in a terminal:
VBoxManage modifyvm "Name of VM" --vram 256
Before we change settings such as the video RAM a pre-existing virtual machine has to be shut down.
Note that for 3D video hardware acceleration from the guest addition's video driver the physical RAM of the host graphics card will be passed through. The video RAM settings of the virtual machine will not affect this.
answered Feb 18 '15 at 21:48
TakkatTakkat
108k37251378
This is the only working way. Updating manually the vbox file doesn't work as the file is refreshed by VirtualBox automatically.
– ZedTuX
Dec 1 '16 at 12:18
This is a TERRIBLE suggestion. Trying this just completely borked my VM. Now it boots to a "FATAL: INT18: BOOT FAILURE"
– krb686
Dec 25 '16 at 0:09
@krb686: sorry to hear that. We can't reproduce this error here. It may not be related to increasing VRAM.
– Takkat
Dec 25 '16 at 9:43
@krb686 this error is related to the bootprocedure. e.g. missing Master Boot Records or similar boot-related parts of an OS
– Foaster
Jun 8 '17 at 13:53
This command caused my machine to cease booting (boots to all black screen, no text). Reversing (running again with128) brought it back.
– mike
Jun 12 '17 at 20:16
|
show 5 more comments
- Stop the virtual machine and close virtualbox
- Using a text editor like "Sublime Text" open YOUMACHINE.vbox. Make a backup beforehand.
Look for vram entry and change its value
<Display VRAMSize="256" monitorCount="1" accelerate3D="true"
accelerate2DVideo="false"/>
Save the file.
Now you can increase the video memory above 128.
answered Apr 23 '15 at 23:12
elsadekelsadek
18914
2
With the virtual machine stopped you should be able to modify the settings through VirtualBox's UI. You don't have to resort to a text editor to change that setting unless something is really wrong.
– jkt123
Apr 24 '15 at 0:30
1
editing .vbox by hand is not recommended.
– Elder Geek
Apr 24 '15 at 1:22
1
@jkt123 I would not have suggested it if it was possible through VB UI, I'm talking here about video ram size which can't be otherwise resized beyond 128.
– elsadek
Apr 24 '15 at 13:22
@ElderGeek not for advanced users, and making a backup before editing is always a best practice.
– elsadek
Apr 24 '15 at 13:25
Shouldn't your answer make that clear to encourage the novice to avoid making a mistake? It's still unnecessary and not recommended - see virtualbox.org/manual/ch08.html
– Elder Geek
Apr 24 '15 at 15:12
add a comment |
As Marvin stated, you need to shutdown the VM before you change things. You also need to sudo apt-get install virtualbox-guest-dkms in the virtual ubuntu. And be advised that 3d acceleration might not work, and Unity is heavy on 3D. Thus using a less graphic intensive desktop like xfce4 might be a better/faster option. Please enable 2D acceleration at least. It should provide some speedup.
answered Feb 18 '15 at 20:44
user283885user283885
40625
Thanks for the info. I already did asudo apt-get install dkms. What doessudo apt-get install virtualbox-guest-dkms? What's the difference?
– ksl
Feb 18 '15 at 20:52
dkms = dynamic/dell kernel management system. virtualbox-guest-dkms are the drivers in guest addition for the ubuntu kernel made to work with dkms. Thus you need both.
– user283885
Feb 18 '15 at 21:00
add a comment |
In VB v5.1.x, if you enable 3D Acceleration first in the UI, VRAM automatically jumps to 256M.
answered Nov 10 '16 at 15:56
albokoalboko
1192
The question refers to an Ubuntu guest, your screenshot is of a Windows 10 guest. VirtualBox has different limits and setting for different types of guests. Linux guest can not use "2D Video Acc", and the max video memory is 128MB
– Richard Pierre
Mar 22 '17 at 4:51
@RichardPierre - don't want to start arguing, but my screenshot was actually from Ubunty. Please recheck.
– alboko
Aug 23 '17 at 21:00
2
you are running a Windows "Guest" on a Linux "Host". Windows "Guest" have different allowable settings. One of those is 2d acceleration is for "Windows Guests" only : virtualbox.org/manual/ch04.html#guestadd-2d You'll also find that that maximum a Linux "Guest" can allocate to Video memory is 128MB. So try again with a Linux "Guest" and let me know if it's otherwise.
– Richard Pierre
Aug 24 '17 at 22:52
add a comment |
- Shutdown VM
- From the elevated command prompt:
"C:Program FilesOracleVirtualBoxVBoxManage.exe" modifyvm "Ubuntu" --vram 256
Replace "Ubuntu" with the name of your VM
Verfied working.
And of course from the terminal from the VM Ubuntu:
- sudo apt-get install dkms & sudo apt-get install virtualbox-guest-dkms
- Reboot VM
edited Feb 24 '18 at 20:57
davidbaumann
1,45911127
answered Feb 24 '18 at 12:43
Johan VijfhuizenJohan Vijfhuizen
111
1
true.. But also the exact location of vboxmanager.exe. (This is missing in previous post) Otherwise it won't work.
– Johan Vijfhuizen
Feb 24 '18 at 13:04
add a comment |
Running vboxmanage itself to find that --vram option but could not, however, using the command in top answer worked. Someone has posted that your VM doesn't need more RAM assigned to your display than needed so am posting my settings for Win7 running in 4k without any acceleration enabled that it complained about "not enough ram". Hope someone will find this useful.
The last post is from Feb18 so this is an update that it works.
Since someone posted here that it went black screen - advice is - clone your VM and test it there first if it works.
Settings before the change:
Settings after the change:
edited Oct 2 '18 at 12:21
Yufenyuy Veyeh Dider
1,5494924
answered Oct 2 '18 at 10:07
VladVlad
1
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f587083%2fvirtualbox-how-to-increase-video-memory%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
7 Answers
7
active
oldest
votes
7 Answers
7
active
oldest
votes
active
oldest
votes
active
oldest
votes
You need to shut down the virtual OS before you can edit settings.
edited Aug 8 '16 at 18:21
JetCrusherTorpedo
33
answered Feb 18 '15 at 20:35
Marvin MicekMarvin Micek
572416
Just an addition, you need to properly shutdown the virtual OS. Saving the state won't work.
– Reeshabh Ranjan
Mar 3 at 17:18
add a comment |
You need to shut down the virtual OS before you can edit settings.
edited Aug 8 '16 at 18:21
JetCrusherTorpedo
33
answered Feb 18 '15 at 20:35
Marvin MicekMarvin Micek
572416
Just an addition, you need to properly shutdown the virtual OS. Saving the state won't work.
– Reeshabh Ranjan
Mar 3 at 17:18
add a comment |
You need to shut down the virtual OS before you can edit settings.
edited Aug 8 '16 at 18:21
JetCrusherTorpedo
33
answered Feb 18 '15 at 20:35
Marvin MicekMarvin Micek
572416
You need to shut down the virtual OS before you can edit settings.
edited Aug 8 '16 at 18:21
JetCrusherTorpedo
33
answered Feb 18 '15 at 20:35
Marvin MicekMarvin Micek
572416
edited Aug 8 '16 at 18:21
JetCrusherTorpedo
33
edited Aug 8 '16 at 18:21
JetCrusherTorpedo
33
edited Aug 8 '16 at 18:21
JetCrusherTorpedo
33
33
answered Feb 18 '15 at 20:35
Marvin MicekMarvin Micek
572416
answered Feb 18 '15 at 20:35
Marvin MicekMarvin Micek
572416
answered Feb 18 '15 at 20:35
Marvin MicekMarvin Micek
572416
572416
Just an addition, you need to properly shutdown the virtual OS. Saving the state won't work.
– Reeshabh Ranjan
Mar 3 at 17:18
add a comment |
Just an addition, you need to properly shutdown the virtual OS. Saving the state won't work.
– Reeshabh Ranjan
Mar 3 at 17:18
Just an addition, you need to properly shutdown the virtual OS. Saving the state won't work.
– Reeshabh Ranjan
Mar 3 at 17:18
Just an addition, you need to properly shutdown the virtual OS. Saving the state won't work.
– Reeshabh Ranjan
Mar 3 at 17:18
add a comment |
Virtual Box supports up to 256 MB of video RAM. This can not be set using the slider of the Virtual Box Manager.
To make full use of all supported memory we can issue the following command in a terminal:
VBoxManage modifyvm "Name of VM" --vram 256
Before we change settings such as the video RAM a pre-existing virtual machine has to be shut down.
Note that for 3D video hardware acceleration from the guest addition's video driver the physical RAM of the host graphics card will be passed through. The video RAM settings of the virtual machine will not affect this.
answered Feb 18 '15 at 21:48
TakkatTakkat
108k37251378
This is the only working way. Updating manually the vbox file doesn't work as the file is refreshed by VirtualBox automatically.
– ZedTuX
Dec 1 '16 at 12:18
This is a TERRIBLE suggestion. Trying this just completely borked my VM. Now it boots to a "FATAL: INT18: BOOT FAILURE"
– krb686
Dec 25 '16 at 0:09
@krb686: sorry to hear that. We can't reproduce this error here. It may not be related to increasing VRAM.
– Takkat
Dec 25 '16 at 9:43
@krb686 this error is related to the bootprocedure. e.g. missing Master Boot Records or similar boot-related parts of an OS
– Foaster
Jun 8 '17 at 13:53
This command caused my machine to cease booting (boots to all black screen, no text). Reversing (running again with128) brought it back.
– mike
Jun 12 '17 at 20:16
|
show 5 more comments
Virtual Box supports up to 256 MB of video RAM. This can not be set using the slider of the Virtual Box Manager.
To make full use of all supported memory we can issue the following command in a terminal:
VBoxManage modifyvm "Name of VM" --vram 256
Before we change settings such as the video RAM a pre-existing virtual machine has to be shut down.
Note that for 3D video hardware acceleration from the guest addition's video driver the physical RAM of the host graphics card will be passed through. The video RAM settings of the virtual machine will not affect this.
answered Feb 18 '15 at 21:48
TakkatTakkat
108k37251378
This is the only working way. Updating manually the vbox file doesn't work as the file is refreshed by VirtualBox automatically.
– ZedTuX
Dec 1 '16 at 12:18
This is a TERRIBLE suggestion. Trying this just completely borked my VM. Now it boots to a "FATAL: INT18: BOOT FAILURE"
– krb686
Dec 25 '16 at 0:09
@krb686: sorry to hear that. We can't reproduce this error here. It may not be related to increasing VRAM.
– Takkat
Dec 25 '16 at 9:43
@krb686 this error is related to the bootprocedure. e.g. missing Master Boot Records or similar boot-related parts of an OS
– Foaster
Jun 8 '17 at 13:53
This command caused my machine to cease booting (boots to all black screen, no text). Reversing (running again with128) brought it back.
– mike
Jun 12 '17 at 20:16
|
show 5 more comments
Virtual Box supports up to 256 MB of video RAM. This can not be set using the slider of the Virtual Box Manager.
To make full use of all supported memory we can issue the following command in a terminal:
VBoxManage modifyvm "Name of VM" --vram 256
Before we change settings such as the video RAM a pre-existing virtual machine has to be shut down.
Note that for 3D video hardware acceleration from the guest addition's video driver the physical RAM of the host graphics card will be passed through. The video RAM settings of the virtual machine will not affect this.
answered Feb 18 '15 at 21:48
TakkatTakkat
108k37251378
Virtual Box supports up to 256 MB of video RAM. This can not be set using the slider of the Virtual Box Manager.
To make full use of all supported memory we can issue the following command in a terminal:
VBoxManage modifyvm "Name of VM" --vram 256
Before we change settings such as the video RAM a pre-existing virtual machine has to be shut down.
Note that for 3D video hardware acceleration from the guest addition's video driver the physical RAM of the host graphics card will be passed through. The video RAM settings of the virtual machine will not affect this.
answered Feb 18 '15 at 21:48
TakkatTakkat
108k37251378
edited Mar 8 '16 at 21:56
answered Feb 18 '15 at 21:48
TakkatTakkat
108k37251378
answered Feb 18 '15 at 21:48
TakkatTakkat
108k37251378
answered Feb 18 '15 at 21:48
TakkatTakkat
108k37251378
108k37251378
This is the only working way. Updating manually the vbox file doesn't work as the file is refreshed by VirtualBox automatically.
– ZedTuX
Dec 1 '16 at 12:18
This is a TERRIBLE suggestion. Trying this just completely borked my VM. Now it boots to a "FATAL: INT18: BOOT FAILURE"
– krb686
Dec 25 '16 at 0:09
@krb686: sorry to hear that. We can't reproduce this error here. It may not be related to increasing VRAM.
– Takkat
Dec 25 '16 at 9:43
@krb686 this error is related to the bootprocedure. e.g. missing Master Boot Records or similar boot-related parts of an OS
– Foaster
Jun 8 '17 at 13:53
This command caused my machine to cease booting (boots to all black screen, no text). Reversing (running again with128) brought it back.
– mike
Jun 12 '17 at 20:16
|
show 5 more comments
This is the only working way. Updating manually the vbox file doesn't work as the file is refreshed by VirtualBox automatically.
– ZedTuX
Dec 1 '16 at 12:18
This is a TERRIBLE suggestion. Trying this just completely borked my VM. Now it boots to a "FATAL: INT18: BOOT FAILURE"
– krb686
Dec 25 '16 at 0:09
@krb686: sorry to hear that. We can't reproduce this error here. It may not be related to increasing VRAM.
– Takkat
Dec 25 '16 at 9:43
@krb686 this error is related to the bootprocedure. e.g. missing Master Boot Records or similar boot-related parts of an OS
– Foaster
Jun 8 '17 at 13:53
This command caused my machine to cease booting (boots to all black screen, no text). Reversing (running again with128) brought it back.
– mike
Jun 12 '17 at 20:16
This is the only working way. Updating manually the vbox file doesn't work as the file is refreshed by VirtualBox automatically.
– ZedTuX
Dec 1 '16 at 12:18
This is the only working way. Updating manually the vbox file doesn't work as the file is refreshed by VirtualBox automatically.
– ZedTuX
Dec 1 '16 at 12:18
This is a TERRIBLE suggestion. Trying this just completely borked my VM. Now it boots to a "FATAL: INT18: BOOT FAILURE"
– krb686
Dec 25 '16 at 0:09
This is a TERRIBLE suggestion. Trying this just completely borked my VM. Now it boots to a "FATAL: INT18: BOOT FAILURE"
– krb686
Dec 25 '16 at 0:09
@krb686: sorry to hear that. We can't reproduce this error here. It may not be related to increasing VRAM.
– Takkat
Dec 25 '16 at 9:43
@krb686: sorry to hear that. We can't reproduce this error here. It may not be related to increasing VRAM.
– Takkat
Dec 25 '16 at 9:43
@krb686 this error is related to the bootprocedure. e.g. missing Master Boot Records or similar boot-related parts of an OS
– Foaster
Jun 8 '17 at 13:53
@krb686 this error is related to the bootprocedure. e.g. missing Master Boot Records or similar boot-related parts of an OS
– Foaster
Jun 8 '17 at 13:53
This command caused my machine to cease booting (boots to all black screen, no text). Reversing (running again with
128 ) brought it back.– mike
Jun 12 '17 at 20:16
This command caused my machine to cease booting (boots to all black screen, no text). Reversing (running again with
128 ) brought it back.– mike
Jun 12 '17 at 20:16
|
show 5 more comments
- Stop the virtual machine and close virtualbox
- Using a text editor like "Sublime Text" open YOUMACHINE.vbox. Make a backup beforehand.
Look for vram entry and change its value
<Display VRAMSize="256" monitorCount="1" accelerate3D="true"
accelerate2DVideo="false"/>
Save the file.
Now you can increase the video memory above 128.
answered Apr 23 '15 at 23:12
elsadekelsadek
18914
2
With the virtual machine stopped you should be able to modify the settings through VirtualBox's UI. You don't have to resort to a text editor to change that setting unless something is really wrong.
– jkt123
Apr 24 '15 at 0:30
1
editing .vbox by hand is not recommended.
– Elder Geek
Apr 24 '15 at 1:22
1
@jkt123 I would not have suggested it if it was possible through VB UI, I'm talking here about video ram size which can't be otherwise resized beyond 128.
– elsadek
Apr 24 '15 at 13:22
@ElderGeek not for advanced users, and making a backup before editing is always a best practice.
– elsadek
Apr 24 '15 at 13:25
Shouldn't your answer make that clear to encourage the novice to avoid making a mistake? It's still unnecessary and not recommended - see virtualbox.org/manual/ch08.html
– Elder Geek
Apr 24 '15 at 15:12
add a comment |
- Stop the virtual machine and close virtualbox
- Using a text editor like "Sublime Text" open YOUMACHINE.vbox. Make a backup beforehand.
Look for vram entry and change its value
<Display VRAMSize="256" monitorCount="1" accelerate3D="true"
accelerate2DVideo="false"/>
Save the file.
Now you can increase the video memory above 128.
answered Apr 23 '15 at 23:12
elsadekelsadek
18914
2
With the virtual machine stopped you should be able to modify the settings through VirtualBox's UI. You don't have to resort to a text editor to change that setting unless something is really wrong.
– jkt123
Apr 24 '15 at 0:30
1
editing .vbox by hand is not recommended.
– Elder Geek
Apr 24 '15 at 1:22
1
@jkt123 I would not have suggested it if it was possible through VB UI, I'm talking here about video ram size which can't be otherwise resized beyond 128.
– elsadek
Apr 24 '15 at 13:22
@ElderGeek not for advanced users, and making a backup before editing is always a best practice.
– elsadek
Apr 24 '15 at 13:25
Shouldn't your answer make that clear to encourage the novice to avoid making a mistake? It's still unnecessary and not recommended - see virtualbox.org/manual/ch08.html
– Elder Geek
Apr 24 '15 at 15:12
add a comment |
- Stop the virtual machine and close virtualbox
- Using a text editor like "Sublime Text" open YOUMACHINE.vbox. Make a backup beforehand.
Look for vram entry and change its value
<Display VRAMSize="256" monitorCount="1" accelerate3D="true"
accelerate2DVideo="false"/>
Save the file.
Now you can increase the video memory above 128.
answered Apr 23 '15 at 23:12
elsadekelsadek
18914
- Stop the virtual machine and close virtualbox
- Using a text editor like "Sublime Text" open YOUMACHINE.vbox. Make a backup beforehand.
Look for vram entry and change its value
<Display VRAMSize="256" monitorCount="1" accelerate3D="true"
accelerate2DVideo="false"/>
Save the file.
Now you can increase the video memory above 128.
answered Apr 23 '15 at 23:12
elsadekelsadek
18914
edited Oct 6 '15 at 12:06
answered Apr 23 '15 at 23:12
elsadekelsadek
18914
answered Apr 23 '15 at 23:12
elsadekelsadek
18914
answered Apr 23 '15 at 23:12
elsadekelsadek
18914
18914
2
With the virtual machine stopped you should be able to modify the settings through VirtualBox's UI. You don't have to resort to a text editor to change that setting unless something is really wrong.
– jkt123
Apr 24 '15 at 0:30
1
editing .vbox by hand is not recommended.
– Elder Geek
Apr 24 '15 at 1:22
1
@jkt123 I would not have suggested it if it was possible through VB UI, I'm talking here about video ram size which can't be otherwise resized beyond 128.
– elsadek
Apr 24 '15 at 13:22
@ElderGeek not for advanced users, and making a backup before editing is always a best practice.
– elsadek
Apr 24 '15 at 13:25
Shouldn't your answer make that clear to encourage the novice to avoid making a mistake? It's still unnecessary and not recommended - see virtualbox.org/manual/ch08.html
– Elder Geek
Apr 24 '15 at 15:12
add a comment |
2
With the virtual machine stopped you should be able to modify the settings through VirtualBox's UI. You don't have to resort to a text editor to change that setting unless something is really wrong.
– jkt123
Apr 24 '15 at 0:30
1
editing .vbox by hand is not recommended.
– Elder Geek
Apr 24 '15 at 1:22
1
@jkt123 I would not have suggested it if it was possible through VB UI, I'm talking here about video ram size which can't be otherwise resized beyond 128.
– elsadek
Apr 24 '15 at 13:22
@ElderGeek not for advanced users, and making a backup before editing is always a best practice.
– elsadek
Apr 24 '15 at 13:25
Shouldn't your answer make that clear to encourage the novice to avoid making a mistake? It's still unnecessary and not recommended - see virtualbox.org/manual/ch08.html
– Elder Geek
Apr 24 '15 at 15:12
2
2
With the virtual machine stopped you should be able to modify the settings through VirtualBox's UI. You don't have to resort to a text editor to change that setting unless something is really wrong.
– jkt123
Apr 24 '15 at 0:30
With the virtual machine stopped you should be able to modify the settings through VirtualBox's UI. You don't have to resort to a text editor to change that setting unless something is really wrong.
– jkt123
Apr 24 '15 at 0:30
1
1
editing .vbox by hand is not recommended.
– Elder Geek
Apr 24 '15 at 1:22
editing .vbox by hand is not recommended.
– Elder Geek
Apr 24 '15 at 1:22
1
1
@jkt123 I would not have suggested it if it was possible through VB UI, I'm talking here about video ram size which can't be otherwise resized beyond 128.
– elsadek
Apr 24 '15 at 13:22
@jkt123 I would not have suggested it if it was possible through VB UI, I'm talking here about video ram size which can't be otherwise resized beyond 128.
– elsadek
Apr 24 '15 at 13:22
@ElderGeek not for advanced users, and making a backup before editing is always a best practice.
– elsadek
Apr 24 '15 at 13:25
@ElderGeek not for advanced users, and making a backup before editing is always a best practice.
– elsadek
Apr 24 '15 at 13:25
Shouldn't your answer make that clear to encourage the novice to avoid making a mistake? It's still unnecessary and not recommended - see virtualbox.org/manual/ch08.html
– Elder Geek
Apr 24 '15 at 15:12
Shouldn't your answer make that clear to encourage the novice to avoid making a mistake? It's still unnecessary and not recommended - see virtualbox.org/manual/ch08.html
– Elder Geek
Apr 24 '15 at 15:12
add a comment |
As Marvin stated, you need to shutdown the VM before you change things. You also need to sudo apt-get install virtualbox-guest-dkms in the virtual ubuntu. And be advised that 3d acceleration might not work, and Unity is heavy on 3D. Thus using a less graphic intensive desktop like xfce4 might be a better/faster option. Please enable 2D acceleration at least. It should provide some speedup.
answered Feb 18 '15 at 20:44
user283885user283885
40625
Thanks for the info. I already did asudo apt-get install dkms. What doessudo apt-get install virtualbox-guest-dkms? What's the difference?
– ksl
Feb 18 '15 at 20:52
dkms = dynamic/dell kernel management system. virtualbox-guest-dkms are the drivers in guest addition for the ubuntu kernel made to work with dkms. Thus you need both.
– user283885
Feb 18 '15 at 21:00
add a comment |
As Marvin stated, you need to shutdown the VM before you change things. You also need to sudo apt-get install virtualbox-guest-dkms in the virtual ubuntu. And be advised that 3d acceleration might not work, and Unity is heavy on 3D. Thus using a less graphic intensive desktop like xfce4 might be a better/faster option. Please enable 2D acceleration at least. It should provide some speedup.
answered Feb 18 '15 at 20:44
user283885user283885
40625
Thanks for the info. I already did asudo apt-get install dkms. What doessudo apt-get install virtualbox-guest-dkms? What's the difference?
– ksl
Feb 18 '15 at 20:52
dkms = dynamic/dell kernel management system. virtualbox-guest-dkms are the drivers in guest addition for the ubuntu kernel made to work with dkms. Thus you need both.
– user283885
Feb 18 '15 at 21:00
add a comment |
As Marvin stated, you need to shutdown the VM before you change things. You also need to sudo apt-get install virtualbox-guest-dkms in the virtual ubuntu. And be advised that 3d acceleration might not work, and Unity is heavy on 3D. Thus using a less graphic intensive desktop like xfce4 might be a better/faster option. Please enable 2D acceleration at least. It should provide some speedup.
answered Feb 18 '15 at 20:44
user283885user283885
40625
As Marvin stated, you need to shutdown the VM before you change things. You also need to sudo apt-get install virtualbox-guest-dkms in the virtual ubuntu. And be advised that 3d acceleration might not work, and Unity is heavy on 3D. Thus using a less graphic intensive desktop like xfce4 might be a better/faster option. Please enable 2D acceleration at least. It should provide some speedup.
answered Feb 18 '15 at 20:44
user283885user283885
40625
answered Feb 18 '15 at 20:44
user283885user283885
40625
answered Feb 18 '15 at 20:44
user283885user283885
40625
answered Feb 18 '15 at 20:44
user283885user283885
40625
40625
Thanks for the info. I already did asudo apt-get install dkms. What doessudo apt-get install virtualbox-guest-dkms? What's the difference?
– ksl
Feb 18 '15 at 20:52
dkms = dynamic/dell kernel management system. virtualbox-guest-dkms are the drivers in guest addition for the ubuntu kernel made to work with dkms. Thus you need both.
– user283885
Feb 18 '15 at 21:00
add a comment |
Thanks for the info. I already did asudo apt-get install dkms. What doessudo apt-get install virtualbox-guest-dkms? What's the difference?
– ksl
Feb 18 '15 at 20:52
dkms = dynamic/dell kernel management system. virtualbox-guest-dkms are the drivers in guest addition for the ubuntu kernel made to work with dkms. Thus you need both.
– user283885
Feb 18 '15 at 21:00
Thanks for the info. I already did a
sudo apt-get install dkms. What does sudo apt-get install virtualbox-guest-dkms? What's the difference?– ksl
Feb 18 '15 at 20:52
Thanks for the info. I already did a
sudo apt-get install dkms. What does sudo apt-get install virtualbox-guest-dkms? What's the difference?– ksl
Feb 18 '15 at 20:52
dkms = dynamic/dell kernel management system. virtualbox-guest-dkms are the drivers in guest addition for the ubuntu kernel made to work with dkms. Thus you need both.
– user283885
Feb 18 '15 at 21:00
dkms = dynamic/dell kernel management system. virtualbox-guest-dkms are the drivers in guest addition for the ubuntu kernel made to work with dkms. Thus you need both.
– user283885
Feb 18 '15 at 21:00
add a comment |
In VB v5.1.x, if you enable 3D Acceleration first in the UI, VRAM automatically jumps to 256M.
answered Nov 10 '16 at 15:56
albokoalboko
1192
The question refers to an Ubuntu guest, your screenshot is of a Windows 10 guest. VirtualBox has different limits and setting for different types of guests. Linux guest can not use "2D Video Acc", and the max video memory is 128MB
– Richard Pierre
Mar 22 '17 at 4:51
@RichardPierre - don't want to start arguing, but my screenshot was actually from Ubunty. Please recheck.
– alboko
Aug 23 '17 at 21:00
2
you are running a Windows "Guest" on a Linux "Host". Windows "Guest" have different allowable settings. One of those is 2d acceleration is for "Windows Guests" only : virtualbox.org/manual/ch04.html#guestadd-2d You'll also find that that maximum a Linux "Guest" can allocate to Video memory is 128MB. So try again with a Linux "Guest" and let me know if it's otherwise.
– Richard Pierre
Aug 24 '17 at 22:52
add a comment |
In VB v5.1.x, if you enable 3D Acceleration first in the UI, VRAM automatically jumps to 256M.
answered Nov 10 '16 at 15:56
albokoalboko
1192
The question refers to an Ubuntu guest, your screenshot is of a Windows 10 guest. VirtualBox has different limits and setting for different types of guests. Linux guest can not use "2D Video Acc", and the max video memory is 128MB
– Richard Pierre
Mar 22 '17 at 4:51
@RichardPierre - don't want to start arguing, but my screenshot was actually from Ubunty. Please recheck.
– alboko
Aug 23 '17 at 21:00
2
you are running a Windows "Guest" on a Linux "Host". Windows "Guest" have different allowable settings. One of those is 2d acceleration is for "Windows Guests" only : virtualbox.org/manual/ch04.html#guestadd-2d You'll also find that that maximum a Linux "Guest" can allocate to Video memory is 128MB. So try again with a Linux "Guest" and let me know if it's otherwise.
– Richard Pierre
Aug 24 '17 at 22:52
add a comment |
In VB v5.1.x, if you enable 3D Acceleration first in the UI, VRAM automatically jumps to 256M.
answered Nov 10 '16 at 15:56
albokoalboko
1192
In VB v5.1.x, if you enable 3D Acceleration first in the UI, VRAM automatically jumps to 256M.
answered Nov 10 '16 at 15:56
albokoalboko
1192
answered Nov 10 '16 at 15:56
albokoalboko
1192
answered Nov 10 '16 at 15:56
albokoalboko
1192
answered Nov 10 '16 at 15:56
albokoalboko
1192
1192
The question refers to an Ubuntu guest, your screenshot is of a Windows 10 guest. VirtualBox has different limits and setting for different types of guests. Linux guest can not use "2D Video Acc", and the max video memory is 128MB
– Richard Pierre
Mar 22 '17 at 4:51
@RichardPierre - don't want to start arguing, but my screenshot was actually from Ubunty. Please recheck.
– alboko
Aug 23 '17 at 21:00
2
you are running a Windows "Guest" on a Linux "Host". Windows "Guest" have different allowable settings. One of those is 2d acceleration is for "Windows Guests" only : virtualbox.org/manual/ch04.html#guestadd-2d You'll also find that that maximum a Linux "Guest" can allocate to Video memory is 128MB. So try again with a Linux "Guest" and let me know if it's otherwise.
– Richard Pierre
Aug 24 '17 at 22:52
add a comment |
The question refers to an Ubuntu guest, your screenshot is of a Windows 10 guest. VirtualBox has different limits and setting for different types of guests. Linux guest can not use "2D Video Acc", and the max video memory is 128MB
– Richard Pierre
Mar 22 '17 at 4:51
@RichardPierre - don't want to start arguing, but my screenshot was actually from Ubunty. Please recheck.
– alboko
Aug 23 '17 at 21:00
2
you are running a Windows "Guest" on a Linux "Host". Windows "Guest" have different allowable settings. One of those is 2d acceleration is for "Windows Guests" only : virtualbox.org/manual/ch04.html#guestadd-2d You'll also find that that maximum a Linux "Guest" can allocate to Video memory is 128MB. So try again with a Linux "Guest" and let me know if it's otherwise.
– Richard Pierre
Aug 24 '17 at 22:52
The question refers to an Ubuntu guest, your screenshot is of a Windows 10 guest. VirtualBox has different limits and setting for different types of guests. Linux guest can not use "2D Video Acc", and the max video memory is 128MB
– Richard Pierre
Mar 22 '17 at 4:51
The question refers to an Ubuntu guest, your screenshot is of a Windows 10 guest. VirtualBox has different limits and setting for different types of guests. Linux guest can not use "2D Video Acc", and the max video memory is 128MB
– Richard Pierre
Mar 22 '17 at 4:51
@RichardPierre - don't want to start arguing, but my screenshot was actually from Ubunty. Please recheck.
– alboko
Aug 23 '17 at 21:00
@RichardPierre - don't want to start arguing, but my screenshot was actually from Ubunty. Please recheck.
– alboko
Aug 23 '17 at 21:00
2
2
you are running a Windows "Guest" on a Linux "Host". Windows "Guest" have different allowable settings. One of those is 2d acceleration is for "Windows Guests" only : virtualbox.org/manual/ch04.html#guestadd-2d You'll also find that that maximum a Linux "Guest" can allocate to Video memory is 128MB. So try again with a Linux "Guest" and let me know if it's otherwise.
– Richard Pierre
Aug 24 '17 at 22:52
you are running a Windows "Guest" on a Linux "Host". Windows "Guest" have different allowable settings. One of those is 2d acceleration is for "Windows Guests" only : virtualbox.org/manual/ch04.html#guestadd-2d You'll also find that that maximum a Linux "Guest" can allocate to Video memory is 128MB. So try again with a Linux "Guest" and let me know if it's otherwise.
– Richard Pierre
Aug 24 '17 at 22:52
add a comment |
- Shutdown VM
- From the elevated command prompt:
"C:Program FilesOracleVirtualBoxVBoxManage.exe" modifyvm "Ubuntu" --vram 256
Replace "Ubuntu" with the name of your VM
Verfied working.
And of course from the terminal from the VM Ubuntu:
- sudo apt-get install dkms & sudo apt-get install virtualbox-guest-dkms
- Reboot VM
edited Feb 24 '18 at 20:57
davidbaumann
1,45911127
answered Feb 24 '18 at 12:43
Johan VijfhuizenJohan Vijfhuizen
111
1
true.. But also the exact location of vboxmanager.exe. (This is missing in previous post) Otherwise it won't work.
– Johan Vijfhuizen
Feb 24 '18 at 13:04
add a comment |
- Shutdown VM
- From the elevated command prompt:
"C:Program FilesOracleVirtualBoxVBoxManage.exe" modifyvm "Ubuntu" --vram 256
Replace "Ubuntu" with the name of your VM
Verfied working.
And of course from the terminal from the VM Ubuntu:
- sudo apt-get install dkms & sudo apt-get install virtualbox-guest-dkms
- Reboot VM
edited Feb 24 '18 at 20:57
davidbaumann
1,45911127
answered Feb 24 '18 at 12:43
Johan VijfhuizenJohan Vijfhuizen
111
1
true.. But also the exact location of vboxmanager.exe. (This is missing in previous post) Otherwise it won't work.
– Johan Vijfhuizen
Feb 24 '18 at 13:04
add a comment |
- Shutdown VM
- From the elevated command prompt:
"C:Program FilesOracleVirtualBoxVBoxManage.exe" modifyvm "Ubuntu" --vram 256
Replace "Ubuntu" with the name of your VM
Verfied working.
And of course from the terminal from the VM Ubuntu:
- sudo apt-get install dkms & sudo apt-get install virtualbox-guest-dkms
- Reboot VM
edited Feb 24 '18 at 20:57
davidbaumann
1,45911127
answered Feb 24 '18 at 12:43
Johan VijfhuizenJohan Vijfhuizen
111
- Shutdown VM
- From the elevated command prompt:
"C:Program FilesOracleVirtualBoxVBoxManage.exe" modifyvm "Ubuntu" --vram 256
Replace "Ubuntu" with the name of your VM
Verfied working.
And of course from the terminal from the VM Ubuntu:
- sudo apt-get install dkms & sudo apt-get install virtualbox-guest-dkms
- Reboot VM
edited Feb 24 '18 at 20:57
davidbaumann
1,45911127
answered Feb 24 '18 at 12:43
Johan VijfhuizenJohan Vijfhuizen
111
edited Feb 24 '18 at 20:57
davidbaumann
1,45911127
edited Feb 24 '18 at 20:57
davidbaumann
1,45911127
edited Feb 24 '18 at 20:57
davidbaumann
1,45911127
1,45911127
answered Feb 24 '18 at 12:43
Johan VijfhuizenJohan Vijfhuizen
111
answered Feb 24 '18 at 12:43
Johan VijfhuizenJohan Vijfhuizen
111
answered Feb 24 '18 at 12:43
Johan VijfhuizenJohan Vijfhuizen
111
111
1
true.. But also the exact location of vboxmanager.exe. (This is missing in previous post) Otherwise it won't work.
– Johan Vijfhuizen
Feb 24 '18 at 13:04
add a comment |
1
true.. But also the exact location of vboxmanager.exe. (This is missing in previous post) Otherwise it won't work.
– Johan Vijfhuizen
Feb 24 '18 at 13:04
1
1
true.. But also the exact location of vboxmanager.exe. (This is missing in previous post) Otherwise it won't work.
– Johan Vijfhuizen
Feb 24 '18 at 13:04
true.. But also the exact location of vboxmanager.exe. (This is missing in previous post) Otherwise it won't work.
– Johan Vijfhuizen
Feb 24 '18 at 13:04
add a comment |
Running vboxmanage itself to find that --vram option but could not, however, using the command in top answer worked. Someone has posted that your VM doesn't need more RAM assigned to your display than needed so am posting my settings for Win7 running in 4k without any acceleration enabled that it complained about "not enough ram". Hope someone will find this useful.
The last post is from Feb18 so this is an update that it works.
Since someone posted here that it went black screen - advice is - clone your VM and test it there first if it works.
Settings before the change:
Settings after the change:
edited Oct 2 '18 at 12:21
Yufenyuy Veyeh Dider
1,5494924
answered Oct 2 '18 at 10:07
VladVlad
1
add a comment |
Running vboxmanage itself to find that --vram option but could not, however, using the command in top answer worked. Someone has posted that your VM doesn't need more RAM assigned to your display than needed so am posting my settings for Win7 running in 4k without any acceleration enabled that it complained about "not enough ram". Hope someone will find this useful.
The last post is from Feb18 so this is an update that it works.
Since someone posted here that it went black screen - advice is - clone your VM and test it there first if it works.
Settings before the change:
Settings after the change:
edited Oct 2 '18 at 12:21
Yufenyuy Veyeh Dider
1,5494924
answered Oct 2 '18 at 10:07
VladVlad
1
add a comment |
Running vboxmanage itself to find that --vram option but could not, however, using the command in top answer worked. Someone has posted that your VM doesn't need more RAM assigned to your display than needed so am posting my settings for Win7 running in 4k without any acceleration enabled that it complained about "not enough ram". Hope someone will find this useful.
The last post is from Feb18 so this is an update that it works.
Since someone posted here that it went black screen - advice is - clone your VM and test it there first if it works.
Settings before the change:
Settings after the change:
edited Oct 2 '18 at 12:21
Yufenyuy Veyeh Dider
1,5494924
answered Oct 2 '18 at 10:07
VladVlad
1
Running vboxmanage itself to find that --vram option but could not, however, using the command in top answer worked. Someone has posted that your VM doesn't need more RAM assigned to your display than needed so am posting my settings for Win7 running in 4k without any acceleration enabled that it complained about "not enough ram". Hope someone will find this useful.
The last post is from Feb18 so this is an update that it works.
Since someone posted here that it went black screen - advice is - clone your VM and test it there first if it works.
Settings before the change:
Settings after the change:
edited Oct 2 '18 at 12:21
Yufenyuy Veyeh Dider
1,5494924
answered Oct 2 '18 at 10:07
VladVlad
1
edited Oct 2 '18 at 12:21
Yufenyuy Veyeh Dider
1,5494924
edited Oct 2 '18 at 12:21
Yufenyuy Veyeh Dider
1,5494924
edited Oct 2 '18 at 12:21
Yufenyuy Veyeh Dider
1,5494924
1,5494924
answered Oct 2 '18 at 10:07
VladVlad
1
answered Oct 2 '18 at 10:07
VladVlad
1
answered Oct 2 '18 at 10:07
VladVlad
1
1
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f587083%2fvirtualbox-how-to-increase-video-memory%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
