What are differences between VBoxVGA, VMSVGA and VBoxSVGA in VirtualBox?
VirtualBox 6.0 provides a new setting called Graphics Controller. There are four options to choose from:
- None
- VBoxVGA
- VMSVGA
- VBoxSVGA
In the user manual I have found this information:
Graphics Controller: Specifies the graphics adapter type used by the guest VM. Note that you must install the Guest Additions on the guest VM to specify the VBoxSVGA or VMSVGA graphics controller. The following options are available:
– VBoxSVGA: The default graphics controller for new VMs that use Linux or Windows 7 or later. This graphics controller improves performance and 3D support when compared to the legacy VBoxVGA option.
– VBoxVGA: Use this graphics controller for legacy guest OSes. This is the default graphics controller for Windows versions before Windows 7.
– VMSVGA: Use this graphics controller to emulate a VMware SVGA graphics device.
– None: Does not emulate a graphics adapter type.
But still it does not describe which of them and why should I prefer.
When should I choose None?
Is VMSVGA better than VBoxSVGA?
What is wrong with VBoxVGA?
I have tested booting of archlinux-2019.02.01-x86_64.iso with virtualbox 6.0.4 in efi and legacy modes:
┌──────────┬─────────────────────────────────┬─────────────┐
│ Adapter │ EFI mode │ Legacy mode │
├──────────┼─────────────────────────────────┼─────────────┤
│ VBoxVGA │ ok │ ok │
│ VMSVGA │ ok in systemd-boot menu, │ ok │
│ │ then black screen for some time │ │
│ │ when booting, then becomes ok │ │
│ VBoxSVGA │ black screen │ ok │
└──────────┴─────────────────────────────────┴─────────────┘
virtualbox vmware vga graphics adapter
add a comment |
VirtualBox 6.0 provides a new setting called Graphics Controller. There are four options to choose from:
- None
- VBoxVGA
- VMSVGA
- VBoxSVGA
In the user manual I have found this information:
Graphics Controller: Specifies the graphics adapter type used by the guest VM. Note that you must install the Guest Additions on the guest VM to specify the VBoxSVGA or VMSVGA graphics controller. The following options are available:
– VBoxSVGA: The default graphics controller for new VMs that use Linux or Windows 7 or later. This graphics controller improves performance and 3D support when compared to the legacy VBoxVGA option.
– VBoxVGA: Use this graphics controller for legacy guest OSes. This is the default graphics controller for Windows versions before Windows 7.
– VMSVGA: Use this graphics controller to emulate a VMware SVGA graphics device.
– None: Does not emulate a graphics adapter type.
But still it does not describe which of them and why should I prefer.
When should I choose None?
Is VMSVGA better than VBoxSVGA?
What is wrong with VBoxVGA?
I have tested booting of archlinux-2019.02.01-x86_64.iso with virtualbox 6.0.4 in efi and legacy modes:
┌──────────┬─────────────────────────────────┬─────────────┐
│ Adapter │ EFI mode │ Legacy mode │
├──────────┼─────────────────────────────────┼─────────────┤
│ VBoxVGA │ ok │ ok │
│ VMSVGA │ ok in systemd-boot menu, │ ok │
│ │ then black screen for some time │ │
│ │ when booting, then becomes ok │ │
│ VBoxSVGA │ black screen │ ok │
└──────────┴─────────────────────────────────┴─────────────┘
virtualbox vmware vga graphics adapter
add a comment |
VirtualBox 6.0 provides a new setting called Graphics Controller. There are four options to choose from:
- None
- VBoxVGA
- VMSVGA
- VBoxSVGA
In the user manual I have found this information:
Graphics Controller: Specifies the graphics adapter type used by the guest VM. Note that you must install the Guest Additions on the guest VM to specify the VBoxSVGA or VMSVGA graphics controller. The following options are available:
– VBoxSVGA: The default graphics controller for new VMs that use Linux or Windows 7 or later. This graphics controller improves performance and 3D support when compared to the legacy VBoxVGA option.
– VBoxVGA: Use this graphics controller for legacy guest OSes. This is the default graphics controller for Windows versions before Windows 7.
– VMSVGA: Use this graphics controller to emulate a VMware SVGA graphics device.
– None: Does not emulate a graphics adapter type.
But still it does not describe which of them and why should I prefer.
When should I choose None?
Is VMSVGA better than VBoxSVGA?
What is wrong with VBoxVGA?
I have tested booting of archlinux-2019.02.01-x86_64.iso with virtualbox 6.0.4 in efi and legacy modes:
┌──────────┬─────────────────────────────────┬─────────────┐
│ Adapter │ EFI mode │ Legacy mode │
├──────────┼─────────────────────────────────┼─────────────┤
│ VBoxVGA │ ok │ ok │
│ VMSVGA │ ok in systemd-boot menu, │ ok │
│ │ then black screen for some time │ │
│ │ when booting, then becomes ok │ │
│ VBoxSVGA │ black screen │ ok │
└──────────┴─────────────────────────────────┴─────────────┘
virtualbox vmware vga graphics adapter
VirtualBox 6.0 provides a new setting called Graphics Controller. There are four options to choose from:
- None
- VBoxVGA
- VMSVGA
- VBoxSVGA
In the user manual I have found this information:
Graphics Controller: Specifies the graphics adapter type used by the guest VM. Note that you must install the Guest Additions on the guest VM to specify the VBoxSVGA or VMSVGA graphics controller. The following options are available:
– VBoxSVGA: The default graphics controller for new VMs that use Linux or Windows 7 or later. This graphics controller improves performance and 3D support when compared to the legacy VBoxVGA option.
– VBoxVGA: Use this graphics controller for legacy guest OSes. This is the default graphics controller for Windows versions before Windows 7.
– VMSVGA: Use this graphics controller to emulate a VMware SVGA graphics device.
– None: Does not emulate a graphics adapter type.
But still it does not describe which of them and why should I prefer.
When should I choose None?
Is VMSVGA better than VBoxSVGA?
What is wrong with VBoxVGA?
I have tested booting of archlinux-2019.02.01-x86_64.iso with virtualbox 6.0.4 in efi and legacy modes:
┌──────────┬─────────────────────────────────┬─────────────┐
│ Adapter │ EFI mode │ Legacy mode │
├──────────┼─────────────────────────────────┼─────────────┤
│ VBoxVGA │ ok │ ok │
│ VMSVGA │ ok in systemd-boot menu, │ ok │
│ │ then black screen for some time │ │
│ │ when booting, then becomes ok │ │
│ VBoxSVGA │ black screen │ ok │
└──────────┴─────────────────────────────────┴─────────────┘
virtualbox vmware vga graphics adapter
virtualbox vmware vga graphics adapter
edited 14 mins ago
Ashark
asked 1 hour ago
AsharkAshark
617
617
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
Based on what I've found in the source code:
VBoxVGA emulates a graphics adapter specific to VirtualBox, the same as in previous versions.
It has some form of 3D passthrough, but – if I remember correctly – uses an insecure approach that just lets the guest dump any and all commands to the host GPU.
This option likely exists just to provide continuity – after upgrading to 6.0, all old VMs have this mode selected automatically so there's no unexpected change in behavior; you don't lose whatever acceleration you previously had.
VMSVGA emulates the VMware Workstation graphics adapter with the "VMware SVGA 3D" acceleration method, which is supposed to provide better performance and security than the old method.
It might also have the advantage of supporting old OS which had VMware guest additions available but not VirtualBox guest additions. (I plan to test this with Windows 9x, which is otherwise a massive pain to get even VESA graphics working with VirtualBox)
VBoxSVGA provides a hybrid device that works like VMSVGA (including its new 3D acceleration capabilities), but reports the same old PCI VID:PID as VBoxVGA.
The advantage of this mode is that you can upgrade existing VMs (which previously used VBoxVGA and had the VirtualBox Video driver installed) and they don't lose their graphics in the process – they still see the same device, until you upgrade the "guest additions" at any later time to enable 3D accel.
Also, because it's still VMware SVGA emulated by VirtualBox, choosing this option and using the VirtualBox driver may still have advantages over the VMware one, e.g. allow to make use of VirtualBox-specific additional features.
"None" is, obviously, no emulated graphics at all. Only use it if you provide a real GPU via PCI Passthrough, or if your system absolutely doesn't need a GPU.
add a comment |
But they do tell you quite explicitly when you should prefer them:
– VBoxSVGA: The default graphics controller for new VMs that use Linux or Windows 7 or later. This graphics controller improves performance and 3D support when compared to the legacy VBoxVGA option.
- Linux or Windows >7
- improves performance and 3D support
– VBoxVGA: Use this graphics controller for legacy guest OSes. This is the default graphics controller for Windows versions before Windows 7.
- (by inference) slightly lower performance but more compatibility with older OSes
- Old OS or Windows < 7
– VMSVGA: Use this graphics controller to emulate a VMware SVGA graphics device.
- Emulates a VMWare device
- probably best when your VM was originally set up on VMWare and has their tools installed
- may not be as fast as VBox cards because it's trying to be compatible with something else.
– None: Does not emulate a graphics adapter type.
- you don't want a graphics adapter
i.e. you want to run the machine headless or over SSH and don't need the overhead of it emulating graphics. - could improve performance as it removes a layer or emulation
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
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%2fsuperuser.com%2fquestions%2f1403123%2fwhat-are-differences-between-vboxvga-vmsvga-and-vboxsvga-in-virtualbox%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Based on what I've found in the source code:
VBoxVGA emulates a graphics adapter specific to VirtualBox, the same as in previous versions.
It has some form of 3D passthrough, but – if I remember correctly – uses an insecure approach that just lets the guest dump any and all commands to the host GPU.
This option likely exists just to provide continuity – after upgrading to 6.0, all old VMs have this mode selected automatically so there's no unexpected change in behavior; you don't lose whatever acceleration you previously had.
VMSVGA emulates the VMware Workstation graphics adapter with the "VMware SVGA 3D" acceleration method, which is supposed to provide better performance and security than the old method.
It might also have the advantage of supporting old OS which had VMware guest additions available but not VirtualBox guest additions. (I plan to test this with Windows 9x, which is otherwise a massive pain to get even VESA graphics working with VirtualBox)
VBoxSVGA provides a hybrid device that works like VMSVGA (including its new 3D acceleration capabilities), but reports the same old PCI VID:PID as VBoxVGA.
The advantage of this mode is that you can upgrade existing VMs (which previously used VBoxVGA and had the VirtualBox Video driver installed) and they don't lose their graphics in the process – they still see the same device, until you upgrade the "guest additions" at any later time to enable 3D accel.
Also, because it's still VMware SVGA emulated by VirtualBox, choosing this option and using the VirtualBox driver may still have advantages over the VMware one, e.g. allow to make use of VirtualBox-specific additional features.
"None" is, obviously, no emulated graphics at all. Only use it if you provide a real GPU via PCI Passthrough, or if your system absolutely doesn't need a GPU.
add a comment |
Based on what I've found in the source code:
VBoxVGA emulates a graphics adapter specific to VirtualBox, the same as in previous versions.
It has some form of 3D passthrough, but – if I remember correctly – uses an insecure approach that just lets the guest dump any and all commands to the host GPU.
This option likely exists just to provide continuity – after upgrading to 6.0, all old VMs have this mode selected automatically so there's no unexpected change in behavior; you don't lose whatever acceleration you previously had.
VMSVGA emulates the VMware Workstation graphics adapter with the "VMware SVGA 3D" acceleration method, which is supposed to provide better performance and security than the old method.
It might also have the advantage of supporting old OS which had VMware guest additions available but not VirtualBox guest additions. (I plan to test this with Windows 9x, which is otherwise a massive pain to get even VESA graphics working with VirtualBox)
VBoxSVGA provides a hybrid device that works like VMSVGA (including its new 3D acceleration capabilities), but reports the same old PCI VID:PID as VBoxVGA.
The advantage of this mode is that you can upgrade existing VMs (which previously used VBoxVGA and had the VirtualBox Video driver installed) and they don't lose their graphics in the process – they still see the same device, until you upgrade the "guest additions" at any later time to enable 3D accel.
Also, because it's still VMware SVGA emulated by VirtualBox, choosing this option and using the VirtualBox driver may still have advantages over the VMware one, e.g. allow to make use of VirtualBox-specific additional features.
"None" is, obviously, no emulated graphics at all. Only use it if you provide a real GPU via PCI Passthrough, or if your system absolutely doesn't need a GPU.
add a comment |
Based on what I've found in the source code:
VBoxVGA emulates a graphics adapter specific to VirtualBox, the same as in previous versions.
It has some form of 3D passthrough, but – if I remember correctly – uses an insecure approach that just lets the guest dump any and all commands to the host GPU.
This option likely exists just to provide continuity – after upgrading to 6.0, all old VMs have this mode selected automatically so there's no unexpected change in behavior; you don't lose whatever acceleration you previously had.
VMSVGA emulates the VMware Workstation graphics adapter with the "VMware SVGA 3D" acceleration method, which is supposed to provide better performance and security than the old method.
It might also have the advantage of supporting old OS which had VMware guest additions available but not VirtualBox guest additions. (I plan to test this with Windows 9x, which is otherwise a massive pain to get even VESA graphics working with VirtualBox)
VBoxSVGA provides a hybrid device that works like VMSVGA (including its new 3D acceleration capabilities), but reports the same old PCI VID:PID as VBoxVGA.
The advantage of this mode is that you can upgrade existing VMs (which previously used VBoxVGA and had the VirtualBox Video driver installed) and they don't lose their graphics in the process – they still see the same device, until you upgrade the "guest additions" at any later time to enable 3D accel.
Also, because it's still VMware SVGA emulated by VirtualBox, choosing this option and using the VirtualBox driver may still have advantages over the VMware one, e.g. allow to make use of VirtualBox-specific additional features.
"None" is, obviously, no emulated graphics at all. Only use it if you provide a real GPU via PCI Passthrough, or if your system absolutely doesn't need a GPU.
Based on what I've found in the source code:
VBoxVGA emulates a graphics adapter specific to VirtualBox, the same as in previous versions.
It has some form of 3D passthrough, but – if I remember correctly – uses an insecure approach that just lets the guest dump any and all commands to the host GPU.
This option likely exists just to provide continuity – after upgrading to 6.0, all old VMs have this mode selected automatically so there's no unexpected change in behavior; you don't lose whatever acceleration you previously had.
VMSVGA emulates the VMware Workstation graphics adapter with the "VMware SVGA 3D" acceleration method, which is supposed to provide better performance and security than the old method.
It might also have the advantage of supporting old OS which had VMware guest additions available but not VirtualBox guest additions. (I plan to test this with Windows 9x, which is otherwise a massive pain to get even VESA graphics working with VirtualBox)
VBoxSVGA provides a hybrid device that works like VMSVGA (including its new 3D acceleration capabilities), but reports the same old PCI VID:PID as VBoxVGA.
The advantage of this mode is that you can upgrade existing VMs (which previously used VBoxVGA and had the VirtualBox Video driver installed) and they don't lose their graphics in the process – they still see the same device, until you upgrade the "guest additions" at any later time to enable 3D accel.
Also, because it's still VMware SVGA emulated by VirtualBox, choosing this option and using the VirtualBox driver may still have advantages over the VMware one, e.g. allow to make use of VirtualBox-specific additional features.
"None" is, obviously, no emulated graphics at all. Only use it if you provide a real GPU via PCI Passthrough, or if your system absolutely doesn't need a GPU.
edited 42 mins ago
answered 1 hour ago
grawitygrawity
237k37503557
237k37503557
add a comment |
add a comment |
But they do tell you quite explicitly when you should prefer them:
– VBoxSVGA: The default graphics controller for new VMs that use Linux or Windows 7 or later. This graphics controller improves performance and 3D support when compared to the legacy VBoxVGA option.
- Linux or Windows >7
- improves performance and 3D support
– VBoxVGA: Use this graphics controller for legacy guest OSes. This is the default graphics controller for Windows versions before Windows 7.
- (by inference) slightly lower performance but more compatibility with older OSes
- Old OS or Windows < 7
– VMSVGA: Use this graphics controller to emulate a VMware SVGA graphics device.
- Emulates a VMWare device
- probably best when your VM was originally set up on VMWare and has their tools installed
- may not be as fast as VBox cards because it's trying to be compatible with something else.
– None: Does not emulate a graphics adapter type.
- you don't want a graphics adapter
i.e. you want to run the machine headless or over SSH and don't need the overhead of it emulating graphics. - could improve performance as it removes a layer or emulation
add a comment |
But they do tell you quite explicitly when you should prefer them:
– VBoxSVGA: The default graphics controller for new VMs that use Linux or Windows 7 or later. This graphics controller improves performance and 3D support when compared to the legacy VBoxVGA option.
- Linux or Windows >7
- improves performance and 3D support
– VBoxVGA: Use this graphics controller for legacy guest OSes. This is the default graphics controller for Windows versions before Windows 7.
- (by inference) slightly lower performance but more compatibility with older OSes
- Old OS or Windows < 7
– VMSVGA: Use this graphics controller to emulate a VMware SVGA graphics device.
- Emulates a VMWare device
- probably best when your VM was originally set up on VMWare and has their tools installed
- may not be as fast as VBox cards because it's trying to be compatible with something else.
– None: Does not emulate a graphics adapter type.
- you don't want a graphics adapter
i.e. you want to run the machine headless or over SSH and don't need the overhead of it emulating graphics. - could improve performance as it removes a layer or emulation
add a comment |
But they do tell you quite explicitly when you should prefer them:
– VBoxSVGA: The default graphics controller for new VMs that use Linux or Windows 7 or later. This graphics controller improves performance and 3D support when compared to the legacy VBoxVGA option.
- Linux or Windows >7
- improves performance and 3D support
– VBoxVGA: Use this graphics controller for legacy guest OSes. This is the default graphics controller for Windows versions before Windows 7.
- (by inference) slightly lower performance but more compatibility with older OSes
- Old OS or Windows < 7
– VMSVGA: Use this graphics controller to emulate a VMware SVGA graphics device.
- Emulates a VMWare device
- probably best when your VM was originally set up on VMWare and has their tools installed
- may not be as fast as VBox cards because it's trying to be compatible with something else.
– None: Does not emulate a graphics adapter type.
- you don't want a graphics adapter
i.e. you want to run the machine headless or over SSH and don't need the overhead of it emulating graphics. - could improve performance as it removes a layer or emulation
But they do tell you quite explicitly when you should prefer them:
– VBoxSVGA: The default graphics controller for new VMs that use Linux or Windows 7 or later. This graphics controller improves performance and 3D support when compared to the legacy VBoxVGA option.
- Linux or Windows >7
- improves performance and 3D support
– VBoxVGA: Use this graphics controller for legacy guest OSes. This is the default graphics controller for Windows versions before Windows 7.
- (by inference) slightly lower performance but more compatibility with older OSes
- Old OS or Windows < 7
– VMSVGA: Use this graphics controller to emulate a VMware SVGA graphics device.
- Emulates a VMWare device
- probably best when your VM was originally set up on VMWare and has their tools installed
- may not be as fast as VBox cards because it's trying to be compatible with something else.
– None: Does not emulate a graphics adapter type.
- you don't want a graphics adapter
i.e. you want to run the machine headless or over SSH and don't need the overhead of it emulating graphics. - could improve performance as it removes a layer or emulation
answered 1 hour ago
Mokubai♦Mokubai
57.2k16135154
57.2k16135154
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- 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%2fsuperuser.com%2fquestions%2f1403123%2fwhat-are-differences-between-vboxvga-vmsvga-and-vboxsvga-in-virtualbox%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