Once you have removed ' xserver-xorg-video-vmware” and rebooted or restarted lightdm, all should be ok. Note, it might be possible to mount the *.vmdk virtual disk containing the Pixel desktop VM to the host and modify the relevant files to allow SSH access.įor SSH access you can get the IP address of the booted but unavailable VM by viewing your routers DHCP table. Once back on the x86 Atom laptop, I booted the VM and logged in via SSH to carry out the investigation & remediation even though I could not log in via the GUI or CLI. However, as the VM worked on another hypervisor (the 12.5.x version) – I switched back to the VM on that machine, enabled SSH and copied the VM to the x86 Atom machine. Now, if your VM is not allowing you CLI or desktop access, then it’s a bit tricky to carry out these commands. … then restart the desktop manager thingy, lightdm:

Sudo apt-get remove xserver-xorg-video-vmware The workaround is to remove ' xserver-xorg-video-vmware”. Modifying the VM to boot to the CLI didn’t work – the same issue was exhibited. In some circumstances the VM machine “window” repeatedly resizes larger, then smaller. On booting the VM on the Atom x86 latop, the guest OS “finishes” the boot process and then displays a black screen. This laptop was running VMWare Player 3.x (as it had no hardware virt support – V3.x was the last to run on hardware which did not support hardware assisted virtualisation). This VM was then transferred to a Intel Atom based x86 laptop. This was installed on a VMWare Player 12.5.x hypervisor with 32 bit flag set in the VM config file so as to install for x86 architecture (the host was a 圆4 bit machine).Īll was fine and dandy – the Guest OS booted and worked fine. Version: Raspberry Pi desktop/PIXEL-rpd-x86-stretch

This is not a request for help as such, more of a fudged workaround. Workaround for: “ After install Pi Desktop for PC, only black/blank screen is available”.

Virtualbox black screen on boot