Page locked

This page is currently locked for editing by another user. You have to wait until this user finishes editing or the lock expires.

Currently locked by: 216.73.216.182
Lock expires at: 2025/11/04 01:10 (15 min)

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.

====== Creating a Proxmox VM without a Template ======

disk
disk default 32 gb, discard on, <hostname>fs storage

cpu
default 4 CPU for SoCS, 2 for Student, or another number
choose host

mem
balooning on

net
bridging with firewall on
vmbr0 for all VMs
vmbr1 for VMs with SoCS server backend network
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