Search results for query: n5105

Good afternoon, maybe someone has a successful solution for activating IGPU for VM via Proxmox on N5105 (Beelink U59 VT-D and VT-X box in Bios are activated but system agen reports that VT-D is Unsupported)

Good afternoon, there was no solution with iGPU forwarding from n5105 to VM?

Hi Networking newbie with zero experience with virtual environments. I purchased a N5105 mini PC (4GB ram + 128gb NVMe) and plan to run both OPN sense and Home assistant using proxmox. I don't really understand how the IP addresses will work and was hoping someone will help me understand the...

Is there a reason you're running an alpha build? Is XCP-NG 8.2 LTS not stable for you? How do you like it compared to Proxmox (and ESXi if you've used that too)?

My intel NUC with N5105 is running XCP-NG alpha 8.3 since release, I can report the freezing issues - so far - disappeared. I am running 3 VMs Ubuntu 22.04 with Docker, also everything is surprisingly stable being an alpha. Quite happy so far. My older NUC gen 8 and 6 are on Proxmox and they are...

I am also having this issue :confused: I am running proxmox on an Intel Celeron N5105 machine with 4*Intel i226-V 2.5G NICs. On proxmox, I am hosting pfsense 2.6 (in use as my firewall) and also LCX for test purposes. For pfsense, I used virtIO bridges due to pci pass-through somehow is not...

...doesn't in my case, posted my experiences a couple of days ago in this thread. And there are others - it seems down to the processor (at least N5105/N6005) and a combination with the 5.1x kernel and c-states. I ran into issues running both bare metal (couple of times a week) and later same...

Did that crash occur only once? Or did your time between failure go back to 8-24 hours after the first crash? It somewhat scares me, that even the "reference design" does have this error... Otherwise I would have thought it's a bios error in cheap third party producers, but that way it feels...

...here, had VMs crashing almost daily on a fresh Proxmox installation and they had been running for almost a month after updating to kernel 5.19 and microcode. This night a VM crashed again (always the same one, Debian 11 with Docker)... I'll be trying the C-State fix. Intel NUC with N5105 CPU.

This would be great news, having the same processor so far have been able to mitigate it but randomly - like every 3 weeks - still a vm freezes. How do you install the kernel 6.1? I was on edge (fabian) kernel, but for now 6.1 is not available yet. Thanks

Are C-States and Enhanced C-States enabled in the BIOS? Is ASPM set to Auto for all PCIe ports in the BIOS? What CPU governor are you using in proxmox? What do your thermals look like in proxmox? Install thermal sensor package on proxmox: apt install lm-sensors run it: watch sensors Check CPU...

Things seem to be running well since upgrading to the 6.1 kernel. Have a CWWK N5105 running Proxmox (6.1 kernel) and an OPNsense VM. Currently at over 2 weeks uptime. No microcode loaded and BIOS settings are basically default (didn't change C states or anything like that). OPNsense is using...

My Topton unit (N5105) seems stable for now (at least for 5 days). I've recently updated Kernel to 5.19 and microcode to 221108, but those things didn't help. In my configuration now I've set: - GRUB_CMDLINE_LINUX_DEFAULT="quiet intel_iommu=on intel_idle.max_cstate=1 mitigations=off" - Updated...

When pfSense based on freeBSD has a kernel panic it creates a crash dump that is downloadable from its web interface.

Where do you get these backtraces from? Running on a odriod h3 with a n5105 and also a frozen vm. in my case it's a Debian/dietpi vm. RHEL and home assistant seem to work. Kernel 5.19. Installed microcode yesterday and it seems to make it worse.

HSIPC with N5105 and Jasper Lake here... Ran fine for approx 5 days with OpnSense and a Debian DockerHost VM, on new year the crashes started... Right now I am running stable 4 days now with: Kernel 5.19 New Microcode Governor on Powersave Additionaly I changed the VMs CPU Type to KVM, but...

I was considering buying an Odroid H3+ with N6005 or N5105 and I've seen mentions of intel C-state issues. I don't know the details, but your symptoms sound similar. No clear solution, but disabling C-states or changing kernel version seems to have helped for some.

I followed this guide and my vm:s have been stable for about a week now with kernel 5.19.17-1. Today I experimented with removing intel_idle.max_cstate=1 and had a crash within 3 hours. I strongly believe cstates is the issue, at least on my setup. I'm running a N6005. domoticz and pfsense as...

Could you elaborate more on your statement? I have VMS random rebooting the hypervisor remains up. only VMs hanging or rebooting randomly every 2-3 days or 1 day. I updated to kernel 6.1 today. If your hypervisor (the host OS) reboots it might be hardware related?

...some days until the crash. I upgraded to 6.1.1 Kernel now (microcode updated, C-States enabled) and it runs 5 days at the moment. I have a CWWK N5105 (v5) with 4 i226 NICs. So the crash seems not Proxmox related. KVM internal error. Suberror: 3 extra data[0]: 0x0000000080000b0e extra...