scyto

ProxMox Cluster - Soup-to-Nutz

aka what i did to get from nothing to done.

note: these are designed to be primarily a re-install guide for myself (writing things down helps me memorize the knowledge), as such don't take any of this on blind faith - some areas are well tested and the docs are very robust, some items, less so). YMMV

Purpose of Proxmox cluster project

Required Outomces of cluster project

memoryleak

#!/usr/bin/env bash
sudo hdiutil create -o /tmp/Monterey -size 16g -volname Monterey -layout SPUD -fs HFS+J
sudo hdiutil attach /tmp/Monterey.dmg -noverify -mountpoint /Volumes/Monterey
sudo /Applications/Install\ macOS\ Monterey.app/Contents/Resources/createinstallmedia --volume /Volumes/Monterey --nointeraction
hdiutil eject -force  /Volumes/Install\ macOS\ Monterey
hdiutil convert /tmp/Monterey.dmg -format UDTO -o ~/Downloads/Monterey
mv -v ~/Downloads/Monterey.cdr ~/Downloads/Monterey.iso
sudo rm -fv /tmp/Monterey.dmg

tomdaley92

Proxmox - SPICE client setup for MacOS

1. Install a working (and compiled) version of virt-viewer. You may view the homebrew package's upstream source on GitHub.

   brew tap jeffreywildman/homebrew-virt-manager
   brew install virt-viewer

2. Once that's installed should be able make a call remote-viewer with a pve-spice.vv file downloaded from proxmox web interface

jarek-przygodzki

WSL 2 Cisco AnyConnect Networking Workaround

Overview

WSL 2 uses a Hyper-V Virtual Network adapter. Network connectivity works without any issue when a VPN is not in use. However when a Cisco AnyConnect VPN session is established Firewall Rules and Routes are added which breaks connectivity within the WSL 2 VM. This issue is tracked WSL/issues/4277

Below outline steps to automatically configure the Interface metric on VPN connect and update DNS settings (/etc/resolv.conf) on connect/disconnect.

Manual Configuration

Set Interface Metrics

cneira

WARNING

These intructions might work, but they need a bit of attention. I've been reading through ipf and smf documentation and have found a few ways to improve this process. When I have time I'll add that information here, until then, be sure to look into the ipf settings if you're having issues with routing. Good luck!

Foreword

This is a modified version of sjorge's instructions for Single IP with NAT. Those instructions can be found here: https://docu.blackdot.be/snipets/solaris/smartos-nat

The primary difference is that this version does not rely on etherstubs for internal switching, but instead uses a vlan configuration. The benefits of this method over using etherstubs are:

1. Project Fifo (project-fifo.net) can create vms and zones with vlans, but does not currently have etherstub support.
2. Vlan switching is supposedly more efficient than creating an etherstub to handle switching. I have not tested this statement.

papertigers

This port of boringtun works on any illumos box that has the tuntap device. SmartOS comes with this device by deafult. You can install this device on OmniOS by running pkg install tuntap. Currently the userland daemon will drop as many privileges(5) as it can after setting up the tunnel etc. The daemon is also currently using epoll/signalfd unil I find time to wire up the event port interface.

Clone the following repo and checkout the illumos branch.

git clone git@github.com:papertigers/boringtun.git

znxDomain

Based on this: http://www.nathanbunn.com/NandUpgradeSteps/
using this: https://github.com/ihaveamac/ninfs
and using this: https://github.com/rajkosto/memloader

Using native MacOS tools + NinFS and memloader on the switch.

- Make Backup of 32G NAND
    Use Hekate
- Install 256G NAND
- Restore boot0/1 backups with hekate

ClaesBas

How to install OpenBSD with bhyve-vm on SmartOS (20190424):

tl;dr:
  Create a bhyve vm with an empty disk, where you put an install image with dd afterwards.
  "bhyve_extra_opts": "-w"
  "bootrom": "uefi"
  "vcpus": 1 (is needed too, some say..)
  Change to serial console when booting the install image

Do it like this:

TyrfingMjolnir

A minor list of how to create and boot a Bhyve-zone in Joyent SmartOS

cd /opt/local/artifacts/
vim zonemanifestBhyveFreeBSD.json
vmadm create < zonemanifestBhyveFreeBSD.json
curl -kLo /zones/UUID/root/FreeBSD-12.0-RC3-amd64-bootonly.iso

The following line is for KVM, not BHYVE, hence obsoleted for non-legacy boot options

cd /zones/<<UUID>>/root/

mgerdts

This shows how to upgrade cloud-init from the one found in the early CentOS 6 bhyve images and create a new image from that.

Create a source instance

First, we will install an instance using image 11891f44-a374-11e8-9c35-c7bfcc724881.

The vmadm payload

{