Fuchsia OS could be edited to also run Windows Programs as Hypervisor

Fuchsia hardware support matrix (2024)

Hey everyone, it's been a while since I've posted here. Hoping everyone had a great Christmas and a Happy New Year!

You can find my hardware matrix here.

Hardware in 2024:

No new CPU hardware has been added. Two devices have been removed. The Acer Switch Alpha 12 and Google Chromebook Go (atlas).

The Acer Switch Alpha 12 was one of the first devices supported by Fuchsia alongside the original Pixelbook (eve) and has been removed from the documentation.

Additionally, the Chromebook build target and documentation have also been removed. The last supported Chromebook was the Pixelbook Go (atlas) released in 2019.

That leaves two official devices supported by Google. Those being the 7th/8th gen Intel NUCs and the Khadas Vim 3.

Software in 2024:

Due to the layoffs in 2023, the workstation project has been deprecated, Google has canceled bringing Fuchsia to their smart speakers along with the cancellation of the full Chrome browser coming to Fuchsia.

The workstation product is being replaced with workbench which will serve a similar purpose.

We intend that workbench will include graphics, audio, and input support (touch, mouse, and keyboard) in addition to the features included by minimal. This will enable full system validation tests which simulate a graphical product (with the exception of hardware accelerated video decoders and DRM/protected memory)

Ya I know yall will defend mega corps like typical redditors, but ok not straight up stolen but paying pennies? Now the project is downgraded and most likely going to die and still have to use shit Android and shit Linux. Really bummed about this.

I randomly found this new Chromium bug where they plan to remove Chrome on Fuchsia. They mentioned that "Chrome browser on fuchsia won't be maintained due to the cancellation of the workstation program."
https://bugs.chromium.org/p/chromium/issues/detail?id=1509109
What do you think about this? I had very high expectations with Fuchsia and I'm afraid it won't become a general-purpose operating system as many of us hoped for.

BSD-likes (Android, Linux, iOS, MacOS) and DOS-likes (Windows ME, WinNT, WinRT, Mobile WinCE Phone).

Will we ever see the day when Fuschia gets released to desktop computers? I think Google is positioned to create an ecosystem like Apple has. Are they scared of pulling the trigger?

I suppose it would auto detect your hardware and download the needed drivers, just like Windows does with updates now

https://fuchsia.dev/whats-new/release-notes/f13

Fuchsia F13 release notes Date: August 3, 2023

Version: F13

The following changes have been implemented:

Application Runtimes (Flutter, Starnix, and Web) Starnix The following updates have been made for Starnix:

Added initial support for generic netlink. Added initial support for sysfs. Added initial support for RISC-V. Added fixes to get more LTP tests to pass. Added support for FUSE syscalls. Added support for mounting ext4 from VMO-backed sources. Added support for block read ahead queue. Added support for inotify. Added support for SIOCGIFFLAGS/SIOCSIFFLAGS in ioctl. Added support for InputDevice and keyboard events. Implemented ioctls for LoopDevice (/dev/loopN). Implemented fork() syscall. Implemented vDSO backed clock_getres() syscall. Implemented /proc/<pid>/oom_*. Initial support for Fxfs in Starnix. Fixed issues related to UTC and timer. Fixed issues related to seccomp. Fixed security related issues and performed general cleanups. Refactored and fixed remote_binder. Developer The following updates have been made for Developer workflows:

Added enforcement of FIDL libraries used in host tools that are part of the SDK. Initial support for Fuchsia-controller available in source tree. Removed legacy overnet protocol. Overnet exclusively used a circuit switched connection. Diagnostics The following updates have been made for Diagnostics:

Removed the Dart Inspect library from the Fuchsia source tree. Updated Archivist to write logs to serial instead of the console. Updated Archivist to no longer ingest CFv1 data. Updated the diagnostics tools to accept monikers prefixed with /,, ./, or nothing. FIDL The following updates have been made for FIDL:

Added requirement for explicit unknown interactions keywords. Moved FIDL Dart support out of the Fuchsia source tree. Removed FIDL C bindings. Software Delivery The following updates have been made for Software Delivery:

Added support for fxblob. Deleted fuchsia.pkg/PackageCache.Open. Stopped exposing the pkgfs/versions directory.

Hello fellow redditors,

Do you know if there is something new about Fuchsia? What are they currently working on? Should we expect something new in the near future?

Today I checked fuchsia.dev and saw nothing new, the version control they use looks pretty alive though, with commits around the clock. Checked the Wikipedia page - nothing new there as well, even the latest version hasn't been updated yet. There are no new articles in the "Fuchsia Friday".

Thanks!

F12 released. You might be interested in this: https://fuchsia.dev/whats-new/release-notes/f12

9to5Google post about the release: https://9to5google.com/2023/08/25/fuchsia-12-nest-hub-update/

https://www.osnews.com/story/136593/google-amazon-rebuked-over-unsupported-chromebooks-still-for-sale/

https://9to5google.com/2023/07/25/google-abandons-assistant-speakers-fuchsia/

So many questions? Why does Fuchsia have "strict CPU requirements"? What does this mean for Fuchsia on phones and with ChromeOS?

EDITED: Changed link from OSnews to source link at 9To5Google.

I know that sometime ago their was a YouTube video that showed fuchsia running on a phone and it really looked different than Android for sure.

However since at the heart of the OS is the Zircon kernel I thought I read it somewhere or got the idea that perhaps Google could swap out the Linux kernel and use Zircon and this could help towards Android OS updates lasting longer for phones since Google would now control everything in the OS right down to the kernel itself vs the current situation of them having to align Android OS support to however long a version of Linux is supported.

Has anyone heard any kind of update as to plans that involve it's use in a mobile phone or android?

https://fuchsia.dev/whats-new/release-notes/f11

Looks like some quality updates. Interestingly I was only able to find this on desktop and not through my phone.

I am working on building and running Fuchsia on an internal project at work. I have not been able to find this information anywhere, but maybe I am looking in the wrong place. I am wondering if there is a separate bootfs image that is created and then put into the zbi image. It seems like it should be because the qemu command template shows guest.kernel_image (passed to -kernel for qemu) and guest.zbi_image (passed to -initrd for qemu). Is the guest.kernel_image the kernel.zbi and the guest.zbi_image the normal zedboot.zbi or is another image used there? I haven't been able to find where the guest context is set for that template.

Hey everyone! I'm really fascinated by the Fuchsia operating system, its ongoing development, and its build process.

I've recently set up a developer workstation and have been diving into studying the operating system for about a month now. Since there's limited information and documentation available on this topic, I wanted to reach out here and ask about building everything from scratch without relying on Jiri/Prebuilt CIPD packages.

Typically, when you build the operating system, you start by bootstrapping Fuchsia and fetching all the prebuilt dependencies using Jiri/CIPD. However, I'm curious to know how I can build the entire operating system directly from the source.

Apologies for the somewhat complex/dumb question, but I'm genuinely eager to expand my understanding of how the Fuchsia operating system works.

Thanks, everybody!

So, I finally bit the bullet and built Fuchsia Workstation to run on my ARM MacBook Pro. It's fair to say I'm impressed with the progress: the OS internals appear to be well-built, there's a solid kernel, the typical POSIX utilities work, and so on. Even though I'm not a developer at that fine-grained level (I lean towards systems engineering, so I see black boxes connected to each other), the OS seems to be, for lack of a better word, all there and functional.

I'm wondering, though, about any apps that could make the experience more "livable" for someone who isn't a bare-metal coder. The browser is there, of course, but I'd welcome an e-Mail client built in Dart; an app launcher built in Dart; basically, the full Monty.

So then, there's Dahlia OS. This would seem to be exactly what I'm after, essentially a shell to make Fuchsia "livable", maybe not daily driver standard (of course not, this is a research OS) but definitely able to perform the tasks of quotidian life. But everything that's available from the main site is actually built on a Linux core (the implication being that they'll move it over to Zircon/Fuchsia once Fuchsia is "done"). I did find this, though. Seems to be a build of Fuchsia Workstation built for running on bare metal ARM?

A little bit of hand holding would be appreciated!

Fuchsia OS seems to be the perfect system for TV sets and their problem with updates. I think this system was perfect for this task could take over the role of a home control center.

Looking a bit inside 9to5google tells something about "undefined android version running VR headsets", "Galaxy Glass" line from Samsung, "Collaboration between Qualcomm, Google and Samsung" "rumored Samsung VR headset [not far away]" and quite much more but knowing android's problems, I have some doubts regarding the android part and that it's not android but an OS that runs android apps which is a reference to starnix since both Linux and Android where mentioned in the "XR OS" job listing from Google which was released right after the "AR OS" list spotted by 9to5google although no idea why this wasn't mentioned (no evidence) so I wanted to ask the experts here

To be fairly honest, this year's Google IO conference might clarify MANY things and I'm looking forward to hear what will happen then

As far as I know, Google TV is very medium with Android has serious problems with updates, I think it would be a great move on the part of Google if Google TV changed the system

Today I typed up a support martix for every device, CPU and SOC that is officially supported by Fuchsia as of today. This includes all the Amlogic, NXP and Intel chips.

For Intel, the CPUs listed on the table are only the ones that support the i915 display driver.

I hope you all find this useful.

https://docs.dahliaos.io/hardware/supported-hardware

Google and Microsoft seem poised to be about to engage on an AI war for browser dominance. Right now, Google is on the defense. As they say, Microsoft can just win over a couple more people. Maybe have people leave Bing as default on Windows more often than currently. Google has a lot to lose. They are the dominant force.

Now, will they lose? Probably not. I believe Google can hit back hard should it want to.

However, Google should not play just defense. Microsoft is attempting to expand its market reach and Google is defending their current market reach. I believe they should attempt to expand it.

Fuchsia provides a great way to do this. Let’s launch high end computer with good specs and an even better OS. Integrate Assistant and Bard (Google’s new lightweight version of Lambda) into it.

Chromebooks were great as lightweight inexpensive devices. But the biggest slice of the market is in high end computing devices.

Releasing Fuchsia laptops and phones (hopefully phones powerful enough that can be used as computers if connected to a monitor) would allow Google to make Microsoft (and Apple if Google plays its cards right) go into the defensive. If Google wants to survive and thrive its time it starts taking big risks.

[1/48971](2) ACTION //src/sys/run_test_suite/directory:directory.clippy(//build/toolchain/fuchsia:x64)

FAILED: gen/src/sys/run_test_suite/directory/directory.clippy

../../build/rust/clippy_wrapper.sh --output gen/src/sys/run_test_suite/directory/directory.clippy --jq ../../prebuilt/third_party/jq/linux-x64/bin/jq --fail -- env ../../prebuilt/third_party/rust/linux-x64/bin/clippy-driver ../../src/sys/run_test_suite/directory/src/lib.rs --sysroot=../../prebuilt/third_party/rust/linux-x64 --crate-type=rlib --cfg=__rust_toolchain=\"ZNFg2CXGsWHMRkg3rqGAMGIQvtIlaSoNCgDpN_ah9LYC\" -L gen/zircon/public/sysroot/cpp/lib -Clinker=../../prebuilt/third_party/clang/linux-x64/bin/lld -Clink-arg=--sysroot=gen/zircon/public/sysroot/cpp -Clink-arg=-L../../prebuilt/third_party/clang/linux-x64/bin/../lib/x86_64-unknown-fuchsia -Clink-arg=-L../../prebuilt/third_party/clang/linux-x64/lib/clang/16/lib/x86_64-unknown-fuchsia -Clink-arg=--pack-dyn-relocs=relr -Clink-arg=-dynamic-linker=ld.so.1 -Clink-arg=--icf=all -Clink-arg=-zrel -Zremap-cwd-prefix=. -Cforce-frame-pointers -Copt-level=0 -Cdebuginfo=2 -Zallow-features= --target x86_64-fuchsia --cap-lints=deny -Wrust-2018-idioms -Dderef-nullptr -Dinvalid-value -Dunused-must-use -Awhere_clauses_object_safety -Dwarnings -Cdebug-assertions=yes -Cprefer-dynamic -Clink-args=-zstack-size=0x200000 -Cpanic=abort -Cforce-unwind-tables=yes -Zpanic_abort_tests -Csymbol-mangling-version=v0 -Dunused_crate_dependencies -Dunused_results -Aunused_results --edition=2021 -Aclippy::all -Dclippy::correctness -Dclippy::missing_safety_doc -Wclippy::expect_fun_call --cfg=fidl_rust_transition_step=\"initial\"

error[E0786]: found invalid metadata files for crate `test_list`

--> ../../src/sys/run_test_suite/directory/src/testing.rs:11:5

|

11 | use test_list::TestTag;

| ^^^^^^^^^

|

= note: failed to mmap file '/home/ja/fuchsia/out/default/obj/src/lib/testing/test_list/libtest_list.rlib': memory map must have a non-zero length

​

​

error[E0786]: found invalid metadata files for crate `test_list`

--> ../../src/sys/run_test_suite/directory/src/v1.rs:18:5

|

18 | test_list::TestTag,

| ^^^^^^^^^

|

= note: failed to mmap file '/home/ja/fuchsia/out/default/obj/src/lib/testing/test_list/libtest_list.rlib': memory map must have a non-zero length

​

​

error[E0786]: found invalid metadata files for crate `test_list`

--> ../../src/sys/run_test_suite/directory/src/lib.rs:19:5

|

19 | test_list::TestTag,

| ^^^^^^^^^

|

= note: failed to mmap file '/home/ja/fuchsia/out/default/obj/src/lib/testing/test_list/libtest_list.rlib': memory map must have a non-zero length

​

​

error: aborting due to 3 previous errors

​

​

[2/48971](1) ACTION //src/sys/pkg/lib/fidl-fuchsia-update-...update-installer-ext.clippy(//build/toolchain/fuchsia:x64

FAILED: gen/src/sys/pkg/lib/fidl-fuchsia-update-installer-ext/fidl-fuchsia-update-installer-ext.clippy

../../build/rust/clippy_wrapper.sh --output gen/src/sys/pkg/lib/fidl-fuchsia-update-installer-ext/fidl-fuchsia-update-installer-ext.clippy --jq ../../prebuilt/third_party/jq/linux-x64/bin/jq --fail -- env ../../prebuilt/third_party/rust/linux-x64/bin/clippy-driver ../../src/sys/pkg/lib/fidl-fuchsia-update-installer-ext/src/lib.rs --sysroot=../../prebuilt/third_party/rust/linux-x64 --crate-type=rlib --cfg=__rust_toolchain=\"ZNFg2CXGsWHMRkg3rqGAMGIQvtIlaSoNCgDpN_ah9LYC\" -L gen/zircon/public/sysroot/cpp/lib -Clinker=../../prebuilt/third_party/clang/linux-x64/bin/lld -Clink-arg=--sysroot=gen/zircon/public/sysroot/cpp -Clink-arg=-L../../prebuilt/third_party/clang/linux-x64/bin/../lib/x86_64-unknown-fuchsia -Clink-arg=-L../../prebuilt/third_party/clang/linux-x64/lib/clang/16/lib/x86_64-unknown-fuchsia -Clink-arg=--pack-dyn-relocs=relr -Clink-arg=-dynamic-linker=ld.so.1 -Clink-arg=--icf=all -Clink-arg=-zrel -Zremap-cwd-prefix=. -Cforce-frame-pointers -Copt-level=0 -Cdebuginfo=2 -Zallow-features= --target x86_64-fuchsia --cap-lints=deny -Wrust-2018-idioms -Dderef-nullptr -Dinvalid-value -Dunused-must-use -Awhere_clauses_object_safety -Dwarnings -Cdebug-assertions=yes -Cprefer-dynamic -Clink-args=-zstack-size=0x200000 -Cpanic=abort -Cforce-unwind-tables=yes -Zpanic_abort_tests -Csymbol-mangling-version=v0 -Dunused_crate_dependencies -Dunused_results -Aunused_results --edition=2021 -Aclippy::all -Dclippy::correctness -Dclippy::missing_safety_doc -Wclippy::expect_fun_call --cfg=fidl_rust_transition_step=\"initial\"

error[E0786]: found invalid metadata files for crate `fidl_fuchsia_update_installer`

--> ../../src/sys/pkg/lib/fidl-fuchsia-update-installer-ext/src/state.rs:9:5

|

9 | fidl_fuchsia_update_installer as fidl, fuchsia_inspect as inspect,

| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

|

= note: failed to mmap file '/home/ja/fuchsia/out/default/obj/src/sys/pkg/fidl/fuchsia.update.installer/fuchsia.update.installer_rust/libfidl_fuchsia_update_installer.rlib': memory map must have a non-zero length

​

​

error[E0786]: found invalid metadata files for crate `fidl_fuchsia_update_installer`

--> ../../src/sys/pkg/lib/fidl-fuchsia-update-installer-ext/src/options.rs:8:5

|

8 | fidl_fuchsia_update_installer, fuchsia_inspect as inspect,

| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

|

= note: failed to mmap file '/home/ja/fuchsia/out/default/obj/src/sys/pkg/fidl/fuchsia.update.installer/fuchsia.update.installer_rust/libfidl_fuchsia_update_installer.rlib': memory map must have a non-zero length

​

​

error[E0786]: found invalid metadata files for crate `fidl_fuchsia_update_installer`

--> ../../src/sys/pkg/lib/fidl-fuchsia-update-installer-ext/src/lib.rs:22:5

|

22 | fidl_fuchsia_update_installer::{

| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

|

= note: failed to mmap file '/home/ja/fuchsia/out/default/obj/src/sys/pkg/fidl/fuchsia.update.installer/fuchsia.update.installer_rust/libfidl_fuchsia_update_installer.rlib': memory map must have a non-zero length

​

​

error: unused import: `TryInto`

--> ../../src/sys/pkg/lib/fidl-fuchsia-update-installer-ext/src/state.rs:13:29

|

13 | std::convert::{TryFrom, TryInto},

| ^^^^^^^

|

= note: `-D unused-imports` implied by `-D warnings`

​

​

error: unused import: `convert::TryInto`

--> ../../src/sys/pkg/lib/fidl-fuchsia-update-installer-ext/src/lib.rs:33:11

|

33 | std::{convert::TryInto, fmt, pin::Pin},

| ^^^^^^^^^^^^^^^^

​

​

error: aborting due to 5 previous errors

​

​

ninja: build stopped: subcommand failed.

Hint: run `fx build` with the option `--log LOGFILE` to generate a debug log if you are reporting a bug.

How can I install something like vim on a Fuchsia instance running on qemu?