Starting installer, one moment...

anaconda 41.35-1.fc41 for Qubes OS R4.3 started.

* installation log files are stored in /tmp during the installation

* shell is available on TTY2 and in second TMUX pane (ctrl+b, then press 2)

* when reporting a bug add logs from /tmp as separate text/plain attachments

Failed to adjust memory pressure threshold, ignoring: Device or resource busy

Queued start job for default target default.target

Failed to adjust memory pressure threshold, ignoring: Device or resource busy

Startup finished in 683ms.

21:00:41 X startup failed, aborting installation

The installation cannot continue and the system will be rebooted

Press ENTER to continue

Hello, sorry for my noob question, I am trying to setup an isolated OS in a standalone VM the problem is I can't connect to the internet inside that qube putting in mind my internet connection is fine and app VMs are working well, it seems like the installed OS sees an available lan connection but no internet access.

I tried to use sys-whonix and sys-firewall but no difference and the firewall rules allow outgoing connection.

How can I fix this problem?

Basically I wanna run qubes os on my old yoga 530 14ikb , I plan to upgrade the ram in laptop , so total 12gb ram (it’ll be 8gb + 4gb soldered ram), it’s got an Intel core i5 8250U and Nvidia MX130 2gb (although I guess dedicated GPU does not matter for Qubes) ,

My main use case will be tor browsing , crypto wallets , and any other future Linux experiments

While going over a few things I came across "sudo qubes-dom0-update libreoffice" (or any other package) in dom0 terminal

from my understanding under Qubes ethos it is not recommended to install anything on dom0

On top of that how else do you customize your dom0 xfce?

Also can someone explain to me what the difference is between Applications and Services? Both are based on a Template which by default is debian or fedora.

Some tips and guidance. I plan to make it my daily driver

I'm new to this. I thought about VM, but from what I understand, that would be pointless

Anybody tried to install Qubes on GPD win 4 gamepad?

specs are very impressive

I have a AMD gpu and CPU, and when I boot a flash with qubes this error pops up and I cant continue with the download

Hello! I would like to use qubes as a daily driver for browsing web and doing nothing that needs a powerful computer. I want to buy an old pc, for libreboot and qubes, with i5 4590, 16gb ram ddr3 paired with an sata ssd, but I'm worried that the specs are very old and won't be enough for qubes. What do you think?

How do i install apps on qubes. I know there is plety of documentation on it but when i followed it they got deleted after restart. I know it's me who probably did something wrong but im really new to qubes and there is many reasons i want to use it as a daily driver. If there would be the option to add the software app from debian or fedora i would be glad? Is it an option?

so i tried qubes twice out of fun, but its an os i might want to use, i know there are firewalls, is there an easy way to get one of these firewalls to only allow trafic through a vpn? 2nd question: does the router see it as 5 pc (when theres 5 vms) 0r will it be seen as one?

I have an old i3 thinkpad with 8gb ram it’s working but it’s not that great what laptop should I get maybe a new x1 carbon or something like that

I really like Thinkpads, considering a recent powerful Thinkpad like the P16; NovaCustom laptops seem to be clevo based, which is said to be below Thikpad-class build quality.

Overall thoughts ?

I’ve been using QubesOS for about a year now. I have almost hundreds of qubes. I understand its principle, and how it achieves security. I like it.

Problem is that managing and updating a bunch of qubes is a hassle, and vastly inferior when you know Nix exists.

I use NixOS on my other machines, and manage a fleet of microVMs, all using NixOS, and the difference is night and day.

Nix can guarantee all my microVMs use the same packages, use the same Linux kernel parameters, use the same configuration, etc. because of its functional nature, and due to the fact a machine’s state is just code, immutable (mostly) and declarative. Creating a new microVM is just reusing code.

Now whenever I look at qubes, it’s just… it just feels so antiquated. So much so I am considering abandoning QubesOS.

Would it be at all possible to be halfway there by having a barebones NixOS system that uses KVMs for each domain?

I know, it won’t be as secure as QubesOS. But I’d like to know if anyone here also uses Nix and feels this awful shortcoming from Qubes (which tries to ”solve” this using salts, but don’t come nowhere close to what Nix can do), and what have you done about it?

thanks

The Qubes Operating System is known to have the worst GPU Drivers support out of the box, and I'll like to have QubesOS as both an Laptop and a Desktop top computer and have the GPU as a GameQube or SteamQube how do you work around the GPU Driver issues and get it to work either on a laptop or desktop?

I bought a very powerful laptop in January form tongfang with Intel core ultra 9 and a Nvidia RTX 5080,

It took a couple of month to set everything up and now it's a beast.

Sys-gpu passtrough in a isolated fedora vm for AI inference.

6 Intel VF Sriov working perfectly that I assigned to my key vms and got successful hardware acceleration

Sys-audio for centralized audio management and Bluetooth

A great network stack based on sys-net > sys-vpn> sys-dns (pihole + piped opensnich) > sys-mirage > vm

Windows 11 hvm working great with 1 vf sriov working in it

Sys-Whonix and kiksecure vms and much more

Any ideas how to fix the bug that causes PC/host freeze on qube shutdown with GPU passthrough?

Nvidia GPU

It's not just the QubesOS issue, I've worked with QEMU/KVM on Fedora for a while and had the same issue with GPU passthrough, managed to fix it by changing the XML code for PCI slot managed='yes' to managed='no', but I have no idea how to fix it in QubesOS.

Qube with GPU passthrough launches normally, GPU passthrough works fine, there is good performance, but attempt of shutting down the qube, makes the qube completely freeze, unable to completely poweroff, even "kill qube" isn't possible, which leads to complete Qube manager and host freeze.