jonp

We just put in an order for 5 that we should get some time in March I think. These things look awesome. Glad to hear you're liking yours so much!!

Exactly! It's one of the reasons I want to build a comprehensive hardware database for HexOS (obviously opt-in). There are a lot of details with hardware that aren't exposed when buying that we could start to map for folks who took the plunge without the insights. Boot up, run a little scan of how the IOMMU groups layout, what happens when you try to pass through a GPU, etc. and then create a filterable database for users to search and get more details. So many ways to improve UX here beyond just the software.

QFT! VFIO and specifically GPU pass through has been a major focus of mine for almost a decade of my career. VFIO is awesome, but a lot of hardware is just not built with it in mind. For example, when you shut down a VM, you're not really shutting down any hardware. But a lot of GPU vendors didn't bother to put a reset mechanism into the GPU because the reset would be a full shutdown or reboot of the physical hardware. So when you go to start a VM back up with a GPU like that, it just hangs or doesn't initialize the display. Not sure how prevalent that is today, but between 2014-2022, I remember it being all too common. Thankfully projects like this one (vendor-reset) have added a plethora of quirks that help overcome this for troublesome equipment, but it's not a silver bullet. Other complications can arise just by turning on the IOMMU setting in the BIOS. I remember there was a time where if you had a Marvell storage controller and you just turned IOMMU on, the whole host would crash. Not sure if that's still the case in 2025 with more modern stuff, but it wouldn't surprise me if there aren't still some examples of that out there. Bottom line: I don't think most hardware manufacturers fully test virtualization (especially IOMMU) on consumer-grade electronics. So "your mileage may vary" is an appropriate statement here. I swear I could write a novel about VFIO, GPU pass through, and IOMMU groups...

We can do that, but our use-case for internal dev/testing of UI/UX/Deck is a little unique. We will use fully virtual storage devices for all of this, which means we're not going to be doing testing in this environment against hardware issues with storage devices. We test storage device failures/replacements/expansions mainly with dedicated physical hardware. That said, it would be possible for us to pass through the entire storage controller to VMs for a more native experience. Might need to ping Tom Lawrence for some advice on this setup 😉

I love this idea and wonder if there is an API we could attach to that would let us report the power usage through our UI to avoid needing another app. Definitely stickying this for the future.

We are actually building a Proxmox setup to run multiple HexOS VMs for additional developers we are hiring (for access to dev/test). We're actually newbies at Proxmox, but it looks pretty straightforward!

Yes I believe we have this ability. I’ll look into it!

Timing is perfect for this topic. I appreciate you all waiting until 2025 to bring this up. The road to 1.0 blog post was just a way to set our targets out there. We didn't communicate a specific timeline because we honestly had no idea how much to estimate we would sell at launch, which would directly in turn impact our ability to expand the team and impact our timelines. We just felt that, conservatively, we would do well enough to deliver the blog post roadmap in 2025....yeah....we had no idea what was about to happen ;-). Beat our expectations by about 5x. With the success we've had, we just onboarded three new people to the company in the past 30 days, with a goal of bringing on at least two more developers in 2025 as well and potentially a few other admin hires. This has completely thrown our previous "back of the napkin" roadmap out the window. Let's just say, we're not going to be talking about features just for 1.0 anymore. You guys have given us enough runway to plot out PAST 1.0. Give us a little more time to get our bearings as we onboard new staff, prepare new development environments, implement new systems, and role out our first software updates. More communication coming soon.

Don't you worry! We have plans for you brave testers out there to keep you on a "beta" track that lets you test out the goodies as we're building them. Basically we will have feature-tagging so we can enroll certain users in new beta features for testing before they are ready for the stable track. When we get to that phase, more will be revealed 😉

Also there is a contact us form you can access at the bottom of this site or just email support@hexos.com.

Saw your post and I’ll add this to the list for us to curate. Seems like a good one!!

Just an fyi, we are not in a position to adjust the system requirements right now. In the future we may be able to provide lower recommendations based on use cases where less features are required. E.g. if you just need a basic file server, no apps, VMs, or other services, it may be possible to run the system reliably with less than 8gb of RAM. That being said, this likely wouldn’t happen until after 1.0. For now, feel free to experiment but if you have “out of memory” issues, you know why 😉

Definitely interested in this. Main concern is scammers. That said, I bet there is a happy middle ground. I would want to consult with our legal team before I commit to this, but I’m certainly not opposed to the idea.

Hey, I think you have some notifications that need clearing 😉

Hi there and sorry for the trouble you're experiencing. Not sure how your post got deleted but I will look into that. We are aware of this install issue affecting certain users and are looking into a fix. Can you repost your issue and send me a DM with a link to it so I can track it?

Screenshots!!

Great feature idea. Having not spent more than 3 seconds thinking about the security implications, I totally see us doing this ;-). The tricky part is granular access control. Maybe you want them to see that server and even do a few things, but maybe you don't want them to be able to do EVERYTHING such as delete or shutdown/reboot. But I think we will have a solution for that too 😉

Yeah we probably should make a change to this policy. I'll review forum settings this week to lax this up a bit. Not looking to create more administrative burden for ourselves.

While I can't get into details just yet, there are multiple security-specific features planned for the future to improve our posture. This is simply the only way to functionally provide this right now with the current TrueNAS SCALE API. That being said, I greatly appreciate having those that are security conscious here on the forum and thank you for suggesting a solution with your post.

It's ok. The update you're seeing right now is 24.10.0.2. .1 and .2 are both hotfix-class releases with minor fixes for specific issues as documented here: https://forums.truenas.com/t/read-notice-truenas-scale-24-10-0-1-and-24-04-2-4-are-now-available/23413 https://forums.truenas.com/t/truenas-scale-24-10-0-2-and-24-04-2-5-are-now-available/23664 Updating to these shouldn't cause any issues with HexOS, but generally speaking, we do not want users updating using the SCALE UI. When you do, we won't provide direct support for issues. All of this said, it is our fault for the current confusion about updates because of how notifications work in the UI today. We pass through notifications directly from SCALE in the current beta, but in the future, we will parse out update notifications in HexOS in favor or our own mechanism. This is one of my shortlist items for improvement in the next HexOS beta update, which as a reminder, does not require you to download anything to your server.

Email support@hexos.com and we'll take care of this for you. We weren't planning to allow this originally, but this use-case is all too common. So long as the transfers are done in a reasonable time-frame after purchase, I think this is fine. The issue is we do not want to create a black market for reselling lifetime licenses. That isn't supportable for us. I will update the FAQ/terms likely tomorrow with better verbiage to address this.

HEY! I figured out how to make search more accessible! It's now a top menu nav item. Should help quite a bit.

I'll get back to you today. We implemented a new support messaging and management system and it's been a bit of a learning curve.

Yes supporting migration from TrueNAS to HexOS is planned.

This warrants further comment but just wanted you to know it's been seen and we fully acknowledge this need.