Jump to content

jonp

Administrators
  • Posts

    627
  • Joined

  • Last visited

  • Days Won

    149

Everything posted by jonp

  1. 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.
  2. 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...
  3. 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 😉
  4. 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.
  5. 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!
  6. Have a team meeting scheduled for this PM to discuss this morning’s outage, the login issue, and a better notification message. Definitely some room to improve UX here.
  7. Right now the team is entirely focused on bug fixes, QoL updates, and pool customization. When we go to shift focus onto our next major feature, we will also select another app for curation (maybe a few). We specifically started with Plex because it’s honestly A) one of the most popular and B) one of the most demanding for configuration. By starting with the hard stuff, we can really focus on honing in support and getting that experience just perfect as well as set a template for all future apps to come. As an example of this, we are very focused on improving the plex experience already. There are issues with remote access, resource assignment, and GPU-assisted transcoding. So those types of things will likely be addressed (at least in part) before we add another curated app. That being said, I am hopeful to really start cranking on a wider App Library sooner than later. Apps are one of the most important features of the product.
  8. We are in phase 1 for apps right now, which means we are curating them by hand. Phase 2 will bring in additional community developers to help further curate. Phase 3 is offering the ability for users to load custom docker containers outside our curation.
  9. Yes I believe we have this ability. I’ll look into it!
  10. This is our first update yes. Doubt we will have another this week unless it’s a hotfix.
  11. Hi there, There is nothing you need to do to receive the update. We've updated the command deck and you automatically receive the latest by logging in. In the future, we will have full OS updates that require a download to your local server, but we haven't reached that point yet. When we do, we'll add an update mechanism to the settings page.
  12. No and honestly I really don’t care what browser anyone uses but I rarely see edge and it just seemed like an easy / fun troll tbh 😉. I hold no ill will towards any browser or platform. Use what you like! I also like quite a bit about Microsoft, though like with any mega tech corporation, it has its blemishes. I’m definitely still a PC guy through and through.
  13. 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.
  14. 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 😉
  15. Also there is a contact us form you can access at the bottom of this site or just email support@hexos.com.
  16. Short answer, yes. This was a pretty quick update today and we were expecting 0 downtime. Reality is I think it was only down for minutes before back up. That said, future maintenance windows will be announced in advance to give people time to prepare. This was mostly backend infrastructure and a few small aesthetic things like fonts. Nothing worth writing up in a release notes post. This is NOT the update I've been talking about since December. The team is actively working on a bugfix release and we're hoping to publish it by end of next week.
  17. As you will notice via the orange community announcement here, we are actively undergoing a maintenance window for the Command Deck to stage if for future updates. Some users will find themselves logged out of the deck while others may not. We will update this message once maintenance is complete. Thank you! UPDATE: As of 2:00 PM CST, Maintenance is complete.
  18. Saw your post and I’ll add this to the list for us to curate. Seems like a good one!!
  19. 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 😉
  20. 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.
  21. Hey, I think you have some notifications that need clearing 😉
  22. 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?
  23. LOL! So true...
×
×
  • Create New...