No drivers need to be installed on the proxmox, from now called host.
Find GIDs of video and render group on host:
cat /etc/group | grep video
cat /etc/group | grep render
public class CustomFragmentsPresenter : MvxFragmentsPresenter | |
{ | |
public interface IMvxFragmentHostEx : IMvxFragmentHost | |
{ | |
void Close(IMvxViewModel viewModel); | |
void ChangePresentation (MvxPresentationHint hint); | |
} | |
private IMvxNavigationSerializer _serializer; |
using Microsoft.Extensions.Configuration; | |
using Org.BouncyCastle.Crypto; | |
using Org.BouncyCastle.Crypto.Parameters; | |
using Org.BouncyCastle.OpenSsl; | |
using Org.BouncyCastle.Security; | |
using System.IO; | |
using System.Security.Cryptography.X509Certificates; | |
using System.Text; | |
namespace PostgreEFCore |
FROM mcr.microsoft.com/dotnet/core/aspnet:2.2 AS base | |
WORKDIR /app | |
EXPOSE 80 | |
# DEBUG | |
FROM mcr.microsoft.com/dotnet/core/sdk:2.2 AS debug | |
WORKDIR /app |
#!/bin/bash | |
sudo apt install build-essential cmake cmake-data debhelper dbus google-mock \ | |
libboost-dev libboost-filesystem-dev libboost-log-dev libboost-iostreams-dev \ | |
libboost-program-options-dev libboost-system-dev libboost-test-dev \ | |
libboost-thread-dev libcap-dev libexpat1-dev libsystemd-dev libegl1-mesa-dev \ | |
libgles2-mesa-dev libglm-dev libgtest-dev liblxc1 \ | |
libproperties-cpp-dev libprotobuf-dev libsdl2-dev libsdl2-image-dev lxc-dev \ | |
pkg-config protobuf-compiler python3-minimal | |
// ==UserScript== | |
// @name noVNC Paste for Proxmox | |
// @namespace http://tampermonkey.net/ | |
// @version 0.2a | |
// @description Pastes text into a noVNC window (for use with Proxmox specifically) | |
// @author Chester Enright | |
// @match https://* | |
// @include /^.*novnc.*/ | |
// @require http://code.jquery.com/jquery-3.3.1.min.js | |
// @grant none |
I ran into the battle of running all of my VMs and the host node under a single public IP address. Luckily, the host is just pure Debian, and ships with iptables. | |
What needs to be done is essentially to run all the VMs on a private internal network. Outbound internet access is done via NAT. Inbound access is via port forwarding. | |
Network configuration | |
Here’s how it’s done: | |
Create a virtual interface that serves as the gateway for your VMs: |
1. Add a virtual serial port to the VM using PVE Web GUI and restart the VM | |
2. Enable and start the virtual serial port on VM, change tty number as needed (Reference: https://askubuntu.com/a/621209/838946) | |
$ sudo systemctl enable [email protected] | |
$ sudo systemctl start [email protected] | |
3. Done! You can now select xterm.js in the PVE Web GUI |