Search results

Thought I should update this thread. I upgraded from Proxmox VE 8 to 9 sometime around March 2026. No issues at all. I upgraded from Proxmox Backup Server (PBS) 3 to 4 too. No issues. Upgrading some of my Oracle DB servers from 19c to 26ai. cool, right? Maybe I should think about building...

Waiting on when I should upgrade from Proxmox VE 8.4.1 to release 9. Any horror stories on upgrading from 8 to 9? I figure I'll wait till middle of 2026 and by then it should be safe.

I forgot to update here on how it is going after fully migrating from ESXi to Proxmox. It is going great. I am extremely happy using proxmox. I've a huge 200 page word document covering EVERTHING from downloading it for first time, to setting up of storage, configuring, setting up ssl certs...

vSphere, ESXi, vCenter is gone forever. Yes! And I'm finally using the onboard m.2 NVMe connection on the X11DPI motherboard for the boot disk on this proxmox installation. I've named it bigdogprox. I'm told that I should have used "dawg" instead of "dog". That server used to be ESXi...

I've finally uploaded all of my guest VMs from the big-dog server (thats what I'm calling the X11DPI-NT with ESXi installed, 2xXeon 6130 16 core CPUs, 396GB RAM, direct attached 40.5 TB SSD storage) up to the miniprox server (that's what I'm calling my Supermicro Minitower with the Xeon D1541 8...

EDIT: RESOLVED! I issued this ipmitool command to lower threshold, such as: ipmitool -I lanplus -H <ipmi_ip_address> -U <ipmi_username> -P <ipmi_password> sensor thresh FAN5 lower 200 200 700 I was completely wrong about not being able to lower the threshold below 500, this worked! EDIT2...

It seems that Veeam Backup Jobs for Proxmox Guest VMs might not be quite ready for primetime. My Veeam Backup Jobs of my Proxmox Guest VMs - full backup of a 600GB guest VM might take 35 minutes total (vbk). An immediate subsequent backup would be an incremental and takes less than 3 minutes...

Veeam Backup and Replication v12.3 for backing up Proxmox Guest VMs I wasn't planning to continue using VEEAM for backups after moving to proxmox, but because the latest Veeam v12.3 (released Dec 2024) now has proxmox backup jobs, I'm recreating my existing Veeam VMware backup jobs to be Veeam...

Summary of my proxmox storage layout and my Reasoning: In my proxmox, I'm utilizing Thin-LVMs (block storage not mounted to a filesystem path). I chose ThinLVMs over LVM or ZFS because it is possible to dactivate a ThinLVM VG (volume group) and reactivate them again later. i.e. I can detach...

Adding more notes for my own future referencing. Importing Windows (10 and 11) guest VMs from ESXi into Proxmox as virtio scsi. The goal: - Uninstall VMware-tools from the windows VM - Install qemu-guest-agent (proxmox own variant of tools) - Install Virtio Drivers - Change the virtual disk...

I'm also excited because proxmox allows for a wider variety of PCIe NVMe SSDs. ESXI vmware comptability requirements killed off my desire to use my affordable m.2 nvme SSDs. I had to use hacks if not using expensive enterprise samsung firmware pcie ssds in esxi. Now I'm going to be using...

Now that I know how to ENABLE qemu-guest-agent in the vm (see my previous post above), the next question is what should the virtual disk controller be that I use in proxmox? When I import an ESXi Guest VM (linux in this case), the disk controller is VMWARE PVSCI. That will would still work...

OH MY WORD! It is working now. qemu-guest-agent is working now in my guest linux VM. I cannot believe how much time I've spent on this. The solution was so easy, but it took me a LONG time to figure it out. Here is the error I would see. I tried everything I could think of. I've been...

Nevermind, that didn't fix it. Now the guest won't even bootup. The prox guest vm just gives a spinning circle until it gives up and goes into Emergency shell mode. Okay, I think I have it figured out. When I convert my Linux VMs from ESXi to Proxmox, I needed to change the import settings...

Screenshot of me installing qemu into my newly converted guest vm. But qemu (manages the drivers, similar to vmware-tools) would fail to startup: Screenshot of the Proxmox 8.3 ESXi Importer plugin settings screen which should fix the qemu_guest_agent: I think I've discovered the reason for...

I've not had much time to work in this in past few weeks, but my next step will be to install qemu agents in the imported VMs. That is proxmix equivalent to vmware-tools or vmtools which handles the virtual driver's in the OS. I ran into some issues trying to install that qemu agent software a...

It completed successfully This 100GB vm imported and converted from the ESXi to Proxmox in about 30 minutes over gigabit LAN. Actually, I won't know if it was successful until I try booting it up.. tomorrow. Time for bed now. Next up will be to boot into the new converted VM, uninstall...

So far so good. My new little supermicro minitower has 10Gb adapters, but my 10Gb switch was full so I'm connected to a 1Gb switch. It's moving pretty good. Here is my first ESXi import progress so far:

When importing an ESXi VM into Proxmox, one of the fields it's needing is to know where we want to store the converted vm. It was only showing me the local-lvm which is on my proxmox boot disk ssd. I wanted to import into my newly created LVM-Thin Pools. To do that I have to tell my...

The latest release of Proxmox is 8.3.0, which I'm using. In release 8.2 they introduce a cool and very convenient ESXi Importer utility. You setup a connection from inside Proxmox to your ESXi Host. Proxmox will show you a list of all the DataStores on that host. You can Import any of the...