Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

is vGPU necessary for hardware 3D acceleration in VirtualBox #93

Open
user18081972 opened this issue Jul 13, 2024 · 7 comments
Open

is vGPU necessary for hardware 3D acceleration in VirtualBox #93

user18081972 opened this issue Jul 13, 2024 · 7 comments
Labels
question Further information is requested

Comments

@user18081972
Copy link

is vGPU necessary for hardware 3D acceleration in VirtualBox?
Also, do i need to check 'Enable 3D acceleration' for it to work? Because when i check it, it always reverts back to VBoxVGA.
image

I'm just trying to play some Win98 games with 3D acceleration with a RTX 3080.

@JHRobotics
Copy link
Owner

Hello,

yes you need it. Please switch guest type to Windows 10 (to use VBoxSVGA) or Linux (to use VMSVGA) - there isn't real difference, but VirtualBox switching automaticaly GPU type base on guest type regardless of the user's opinion.

@JHRobotics JHRobotics added the question Further information is requested label Jul 30, 2024
@user18081972
Copy link
Author

user18081972 commented Jul 31, 2024

Thanks.
OK well enabling vGPU on my 3080 feels a bit risky, because i cant figure out the exact model i have. I really really dont want to brick it.

No where did i find instructions telling me i need vGPU, or set the vm guest type to Windows 10 to use VBoxSVGA. Either im blind or naive, or adding those instructions somewhere would be nice.

@Torinde
Copy link
Contributor

Torinde commented Aug 27, 2024

I don't think you can brick something (hardware wise) on the host by doing anything in the Virtual machine.

Also, you don't need to know the exact type of host GPU - see the installation instructions.

@user18081972
Copy link
Author

I don't think you can brick something (hardware wise) on the host by doing anything in the Virtual machine.

My gpu doesnt have vGPU enabled by default. As far as i can figure out by researching online, to enable it, you need to patch the GPUs firmware, which i imagine can brick the GPU. The install instructions you link dont explain how to enable vGPU on a GPU.

@Torinde
Copy link
Contributor

Torinde commented Aug 28, 2024

I don't think SoftGPU uses "vGPU" (paravirtualization). Just follow the instructions and report back when/if there is a problem.

@user18081972
Copy link
Author

user18081972 commented Aug 28, 2024

I don't think SoftGPU uses "vGPU" (paravirtualization).

The project maintainer told me in the reply that it does need vGPU. #93 (comment)

@ride2x4
Copy link

ride2x4 commented Aug 28, 2024

He meant that you need to enable "Enable 3D Acceleration" checkbox.
In this case "vGPU" is a virtual software GPU emulated by VirtualBox within the guest environment. It can emulate VBoxVGA, VBoxSVGA or VMSVGA video cards (vGPUs), to put it simple.
No hardware modifications (including BIOS patching) are needed for vGPU to work. All you need is a more or less modern PC (assuming you have an RTX 3080- it is more than enough) with VirtualBox or other software hypervisor installed. All the actions you do, you do within the VirtualBox environment, and they don't affect either your host operating system or your real hardware. So there are no chances to brick anything.
The typical settings for Virtual Box include:

  1. A virtual machine created with "Windows 10 32bit" or "Other Linux 32bit" OS type selected.
  2. "Enable 3D Acceleration" checkbox enabled with VBoxSVGA or VMSVGA controller selected
  3. AC97 audio codec selected in the audio settings on the virtual machine.
  4. Then you install Windows 98 SE and SoftGPU according to the readme provided in the repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

4 participants