Recent content by bolzerrr

I figured that the behaviour changes once i disable sr-iov for my GPU. Strange enough that the second nvme is not affected and working also with sr-iov in place. 04:00.0 Non-Volatile memory controller [0108]: Kingston Technology Company, Inc. KC3000/FURY Renegade NVMe SSD E18 [2646:5013] (rev...

Yes thats wrong syntax: update-initramfs -u -k all update-initramfs: Generating /boot/initrd.img-6.8.8-2-pve libkmod: ERROR ../libkmod/libkmod-config.c:712 kmod_config_parse: /etc/modprobe.d/vfio.conf line 1: ignoring bad line starting with 'options' I don`t want to passthrough the nvme at...

As kernel command line a dot is used. I added the subdevie id to harden it but still the nvme gets vfio-pci: cat /etc/kernel/cmdline root=ZFS=rpool/ROOT/pve-1 boot=zfs mitigations=off intel_iommu=on iommu=pt vfio-pci.ids=544d:6178:6909:0001 i915.enable_guc=3 i915.max_vfs=3

Hello, i have following configuration: cat /etc/kernel/cmdline root=ZFS=rpool/ROOT/pve-1 boot=zfs mitigations=off intel_iommu=on iommu=pt i915.enable_guc=3 i915.max_vfs=3 cat /etc/modprobe.d/vfio.conf options vfio-pci ids=544d:6178 And that device get the correct module: lspci -nnk | grep -A...

The energy aspect is also something i am considering: 4 SSD`s + H310 vs NVME riser card is expected to be significant considering a overall low energy environment. Also in terms of invest the NVME is much lower compared to 3 extra SSD drives. I didnt look into pbs yet, but will invertigate...

Thanks for your hint, i even had a new idea: Put another NVMe which i have spare to a PCIe slot using a Sabrent PCIe m2 Adapter. This would replace the SSD and hopefully provide better speeds. Cache and log would stay on separated partitions one of each of the drives. Question is, would that be...

Hi, i wonder what setup would make most sense. Give the following situation: Asrock N100M 32 gb RAM - 1x NVME drive 512gb - 1x SSD 512gb Current setup: ZFS Raid 1 with both drives ~90% of the capacity. Spare 10% are used as cache or log for ZFS. I am not very happy with the performance...

Just came across same issue, same cpu. So everyhting is fine? The VM feels a bot slow but maybe it simply is what it is.

Here is the next crash. Apr 19 20:17:01 pve CRON[148813]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0) Apr 19 20:17:01 pve CRON[148814]: (root) CMD (cd / && run-parts --report /etc/cron.hourly) Apr 19 20:17:01 pve CRON[148813]: pam_unix(cron:session): session closed...

I am using this PSU: PicoPSU-90 12V DC-DC ATX Mini-ITX 0-90W Netzteil Power Supply PSU usage is reported: This is the last temp reported just before the crash (the flatline). RAM was already tested. Harddrives will be complicated to test..

You are right about the MB and yes it is fanless. However i prefer cooler hardware thats why i added 2 system fans to the case. I also suspected the temp first, therefore i added a watcher, i would not consider there temperatures critical. Spec of CPU telling critical 105c max. I was also...

Thanks for your hint. I did investigate the log and here is the moment it happened and i hit the reset button. All logs earlier look unsuspicious. Apr 17 16:59:40 pve qmeventd[472366]: Starting cleanup for 101 Apr 17 16:59:40 pve qmeventd[472366]: Finished cleanup for 101 Apr 17 16:59:40 pve...

Hi, i have regular crashes since i updated to PVE 8.1 and a newer hardware (n100m cpu). It happens between every 2-7 days, too much time between it to actively monitor it but often enough to be very annoying. When it happens system becomes unresponsive, doesn't react upon shutdown button and fan...

I am using this now, and it is working fine so far: https://www.derekseaman.com/2023/11/proxmox-ve-8-1-windows-11-vgpu-vt-d-passthrough-with-intel-alder-lake.html https://www.michaelstinkerings.org/gpu-virtualization-with-intel-12th-gen-igpu-uhd-730/

I just gave the latest kernel a try and it seems the error is gone (Linux pve 6.5.11-7-pve #1 SMP PREEMPT_DYNAMIC PMX 6.5.11-7 (2023-12-05T09:44Z) x86_64 GNU/Linux) I get this warning now: [ 0.430482] pnp 00:03: disabling [mem 0xc0000000-0xcfffffff] because it overlaps 0000:00:02.0 BAR 9...