anomixer

#!/bin/bash
# Removes old revisions of snaps
# CLOSE ALL SNAPS BEFORE RUNNING THIS
set -eu

LANG=en_US.UTF-8 snap list --all | awk '/disabled/{print $1, $3}' |
    while read snapname revision; do
        snap remove "$snapname" --revision="$revision"
    done

anomixer

#!/usr/bin/env bash

set -e

sudo -v

sudo apt-get update
sudo apt-get dist-upgrade -y
sudo apt-get autoremove -y

anomixer

#!/usr/bin/env bash

set -e

cd ~

sudo -v

sudo apt-get -y install nvidia-prime vim git mesa-utils net-tools \
gnupg2 software-properties-common apt-transport-https gpg wget \

anomixer

#!/usr/bin/env bash

set -e

cd ~

sudo -v

# Make sure system is in a good, updated, clean, state.
sudo apt-get -y update

anomixer

#!/usr/bin/env bash

set -e

sudo -v

sudo apt install -y make git g++ nasm

git clone https://github.com/cisco/openh264.git ~/openh264
cd ~/openh264

anomixer

#!/usr/bin/env bash

set -e

sudo -v

sudo apt-get update
sudo apt-get dist-upgrade -y
sudo apt-get autoremove -y

anomixer

#!/bin/bash
# Install Latest XRDP with XORGXRDP and GFX

BUILD_DIR=/tmp/xrdpbuild

# Prepare Build Directory
rm -f -r $BUILD_DIR
mkdir -p $BUILD_DIR

# Install Dependencies - Dev

anomixer

GSOC 2017 | Virgl Windows Driver

Project links

The project is split into several parts:

• The kernel driver, with simple 3D command forwarding and 3D resource allocation
• The userland driver, in fact the OpenGL backend
• The reference, explaining virtio-gpu commands

https://github.com/Keenuts/virtio-gpu-win-icd \

anomixer

Enable & Using vGPU Passthrough

This gist is almost entirely not unlike Derek Seaman's awesome blog:

Proxmox VE 8: Windows 11 vGPU (VT-d) Passthrough with Intel Alder Lake

As such please refer to that for pictures, here i will capture the command lines I used as i sequence the commands a little differently so it makes more logic to me.

This gists assumes you are not running ZFS and are not passing any other PCIE devices (as both of these can require addtional steps - see Derek's blog for more info)

This gist assumes you are not running proxmox in UEFI Secure boot - if you are please refer entirely to dereks blog.

anomixer

# This script will manually rip out all VMware Tools registry entries and files for Windows 2008-2019
# Tested for 2019, 2016, and probably works on 2012 R2 after the 2016 fixes.

# This function pulls out the common ID used for most of the VMware registry entries along with the ID
# associated with the MSI for VMware Tools.
function Get-VMwareToolsInstallerID {
    foreach ($item in $(Get-ChildItem Registry::HKEY_CLASSES_ROOT\Installer\Products)) {
        If ($item.GetValue('ProductName') -eq 'VMware Tools') {
            return @{
                reg_id = $item.PSChildName;