This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
computing:proxmux [2023/06/18 18:43] – oemb1905 | computing:proxmux [2023/12/23 21:45] – oemb1905 | ||
---|---|---|---|
Line 19: | Line 19: | ||
vzdump < | vzdump < | ||
+ | vzdump < | ||
| | ||
- | This will create a VM in .vma format. | + | This will create a VM in .vma format. |
+ | |||
+ | vma extract / | ||
+ | |||
+ | Optionallly, you can use the python tool [[https:// | ||
python3 vma.py vzdump-qemu-101-2023_06_18-12_17_40.vma / | python3 vma.py vzdump-qemu-101-2023_06_18-12_17_40.vma / | ||
+ | |||
+ | In order to see where the virtual machine' | ||
+ | |||
+ | zfs list | ||
| | ||
- | You can also use vma extract as follows: | + | To delete one (be careful), |
+ | zfs destroy pool/ | ||
+ | |||
+ | I've migrated my Windows VM here for testing to avoid cumbersome EFI/TPM setup on virt-manager. Here's a page from ProxMux wiki on best practices for [[https:// | ||
+ | |||
+ | vms/ | ||
+ | vms/ | ||
+ | vms/ | ||
| | ||
+ | Be careful not to delete those thinking wrongly that they are extraneous - those are obviously required for booting, but it might not be clear upon first look. Also, I chose to install those on the '' | ||
+ | |||
+ | To verify sockets and cores | ||
+ | |||
+ | grep " | ||
+ | | ||
+ | Had to switch to postfix with my relay, so used satellite and: | ||
+ | |||
+ | [relay.haacksnetworking.org]: | ||
+ | |||
+ | Created bridge on pve instance with this recipe: | ||
+ | |||
+ | source / | ||
+ | auto lo | ||
+ | iface lo inet loopback | ||
+ | iface enp0s31f6 inet manual | ||
+ | auto vmbr0 | ||
+ | iface vmbr0 inet static | ||
+ | address 10.18.18.2/ | ||
+ | gateway 10.18.18.1 | ||
+ | bridge-ports enp0s31f6 | ||
+ | bridge-stp off | ||
+ | bridge-fd 0 | ||
+ | | ||
+ | Make sure the PVE instance, which is also our reverse proxy has the FQDN set up in ''/ | ||
+ | |||
+ | sudo nano /etc/hosts | ||
+ | < | ||
+ | sudo nano / | ||
+ | < | ||
+ | |||
+ | Set up configurations for each website on nginx as follows: | ||
+ | |||
+ | sudo apt install nginx | ||
+ | sudo nano / | ||
+ | | ||
+ | Enter this in the file | ||
+ | |||
+ | server { | ||
+ | server_name | ||
+ | location / { | ||
+ | proxy_pass http:// | ||
+ | # | ||
+ | } | ||
+ | } | ||
+ | |||
+ | Repeat this as needed for each VM within PVE. Once this is done, set up TLS on the PVE/RP instance as follows: | ||
+ | |||
+ | sudo apt install certbot letsencrypt python3-certbot-nginx | ||
+ | sudo certbot --authenticator standalone --installer nginx -d example.domain.com --pre-hook " | ||
+ | |||
+ | | ||
+ | |||
- | Dreamhost - prepare haacknet for home router. | ||
- | --- // | + | --- // |