Differences

This shows you the differences between two versions of the page.

--- sysadmin:procedures:proxmox:newvm [2018/02/22 19:13] – kjohns23
+++ sysadmin:procedures:proxmox:newvm [Unknown date] (current) – removed - external edit (Unknown date) 127.0.0.1
@@ Line 1: / Line 1: @@
-====== Creating a Proxmox VM without a Template ======
-disk
-disk default 32 gb, discard on, <hostname>fs storage
-cpu
-enable numa for dual+ socket systems
-choose skylake-client type, or other option depending on your architecture name
-mem
-balooning on
-net
-bridging with firewall on
-if migrating, reuse the mac addr of the existing machine. Note that mac's must be distinct on a lan, so you won't be able to have both running at once if you do this.
-====== Creating a Proxmox VM with a Template ======
-====== Migrating from KVM ======
-copy /var/lib/libvirt/image/ qcow2 file to proxmox host (check the timestamp or config to make sure you get the active disk for the vm you are migrating)
-to import the disk run: qm importdisk <VMID> <disk>.qcow2 <proxmox storage pool name> This creates a second disk for your target vm.
-THERE BE DRAGONS:
-  *
-  * run **zfs list** to get the name of the existing disk for the new vm
-  * run **zfs destroy <NAME>** this is irreversible so be careful
-  * run **zfs rename <disk 2 name> <disk 1 name>**
-  * open //etc/pve/local/qemu-server/<disk num.conf>// and remove 'unused' line for the 2nd disk
-You can now start the new target vm and confirm that the services still function
-final steps:
-  * Update the disk device(s) in fstab to use sd*
-  * Update the nagios disk check in ///etc/nagios/nrpe.cfg// to reference the new sd* device