Search results

Thank you, I wound up finding out it is indeed a strange edge case needing a beta bios AND settings changed. Found the details here: https://forum.asrock.com/forum_posts.asp?TID=19749&PID=103124&title=x470d4u-p4-20-ryzen5600g-fatal-error-gpu-boot

*edit* Problem Solved For anyone from the future who may have a similar problem this turned out to be a super weird/annoying BIOS version + settings issue. In my case it required updating to a beta bios, changing the boot option to UEFI and some settings under CSM to UEFI only as well. These...

I have a small form factor system with only 2 m.2 slots. I've populated these with 2 micron 7450 Pro 1.92TB drives. I would like to use these 2 nvme drives in a zfs mirror for the rpool, but I would like to reserve some amount of space, maybe 100GB on each drive to create a mirrored special...

I'm curious what your cpu usage looks like when HDR tone mapping? I just followed this guide on a intel 13700 and while plex indicates (hw) transcoding when tone-mapping an h265 hdr10 video to sdr h264 and intel_gpu_top is showing a good amount of usage when run in the lxc container i'm still...

Does anyone know if there are any recommended scheduler adjustments that should be made for balanced power/performance ratio in a home environment when using this kernel with the latest gen intel processors (13th gen raptor lake with p+e cores)? Is enabling schedutil recommended or a bad idea...

On my Proxmox 6.4 host the guide worked perfectly for me with debian 11 lxc and zfs. I didn't run anything on the proxmox host. I'm also running docker from the official docker repo, no need to install the debian specific version noted in that post.

Thank you that was very helpful! For anyone who may find this, I was able to disable mitigations by adding mitigations=off to the end of /etc/kernel/cmdline followed by running proxmox-boot-tool refresh That file now looks like this: root=ZFS=rpool/ROOT/pve-1 boot=zfs mitigations=off

My system is apparently being managed with promxox-boot-tool, when I ran update-grub after adding mitigations=off to the GRUB_CMDLINE_LINUX_DEFAULT line in /etc/default/grub. However I cannot figure out how to apply mitigations=off or its equivalent to the system as it doesn't seem to be using...

Is there anything else you recommend I can try to troubleshoot? I can roll back to a 6.2 installation and never upgrade but knowing this is likely to re-occur the second I upgrade again has me worried.

Yes sorry that is what I did first, I only installed 5.11 as a last ditch effort to see if any difference was made.

Recently upgraded from proxmox 6.2 to 6.3 and this is when the trouble started. I eventually gave up troubleshooting and just completed a fresh install from the 6.3 iso followed by a quick apt dist-upgrade, which is when the exact same issues have happened again. When my 5-drive raidz disks are...

Did the 5.11 kernel work? I'm considering a nuc 11 purchase but proxmox working is a requirement.

I'm having this extremely strange issue I have never seen before and unfortunately have been unable to debug. I've installed photoprism (self hosted google photos competitor, kind of amazing) in a ubuntu 20.04 VM. Inside this vm I'm running docker from the docker repository. I don't know if...

I noticed the SIMD changes have been merged on the ZoL side. Is there a ballpark for when these will make it into proxmox, even proxmox beta? Thanks!

Any guidance on this? My yubikey functionality seems to be broken now. I'm guessing this is related? I checked the proxmox wiki but it hasn't been updated. Thanks!

Not entirely sure what's going on, it works fine with KVM guests. The LXC guest does have several Mount Points, is that a problem? pve-zsync create --source 125 --dest tank/proxmoxbackup --verbose --maxsnap 7 Use of uninitialized value $stor in concatenation (.) or string at /usr/sbin/pve-zsync...

I have a basic setup where eth0/vmbr0 are the "WAN" connection in a pfsense install and vmbr1 is the "lan" interface all vm's share and use the pfsense vm to route to the internet. Everything works great except for 1 exception. The proxmox vmbr1 interface has an IP of 192.168.2.3, and every VM...

In this thread for pfsense they also discuss turning off checksumming on the proxmox host as well: https://forum.pfsense.org/index.php?topic=88467.0 Is that something you also recommend doing, or is doing in on the VM side sufficient? I haven't been able to find clear instructions on how to do...

Awesome, can I ask which version of freebsd? And also with hardware offload switched off only in the guest or also in proxmox?

Sorry to bump an old thread but i'm curious if anyone has noticed if any progress has been made on this? Is freebsd virtio still horribly slow on proxmox/kvm?