Arch Linux

zgR3Vr

Member

Registered: 2020-05-18

Posts: 26

[Solved] Windows VM graphics

Hello.

I have never installed Arch on a computer without a dedicated nvidia graphics card, and now I have some problems with a windows vm running inside Virtualbox.

If I install the virtualbox guest additions on the Windows VM, all the graphics fuck up. The process bar losses its color, and you can see the desktop background through it.
The Windows menu is barely functional, and I cannot see edge browser at all if I try to open that up.

Everything works fine before installing the guest additions, but if I don't have them installed, I cannot resize the window and so on.

I have tried to read through this part of the wiki, but haven't had any luck in finding where the enable_fbc=1 option should be set. The wiki doesn't lead me anywhere specific.
I have tried to look in the locations that are specified in earlier steps, but either the file doesn't exist, or the options isn't set.
It is not set in the kernel parameters, nor is it set in /etc/modprobe.d/i915.conf.

I don't know whether or not that option has anything to do with this, since it first fucks up after I install the guest addition.
But then again, I do not know if that option is specified anywhere else, so I am kinda stuck here.

Any help appreciated.

Last edited by zgR3Vr (2020-08-11 19:19:23)

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 25,372

Re: [Solved] Windows VM graphics

I doubt that enabling/disabling fbc will help you, but I'm unsure as to why you are unsure where you have to add that. The wiki contains both an example file (if the wiki talks about a file and it's contents, the usual thing you should do if that file isn't present, is to create it with the mentioned content) as well as links on how to specify that same option in your kernel parameters. It isn't going to be set if you do not consciously set it yourself (or rather it is set to a default value that varies by hardware and how safe the developer consider the option to be for the hardware).

For the actual problem, one thing you can often change here and should be the first thing you do look at is switch between the newer vmware based 3d renderer and the older VBoxSVGA in virtualbox's settings. One might work better than the other. Is VT-d enabled in your BIOS/UEFI ?

Last edited by V1del (2020-08-11 12:36:42)

d_fajardo

Member

Registered: 2017-07-28

Posts: 1,687

Re: [Solved] Windows VM graphics

You can try and test the different Graphics Controller for your VM in Virtualbox settings. Also while testing, disable 3D Acceleration.
And it's not clear, are you using nvidia in your host machine?
I wouldn't think the intel driver will make a difference but I could be wrong. Virtualbox doesn't support GPU passthrough and uses its own controller.

zgR3Vr

Member

Registered: 2020-05-18

Posts: 26

Re: [Solved] Windows VM graphics

I doubt that enabling/disabling fbc will help you, but I'm unsure as to why you are unsure where you have to add that. The wiki contains both an example file (if the wiki talks about a file and it's contents, the usual thing you should do if that file isn't present, is to create it with the mentioned content) as well as links on how to specify that same option in your kernel parameters. It isn't going to be set if you do not consciously set it yourself (or rather it is set to a default value that varies by hardware and how safe the developer consider the option to be for the hardware).

For the actual problem, one thing you can often change here and should be the first thing you do look at is switch between the newer vmware based 3d renderer and the older VBoxSVGA in virtualbox's settings. One might work better than the other. Is VT-d enabled in your BIOS/UEFI ?

You are absolutely right, I just didn't read it probably to begin with. Sorry about that.
I checked my BIOS, and VT-d was enabled. What fixed it was turning off 3d acceleration. I will try the different renders as well.

You can try and test the different Graphics Controller for your VM in Virtualbox settings. Also while testing, disable 3D Acceleration.
And it's not clear, are you using nvidia in your host machine?
I wouldn't think the intel driver will make a difference but I could be wrong. Virtualbox doesn't support GPU passthrough and uses its own controller.

Thank you! It worked after turning off 4d acceleration, will have to test the different renders too.