austin

Ok so everything went smooth as butter following the older spaceinvader video the only weird part was when I downloaded OpenCore configurator it said this is an older efi, i just ignore this and continued following along. The next "weird" thing was that the EFI partition didn't include the NvVars file, just the EFI folder. Again, ignore and copied it to the correct partition. After this, I shutdown and followed some of his edits to the VM helper script (adding name, etc). I tried adding some CPU's and updating RAM and I've never been able to boot again. I get this error in the log at the moment: 2024-01-13T22:46:40.073081Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] 2024-01-13T22:46:40.073111Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.fma4 [bit 16] 2024-01-13T22:46:40.074095Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] 2024-01-13T22:46:40.074103Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.fma4 [bit 16] 2024-01-13T22:46:40.074948Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] 2024-01-13T22:46:40.074955Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.fma4 [bit 16] 2024-01-13T22:46:40.075725Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17] 2024-01-13T22:46:40.075732Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.fma4 [bit 16] qxl_send_events: spice-server bug: guest stopped, ignoring I tried changing the topology setting in the helper script and changing the custom to "unraid" neither of those changes made any difference. So I also tried putting my CPU's and memory back to where they started thinking it was related to that and it seemed to still have an issue. Any ideas what I can try or do I have to start over all together?

Overview: The Falcon Player (FPP) is a lightweight, optimized, feature-rich sequence player designed to run on low-cost Single Board Computers (SBC). It was originally created to run on the $35 Raspberry Pi, hence the middle 'P' in the short name but now the FPP supports many more systems. It is still mostly commonly used on a Raspberry Pi (Zero, 2, 3, 4) or a Beagle Bone (Black, Green, Pocket). The FPP shorthand is still used but it is now just called Falcon Player. FPP aims to be controller agnostic, it can talk E1.31, DDP, DMX, Pixelnet, and Renard to hardware from multiple hardware vendors. Using various capes, FPP can also be a controller on P5 and P10 Matrixes, or strings of ws2811 pixels. Application: FPP - Falcon Player GitHub: https://github.com/FalconChristmas/fpph

I haven't heard anyone talk about this, but makes sense to do. Let us know what you find out, as i would do the same.

You'll probably want to contact the developer in Discord channel. I'm not able to provide support for the app itself, just the unraid community app configuration in this thread.

Fixed in the XML. Thought I fixed this last night but realized I didn't. Should work now.

Overview: StreamMaster is a versatile streaming application that allows users to import an unlimited number of M3U and EPG files for a wide range of streaming content. The platform offers robust analytics tools for tracking performance and gaining insights, as well as customizable logos for a unique user experience. It also features seamless integration with popular streaming platforms like Plex and Emby. Built on the latest React and C# core technologies, StreamMaster ensures fast and reliable streaming across various operating systems. Additional features like robust proxying and the ability to have multiple clients on a single backend stream make it a comprehensive solution for today's streaming needs. Application: StreamMaster GitHub: https://github.com/SenexCrenshaw/StreamMaster Discord: https://discord.gg/zACbUp6XvW

Following because I'd like to give this a try as well

Seems like most of the official documentation around hardware is deprecated and not really very usable. I last built an unraid server in 2012. It's still going strong but it is using a bunch of random drives from all PC's and the cache drive is throwing errors, another over heats all the time, but it still hums along quite nice with a AMD FX processor. However, I'm trying to just start to understand what is required these days for an effective unraid machine. I've tried reviewing some forums here and watching some guides on youtube, but really, what are the key features you need to get the best bang for your buck? I recall when I bought the AMD processor there was something about core virtualization and making sure it was compatible. Does stuff like that still exist? Do I need to make sure it can do something like GPU passthrough, special PCI lanes for speedy cache drives, ECC memory? What would you tell someone looking to build a "bang for your buck" build to look for? I'm sure the main question is, well it depends on what you are doing. Let's assume running a VM, maybe a few docker images, storage, and maybe attempting something fancy like running Starcraft 2 remotely (is that even a thing?). Anything that'll get me down the right path would be super useful. Right now i'm at the throwing darts at the wall stage and don't know where to start.