Virtual Server on IBM Cloud doesn't boot any more after install

parsec-cloud / Parsec-Cloud-Preparation-Tool

Launch Parsec enabled cloud computers via your own cloud provider account.

925 stars 168 forks source link

Virtual Server on IBM Cloud doesn't boot any more after install #30

Closed bn326160 closed 4 years ago

bn326160 commented 4 years ago

On IBM Cloud I was able to get the System partially working using a YouTube tutorial, but was stuck on 1280x1024 resolution, so started a new instance and gave this script a try.

On both Windows Server 2016, as well as Windows Server 2019 I have this issue after I ran the script for installation, drivers and autologin, the server is unreachable. It doesn't show up on Parsec, can't connect to it over VNC, can't RDP any more and can't even ping it. Rebooting it in the cloud console doesn't help either.

Any advice on how to approach this issue? Is there a firewall being installed or activated?

jamesstringerparsec commented 4 years ago

I have not used IBM's cloud platform nor run this script on it. I have no idea.

bn326160 commented 4 years ago

Investigated further today. The issue might be a combination of the Parsec GPU updater tool with the Auto-logon tool causing the system to go in boot-loop.

The Parsec GPU tool sets a startup script to change the GPU mode from TCC to WCCM using N(vidia)SMI on login and then reboot. This is unsuccessful, but still reboots. Retrying on every every login.

Re-imaging now and will retry your script, but install this Nvidia GRID driver instead of using the GPU tool.

jamesstringerparsec commented 4 years ago

You shouldn't install the Google cloud driver on an IBM machine. You should see if IBM provides a licensed driver, or install the default driver from the Nvidia support site.

Good luck