Search results

I was told (three messages above this) you are supposed to put it on the bridge, not the physical interface

It seems like virtio-win-0.1.248 doesn't have proper VirtIO drivers for 24H2. However, E1000E works with Server 2025. Not ideal, but Server 25 isn't fully out yet, so you could use that for testing.

Thanks. And just to be sure, this only affects the Intel e1000e driver, for Intel NICs? I have two very similar HP miniPCs, but the second one has a Realtek NIC. I assume that one doesn't need this "fix"?

Should I add this to my physical interface or my bridge? cat /etc/network/interfaces auto lo iface lo inet loopback iface eno1 inet manual post-up /sbin/ethtool -K $IFACE tso off gso off gro off auto vmbr0 iface vmbr0 inet static address 10.0.1.10/24 gateway 10.0.1.1...

Just curious, does LXC passthrough still keep the GPU to the host? I have it currently passed through to a SeaBIOS VM (and JF itself in Docker in that VM). Would there be any advantage in going LXC?

I know it's an old thread, but thanks! I didn't realize I had to enable firewall both in the LXC Network settings AND in the LXC Firewall settings.

I would add that I since I had only two nodes I also had to run "pvecm expected 1" to actually delete the node (since with default 2 both would have to be online to vote on the removal) https://forum.proxmox.com/threads/removing-cluster-nodes-cluster-not-ready-no-quorum.23622/post-118347

So far I'm at 60 hours myself. (totally stock install, no disabling iGPU power management) Maybe there was an upstream fix that is alread out?

Proxmox 8.0.4 I assume? If this https://gitlab.freedesktop.org/drm/intel/-/issues/9244 issue affects Kernel 6 on Intel 8000 CPUs (now also mobile assuming your issue is the same thing), it might be worth trying Proxmox 7

We will see. Installing PVE right now, see if it survives tomorrow without a reboot. I don't want to disable the iGPU power management.

You could try throwing Windows Server on a spare SSD for a day. If it still crashes, it's hardware.

For some reason yesterday most of this thread didn't load for me. I will need to try the GPU power management workaround to see power consumption figures. I really don't want to run HyperV Other threads https://forum.proxmox.com/threads/proxmox-restarts-randomly.116080/page-2 recommend...

Did you fix this? I also have an issue with PVE crashing on a HP 400 G4 Mini. When I loaded Windows Server, it hasn't crashed in a week. Is there some sort firmware issue with Coffee Lake T CPUs?

Now I can, but I had to use the ACS patch to split my IOMMU groups even further in software Added this to my grub config quiet amd_iommu=on pcie_acs_override=downstream,multifunction Some say this is insecure, but I haven't found another way to do it

Is your HBA in it's own group?

In my case disabling ROM Bar allowed my 2308-IT (well, a 9217-8i) to boot. Thanks!

I second that. Macrium Rescue spoiled me for home use.

Yep, learned that about 20 minutes ago. I had to pick between pass thru of my GPU or my HBA. Fortunately it is possible to pass through the physical disc (why is that not in the webgui?), so I picked that one. Thanks for confirming what I managed to get working (I landed here through Google so...

I can confirm the same issue with a Gigabyte B350Gaming 3 and LSI 9217-8i. Did you ever solve this?

Well, just to be curious I tried to copy over SSH instead of SMB, same behavior, so it isn't Sambas fault. I also tried to copy to the VM itself (VM is on an SSD, those two mirrored disks are mounted in /media) and no transfer speed issues. So there is definitely something wrong with either my...