Live data from Hacker News

Proxmox Virtual Environment 9.0 with Debian 13 released

proxmox.com

61–70 of 80 posts

Re: Proxmox Virtual Environment 9.0 with Debian 13 released

#61
For my homelab I switched from ESXi to Proxmox a few years ago because the consumer-level hardware I mostly used didn't have Intel network cards and ESXi didn't support the Realtek network devices that were ubiquitous in consumer gear at the time.

Love Proxmox, it's done everything I needed of it.

I don't use it to anywhere near it's potential, but I can vouch for the robustness of its backup process. I've had to restore more than handful of VMs for various reasons, and they've all been rock-solid upon restoration. I would like to use its high-availability features, but haven't needed them and don't really have the time to tinker so much these days.

Re: Proxmox Virtual Environment 9.0 with Debian 13 released

#62

Earlier quoted context omitted.

There are various terraform providers for proxmox.

Yeah, this is the way. You end up treating Proxmox like it is AWS and asserting your desired state against it.

You don't. The existing providers only deal with spinning up VMs and containers.

Most of the operations and configurations that exist in Proxmox are not present in the providers, like SDN, firewall and the various storage options. The reason is that the API is all over the place and really badly documented.

Note that I still quite like the product. I have a 2- (soon to be 3-) node cluster at home and at this moment I have no plans to migrate away from it.

I looked into Incus but it's also far from mature, with an API and general data structure being full of inconsistencies, and again the documentation is not quite there.

Re: Proxmox Virtual Environment 9.0 with Debian 13 released

#63
post #51

I would see Proxmox come up in so many homelab type conversations so I tried 8.* on a mini pc. The impression I got was that the project probably provides the most value in a clustered environment or even on a single node if someone prefers using a web UI. What didn't seem very clear was an out-of-box way for declaring VM and container configurations [1] that could then be version controlled. Common approaches seemed…

I have similar feelings.

I really wish proxmox had nicer container support.

If a proxmox container config could specify a dockerfile as an option, I think proxmox would be 1000% more useful (and successful)

Instead with LXC and their config files, I feel like i have to put on a sysadmin hat to get a container going. Seems like picking up an adding machine to do my taxes.

(also, lxc does have a way to specify a container, but it is not used)

Instead I have written scripts to automate some of this, which helps,

There is also cloud-init, but I found it sort of unfriendly and never went anywhere with it.

Re: Proxmox Virtual Environment 9.0 with Debian 13 released

#64

"It’s also possible to install Proxmox VE 9.0 on top of Debian." Has that always been the case? I have a faint memory of trying once and not being able to with Proxmox 7.x

I wonder about things like this.

It seems to me people who try things like this might also be ok with spaces in filenames, or replacing bash with csh...

It should work, but you might want to cross your fingers.

Re: Proxmox Virtual Environment 9.0 with Debian 13 released

#65
post #34

Earlier quoted context omitted.

Yes, you can do this with ceph on commodity hardware (or even your compute nodes, if you are brave), or if you have a bit of cash, something like a netapp to do NFS/iSCSI/NVME-oF Use any of these with the built in HA manager in proxmox

As far as I understand it, Ceph allows you to create distributed storage by using the hardware across your hosts. Can it be used to format a single shared block device that is accessed by multiple hosts like VMFS does? My understanding is this isn't possible.

From what I read about VMFS yes ceph allows you to have a shared block devices (RBD = rados block devices) across a cluster, and proxmox VE HA makes sure only one instance of the VM is active on the cluster to avoid having multiple writers to the same disk image.

Re: Proxmox Virtual Environment 9.0 with Debian 13 released

#67

I have only recently moved to proxmox as the Hyper-V licensing became too opressive for hobby/one-person projects use. Can someone tell me wether proxmox upgrades are usually smooth sailing, or should I prepare for this being an endeavour?

Proxmox ships a tool that verify if everything is right for the update (eg: pve8to9), and the wiki documentation is extensive and kept up to date.

At work we started with 6.x a few years ago, upgraded to 7.x a bit after releases, then same with 8.x without issue.

We'll wait a reasonable while before upgrading to 9.x but I don't expect any issue.

Note : same with integrated ceph update, did Reef to Squeed a few weeks ago, no issue.

Re: Proxmox Virtual Environment 9.0 with Debian 13 released

#68

Seems like it still has no official support for any kind of disk encryption, so you are on your own if you fiddle that in somehow and things may break. Such a beautiful, peaceful world where disk encryption is not needed!

Proxmox supports ZFS and ZFS has disk encryption.

Re: Proxmox Virtual Environment 9.0 with Debian 13 released

#69

Seems like it still has no official support for any kind of disk encryption, so you are on your own if you fiddle that in somehow and things may break. Such a beautiful, peaceful world where disk encryption is not needed!

In the hypervisor? Because I have plenty of VMs with LUKS and BitLocker.

Re: Proxmox Virtual Environment 9.0 with Debian 13 released

#70
post #51

I would see Proxmox come up in so many homelab type conversations so I tried 8.* on a mini pc. The impression I got was that the project probably provides the most value in a clustered environment or even on a single node if someone prefers using a web UI. What didn't seem very clear was an out-of-box way for declaring VM and container configurations [1] that could then be version controlled. Common approaches seemed…

cloud-init support is sorely missed.
Post reply on HN