Search results

I have a /29 so basically I would like to assign dedicated/static IPs to the KVMs or Containers I will be creating. How can I achieve this?

So having the eno* interfaces with their IP addresses is pointless? Since the IP will be assigned manually when creating a container? What about cloud-init?

Got it up and running, finally. Tested creating a container and that seems to work as well. Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier...

Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: C3C843DA-C836-4124-B07C-E067B6160FBE Device Start End Sectors Size Type /dev/sda1 34...

Yeah figured I'd rebuild using the ISO now.

Very new to this but I'm trying.

Yeah that would be best but I'm currently just utilizing this unused dedicated server which only has 1 disk :|

Would they need to be pre-partitioned or can it be done all in Proxmox?

I have installed Proxmox on top of Debian Buster but how do I manage partitions since I only have 1 disk. Proxmox doesn't seem to see those other partitions which I have created, supposedly for ISO and VM data. Device Boot Start End Sectors Size Id Type /dev/sda1 *...

The hardware is a E3-1270 v3 with 32GB memory and a single 480GB SSD disk. This is for R&D/test purposes so it can go full on for performance.

I have this now installed on a single disk (480GB). Would I need to re-partition this single disk and split to 2 or more drives for ISO and VM/Containers?

I am planning on setting up Proxmox on a server with 2 x 480 GB SSD. Server will be used for test/dev purposes and expected to be deploying 3-4 VMs on it. This is new to me so any recommendations on how I should be partitioning this and then build it? Should I install Proxmox directly from...