Running Manjaro in VMware

Hi, I’m trying to run manjaro-xfce in VMware workstation pro using a laptop with external monitor. The display issues occur after trying to access the external monitor. First, I’m not able to cycle the monitors to gain access. Thus, manjaro will either switch screens or workspaces but stay on the monitor. Second, manjaro is not scaled properly and displays a black screen after trying an multi-screen setup therefore, only fullscreen works at this point. I have tried changing the kernel, restarting display manager, minimal installation. I’m hoping that someone will help me resolve these issues. I have used the xfce versions of linux mint and kali linux without issue.

hello @manArch

please post the output of the 2 following commands to give us an overview

inxi --admin --verbosity=7 --filter --no-host --width

echo $XDG_SESSION_TYPE && glxinfo | grep server

x11 or wayland ? my personal experience with kvm/qemu shows that wayland isn’t that compatible with virtualization due the reason that a lot of virtualization still rely on x11 and i expect that vmware isn’t different.

[manjaro@manjaro ~]$ inxi --admin --verbosity=7 --filter --no-host --width
System:
  Kernel: 6.9.0-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-x86_64 lang=en_US keytable=us tz=UTC
    misobasedir=manjaro misolabel=MANJARO_XFCEM_240 quiet
    systemd.show_status=1 splash apparmor=1 security=apparmor driver=free
    nouveau.modeset=1 i915.modeset=1 radeon.modeset=1
  Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 wm: xfwm4 v: 4.18.0
    with: xfce4-panel tools: xfce4-screensaver vt: 7 dm: LightDM v: 1.32.0
    Distro: Manjaro base: Arch Linux
Machine:
  Type: Vmware System: VMware product: VMware20,1 v: N/A
    serial: <superuser required> Chassis: No Enclosure type: 1
    serial: <superuser required>
  Mobo: Intel model: 440BX Desktop Reference Platform
    serial: <superuser required> uuid: <superuser required> UEFI: VMware
    v: VMW201.00V.21805430.B64.2305221830 date: 05/22/2023
Memory:
  System RAM: total: 4 GiB available: 3.79 GiB used: 1.1 GiB (28.9%)
  Message: For most reliable report, use superuser + dmidecode.
  Array-1: capacity: 65 GiB note: check slots: 31 note: check modules: 1
    EC: None max-module-size: N/A
  Device-1: RAM slot #0 type: DRAM detail: synchronous size: 4 GiB
    speed: 4800 MT/s volts: note: check curr: 1 min: 1 max: 1 width (bits):
    data: 64 total: 64 manufacturer: VMware Virtual RAM part-no: VMW-4096MB
    serial: <filter>
  Device-2: RAM slot #1 type: no module installed
  Device-3: RAM slot #2 type: no module installed
  Device-4: RAM slot #3 type: no module installed
  Device-5: RAM slot #4 type: no module installed
  Device-6: RAM slot #5 type: no module installed
  Device-7: RAM slot #6 type: no module installed
  Device-8: RAM slot #7 type: no module installed
  Device-9: RAM slot #8 type: no module installed
  Device-10: RAM slot #9 type: no module installed
  Device-11: RAM slot #10 type: no module installed
  Device-12: RAM slot #11 type: no module installed
  Device-13: RAM slot #12 type: no module installed
  Device-14: RAM slot #13 type: no module installed
  Device-15: RAM slot #14 type: no module installed
  Device-16: RAM slot #15 type: no module installed
  Device-17: RAM slot #16 type: no module installed
  Device-18: RAM slot #17 type: no module installed
  Device-19: RAM slot #18 type: no module installed
  Device-20: RAM slot #19 type: no module installed
  Device-21: RAM slot #20 type: no module installed
  Device-22: RAM slot #21 type: no module installed
  Device-23: RAM slot #22 type: no module installed
  Device-24: RAM slot #23 type: no module installed
  Device-25: RAM slot #24 type: no module installed
  Device-26: RAM slot #25 type: no module installed
  Device-27: RAM slot #26 type: no module installed
  Device-28: RAM slot #27 type: no module installed
  Device-29: RAM slot #28 type: no module installed
  Device-30: RAM slot #29 type: no module installed
  Device-31: RAM slot #30 type: no module installed
CPU:
  Info: model: Intel Core i5-8250U bits: 64 type: MCP arch: Coffee Lake
    gen: core 8 level: v3 note: check built: 2017 process: Intel 14nm family: 6
    model-id: 0x8E (142) stepping: 0xA (10) microcode: 0xF0
  Topology: cpus: 1x cores: 2 smt: <unsupported> cache: L1: 128 KiB
    desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB L3: 6 MiB
    desc: 1x6 MiB
  Speed (MHz): avg: 1800 min/max: N/A cores: 1: 1800 2: 1800 bogomips: 7202
  Flags: 3dnowprefetch abm adx aes apic arat arch_capabilities arch_perfmon
    avx avx2 bmi1 bmi2 clflush clflushopt cmov constant_tsc cpuid cx16 cx8 de
    f16c flush_l1d fma fpu fsgsbase fxsr ht hypervisor ibpb ibrs invpcid
    lahf_lm lm mca mce md_clear mmx movbe msr mtrr nonstop_tsc nopl nx pae pat
    pcid pclmulqdq pdpe1gb pge pni popcnt pse pse36 pti rdrand rdseed rdtscp
    sep smap smep ss ssbd sse sse2 sse4_1 sse4_2 ssse3 stibp syscall tsc
    tsc_adjust tsc_deadline_timer tsc_known_freq tsc_reliable vme x2apic
    xgetbv1 xsave xsavec xsaveopt xsaves xtopology
  Vulnerabilities:
  Type: gather_data_sampling status: Unknown: Dependent on hypervisor status
  Type: itlb_multihit status: KVM: VMX unsupported
  Type: l1tf mitigation: PTE Inversion
  Type: mds mitigation: Clear CPU buffers; SMT Host state unknown
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT Host state unknown
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed mitigation: IBRS
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: IBRS; IBPB: conditional; STIBP: disabled; RSB
    filling; PBRSB-eIBRS: Not affected; BHI: SW loop, KVM: SW loop
  Type: srbds status: Unknown: Dependent on hypervisor status
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: VMware SVGA II Adapter driver: vmwgfx v: 2.20.0.0 ports:
    active: Virtual-1 empty: Virtual-2, Virtual-3, Virtual-4, Virtual-5,
    Virtual-6, Virtual-7, Virtual-8 bus-ID: 00:0f.0 chip-ID: 15ad:0405
    class-ID: 0300
  Display: x11 server: X.org v: 1.21.1.13 compositor: xfwm4 v: 4.18.0 driver:
    X: loaded: vmware unloaded: modesetting alternate: fbdev,vesa dri: vmwgfx
    gpu: vmwgfx display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1664x874 s-size: <missing: xdpyinfo>
  Monitor-1: Virtual-1 mapped: Virtual1 res: 1664x874 hz: 60 size: N/A modes:
    max: 1664x874 min: 640x480
  API: EGL v: 1.5 platforms: device: 0 egl: 1.4 drv: vmwgfx device: 1
    drv: swrast gbm: egl: 1.4 drv: vmwgfx surfaceless: egl: 1.4 drv: vmwgfx x11:
    egl: 1.4 drv: vmwgfx inactive: wayland
  API: OpenGL v: 4.5 compat-v: 4.3 vendor: vmware mesa v: 24.0.6-manjaro1.1
    glx-v: 1.4 direct-render: yes renderer: SVGA3D; build: RELEASE; LLVM;
    device-ID: 15ad:0405 memory: 1000 KiB unified: no
Audio:
  Device-1: Ensoniq ES1371/ES1373 / Creative Labs CT2518 driver: snd_ens1371
    v: kernel bus-ID: 02:02.0 chip-ID: 1274:1371 class-ID: 0401
  API: ALSA v: k6.9.0-1-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: JACK v: 1.9.22 status: off tools: N/A
  Server-2: PipeWire v: 1.0.5 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel 82371AB/EB/MB PIIX4 ACPI vendor: VMware Virtual Machine
    type: network bridge driver: N/A modules: i2c_piix4 port: N/A bus-ID: 00:07.3
    chip-ID: 8086:7113 class-ID: 0680
  Device-2: Intel 82545EM Gigabit Ethernet vendor: VMware PRO/1000 MT Single
    Port driver: e1000 v: kernel port: 1040 bus-ID: 02:01.0 chip-ID: 8086:100f
    class-ID: 0200
  IF: ens33 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IP v4: <filter> type: dynamic scope: global broadcast: <filter>
  IP v6: <filter> type: noprefixroute scope: link
  Info: services: NetworkManager,systemd-timesyncd
  WAN IP: <filter>
Bluetooth:
  Device-1: VMware Virtual Bluetooth Adapter driver: btusb v: 0.8 type: USB
    rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-2.1:4 chip-ID: 0e0f:0008
    class-ID: e001 serial: <filter>
  Report: rfkill ID: hci0 rfk-id: 0 state: down bt-service: enabled,running
    rfk-block: hardware: no software: yes address: see --recommends
Logical:
  Message: No logical block device data found.
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 60 GiB used: 0 KiB (0.0%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: VMware model: Virtual SATA Hard Drive
    size: 60 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    tech: N/A serial: <filter> fw-rev: 0001 scheme: GPT
  Optical-1: /dev/sr0 vendor: NECVMWar model: VMware SATA CD01 rev: 1.00
    dev-links: cdrom
  Features: speed: 1 multisession: yes audio: yes dvd: yes
    rw: cd-r,cd-rw,dvd-r,dvd-ram state: running
Partition:
  Message: No partition data found.
Swap:
  Alert: No swap data was found.
Unmounted:
  ID-1: /dev/sda1 maj-min: 8:1 size: 300 MiB fs: vfat label: N/A
    uuid: E5AF-2704
  ID-2: /dev/sda2 maj-min: 8:2 size: 59.7 GiB fs: ext4 label: N/A
    uuid: 5a1eb5be-3934-46cb-a4be-bd24667aec6c
USB:
  Hub-1: 1-0:1 info: full speed or root hub ports: 2 rev: 1.1
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 chip-ID: 1d6b:0001
    class-ID: 0900
  Device-1: 1-1:2 info: VMware Virtual Mouse type: mouse
    driver: hid-generic,usbhid interfaces: 1 rev: 1.1 speed: 12 Mb/s (1.4 MiB/s)
    lanes: 1 mode: 1.1 chip-ID: 0e0f:0003 class-ID: 0301
  Hub-2: 1-2:3 info: VMware Virtual USB Hub ports: 7 rev: 1.1
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 chip-ID: 0e0f:0002
    class-ID: 0900
  Device-1: 1-2.1:4 info: VMware Virtual Bluetooth Adapter type: bluetooth
    driver: btusb interfaces: 2 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s) lanes: 1
    mode: 1.1 chip-ID: 0e0f:0008 class-ID: e001 serial: <filter>
  Hub-3: 2-0:1 info: full speed or root hub ports: 6 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
Sensors:
  Src: lm-sensors+/sys Message: No sensor data found using /sys/class/hwmon or
    lm-sensors.
Info:
  Processes: 301 Power: uptime: 2m states: freeze,standby,mem,disk
    suspend: s2idle avail: shallow wakeups: 0 hibernate: platform avail: shutdown,
    reboot, suspend, test_resume image: 1.47 GiB
    services: upowerd,xfce4-power-manager Init: systemd v: 255
    default: graphical tool: systemctl
  Packages: pm: pacman pkgs: 1028 libs: 288 tools: pamac Compilers: N/A
    Shell: Bash v: 5.2.26 running-in: xfce4-terminal inxi: 3.3.34

x11
server glx vendor string: SGI
server glx version string: 1.4
server glx extensions:

Mod edit: Added the post formatting to tidy the thread, since the OP has seemingly disappeared into the sunset.

Hi @manArch

Please edit your previous post to make it more readable. Specifically, place all of the command output between three ``` (backtick) characters before and after the content using the ` key usually found underneath the Esc key (on a full keyboard).

When posting any command output use the </> button to create these backticks more easily. This places the rendered text in a scrollable text box suitable for code.

I hope this is helpful. Cheers.

Arch based distributions are unsupported by VMware and Manjaro does not make any effort to support running on vmware as a guest.

The display and monitor is controlled by vmware.

If you have issues with how the display and monitor is passed on to the guest you should use your vmware support channels.

I am using vmware workstation pro as well. I came to be that way a while ago because I had recurring network issues with my virtual Windows workstation - issues I simply could not work with.

Both kali and mint are supported by vmware - due to their origin - the assumption that so should Manjaro, is not valid as Arch is not supported by vmware - propably caused by the high kernel refresh rate - making it impossible for the vmware developers to keep a stable experience for their enterprise customers.

I have explored the multi monitor setup provided by vmware but I can make neither windows nor manjaro work with multiple monitors.

I have not bothered to investigate :man_shrugging: it is - I guess - just how it is.

The remainder of my life is too short to bother with finding a workaround.

well the screen is assigned as Virtual1-screen, that should be okay. i’m not aware about vmware but if i use kvm/qemu and try to work with physical-screens that are assigned as Virtual-screen then all the applications (i know and used) to control it had always the limitations that they can only work in 1920x1080 at maximum. trying to assign larger display-resolutions always failed.