Create Virtual Machine from a template - Revision history

Sailor: /* Creating a New Template */

2025-03-13T09:05:10Z

Creating a New Template

← Older revision		Revision as of 09:05, 13 March 2025
Line 9:		Line 9:
	* LDT24.o4 is Linux Desktop version 24.02		* LDT24.o4 is Linux Desktop version 24.02
	* W11P is Microsoft Windows 11 Pro		* W11P is Microsoft Windows 11 Pro
	Run through the installation of the the OS and configure anything that may be required ~~some~~ things will be required on every Linux like the qemu agent. other things like setting the max auth tries on SSH might be good setting up the additional user photoup and photoshare are other things that may save some time in the future.		Run through the installation of the the OS and configure anything that may be required. When everything has been added and configured shutdown the VM and convert to template.

			====Linux Adfditional config ====

			Some things will be required on every Linux like the qemu agent. other things like setting the max auth tries on SSH might be good setting up the additional user photoup and photoshare are other things that may save some time in the future.
	sudo apt update		sudo apt update
	sudo apt install cloud-init		sudo apt install cloud-init
	sudo apt qemu-guest-agent		sudo apt qemu-guest-agent
			sudo apt upgrade

	sudu nano /etc/ssh/sshd_config		sudu nano /etc/ssh/sshd_config
Line 23:		Line 28:
	sudo useradd -u 4001 -g 5001 photoup		sudo useradd -u 4001 -g 5001 photoup
	sudo passwd photoup		sudo passwd photoup
			clearing the history would be good and any ssh keys and clesr package manage cache
			history -c
			sudo rm /etc/ssh/ssh_host_*
			sudo apt clean
			when all options have been configured and completed shutdown
			sudo shutdown -h now

	==Creating VMs on Command==		==Creating VMs on Command==

Sailor: /* Introduction */

2025-03-13T08:40:39Z

Introduction

← Older revision		Revision as of 08:40, 13 March 2025
Line 3:		Line 3:
	This is not a deep dive in to ansible or similar but a simple quick and dirty guide to creating a new VM from a template and configuring some of the networking with cloud init.		This is not a deep dive in to ansible or similar but a simple quick and dirty guide to creating a new VM from a template and configuring some of the networking with cloud init.

			==Creating a New Template==

			To create a template it would be better if the source VM did not have loads of junk on it, so we start from scratch and make a new VM. Set the host name to be something to mach the template eg LST24.04 is Linux Server V24.04 (as we use Ubuntu as a default only give distro if it is something different).
			* LST24.04 is Linux Server version 24.04
			* LDT24.o4 is Linux Desktop version 24.02
			* W11P is Microsoft Windows 11 Pro
			Run through the installation of the the OS and configure anything that may be required some things will be required on every Linux like the qemu agent. other things like setting the max auth tries on SSH might be good setting up the additional user photoup and photoshare are other things that may save some time in the future.
			sudo apt update
			sudo apt install cloud-init
			sudo apt qemu-guest-agent

			sudu nano /etc/ssh/sshd_config
			uncomment MaxAuthTries and change the 6 to 10. then save and exit
			sudo systemctl restart ssh
			sudo systemctl enable ssh
			sudo systemctl status ssh

			sudo groupadd -g 5001 photoshare
			sudo useradd -u 4001 -g 5001 photoup
			sudo passwd photoup

	==Creating VMs on Command==		==Creating VMs on Command==

Sailor: /* Other Properties */

2025-03-13T07:12:10Z

Other Properties

← Older revision		Revision as of 07:12, 13 March 2025
Line 54:		Line 54:
	=='''Other Properties'''==		=='''Other Properties'''==

	When creating a VM from a template in Proxmox, you can specify a wide range of parameters beyond just the IP address, hostname, and DNS. These parameters allow you to customize the VM's hardware, storage, networking, and other settings during the cloning process.		When creating a VM from a template in Proxmox, you can specify a wide range of parameters beyond just the IP address, hostname, and DNS. These parameters allow you to customize the VM's hardware, storage, networking, and other settings during the cloning process. These will override the templates setting so it is only neeassary to add the values that differ from the template

	Here's a comprehensive list of what you can specify using the `qm clone` command and related options:		Here's a comprehensive list of what you can specify using the `qm clone` command and related options:

Sailor: /* Example with Multiple Options */

2025-03-13T07:08:07Z

Example with Multiple Options

← Older revision		Revision as of 07:08, 13 March 2025
Line 109:		Line 109:
	* Tags (`--tags <tags>`): Adds tags to the VM.		* Tags (`--tags <tags>`): Adds tags to the VM.

	===Example with Multiple Options===		=====Example with Multiple Options=====

	<pre>		<pre>

Sailor: /* Other Options */

2025-03-13T07:07:55Z

Other Options

← Older revision		Revision as of 07:07, 13 March 2025
Line 103:		Line 103:
	* =DNS Name Server (`--nameserver <ns>`)=: DNS name server.		* =DNS Name Server (`--nameserver <ns>`)=: DNS name server.

	====Other Options====		=====Other Options=====

	* Start VM (`--start <0\|1>`): Starts the VM after creation.		* Start VM (`--start <0\|1>`): Starts the VM after creation.

Sailor: /* Cloud-Init Configuration */

2025-03-13T07:07:40Z

Cloud-Init Configuration

← Older revision		Revision as of 07:07, 13 March 2025
Line 95:		Line 95:
	* Search Domain (`--searchdomain <domain>`): DNS search domain.		* Search Domain (`--searchdomain <domain>`): DNS search domain.

	===Cloud-Init Configuration===		=====Cloud-Init Configuration=====

	* =User Data (`--ciuser <user>`)=: The username for Cloud-Init.		* =User Data (`--ciuser <user>`)=: The username for Cloud-Init.

Sailor: /* Network Configuration */

2025-03-13T07:07:25Z

Network Configuration

← Older revision		Revision as of 07:07, 13 March 2025
Line 85:		Line 85:
	* IO Thread (`--iothread <0\|1>`): Enables or disables I/O threading.		* IO Thread (`--iothread <0\|1>`): Enables or disables I/O threading.

	===Network Configuration===		=====Network Configuration=====

	* Network Bridge (`--net<n> bridge=<bridge>`): The network bridge to connect the VM to.		* Network Bridge (`--net<n> bridge=<bridge>`): The network bridge to connect the VM to.

Sailor: /* Hardware Configuration */

2025-03-13T07:07:06Z

Hardware Configuration

← Older revision		Revision as of 07:07, 13 March 2025
Line 75:		Line 75:
	* BIOS (`--bios <type>`): The BIOS type (e.g., `seabios`, `ovmf`).		* BIOS (`--bios <type>`): The BIOS type (e.g., `seabios`, `ovmf`).
	* VGA (`--vga <type>`): The VGA adapter type (e.g., `std`, `virtio`).		* VGA (`--vga <type>`): The VGA adapter type (e.g., `std`, `virtio`).
	* Keyboard Layout (`--keyboard <layout>`)~~'''~~: The keyboard layout (e.g., `en-us`, `de`).		* Keyboard Layout (`--keyboard <layout>`): The keyboard layout (e.g., `en-us`, `de`).

	=====Storage Configuration=====		=====Storage Configuration=====

Sailor: /* Storage Configuration */

2025-03-13T07:06:42Z

Storage Configuration

← Older revision		Revision as of 07:06, 13 March 2025
Line 77:		Line 77:
	* Keyboard Layout (`--keyboard <layout>`)''': The keyboard layout (e.g., `en-us`, `de`).		* Keyboard Layout (`--keyboard <layout>`)''': The keyboard layout (e.g., `en-us`, `de`).

	===Storage Configuration===		=====Storage Configuration=====

	* Disk Size (`--disk <disk>[,size=<n>]`): Size of the new virtual disk.		* Disk Size (`--disk <disk>[,size=<n>]`): Size of the new virtual disk.

Sailor: /* Hardware Configuration */

2025-03-13T07:06:25Z

Hardware Configuration

← Older revision		Revision as of 07:06, 13 March 2025
Line 65:		Line 65:
	* Full Clone (`--full`): Creates a full, independent copy of the VM's disk. (Default is linked clone)		* Full Clone (`--full`): Creates a full, independent copy of the VM's disk. (Default is linked clone)

	=== Hardware Configuration===		=====Hardware Configuration=====

	* CPU Cores (`--cores <n>`): The number of CPU cores assigned to the VM.		* CPU Cores (`--cores <n>`): The number of CPU cores assigned to the VM.