Configuring Ubuntu 18.04 LTS for remote GUI

There is a chance that you won't be able to enable Screen Sharing in the system settings. When attempting to enable, I saw the list of networks for sharing as "No Networks Selected for Sharing". You should see something like Wired Connection 1 or something like that.

I fixed this issue by going to /etc/netplan/, and overwriting the auto-generated file with the following:

network:
 version: 2
 renderer: NetworkManager

After you save this file, reboot the system. You should be able to see Wired Connection as a network option when enabling Screen Sharing now.

MSR on Linux

Before trying to access MSR's, make sure to load the MSR driver.
Run > modprobe msr on the command line to load the driver.

First steps in configuring linux server for remote access.

When setting up a new Linux server (in a corporate network) for remote debugging/ssh/whatever, you'll first need to install openssh-server if it isn't installed already. To use apt-get, ensure you have a proxy set up. It is likely you'll need to modify/create /etc/apt/apt.conf, and add the following line to it.

Acquire::http::Proxy "<your-proxy-address-here>:<port>"

After doing this, you should be able to use apt to update and install the latest openssh-server package.

Error when scanning ACPI table DMAR

Error when scanning for DMAR table on certain Linux flavors. Highly likely that the BIOS has not reported this table. Check the listing in /sys/firmware/acpi/tables to verify if table DMAR is there or not. If it's not there, the BIOS was probably not configured to report this table. Make sure VT-D is enabled in the BIOS, then reboot the server.

Compiled .py files (.pyc) cautions

Running compiled python scripts (.pyc files) could cause issues if the python version that compiled the script is different from the python version running the script.

Python version X compiles test.py into test.pyc.
Python version Y runs test.pyc.

This could cause issues if X and Y are different.

RHEL TCP/IP Enable

By default, Redhat will have TCP/IP connections blocked. I used the following commands to open some ports for TCP/IP connections.

 > firewall-cmd --zone=dmz --add-port=1861/tcp --permanent 

Repeat this command with [public,home] in the <zone> option. There is a chance that a different default zone is being used. Check firewalld.conf to see which zone is default, and make sure to enable it for that.

The port number is whatever port you want to have open for connections, and --permanent will make this change... permanent. Leave this option out if you only want a temporary connection for testing. You'll need to run > firewall-cmd --reload to have these changes take effect.