Search results

I hoped either to get finally rid from NFS, but after reading this, virtiofs seems to be senseless :-(

Yeah test repos :-)

I seen that 6.14 is available xD How dangerous is it @Thomas Lamprecht Should i wait for zfs 2.3 before upgrading and testing? :-)

"Does QEMU 9.2.0 affect the CPU usage of Windows?" if you use the "host" profile -> NO But other Profiles should be updated either -> so 99,999% no either. "Does disabling HPET timer affect the performance of Windows virtual machines" Dunno, some years ago where Intel had broken timers...

sorry, i missreaded. but replyed you on the other thread.

IGPU needs at boot some firmware injected. [drm] Finished loading DMC firmware i915/dg2_dmc_ver2_08.bin [drm] GT0: GuC firmware i915/dg2_guc_70.bin version 70.36.0 [drm] GT0: HuC firmware i915/dg2_huc_gsc.bin version 7.10.16 It maybe the reason youre getting issues. Im not sure if this happens...

Try to disable multicast snooping on the bridge. I need todo the same for example to get ospf properly working, ospf works without either but not reliable for me on opnsense for example. auto vmbr0 iface vmbr0 inet static address 172.20.1.6/24 gateway 172.20.1.1...

Oh just for the sake of completeness, everywhere i use passthrough, im using q35. Im using q35 even for almost everything, i think there may be 2-3 i440fx vms out of ~40-50. That time i started to passthrough devices it wasnt possible with i440fx, there was at that time some bug on freebsd...

PS, i forgot, can you change error correction mode on your switch? If yes, try to switch between them and check, maybe the module comes up then. I had one case, where changing fec brought a link up again.

ethtool --module-info enp1s0f1np1 Identifier : 0x03 (SFP) Extended identifier : 0x04 (GBIC/SFP defined by 2-wire interface ID) Connector : 0x07 (LC) Transceiver codes ...

We/i dont have anymore any x520 cards, however if you want transceiver recommendations, it's hard, because almost everything worked here great. For the most part, we use flashable transceivers from Flexoptix. Those are amazing, because you can reflash them to any brand you need. If it has to be...

if you added your new values to /etc/modprobe.d/zfs.conf (or any other file in modprobe.d) you need to update initramfs and update-grub or proxmox-boot-tool refresh (or simply both) then reboot. One of those you have clearly missed :-)

Everyone should simply use "host" as CPU. The only exception is, if you run a Cluster and all nodes in the Cluster doesn't have the identical CPU Generation. Funny thing is, i have only a single VM in one of my Clusters, that is not working with host as CPU and freezes during migration. On all...

There is no fix. Disabling Wallpapers, changing group policys etc, nothing will help. Its simply a bug, i have the same issue on all Windows 11 Instances (Physical and VM's) where you have more as one Account on the PC/VM. There is no fix. And everyone has the same issue! BTW, This happens...

Yeah it does only in one case, if you migrate multiple VM's/Containers at the same time. But in real life thats almost never the case (at least i never use that), i usually migrate only one vm. If you Shutdown one Server from a Cluster that is in HA, it does migrate only one VM at once either...

Lacp for redundancy, but not for Performance. The only cool thing that you can do is disabling encryption for the Cluster/Migration Network. That makes migration at least twice as fast, but i would do it only if you make a separate closed vlan on the switches. (So that its still safe) I have a...

It's funny, im using pvetest since forever and never had any issues or bugs. Using qemu 9.2 since a week, - changed all Windows-VM's to 9.2 / Linux-VM's are anyway automatically on 9.2 - Have some VM's with passthrough, for NICS's and GPU And everything runs absolutely Perfect on all 11...

I have the same issue on all 7 Proxmox Servers, but only with W11 VM's (i think since the 24h2 update). On all W7/W10/Server 2016/2019/2022, there aren't any issues and everything is Perfect.

Can you try to Pin all your VM-Cores to the same Socket on your host? numactl --hardware So that all Cores of VM1 runs on Socket1, VM2 on Socket2 and so on? Dont forget to shutdown/start the VM or LXC Container after you changed the config. Just for testing, to rule that out.

Do you use primarycache=metadata or something else on zfs?