Recent content by marcosscriven

Thanks for your help. Here's the output: lscpu Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Address sizes: 48 bits physical, 48 bits virtual Byte Order: Little Endian CPU(s): 32 On-line CPU(s) list: 0-31 Vendor ID...

No definitely not the disk here. Locally copying the same file is way faster.

I just tried the E1000 emulation - although I still see high DPCs, it's not as high as with the virtio driver, and although there's a little jerkiness, it's much more responsive.

I see someone else had the same issue https://forum.proxmox.com/threads/windows-high-dpc-usage.99567/, but unresolved.

Sorry to bring up the old thread, but did you find the solution here? Your post is the top result for "ndis.sys" on here.

Having discovered that DPCs were involved here - it helped a bit with Googling. I thus found a Windows program called latencymon. It reports all green until I run the SMB transfer, and then says there are problems with the "ndis.sys" driver. At 2.5gbit it certainly shouldn't be having problems.

I just tried reducing from 16 to 8 - and I see the same behaviour. To be clear this isn't some very slight latency issue - the whole Windows system becomes jerky and unresponsive at random points during the transfer. Whether it's the hypervisor or Windows I don't know, but it certainly seems to...

Sorry I wasn't clear on the SMB setup. The SMB client is in a Windows 10 VM guest, where the host has a 10gbit connection. I've tried two different SMB servers, both on different physical hardware to the Windows guest I'm seeing this. I perf from the Proxmox host to both the SMB servers show...

Sorry - I ought to know better! Here's the guest config: agent: 1 balloon: 0 bios: ovmf boot: order=scsi0;net0 cores: 16 cpu: host efidisk0: local-lvm:vm-110-disk-0,efitype=4m,pre-enrolled-keys=1,size=4M hostpci0: 0000:01:00,pcie=1,rombar=0,x-vga=1 hostpci1: 0000:15:00.0,pcie=1,rombar=0...

Quick update to this - while running the SMB copy, I see "Hardware Interrupts and DPCs" go from 0 to 8% (total) CPU, which seems to account for the CPU core being pegged. Wondering if that's something to do with QEMU or a native Windows 10 problem.

I have a strange Windows 10 guest issue. I don’t have any native Windows systems to just try it. When I copy a 20GB file over SMB, Windows 10 stutters - not just the mouse pointer, but animations in a running browser (for instance). I tried copying the file locally, while also running iPerf...

It seems odd to be forced to move root and swap off the “PVE” VG, just to be able to have “local-lvm” on a different SSD. So I’d be trading one quirk for another. What’s the recommended way of doing this? I can’t believe I’m the only one that would want the Proxmox root on its own disk, but...

Thanks again - but wouldn't that just then move the problem to the `local` storage?

Thanks - but here's the issue: vgs VG #PV #LV #SN Attr VSize VFree data 1 1 0 wz--n- <3.64t 376.00m pve 1 2 0 wz--n- <118.24g <70.68g I already have a volume group called "pve" - and as I suspected, I can't renamed the 'data' one: lvm vgrename...

Thanks for your help - but I'd like to do the opposite, and make the storage on this new node match the others. Is that not possible from a logical level, if the underlying storage is instead on a different SSD to the pve/lvm volume?