[Simpler / Easier PCI Device Pass Through for NON-GPUs]

On 5/14/2020 at 1:43 AM, saarg said:

You need to stub them before they appear in the list.

Install the VFIO PCI Config plugin and stub the devices there. You can also append the ID to the syslinux.conf file, but the plugin is probably easier.

Cool! That subbed it correctly.

 

Is there a place I could request a "multifunction" checkbox be added when selecting multiple functions of the same device? Within my VM, the drivers are expecting two functions on one device (I don't ask why), and by default without the "multifunction" flag, they will show up as two unique devices within the Guest....great for SRIOV where the functions are usually two "devices", but in my case they're not

[Simpler / Easier PCI Device Pass Through for NON-GPUs]

On 5/8/2020 at 11:29 PM, saarg said:

There is already support for it. All you have to do is stub them.

When I am in the GUI for VM creation I can't select any of my PCIe devices (USB show up fine). I have to manually "virsh edit <vm_name>" and manually add the device/function assignments. Not the worst thing in the world. Am I doing something wrong? I am also on the free trial at the moment, kicking the tires.

[Simpler / Easier PCI Device Pass Through for NON-GPUs]

Is there an ETA for getting non-GPU devices selectable (or at least IOMMU groups)?

[VM RAM limitation]

On 3/10/2020 at 12:14 PM, johnnie.black said:

No problem, I expect this to be fixed next release.

Awesome! He's not the only one with >1TB of RAM.

 

Is there an ETA to the fix?

 

Thanks!

[Does the parity drive density ever limit total data density?]

49 minutes ago, jonathanm said:

Keep in mind though, that as you increase the number of drives, your risk increases. When doing a parity reconstruction, every other drive is used to reconstruct the failed drive. The more drives you have, the more the risk that another drive will fail while rebuilding the first failed drive.

 

The parity drive does NOT keep any of your data. If you lose a drive, it does the maths using ALL the other data drives plus the parity drive and solves for the missing bit. If you lose 2 drives and you only have 1 parity drive, the answer is no longer solvable, the missing bits could be 1's or 0's.

 

Here is the full explanation.

https://lime-technology.com/wiki/Parity

 

Keeping up with drive health and being sure to replace drives at the first sign of failure is critical.

 

Ahhh, that page is the answer. So the parity drive, as the name implies, only stores the calculation of all the drives parity on a bit by bit basis. Since all the drives will only have 10TByte, and a parity calculation's result is one bit, then no matter how many drives exist, the parity drive will never use more than 10TB. Got it; thanks.

 

 

 

[Does the parity drive density ever limit total data density?]

Hi all. This question is a twist on "how big of a parity disk do I need?". I understand that my parity drive limits the density of the disks I can use for my data (i.e. a 6TB Parity disk limits any individual data disk to 6TB in density). However, my question is related to total data density.

 

For example, if I have a 10TB parity drive, is there a limit to the total number of 10TB data disks? I imagine at some point the parity syndrome/calculations for all my data drives will exceed the capacity of the Parity drive.