scorcho99

Members
  • Content Count

    131
  • Joined

  • Last visited

Community Reputation

15 Good

About scorcho99

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

  1. I like this idea. I don't even really see why btrfs needs to be involved though. You just need the concept of a second simulated failed disk that has the file that failed hash check. That dynamix file integrity plugin could probably be linked up to that. Make sure you keep "write corrections to parity disk" off I suppose you could do it now by temporarily unplugging the disk but that is hardly seamless.
  2. There's a third party (asmedia) PCIe to PCI bridge listed in your first post. So the device is actually a legacy PCI device with a converter chip basically. Not a lot of people try to run legacy PCI stuff but it does work sometimes at least. Maybe try binding the device to vfio at boot if it isn't already.
  3. No. You'd have to handle it in the guest some how in that case, or perhaps some drive image software could be used when the VM was offline. Its the main reason I don't use direct device drive passthrough personally.
  4. @SpaceInvaderOne This is an old necro thread so this might be old news. I run a virtual sound device on my unraid server (ac97) and use it fine through virt-manager with spice to view. I found your post kind of amusing since I used your guide to setup the virt-manager link. Maybe unraid devs added something since your post though that made this possible. If that didn't work I was probably going to use scream audio or some other network sound device but it would be a long clunkier of a workflow.
  5. Try installing the adapter+card in different PCI-e slots. I've noticed the IRQ sharing actually comes into play with legacy PCI devices and passthrough. Its also possible this device is simply not going to get along with PCI passthrough, not all of them do. I think there is also an option in VM settings for "allow unsafe interrupts". I've never used it and am not sure what it does but it might be worth a shot.
  6. Wish they made some of those new cases in white. I'm not interested in building in anymore black hole cases, can't see anything.
  7. @meep I came to the same conclusion on this as you did. The price and availability of working 4 port cards is kind of wonky so rolling your own has some advantages. I use a 4 port mining riser which I bought for ~$15, they're pretty easy to find all over. I seem to have better luck with ones using the asmedia chipset which is what most of them use. Advantages are easier to find and flexibility. You can mix and match devices (including SATA controllers and different types of USB controllers, even video cards). Also you can install 4 port cards instead of need
  8. So you backup my VMs on my cache drive I have a userscript that runs. It shuts down all running VMs, creates a read only btrfs snapshot of the VM directory and then boots them all back up for minimal downtime. Then the backup runs off the snapshot. This has worked fine for a few years. A second share appears in the share list (VMs_backup in my case) whenever the snapshot is active, I can't remember if I actively set this up or it happened automatically. Anyway, I suddenly cannot access this share from anywhere. The base share (VMs) still works fine, it is only the snapshot share th
  9. The secondary slot is going to be a chipset driven pcie 4x 2.0 on that board. 50% performance loss still seems a bit extreme in that configuration but there would be a hit. Regarding your option 1: Try to find an option to disable your CSM in the bios. On Ryzen at least, that seems to swap the primary boot GPU to chipset ports.
  10. Anyone get this working with a more recent version of virt-manager? With mint 20 there is not method drop down (~7:35 in video) to pick TCP. Nevermind, I solved this. Custom "URIs" are created for this behind the scenes. I created a connection on my old rig and copied the text. Example: qemu+tcp://root@192.168.1.99/system
  11. Anyone ever solve this? I'm having the same issue with linux mint 20. Nevermind, I solved this. Custom "URIs" are created for this behind the scenes. I created a connection on my old rig and copied the text. Example: qemu+tcp://root@192.168.1.99/system
  12. Good tip on the uefi shell. I think I actually had to do that when I installed the modded bios to disable write protection or something, I didn't get that far but I did wonder at the time if I could have just used the shell to change the option. I don't know much about bios modding (more than I did now) A guy on win-raid forums created the bios mod for me and I sent him a amazon card as thanks. Anyway, I ultimately decided against using GVT-g, but it was a fun experiment...required me to figure out a lot of pieces I didn't know anything about. It was a death of a thousand cuts for
  13. Is there a reason you have all the acs override options on? I'm mostly asking because I don't know if its required for this chipset or not since its so new!
  14. I tried yesterday to run 3dmark firestrike for first time ever on a z77 and rx 470 with a windows 8.1 VM, seabios based. I got crashing on scan systeminfo as well. So as a sanity test, I installed Windows 10 (1709?) fresh onto bare metal and tried it today and the benchmark ran without any apparent issues. I'm not sure the cause or if it ever worked. I was running unraid 6.8.3, its just on my test rig. I'll have to try and isolate the issue I guess. It seemed pretty stable, I was running heaven benchmark before. The system was having a lot of issues once I tried 3dmark
  15. Are you doing primary GPU passthrough? (You only have one GPU) If so have you tried adding video=efifb:off,video=vesafb:off to your syslinux.cfg? I had to do that to get primary working with my nvidia gpus. Note you will lose unraid console video out early in the process.