Search results

  1. M

    ERROR: Backup of VM <id> failed - PCI device <device> already in use by VMID '<id>'

    Thanks for your response. I've raised https://bugzilla.proxmox.com/show_bug.cgi?id=6189
  2. M

    ERROR: Backup of VM <id> failed - PCI device <device> already in use by VMID '<id>'

    Thanks - are you saying that essentially right now this would have to be a new feature, and there's not a recommended way to work around it? Where's the best place to formally request such a feature? Also, would an alternative be for passthrough failures simply mean the backup was tried without...
  3. M

    ERROR: Backup of VM <id> failed - PCI device <device> already in use by VMID '<id>'

    Is anyone able to help with this please? I've not been able to find anything other than a workaround.
  4. M

    ERROR: Backup of VM <id> failed - PCI device <device> already in use by VMID '<id>'

    Sorry to bump this, but curious how other people manage this? All I can think is either you simply have to script bringing down all hosts the share a PCI resource before backup (not ideal), or there's some way to script removing the resource as a dependency before and after backup (if it's not...
  5. M

    ERROR: Backup of VM <id> failed - PCI device <device> already in use by VMID '<id>'

    I got the following error when backing up overnight: ERROR: Backup of VM 114 failed - PCI device '0000:15:00.0' already in use by VMID '107' Now I know why this is - just as it says, the PCI device (a GPU in this case), is already in use. However, I wonder what the recommended solution is? I...
  6. M

    Backup notifications only on error

    Thanks for this - your solution came near the top searching for "email notifications". I wanted to add to the feedback that this is a bit confusing: 1. It totally surprised me my email provider (Fastmail) even allows this through! SMTP comes up as a Fastmail SMTP, and I had no idea this was...
  7. M

    Whole system rebooting when I restart a particular Windows 10 VM from host

    Sorry to bump this - but any ideas where to start on this one please? I found that eventually this started affecting even the clone. So no idea what's happening specifically with a "restart" of VM from Proxmox host.
  8. M

    Whole system rebooting when I restart a particular Windows 10 VM from host

    I've found that selecting "restart" on a particular Windows 10 VM from Proxmox UI will freeze and restart the whole system. To start with I thought I selected the wrong thing, and restarted the node. However, I've found this is reproducible. The only different log I get from a normal VM restart...
  9. M

    Proxmox installation stuck on 3% "Creating LV's" PLEASE HELP GUYS

    I just found this thread Googling "proxmox create lvs stuck". I see it was started a couple of years ago, but then there's been a few posts, all regarding the N100. I've installed Proxmox dozens of times and never seen this, so I wonder why it's an issue just on some of these N100 mini PCs...
  10. M

    [SOLVED] Windows 10 VM - memory errors when passing through GPU, after upgrading to Proxmox 8.2

    Thanks @dcsapak! Blacklisting worked. Not sure how I missed that Google result - but I see it was from two years ago. I wonder what changed that blacklisting is now necessary, when it wasn't (or didn't appear to be) before?
  11. M

    [SOLVED] Windows 10 VM - memory errors when passing through GPU, after upgrading to Proxmox 8.2

    Thanks @dcsapak I did a complete fresh install straight to 8.2, so I don't have the older kernels. Whatever was latest in 8.1 definitely worked. Right now I have this: Linux pve-maxi 6.8.4-3-pve #1 SMP PREEMPT_DYNAMIC PMX 6.8.4-3 (2024-05-02T11:55Z) x86_64 GNU/Linux I also tried the only...
  12. M

    [SOLVED] Windows 10 VM - memory errors when passing through GPU, after upgrading to Proxmox 8.2

    I'm trying to run a Windows 10 VM clone from a template I've been using absolutely fine. When I passthrough an Nvidia GPU I get these errors in the logs: [Fri May 17 08:31:12 2024] x86/PAT: memtype_reserve failed [mem 0xf800000000-0xf801ffffff], track uncached-minus, req uncached-minus [Fri...
  13. M

    Windows 10 guest stutters during SMB file copy

    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...
  14. M

    Windows 10 guest stutters during SMB file copy

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

    Windows 10 guest stutters during SMB file copy

    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.
  16. M

    Windows 10 guest stutters during SMB file copy

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

    Windows High DPC % Usage

    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.
  18. M

    Windows 10 guest stutters during SMB file copy

    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.
  19. M

    Windows 10 guest stutters during SMB file copy

    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...
  20. M

    Windows 10 guest stutters during SMB file copy

    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...