Creating a Proxmox or QEMU ChromeOS Flex VM(kevindavid.org)
kevindavid.org
Creating a Proxmox or QEMU ChromeOS Flex VM
https://kevindavid.org/code/2024/03/20/chrome-os-flex-proxmox.html
21 comments
The main problem with ChromeOS Flex is it's limited hardware support. I installed it on my mum's old Dell Optiplex as a trial, and whilst it worked fine, it didn't support her Canon Pixma printer/scanner. I looked it up online and others had the same issuse as well, and Google said unfortunately there was nothing you could do besides getting a compatible printer.
The second problem is that ChromeOS Flex has a limited support period. It's no doubt longer than Android, but it's still artificially limiting the life of older hardware that has potentially still many more years of service left. Like my mum's Optiplex 9020 which reaches end of support in 2026 - whereas I believe it's got at least 5 years, if not more, especially considering that I could upgrade the RAM/CPU/disk if required.
The third issue is that it's Google. There's no telling when they'll pull the plug on this.
The "PHD" solution I ended up going for was Aurora (an immutable distro based on Fedora Atomic). Aurora uses KDE, which was simple and familiar enough for my mum to use with almost no training, and its got atomic automatic updates with the last two images also available in the boot menu, in the rare event something goes wrong. It's practically zero-maintenance like ChromeOS, with none of the drawbacks.
Oh and in case Aurora ever decides to fold, it's easy enough to rebase to another Fedora Atomic variant with just a single command, without affecting your data.
The second problem is that ChromeOS Flex has a limited support period. It's no doubt longer than Android, but it's still artificially limiting the life of older hardware that has potentially still many more years of service left. Like my mum's Optiplex 9020 which reaches end of support in 2026 - whereas I believe it's got at least 5 years, if not more, especially considering that I could upgrade the RAM/CPU/disk if required.
The third issue is that it's Google. There's no telling when they'll pull the plug on this.
The "PHD" solution I ended up going for was Aurora (an immutable distro based on Fedora Atomic). Aurora uses KDE, which was simple and familiar enough for my mum to use with almost no training, and its got atomic automatic updates with the last two images also available in the boot menu, in the rare event something goes wrong. It's practically zero-maintenance like ChromeOS, with none of the drawbacks.
Oh and in case Aurora ever decides to fold, it's easy enough to rebase to another Fedora Atomic variant with just a single command, without affecting your data.
> third issue is that it's Google. There's no telling when they'll pull the plug on this.
That is exactly the reason to use ChromeOS/flex.
The UI is well designed to use cloud as storage space. i.e no worries when anything folds including hardware failure.
I have not used Aurora but does it automatically do FDE? Does the user need to install chrome or Firefox? I have seen people saving passwords locally and not syncing. One fine day Xorg (or wayland gives up). Then one needs to go to users place and fix it. I did install flex on my parents machine in the other side of globe. It still works updates seamless.
I recommended ChromeOS (despite the pain of needed ublock origin ) mainly because users need to remember only one password. i.e Google 's password.
While I am a daily driver of Linux/Xubuntu, the UI from kde/gnome etc is not that friendly as ChromeOS (which mimics Android).
Not detecting printer is specific situation. This could also happen with many Linux distros.
Of course it is all IMHO.
That is exactly the reason to use ChromeOS/flex.
The UI is well designed to use cloud as storage space. i.e no worries when anything folds including hardware failure.
I have not used Aurora but does it automatically do FDE? Does the user need to install chrome or Firefox? I have seen people saving passwords locally and not syncing. One fine day Xorg (or wayland gives up). Then one needs to go to users place and fix it. I did install flex on my parents machine in the other side of globe. It still works updates seamless.
I recommended ChromeOS (despite the pain of needed ublock origin ) mainly because users need to remember only one password. i.e Google 's password.
While I am a daily driver of Linux/Xubuntu, the UI from kde/gnome etc is not that friendly as ChromeOS (which mimics Android).
Not detecting printer is specific situation. This could also happen with many Linux distros.
Of course it is all IMHO.
Aurora does indeed use FDE (via LUKS). Firefox and other common applications are pre-installed (as Flatpaks) and get updated independently of the OS, without needing a reboot. There is an app store of sorts (called "Discover") which allows users to easily install/update apps - no sudo password needed - just like ChromeOS, minus the adware/spyware.
I got my folks to switch to Firefox decades ago (back in the IE 6 era), so they're comfortable with it and never had any issues with its password sync.
Wayland hasn't been a problem either. My folks don't use any fancy GPUs like nVidia (which seem to be the common cause of Linux display issues). And as I said, in case something does break, they can easily boot the previous to images right from the boot menu, no need to even press any secret keys or do a restore. My folks are also on the other side of the globe, so stability and support were my main considerations, and I liked the idea of being able to easily rollback to a previous update.
I agree with Gnome not being friendly, but don't include KDE with that - it uses the same, old-school desktop metaphor that old Windows versions used - which my folks were familiar with. Of course, this is a subjective thing, luckily my folks had no issues finding their way around. But it's not like they do any complicated computing stuff.
Yes the printer is a specific situation, but I mentioned it because I was surprised ChromeOS didn't detect it when Aurora had no issues. You'd think that ChromeOS, being based on Linux, would work fine as well... but clearly they're not alike.
I got my folks to switch to Firefox decades ago (back in the IE 6 era), so they're comfortable with it and never had any issues with its password sync.
Wayland hasn't been a problem either. My folks don't use any fancy GPUs like nVidia (which seem to be the common cause of Linux display issues). And as I said, in case something does break, they can easily boot the previous to images right from the boot menu, no need to even press any secret keys or do a restore. My folks are also on the other side of the globe, so stability and support were my main considerations, and I liked the idea of being able to easily rollback to a previous update.
I agree with Gnome not being friendly, but don't include KDE with that - it uses the same, old-school desktop metaphor that old Windows versions used - which my folks were familiar with. Of course, this is a subjective thing, luckily my folks had no issues finding their way around. But it's not like they do any complicated computing stuff.
Yes the printer is a specific situation, but I mentioned it because I was surprised ChromeOS didn't detect it when Aurora had no issues. You'd think that ChromeOS, being based on Linux, would work fine as well... but clearly they're not alike.
Indeed it looks impressive. Thanks for the tip.
It's a shame then that Google are moving away from ChromeOS in favor of Android. This also explains the improvements to desktop mode in the latest Android betas.
First, a disclaimer: I also overwhelmingly prefer ChromeOS over Android for a bunch of reasons and wish that if they had to merge them the result was a thin Android compatibility layer on the much more robust bones of ChromeOS.
That said... if Google wants to fold ChromeOS into Android, I think they'll have to make Android fully supported on x86 as a first-class platform (because most Chromebooks are x86). And if they do that, they should have little problem making a... Android Flex or whatever you'd call it that boots on normal PC hardware just like ChromeOS Flex does today and fills the same role.
That said... if Google wants to fold ChromeOS into Android, I think they'll have to make Android fully supported on x86 as a first-class platform (because most Chromebooks are x86). And if they do that, they should have little problem making a... Android Flex or whatever you'd call it that boots on normal PC hardware just like ChromeOS Flex does today and fills the same role.
Asus and other OEMs have had Android tablets on x86 for quite some time.
In any case, except for shared objects written with the NDK, the actual CPU hardly matters, even across ARM there is enough variation.
In any case, except for shared objects written with the NDK, the actual CPU hardly matters, even across ARM there is enough variation.
Manythings like network/Bluetooth/Display server stack are better optimised in android. Low power long battery life.
If similar to ChromeOS it is directly updated by Google then it will be a huge win for all computer users. No pain from OEM. I mean some Gemini crap from Google but that is tolerable.
If similar to ChromeOS it is directly updated by Google then it will be a huge win for all computer users. No pain from OEM. I mean some Gemini crap from Google but that is tolerable.
ChromeOS Flex is what CentOS was to RH. I don't see it lasting very long.
In case the author reads this: instead of `losetup` you could have imported the image with `qm disk import VMID path/to/source TARGET_STORAGE`
It would then show up as unused disk in the VM config to be further configured :-)
[deleted]
At the risk of sounding negative… Is there a value to do this?
I mean, its interesting that you can, but I’m working the opposite way, I run Proxmox so that I can run ChromeOS as my main working OS.
I mean, its interesting that you can, but I’m working the opposite way, I run Proxmox so that I can run ChromeOS as my main working OS.
Testing. Installing ChromeOS on a bare-metal machine and then switching back if you dislike it can be a bit of a hassle.
Why can you not install ChromeOS Flex directly on your hardware?
What I mean is that I run proxmox predominantly so I don’t have to run Windows on my hardware.
Isn't that what this post is about? Creating a ChromeOS Flex VM that can then run in Proxmox?
Proxmox is generally run in a client-server arrangement where Proxmox and its VMs are on a server somewhere and users connect from a lightweight (probably browser) client. So the idea is that the device you use directly is a Chromebook acting as essentially a thin client, and then your real work happens in VMs on proxmox. Notably, those VMs can include Windows while containing it and not having to deal with Windows on hardware. (And I mean yes you could have a Chromebook thin client connecting to a server running a different instance of ChromeOS... and I can see ways for that to be useful, even... but that's not the idea being espoused here.)
Has anyone tried gpu passthrough to a ChromeOS flex vm
ChromeOS Flex doesn't get enough credit. While I recently migrated from Windows to Linux on my production machine, ChromeOS Flex is my OS of choice for a simple Push Here Dummy (PHD) machine. There is zero maintenance from an OS standpoint and the ChromeOS Flex Certified models list allows me to pick from a variety of quality hardware, not just some cheap Chromebook. I have more than one of these lying around the house and I often take one on personal trips as well.