kode54

Members
  • Posts

    246
  • Joined

  • Last visited

Everything posted by kode54

  1. Bumping with a report that I found the "cause" of my problem. It's purely down to trying to use multiple virtual machines on a non-ACS configuration. I need either a Core Extreme or Xeon board and processor to have full ACS support, which would allow splitting up PCIe roots and GPUs in adjacent slots. I'll consider that next time I'm in the market to buy a new motherboard and processor, and likely also memory.
  2. I am trying to insert my Intel HD Audio family device (8086:1E20) into a Windows 10 VM, and the VM is either not seeing it, or seeing it disconnected from the machine. lspci on the host displays that it is device 00:1b.0, and a listing of the IOMMU groups shows it's in its own dedicated grouping, without forcing a regrouping. Do I need unsafe interrupts to be enabled? E: Another one I dealt with myself. I had to remove the existing device entries from before I migrated the native SSD installation inside the VM, and re-detect hardware.
  3. I may try that if I'm desperate to find if the slot works for a separate PCIe root, but it wouldn't be a permanent solution, as this case has absolutely nowhere else to put a video card, especially not a full length one like this.
  4. In my current case configuration, I cannot test any other x16 ports, as the bottom slot is blocked to a single slot by my current case. I have decided to give up on importing two separate video cards into separate VMs at this time, and will consider using those two slots with the one Windows 10 VM in the future, if I ever get more than one identical video card for the purpose. The problem was that the two slots share an IOMMU group with the PCIe root node, so they cannot be broken up without ACS overrides, and even with overrides, each individual video card slot still needs the one root node.
  5. Resurrecting this old thread again, to point out how you can easily create a RAID0 cache from the SSH console, in the event that you have a weird setup, like mine. I have a 256GB SSD and an older 128GB SSD, and the web interface was simply showing that there was no balance in the arrangement at all. It was creating an unbalanced RAID1 of a 192GB capacity, with 2/3 of the 256GB drive mirrored by the other 1/3 of the 256GB and the 128GB drive. First you need to take your array offline, and configure the cache to the number of drives you wish to merge. Then you need to find the /dev/sdx nodes for the two or more SSDs you wish to add. Then you need to run the following from a bash prompt logged into unRAID: mkfs.btrfs -d raid0 -m raid0 -f /dev/sdx /dev/sdx <etc> Where /dev/sdx items listed above are the cache drives, in the order you want them in. These steps are only necessary if you want to format the cache manually. A rebalance may work now, but there's one addition you need, as of some version of the btrfs tool, is the -f switch, to force conversion. This step is necessary now, as it will otherwise error out at the attempt to convert down to an insecure RAID0 array.
  6. I ran into a similar issue with my unRAID server. In my case, the first two x16 slots are paired with the PCIe root controller, so it's not possible to split them up into separate IOMMU groups, and the third x16 slot can't be tested in the case I have since there's no room for a double width card in the bottom slot. So, in all likelihood, if you are trying to split separate x16 slotted video cards into separate VMs, you will probably not succeed, as it depends on the motherboard.
  7. I am trying to split two separate video cards up on my MSI Z77A-GD65 motherboard, and when they're in the top and middle x16 ports, they both end up in the same IOMMU group with the PCIe root controller. I've tried ACS override, but that just results in outright failure when attempting to bind either card.
  8. I am attempting to install an operating system from its setup ISO, and the software does not have PS/2 mouse support. It does appear to respond to the keyboard, however. I am unable to change the mouse or keyboard entries to USB type. Changing them results in an identical pair of mouse/keyboard options appearing in the XML, only of PS/2 type. I may just give up and attempt to install the software with keyboard only for now. EDIT: I found what I needed on the correct guide. -device usb-mouse and -device usb-kbd