Jump to content

toastman

Members
  • Content Count

    53
  • Joined

  • Last visited

Community Reputation

5 Neutral

About toastman

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Modern cards are pretty good about idling-down when not in use. My guess is the card may use <5 watts just to keep the 'idle' circuits energized, but its really not enough to worry about.
  2. "Failed to find romfile" Are you absolutely sure the file is where its looking and its name is correct (capitals matter). You could try changing the filename to something a little simpler as well - I don't know how the code handles an equals sign, for example. Its probably fine, but I like to address the simple things first
  3. You can also download it straight into the VM and extract the drivers from there. That avoids any messing around with the VM settings. That being said, if everything is working properly there usually isn't much reason to update the drivers.
  4. Is your VM trying to hibernate or go into standby? I've had issues with VMs waking back up when they do.
  5. Does anyone know why SSD Trim spins up my whole array rather than just being confined to the cache drive?
  6. Are you referring to passing through the 2 ports on the motherboard, or do you have an additional dual-port NIC to pass through?
  7. If it doesn't let me delete it, I know its in active use. I have a passthrough USB card, so I don't delete that otherwise I'd lose my KB/mouse. Interestingly, I delete them rather than disable them, and some come back on a restart, but not all of them I'm not sure if it makes a difference anymore but its still part of my setup process: XML edits: 1. Enable HPET 2. Enable multifunction='on' for the GPU and GPU Audio and set the bus appropriately 3. KVM=hidden 4. Disable the hypervisor CPU flag VM itself: 1. Let windows install the GPU drivers. I don't game much on the VM so I've never seen a need for the newest 2. Delete unused USB root hubs. 3. Update all virtio drivers 4. Ensure 'exclusive mode' is enabled for audio That is part of my regular setup process. I can't tell anymore which makes the biggest difference but I had awful audio latency and CPU idle (15-25%) until I did at least the HPET and deleted the USB root hubs.
  8. I cannot for the life of me get speeds faster than 11MB/s. My server is on a 300Mbps (up) connection, the Windows client is on a 300Mbps (down) connection, and are located two blocks away from each other. I don't know if its limited to Wireguard. I tried using FileBrowser and it was similarly limited to 11MB/s. Makes me think something somewhere is thinking there is a 100Mbps link somewhere, but my VMs can each achieve 300Mbps speeds to speedtest.net. Anyone have any ideas?
  9. Are you doing any custom XML edits?
  10. That's "normal". unRAID can't reset the card after the VM stops using it. But it can reset it after a full server reboot. So you're stuck in the situation where anytime you power down the VM, you need to reboot the server before powering on a VM that uses the card. If your BIOS is up to date, do a search for 127 errors. There are a LOT of posts on here about that
  11. Do you have the latest BIOS for the motherboard? There are issues with passthrough that was only fixed recently
  12. Try using i440fx/Seabios or a Q35 older than 2.6
  13. When you say "horrible CPU usage" are you referring to idle usage, or problems in normal operation? I had idle usage of 10-15% and I had to set <timer name='hpet' present='yes'/> (you have it set to 'no') to get it to drop down to 0-1% at idle. In a previous VM, I also had to delete unused USB root hubs in the VM device manager. I don't see any hyper-v settings enabled in your XML. You need those for stimer, etc. My xml for comparison <features> <acpi/> <apic/> <hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vendor_id state='on' value='none'/> </hyperv> </features> <cpu mode='host-passthrough' check='none'> <topology sockets='1' cores='4' threads='1'/> </cpu> <clock offset='localtime'> <timer name='hypervclock' present='yes'/> <timer name='hpet' present='yes'/> </clock>
  14. Its possible it is that Dell stripped that option out of their BIOS... Check to see if there is a BIOS update Check every entry for something that looks like VT-X, VT-D, and Virtualization Technology. They all need to be enabled.
  15. Disabled within the VM, or did you delete the section in the XML? If you deleted it within the XML, just create a new VM, then copy-paste the relevant XML settings over to the 'old' VM If in the device manager in your VM, just go in (using VNC) and un-disable it