Twisted

I followed the guide and was able to get my controller to pass to the VM, but I still cant get it into its own IOMMU group. I am current booting in legacy mode and have PCIe ACS override turned on and Downstream selected. Has anyone found a better method? IOMMU group 8: [8086:a148] 00:1f.0 ISA bridge: Intel Corporation B150 Chipset LPC/eSPI Controller (rev 31) [8086:a121] 00:1f.2 Memory controller: Intel Corporation 100 Series/C230 Series Chipset Family Power Management Controller (rev 31) [8086:a170] 00:1f.3 Audio device: Intel Corporation 100 Series/C230 Series Chipset Family HD Audio Controller (rev 31) [8086:a123] 00:1f.4 SMBus: Intel Corporation 100 Series/C230 Series Chipset Family SMBus (rev 31)

@clowrym Thanks for getting back to me. With the shift moving towards cross platform gaming, I think there will be a greater demand for the Bedrock Edition. I am not sure where the project is now. I did see some posts back in November of last year. https://github.com/hexparrot/mineos-ruby

Do you have any future plans to update the MineOS node Docker container to Mineos-ruby? I am trying to find a solution to build a Minecraft server for the Bedrock Edition.

Do you have any future plans to update the mineos-node Docker container to Mineos-ruby? I am trying to find a solution to build a Minecraft server for the Bedrock Edition.

Area 51 - I am hoping to replace the Lime Tech logo with my Area 51 logo in the future.

After following this guide, I can boot up with my graphics card, but it is stuck in 800 x 600 resolution. There is an exclamation point next to the Nvidia display adapter in device manager. If I download the driver software from Nvidia, it crashes the VM. Anyone experience this or have any suggestions?

I have been trying to fix this error for a few weeks and I am stuck. Any suggestions would be greatly appreciated: internal error: qemu unexpectedly closed the monitor: 2018-06-15T04:06:51.898169Z qemu-system-x86_64: -device vfio-pci,host=01:00.0,id=hostdev0,bus=pci.0,addr=0x5,romfile=/mnt/cache/system/domains/vbios/GTX1050.dump: Failed to mmap 0000:01:00.0 BAR 3. Performance may be slow 2018-06-15T04:06:51.912861Z qemu-system-x86_64: -device vfio-pci,host=00:1f.3,id=hostdev2,bus=pci.0,addr=0x8: vfio error: 0000:00:1f.3: group 9 is not viable Please ensure all devices within the iommu_group are bound to their vfio bus driver. XML File.txt IOMMU Groups.txt

Does this work if your cache drive is an M.2 drive with an XFS file system? or do you have to run BTRFS? I only have one drive, so I set it up as XFS.

I had never thought about that approach before. Since I only want my music and docs on an SSD, do you recommend using Sync to move files from the SSD over to the main array for backup as a better option?

The only challenge I have is I have 250GB & 500GB SSD drives. I could send back the 500GB, but I think my data would fill up most of the cache drive at 250GB. I was hoping to find an alternative, so I can use what I have.

Has anyone tried to use a Docker Sync to pull data off of an unassigned SSD and copy it to the main array nightly? I think this seems to be the best option for those of us who have a random stack of SSD sizes laying around.

My challenge is I need redundancy. So i need to put an SSD in the main array or figure out how to setup Sync. So if TRIM support is coming, I am not going to hassle with trying to find an alternate solution.

@Jcloud How do you handle redundancy?

@trurl Thank you for the advice. I was going to go this way initially, but I just bought a 500GB SSD and I have a 250GB SSD laying around and didn't want to send back the 500 for a 250. I am worried 250GB may not be enough space. I already have a 250GB M.2 drive for my VMs and Dockers, so I don't see any other use case for the 250GB SSD. If I cant get Sync to work and TRIM support is not coming, I may just send back the 500GB SSD.

Have there been any updates on TRIM support for SSDs in the main array? I would like to keep my music and documents on an SSD to keep all of my large HDDs (Movie Drives) spun down on the array. I have been trying to setup the Sync Docker to keep it in unashinged devices, but am having no luck. I am curious if TRIM is coming soon to the main array, so I can store my SSD there for now. I am not concerned about write speeds since I will be using a cache drive. My main goals are focused on fast seek times, data parity, low power consumption and drive health.