Search results

The upgrade process is pretty easy. The iomemory-vsl for 7.4 does not compile for 8.x versions of proxmox. Before starting the 7 -> 8 proxmox upgrade process, remove the iomemory-vsl dkms module after shutting down anything using it. Next do the proxmox upgrade process to 8. Download the...

Are you guys using the iomenory package from https://www.dropbox.com/s/df06nuzvqndlvnk/iomemory-vsl-5.12.1.zip or https://github.com/RemixVSL/iomemory-vsl The version from github works with the latest kernel proxmox 7 and the current kernel with proxmox 8. I have FusionIO drives running...

This also isnt a bug in the SATA/IDE emulation code as all three of these VM where using the VirtIO SCSI controller for the disks.

This is great, I have had 3 more vm get killed by their hard disk loosing the partition table. This is now far from 'rare' and down right common. Can this please get prioritized higher?

Looks like it, the disk has no partition table. Do we have an ETA on the fix? Having this occur during backups kinda defeats the purpose of doing a backup ;)

I updated to the following here: Kernel Version Linux 5.15.108-1-pve #1 SMP PVE 5.15.108-2 (2023-07-20T10:06Z) PVE Manager Version pve-manager/7.4-16/0f39f621 Now I have a VM that is dead where it cant boot. Looks like it is not finding the os on the hard disk and is defaulting to booting...

Well just deleting everything in the .chunks directory caused more problems. I ended up killing the directory and recreating it. We really, really, really need to get these steps automated through the GUI to cleanly remove/delete/wipe a directory and its disk so either the directory or...

I have removed all the jobs on the VE servers, so nothing should be referencing the PBS server. Can I just delete everything in the .chunks directory?

fstrim -a didnt do anything. Here is the last part of the log from running GC: 2023-07-30T14:40:00-06:00: processed 94% (763694 chunks) 2023-07-30T14:40:00-06:00: processed 95% (771937 chunks) 2023-07-30T14:40:01-06:00: processed 96% (779968 chunks) 2023-07-30T14:40:02-06:00: processed 97%...

I have a PBS running the latest non version and I am seeing an issue I cant figure out. I manually removed all the backups on the server, but it is still show about 2.9TB of 12TB being used by something. How do I reclaim the space on the directory allocated? I have run garbage collection...

Any idea when this is going to be fixed? It would be really nice if the automated backups would be setting this. Current version of pbs and the server is still not doign this.

I do know that the UPS is supported/driven by apcupsd and NUT, but various manufactures have differing levels of support and functionality by the driver and higher level software. I am mainly looking for peoples experience with different manufactures/models that have good usable support.

hello, i am looking for a UPS backup unit that is compatible with proxmox where it can read the remaining battery life and shut down things based on life left thresholds. Not looking for a mid level range unit.

Getting this same error also with several GPU passthroughs: pve-manager/7.2-7/d0dd0e85 5.13.19-6-pve, 5.15.39-3-pve, and 5.15.53-1-pve kernels.

Got it figured out The following will list out all parameters for all modules currently loaded: cat /proc/modules | cut -f 1 -d " " | while read module; do echo "Module: $module"; if [ -d "/sys/module/$module/parameters" ]; then ls /sys/module/$module/parameters/ | while read parameter; do...

I am hitting the power write governing because of the default wattage limit of 25 watts. Anyone know how to bump that up? I found this, but I cant find the fio-config app: fio-config -p FIO_EXTERNAL_POWER_OVERRIDE <device serial number>:<power in watts> Also found that it can be set using...

https://github.com/RemixVSL/iomemory-vsl Just did an install this morning. You just need to replace the steps of downloading the iomemory-vsl zip file with the download from the above github link with a rename of the unzipped directory. root@odin:~# uname -a && fio-status -a Linux odin...

Are you guys grabbing the latest version( aka master ) of the driver? Using the one listed in the first post and trying to compile it against the 5.30.X versions of the kernel will only fail to build.

Same here. You just need to download and install the latest drivers. Only bad side affect is that I lost everything that was on the drive when the new drivers where installed. I had recent backups so not a big deal.

Made the mistake of upgrading, now gpu passthrough is broken. The VM fails to start up with the helpful error message: "failed: got timeout". Basically the same thing is syslog. If I remove the GPU, the boots and runs fine. Add the GPU back as passthrough, fails to start. Is there any...