Why not to base next dom0 on fedora 42 as it will offer new xfce version.
Is 4.3 release is eminent? So can’t be delayed for that.
2 Likes
Newest version I have in templates is fedora 40, why do you think dom0 should jump to 42 ?
What features does new xfce have ?
Why do people prefer xfce over kde ?
1 Like
right now people are working on fedora 41 to be the dom0 version.
fedora41 was just released.
dom0 / qubes 4.3 is estimated somewhere q1 or q2 in 2025.
to plan further with an unreleased version of fedora isnt very viable except if you want a much later release of qubes 4.3.
thats my opinion and does not reflect the views of the dev team.
4 Likes
In feb/march 25 Fedora 42, (the answer for all questions) will be in beta freeze. It is a moving target but as the qubes dom0 release cycles are longer one could end in out dated releases of dom0 linux distribution.
I am not a qubes developer, but maybe I will become better and could help a bit in the future.
https://fedorapeople.org/groups/schedule/f-42/f-42-all-tasks.html
I think one could use 42 and follow them in an approach of “simultaneous engineering”.
Qubes 4.3 and Fedora 42 would be in the beta stages about the same time.
2 Likes
Now that Xen 4.20 is round the corner, fedora 42 soon releasing, I think if developers should give these a thought for 4.3.
Maybe even Cosmic UI can release soon.
Yah, I know it seems like I am just saying to delay as much as possible, but new hardwares will most likely get benefits.
2 Likes
Xen 4.20 released and Fedora 42 is targeting April for release.
Would be nice if Xen could handle Efficient/performance core topology on Intel CPUs 
it does not seem it’s still the case
I‘m very pessimistic … as noted elsewhere.
1 Like
I don’t care much about xfce, but e2fs FEATURE_C12 is a good reason to upgrade fedora version asap.
I’m running Qubes OS on a 13th-gen CPU with P-cores and E-cores. Could you please explain what will happen if Xen cannot handle this? Will there be a security issue or a performance drop?
It’s just xen distribute the load on all cores without caring about if they are e or p cores, which gives bad battery life on battery and bad performance overall. It’s not a huge deal, but annoying.
1 Like
This feature is related to faster file orphaning. How is it going to be that useful on dom0?
I do not care about file orphaning, but if your guest OS enabled it which debian 12 now does by default, your dom0 e2fs-utils cannot handle this filesystem.
You can use tune2fs to remove orphan_file feature and you are good to go.
VM filesystems should never be handled in dom0 at all:
I have been using (testing) Fedora 42 as my default Templates for over a week (including minimal Fedora 42 templates for ServiceVMs). Details here:
In addition to the explanation in the above post, Fedora 42 has some other cool features. Bees is packaged for it (For BTRFS de-duplication if you need it). Xfce 4.20 has experimental Wayland support features. A pretty new Anaconda installer (which itself is wayland based), DNF/RPM CoW, etc.
Having said that, we do not have enough time. It is more feasible to backport highly essential packages to Fedora 41 for dom0 rather than supporting all of the above for Qubes OS 4.3 (as there are a tone of them). And Fedora 42 templates could be individually provided. I believe we will have to wait for Qubes OS 4.4 (or maybe 4.3.1) for Fedora 42 support.
4 Likes
If you need to, say, shirnk a filesystem from dom0 side, it is your only option.
You can shrink the filesystem with qvm-console-dispvm, or by attaching it to another (e.g. Disposable)VM.
well ok (need to do it headless mode, but still doable probably)
Qubes 4.4 will be atleast 2 years ahead. Sad to hear that fedora 42 can’t make into Qubes 4.3.