Arch Linux

MikMe

Member

Registered: 2018-12-16

Posts: 4

Arch as VMWare guest

I am completely new to Arch Linux. I manages to install Arch in an VMWare virtual-machine successfully.

I rad https://wiki.archlinux.org/index.php/VM … as_a_guest, but could not find an answer to my question.

I have installed mesa, mesa-demos (for glxinfo) and xorg, (gtkmm, gtkmm3 for the copy and paste)) and xf86-video-vmware and open-vm-tools.

But for some reason linux just loads the kms driver vmwgfx and not the gallium driver.

glxinfo | grep OpenGL:

OpenGL vendor string: VMware, Inc.
OpenGL renderer string: SVGA3D; build: RELEASE;  LLVM;
OpenGL core profile version string: 3.3 (Core Profile) Mesa 18.3.1
OpenGL core profile shading language version string: 3.30
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 3.3 (Compatibility Profile) Mesa 18.3.1
OpenGL shading language version string: 3.30
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.0 Mesa 18.3.1
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00
OpenGL ES profile extensions:

I have a copy of my virtual-machine and I also tested not to install xf86-video-vmware. And I am getting the same glxinfo. So why do I have to install the vmware video driver if it is not loaded? And how can I activate the  xf86-video-vmware driver? I added vmwfgx on /etc/mkinitcpio.conf, could that be the reason? And finnaly if i quiet my Xorg session the grap/release input wont work anymore (I have to press CTRL+ALT (bevor startx it works automatically)) in the virtual-console, why is that?

Lone_Wolf

Administrator

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 15,538

Re: Arch as VMWare guest

I added vmwfgx on /etc/mkinitcpio.conf, could that be the reason?

Seems likely, why don't you remove it from mkinitcpio.conf modules line and check ?

post xorg log .

---

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky