Proxmox VE 8.4 released!

Since the upgrade, i have very slowly VMs (all) (windows & Linux) in all my server
Did you try to boot with the previous kernel?

Check the speed of the CPU with grep MHz /proc/cpuinfo if it is able to reach nominal/turbo speeds. I've had a few cases (unrelated to this update) where the CPU for some reason can't raise it's speed (faulty PSU, BIOS gone mad, faulty cooling). If it can't reach at least nominal speed, it will lack capacity, hence increasing the load and making everything slow.
 
Awesome news. One feature I'd like to see is an easier way to share GPU (or partials) with LXC for things like LLMs so I don't have to dedicate a whole card to an LXC that may not be running all the time. Maybe this is already possible but it seems it's a cumbersome process with some mapping user/groups and all this rigamarole that I could never quite get working... If there's a more recent guide to set this up, please point me at it.
I worte a tutorial about it that yo can adapt for your needs. It goes through the basics of passing an AMD card to an LXC with Proxmox's new-ish feature implemented a few releases ago.

https://forum.proxmox.com/threads/t...nd-rocm-in-unprivileged-lxc-container.157920/
 
Did you try to boot with the previous kernel?

Check the speed of the CPU with grep MHz /proc/cpuinfo if it is able to reach nominal/turbo speeds. I've had a few cases (unrelated to this update) where the CPU for some reason can't raise it's speed (faulty PSU, BIOS gone mad, faulty cooling). If it can't reach at least nominal speed, it will lack capacity, hence increasing the load and making everything slow.
I have a stopping Proxmox installation here - sorry, I am new to this. How to downgrade to the prev. kernel. Can you help, please
 
I use NFS to mount a directory in my Debian VM and I tried the new virtiofs. It was around the same. Is that expected?

virtiofs
sudo sync; sudo dd if=/dev/zero of=/mnt/test/output conv=fdatasync bs=1G count=5
5+0 records in
5+0 records out
5368709120 bytes (5.4 GB, 5.0 GiB) copied, 6.29989 s, 852 MB/s

NFS

sudo sync; sudo dd if=/dev/zero of=/pve1storage/output2 conv=fdatasync bs=1G count=5
5+0 records in
5+0 records out
5368709120 bytes (5.4 GB, 5.0 GiB) copied, 6.1124 s, 878 MB/s

Not a scientific test by any means, but am I missing something or is NFS already getting the best out of my NAS? Appreciate your time replying to my question
 
Hi,
In past I have tried install a vm with MacOS Ventura and it worked very well, but now when I change media=cdrom to cache=unsafe on my vm config file and try to start the vm to begin installation the vm do not start and I get error on Proxmox logs : "error ide0 explicit media parameter is required for iso images"
Something wrong with my software or this is caused by some changes on Proxmox 8.4 ?
yes, there was a change. You need to specify media=cdrom for the image like the error message says. Why do you want to remove that parameter manually?
 
Hi, disk in vm no more possible to resized automatically, debian 12. Possible also udp port 53 not working in wm' s, dns server (test mikrotik cloud). in previos version all was ok.
 
Last edited:
Hi,
Hi, disk in vm no more possible to resized automatically, debian 12. Possible also udp port 53 not working in wm' s, dns server (test mikrotik cloud). in previos version all was ok.
please open a dedicated thread and provide more details there: output of pveversion -v, qm config <ID>, exact commands you are using.
 
Hi
First of all thank you very much for this great software.
I always make all updates , so my system is always up to date.
This time was no exception, so now my system is updated to 8.4.1
Everything seems to be working very well, except for the following:

In past I have tried install a vm with MacOS Ventura and it worked very well, but now when I change media=cdrom to cache=unsafe on my vm config file and try to start the vm to begin installation the vm do not start and I get error on Proxmox logs : "error ide0 explicit media parameter is required for iso images"

Something wrong with my software or this is caused by some changes on Proxmox 8.4 ?

Any idea appreciated.
Thank you very much.
use media=disk
 
We have a few example plugins where that we currently polish for being a bit more presentable and available through a single git repo.
You can see the current version of two Perl plugins over here:
https://lore.proxmox.com/all/20250407120439.60725-1-f.ebner@proxmox.com/
And there is also a Rust based plugin to showcase that this is not locked to a single programming language, we'll try to get that all up until the end of the week.
What is the current status here?
 
been running a couple of weeks no issues. some features i would like to see under the theme more ceph management / backup integration.

  • ability to schedule pbs jobs to backup cephFS volumes without mouting them in a CT or VM to show up in the UI
  • ability to clone rbds and then backup the rbs to pbs without mounting them in a CT or VM to show up in the UI
  • adding of cephFS volumes or rbds optionally makes all the needed ceph.conf / keyrings / ceph auth entries to copy to clients to be used
  • images created in an rbd that are not used by QEMU directly (i.e. mounted in client using libceph or fuse) should still show in UI so one can see all images in all namespaces
I have fguured out how to do all of these manually / have chatgpt create scripts that do all these things for me, would be nice to have UI for all these things

oh i also upgraded to latest ceph no issues (still trying to work out if i should / how do i move to the new OSD engine)
 
The Proxmox 8.4 ISO (written to a USB drive) is not bootable by an Intel NUC8 -- the NUC doesn't even show it as an option. A 7.4 ISO works just fine, with the same bios configs (legacy boot disabled, secure boot disabled).
 
The Proxmox 8.4 ISO (written to a USB drive) is not bootable by an Intel NUC8 -- the NUC doesn't even show it as an option. A 7.4 ISO works just fine, with the same bios configs (legacy boot disabled, secure boot disabled).
Write it with balena etcher not any other tool.
 
Write it with balena etcher not any other tool.
What do you expect etcher to do differently than dd? (As it happens, I did also try etcher as I was originally making the usb stick on a mac before I switched to linux to remove variables. 8.4 doesn't work when written with etcher or dd, 7.4 worked with dd.)
 
I would like an option to make lzo the default for backups, on my proxmox its about 3-4x as fast as zstd for only slightly bigger images. I tried to add to vzdump.conf compress: lzo but it has no impact.
 
I tried to add to vzdump.conf compress: lzo but it has no impact.
No impact? So even when using the CLI command: vzdump <vmid> it still doesn't do lzo compression by default after that change? That would be surprising.

AFAIK, any backup jobs specific settings will override those in the vzdump.conf .

If you are looking for a GUI default - I'm not sure why you would want that, you can easily select it from the dropdown-menu (maybe laziness or for other sysadmins?).

Note: I have not tested if changing the compression in the vzdump.conf file changes the default chosen in the GUI - but I can understand that it does not.
 
We have a few example plugins where that we currently polish for being a bit more presentable and available through a single git repo.
You can see the current version of two Perl plugins over here:
https://lore.proxmox.com/all/20250407120439.60725-1-f.ebner@proxmox.com/
And there is also a Rust based plugin to showcase that this is not locked to a single programming language, we'll try to get that all up until the end of the week.

And there's naturally basic documentation in the base module for the backup provider plugin API:
https://git.proxmox.com/?p=pve-stor...7;hb=0c6234f0bc9772320786ca7ce5f45018630557de
Hi @t.lamprecht,
I have tried to use the sample to integrate the borg module to our Proxmox Server, but I haven't see any change on the GUI to check the borg.
Can you introduce some document about how to integrate the borg module.