35 ms·

Proxmox VE 7.0 Released

80 points by noja 5y ago

bityard 5y ago
It was released back in July... (And was shipping Debian bullseye before _that_ was fully released, so they must have had a lot of confidence in it!)
- guerby 5y ago
  The debian installer was holding back bullseye release, proxmox uses its own installer (and kernel, qemu) so minimal risk as debian was frozen.
gkhartman 5y ago
Can anyone comment on update/package stability when using the free version of Proxmox. It's my understanding that only the paid license allows access to stable repos. I find the community tier price a bit too expensive for my current home use case (mostly nas + plex).
- LeoPanthera 5y ago
  Been running the free version for a couple of years now. No problems at all. I update and reboot it maybe once a month, or whenever there's a severe security update (that I don't miss). It's uneventful.
  - radiowave 5y ago
    Likewise, have run it for years on a bunch of machines, never had a problem. I think I've got at least one that's been dist-upgraded all the way from a 4.x release to the current 7.0.
  - sokoloff 5y ago
    Same. I’ve been running it a little over 2 years for home/family services and it’s been entirely stable for me. I update slightly less often than parent comment, but have had zero issues from updates.
- RamRodification 5y ago
  Your understanding is correct. See here: https://pve.proxmox.com/wiki/Package_Repositories https://pve.proxmox.com/wiki/Package_Repositories We run Proxmox for non-production-critical VMs. Nothing fancy, just Proxmox hosts, iSCSI storage and standard VMs on that (Windows and Linux). Every now and then we update hosts using the No-Subscription Repository. No issues from that so far. Maybe if we updated more frequently we would see more issues. I think we only do it once or twice between each new official version release. That's out of laziness/lack of time, not out of fear of issues from less tested packages.
- solarkraft 5y ago
  Have been running it as a Debian system (realized I don’t need Proxmox, but already had some stuff set up) for about a year and had no idea. Absolutely no problems.
the_third_wave 5y ago
For those who a) use Proxmox to b) manage containers c) some of which are of ostype: unmanaged (e.g. those who run a virtual OpenWRT router, like me...) be warned that the current version of Proxmox will not start those containers due to a bug/an omission in the PVE::LXC::Setup package (/usr/share/perl5/PVE/LXC/Setup.pm) which makes it attempt to call a non-existing method to configure cgroupv2 support on such containers. The following patch will work for now while the problem has not yet been solved in the repo: --- /usr/share/perl5/PVE/LXC/Setup.pm.org +++ /usr/share/perl5/PVE/LXC/Setup.pm @@ -424,6 +424,8 @@ sub unified_cgroupv2_support { my ($self) = @_; + $self->{plugin} //='PVE::LXC::Setup::Base'; # unmanaged + $self->protected_call(sub { $self->{plugin}->unified_cgroupv2_support(); }); I hit upon this snag when updating the server-under-the-stairs which went off without any problems except for the router container not starting.
- cridenour 5y ago
  Thanks for the heads up! I’ll wait for the .1 release to avoid messing up videos for my bossy toddlers.
LeoPanthera 5y ago
(July 6, 2021)
amanzi 5y ago
I upgraded my three-node homelab cluster to Proxmox 7 a while back and everything worked perfectly for me.
thrwawy283 5y ago
My absolute wish is to run Proxmox on a laptop and have a VM drive the laptop display. Currently this is not possible. There are many guides on passing through the integrated or dedicated GPU, but NOT using the laptop display in a guest VM. The host/Proxmox doesn't need the display. I want the guest to own it. No looking glass no spice no gl window no virt-gpu. The VM should directly own and exclusively operate the gpu and laptop display. My dream setup is Proxmox being very minorly configured - a stable base that's easy to restore. Within it 5 VMs: firewall, primary-linux, rescue-linux, linux-for-containers, and Windows 10. I recognize most folks are running Proxmox on a desktop but I have a very nice laptop. I want to isolate my firewall into a guest VM (opnsense). I want to run my primary Linux in another guest VM - with the Intel iGPU passed through and using the laptop display. I want to run Windows - when I need it - for games that intentionally disallow VMs. I want to run a separate Linux (Rancher) for containers/development. Finally I want a rescue-linux so if the primary fails for whatever reason, Proxmox would fail over by starting the rescue VM - just something with enough for me to remote into the host/proxmox and fix things. Windows would be viewable from RDP or looking glass. The container Linux would be ssh-administered. Same as firewall or web admin. I LOVE the idea of Proxmox making it easy to backup/transfer/experiment with different OS's. Because I can't get Proxmox to drive the laptop display - something not possible on AMD or Intel afaik - I settled on NixOS as the host with explicitly configured everything. Windows in a VM. Docker available on the host. It's the best I can do :( Someday I hope hypervisors-against-metal on laptops is commonplace. Seriously: If someone can get the laptop display to work from a guest VM on any laptop I would be so happy. I hope AMD gets this because I am so done paying for baby steps with Intel. EDIT: Looks like I'm trying this again tonight: https://github.com/patmagauran/i915ovmfPkg https://github.com/patmagauran/i915ovmfPkg (purportedly a romfile for the igpu that _will_ drive the laptop display) I've tried it before about a month ago but it looks like I was using the "2.1" release from last year. A few things have been updated in June/July.
- HumblyTossed 5y ago
  Oh you're not alone here. I've often wanted to do that too. It would make certain things easier toast up.
- jchw 5y ago
arange 5y ago
one day we'll get native Docker support... love the distro otherwise
- apfsx 5y ago
  Have they said anything about this possibly ever coming to the platform?
rektide 5y ago
this seems like such a really good baseline for a home-cloud. there's such good host infrastructure here. i'm such a huge Debian lover but there's so much more required to turn it into a decent host environment, and Proxmox covers so much ground to do just that. but i still want Kubernetes as my primary interface atop it. since LXC is the primary container system on Proxmox (and a damned fine one at that), it seems like one might be able to make something like LXE[1] run, as a shim, to provide a Container Runtime Interface & start running kubelet (the thing that runs containers) atop that. [1] https://github.com/automaticserver/lxe https://github.com/automaticserver/lxe
- moondev 5y ago
  Have you checked out https://kubevirt.io https://kubevirt.io An operator for kvm virtual machines that run on the kubernetes nodes. Kubernetes instead of the proxmox html5 UI
- the_third_wave 5y ago
  Just out of interest, why do you want to use Kubernetes in a home cloud environment? Given the limited scale of such an environment I don't see the need for something like Kubernetes here, just have those containers managed by Proxmox and be done with it. That is how I use it, with task-specific containers (auth, mail, (data)base, a few build environments, p2p, media, reverse web proxy, router, etc) directly managed through pct (Proxmox LXC CLI).
  - zekrioca 5y ago
    I also don’t get why Kubernetes would be in any way needed in such setup.
    - rektide 5y ago
      A lot of people don't see. I think that trying to turn a blind eye to complexity is a foolish mistake. There's so much you're given, that helps so much with out of the box Kubernetes. Logging & load balancing/services, and gateway/ingress, and daemon-sets and... how convinced are you that you understand these features well enough to confirm that you don't & wont need them? It also sounds exhausting to me to try to start from the basis that's what's good enough for everyone is too much for me. That, because we are scared of complexity, we're going to go bake our own systems, go back & re-assess less-popular less common less comprehensive options. And how happy are you knowing that the ops you do will be unintelligible to 90% of engineers? To me, getting to participate & share & work with other cloud native projects, to get to explore pull in the future, as it is happening, is an option I would give up for nothing. I also highly recommend this other thread I have, on how home-computing has never ever had a basis to stand from before, and how now that the computing community finally has it's first chance ever to grow good at ops together[1]. But I see enormous vast huge waves of radical retro-conservatism. "I don't know if I need Kubernetes" is a critical mindset that I think is worth assessing, but honestly, 99.999% of the time, you should use Kubernetes. It works fantastically well at all levels of scale, you can decide as you go what pieces you're going to want to make use of, there are super easy get-going-get-containers-started resources, you will have far far far more chance to bring in & use potentially helpful emerging technology. Please everyone: don't fucking decide to hike the fuck off to your stupid ass cabin in the woods computing environment cause you're all "I don't think this is needed." You are punking yourself. Asking what you need is a question you can harp on for a long time, but the risk of starting with the good comprehensive, proven, well-integrated, robust, scalable (low and high), known, well used/well liked not hard to start with default option is- I think- a low enough that you should probably just give it a spin. [1] https://news.ycombinator.com/item?id=28332604 https://news.ycombinator.com/item?id=28332604
tyingq 5y ago
I had a good experience with Proxmox myself, though Lxd seems to be something of a new competitor now that it supports both containers and VMs.
unixhero 5y ago
Mad fan of Proxmox. I reeeeally wish they would build support for Docker containers. Yes, I can run them in a VM and currently do just that.
- moondev 5y ago
  you can run docker inside lxc as well lxc.apparmor.profile: unconfined lxc.cgroup.devices.allow: a lxc.cap.drop:
  - unixhero 5y ago
    Aww yeah! For real? I can't wait to try this out.
    - radiowave 5y ago
      Note that it doesn't play well with ZFS, but see here for workaround: https://old.reddit.com/r/Proxmox/comments/m9ce8s/got_docker_running_on_lxc_zfs_so_now_im_vm_free/ https://old.reddit.com/r/Proxmox/comments/m9ce8s/got_docker_...
- salmon 5y ago
  There’s actually three ways to run Docker on Proxmox: in a VM, in an LXC container, or directly in Proxmox itself. I wrote about it here: https://danthesalmon.com/running-docker-on-proxmox/ https://danthesalmon.com/running-docker-on-proxmox/
nix23 5y ago
Proxmox is in all honesty the best Virtualization platform out there.
- sekh60 5y ago
  Personally I much prefer OpenStack. Probably overkill for most though.

80 points by noja 5y ago

It was released back in July... (And was shipping Debian bullseye before _that_ was fully released, so they must have had a lot of confidence in it!)

guerby 5y ago
The debian installer was holding back bullseye release, proxmox uses its own installer (and kernel, qemu) so minimal risk as debian was frozen.

gkhartman 5y ago

Can anyone comment on update/package stability when using the free version of Proxmox. It's my understanding that only the paid license allows access to stable repos. I find the community tier price a bit too expensive for my current home use case (mostly nas + plex).

LeoPanthera 5y ago
Been running the free version for a couple of years now. No problems at all. I update and reboot it maybe once a month, or whenever there's a severe security update (that I don't miss). It's uneventful.
- radiowave 5y ago
  Likewise, have run it for years on a bunch of machines, never had a problem. I think I've got at least one that's been dist-upgraded all the way from a 4.x release to the current 7.0.
- sokoloff 5y ago
  Same. I’ve been running it a little over 2 years for home/family services and it’s been entirely stable for me. I update slightly less often than parent comment, but have had zero issues from updates.
RamRodification 5y ago
Your understanding is correct. See here: https://pve.proxmox.com/wiki/Package_Repositories https://pve.proxmox.com/wiki/Package_Repositories We run Proxmox for non-production-critical VMs. Nothing fancy, just Proxmox hosts, iSCSI storage and standard VMs on that (Windows and Linux). Every now and then we update hosts using the No-Subscription Repository. No issues from that so far. Maybe if we updated more frequently we would see more issues. I think we only do it once or twice between each new official version release. That's out of laziness/lack of time, not out of fear of issues from less tested packages.
solarkraft 5y ago
Have been running it as a Debian system (realized I don’t need Proxmox, but already had some stuff set up) for about a year and had no idea. Absolutely no problems.

the_third_wave 5y ago

For those who a) use Proxmox to b) manage containers c) some of which are of ostype: unmanaged (e.g. those who run a virtual OpenWRT router, like me...) be warned that the current version of Proxmox will not start those containers due to a bug/an omission in the PVE::LXC::Setup package (/usr/share/perl5/PVE/LXC/Setup.pm) which makes it attempt to call a non-existing method to configure cgroupv2 support on such containers. The following patch will work for now while the problem has not yet been solved in the repo: --- /usr/share/perl5/PVE/LXC/Setup.pm.org +++ /usr/share/perl5/PVE/LXC/Setup.pm @@ -424,6 +424,8 @@ sub unified_cgroupv2_support { my ($self) = @_; + $self->{plugin} //='PVE::LXC::Setup::Base'; # unmanaged + $self->protected_call(sub { $self->{plugin}->unified_cgroupv2_support(); }); I hit upon this snag when updating the server-under-the-stairs which went off without any problems except for the router container not starting.

cridenour 5y ago
Thanks for the heads up! I’ll wait for the .1 release to avoid messing up videos for my bossy toddlers.

LeoPanthera 5y ago

(July 6, 2021)

amanzi 5y ago

I upgraded my three-node homelab cluster to Proxmox 7 a while back and everything worked perfectly for me.

thrwawy283 5y ago

My absolute wish is to run Proxmox on a laptop and have a VM drive the laptop display. Currently this is not possible. There are many guides on passing through the integrated or dedicated GPU, but NOT using the laptop display in a guest VM. The host/Proxmox doesn't need the display. I want the guest to own it. No looking glass no spice no gl window no virt-gpu. The VM should directly own and exclusively operate the gpu and laptop display. My dream setup is Proxmox being very minorly configured - a stable base that's easy to restore. Within it 5 VMs: firewall, primary-linux, rescue-linux, linux-for-containers, and Windows 10. I recognize most folks are running Proxmox on a desktop but I have a very nice laptop. I want to isolate my firewall into a guest VM (opnsense). I want to run my primary Linux in another guest VM - with the Intel iGPU passed through and using the laptop display. I want to run Windows - when I need it - for games that intentionally disallow VMs. I want to run a separate Linux (Rancher) for containers/development. Finally I want a rescue-linux so if the primary fails for whatever reason, Proxmox would fail over by starting the rescue VM - just something with enough for me to remote into the host/proxmox and fix things. Windows would be viewable from RDP or looking glass. The container Linux would be ssh-administered. Same as firewall or web admin. I LOVE the idea of Proxmox making it easy to backup/transfer/experiment with different OS's. Because I can't get Proxmox to drive the laptop display - something not possible on AMD or Intel afaik - I settled on NixOS as the host with explicitly configured everything. Windows in a VM. Docker available on the host. It's the best I can do :( Someday I hope hypervisors-against-metal on laptops is commonplace. Seriously: If someone can get the laptop display to work from a guest VM on any laptop I would be so happy. I hope AMD gets this because I am so done paying for baby steps with Intel. EDIT: Looks like I'm trying this again tonight: https://github.com/patmagauran/i915ovmfPkg https://github.com/patmagauran/i915ovmfPkg (purportedly a romfile for the igpu that _will_ drive the laptop display) I've tried it before about a month ago but it looks like I was using the "2.1" release from last year. A few things have been updated in June/July.

HumblyTossed 5y ago
Oh you're not alone here. I've often wanted to do that too. It would make certain things easier toast up.
jchw 5y ago

arange 5y ago

one day we'll get native Docker support... love the distro otherwise

apfsx 5y ago
Have they said anything about this possibly ever coming to the platform?

rektide 5y ago

this seems like such a really good baseline for a home-cloud. there's such good host infrastructure here. i'm such a huge Debian lover but there's so much more required to turn it into a decent host environment, and Proxmox covers so much ground to do just that. but i still want Kubernetes as my primary interface atop it. since LXC is the primary container system on Proxmox (and a damned fine one at that), it seems like one might be able to make something like LXE[1] run, as a shim, to provide a Container Runtime Interface & start running kubelet (the thing that runs containers) atop that. [1] https://github.com/automaticserver/lxe https://github.com/automaticserver/lxe

moondev 5y ago
Have you checked out https://kubevirt.io https://kubevirt.io An operator for kvm virtual machines that run on the kubernetes nodes. Kubernetes instead of the proxmox html5 UI
the_third_wave 5y ago
Just out of interest, why do you want to use Kubernetes in a home cloud environment? Given the limited scale of such an environment I don't see the need for something like Kubernetes here, just have those containers managed by Proxmox and be done with it. That is how I use it, with task-specific containers (auth, mail, (data)base, a few build environments, p2p, media, reverse web proxy, router, etc) directly managed through pct (Proxmox LXC CLI).
- zekrioca 5y ago
  I also don’t get why Kubernetes would be in any way needed in such setup.
  - rektide 5y ago
    A lot of people don't see. I think that trying to turn a blind eye to complexity is a foolish mistake. There's so much you're given, that helps so much with out of the box Kubernetes. Logging & load balancing/services, and gateway/ingress, and daemon-sets and... how convinced are you that you understand these features well enough to confirm that you don't & wont need them? It also sounds exhausting to me to try to start from the basis that's what's good enough for everyone is too much for me. That, because we are scared of complexity, we're going to go bake our own systems, go back & re-assess less-popular less common less comprehensive options. And how happy are you knowing that the ops you do will be unintelligible to 90% of engineers? To me, getting to participate & share & work with other cloud native projects, to get to explore pull in the future, as it is happening, is an option I would give up for nothing. I also highly recommend this other thread I have, on how home-computing has never ever had a basis to stand from before, and how now that the computing community finally has it's first chance ever to grow good at ops together[1]. But I see enormous vast huge waves of radical retro-conservatism. "I don't know if I need Kubernetes" is a critical mindset that I think is worth assessing, but honestly, 99.999% of the time, you should use Kubernetes. It works fantastically well at all levels of scale, you can decide as you go what pieces you're going to want to make use of, there are super easy get-going-get-containers-started resources, you will have far far far more chance to bring in & use potentially helpful emerging technology. Please everyone: don't fucking decide to hike the fuck off to your stupid ass cabin in the woods computing environment cause you're all "I don't think this is needed." You are punking yourself. Asking what you need is a question you can harp on for a long time, but the risk of starting with the good comprehensive, proven, well-integrated, robust, scalable (low and high), known, well used/well liked not hard to start with default option is- I think- a low enough that you should probably just give it a spin. [1] https://news.ycombinator.com/item?id=28332604 https://news.ycombinator.com/item?id=28332604

tyingq 5y ago

I had a good experience with Proxmox myself, though Lxd seems to be something of a new competitor now that it supports both containers and VMs.

unixhero 5y ago

Mad fan of Proxmox. I reeeeally wish they would build support for Docker containers. Yes, I can run them in a VM and currently do just that.

moondev 5y ago
you can run docker inside lxc as well lxc.apparmor.profile: unconfined lxc.cgroup.devices.allow: a lxc.cap.drop:
- unixhero 5y ago
  Aww yeah! For real? I can't wait to try this out.
  - radiowave 5y ago
    Note that it doesn't play well with ZFS, but see here for workaround: https://old.reddit.com/r/Proxmox/comments/m9ce8s/got_docker_running_on_lxc_zfs_so_now_im_vm_free/ https://old.reddit.com/r/Proxmox/comments/m9ce8s/got_docker_...
salmon 5y ago
There’s actually three ways to run Docker on Proxmox: in a VM, in an LXC container, or directly in Proxmox itself. I wrote about it here: https://danthesalmon.com/running-docker-on-proxmox/ https://danthesalmon.com/running-docker-on-proxmox/

nix23 5y ago

Proxmox is in all honesty the best Virtualization platform out there.

sekh60 5y ago
Personally I much prefer OpenStack. Probably overkill for most though.