Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | Last revisionBoth sides next revision |
| computing:proxmux [2023/12/24 04:44] – oemb1905 | computing:proxmux [2023/12/24 11:18] – oemb1905 |
|---|
| ------------------------------------------- | ------------------------------------------- |
| |
| Been testing proxmux on home back up server. The server is my old production SuperMicro, which is now used for offsite backups in the home office. I have two 6TB drives in a zfs mirror for vm spinning (no spare), and the other 6x 6TBs are in 3 two-way mirrors for actual production backups. I am using the Debian underbelly with the 3 two-way mirrors to run my normal rsnapshot version control scripts, etc., while I use one pool for testing proxmux functionality. So far everything is working fine, and it's fun to use. Until I am offering advanced business / small enterprise support though, there's not really a need for the tools. But/and, that's not the purpose - the purpose is testing for now for a later date. The first thing I tested was how to bring in an existing virtual machine. To do that, create a machine in the GUI with no OS, and a trivial small HD size. Make sure the other resources match what you need for the VM. Then, run these commands on the command line within the proxmux host: | Most important thing about proxmox is knowing how to get the VMs in and out of it. Let's start with getting them in. First, create an empty VM in the gui, then use the following command changing 500 to match your vmid. |
| |
| qm importdisk 500 hub.jonathanhaack.com.qcow2 <dataset> | qm importdisk 500 hub.jonathanhaack.com.qcow2 <dataset> |
