Best system/way to learn Qubes OS?

Hello everyone. New here, first post etc.

I had hoped to get some brief advice initially on a couple of things.

Firstly, would a Lenovo Thinkpad T470 i5 7th gen laptop be ok to install QubesOS onto? Or would you suggest installing via VM in the first instance?

Secondly, as someone who isn’t ‘technical’ in the sense that I’ve never written code etc. and would in effect be a complete beginner, would you advise against me using QubesOs in any event?

My reason for wanting to use it is nothing more than I like the concept, and the privacy aspect (I use, and love, Graphene OS).

Are there are tutorials that I can be pointed to that makes the initial process a little easier than reading through all of the pages of the QubesOS documentation, or is that a necessary part of learning just how complex the system is so as not to make any missteps when using?

Thank you all in advance for any advice and best regards.

3 Likes

Check System requirements — Qubes OS Documentation

QubesOS should run on bare metal.

You don’t need coding knowledge for using Qubes, but same networking and system basics may help you manage your own device.

Follow guides, documentations, ask us on forum if you get into trouble and your experience with Qubes will improve over time.
Don’t afraid from try and make mistakes.

QubesOS is more open for end user changes then GrapheneOS.

  • QubesOS is a lego, while GrapheneOS ready to use out of box.

You can find same youtube content about Qubes, but mainly it self learning process that you should pass over.

3 Likes

Hi and welcome here!

I have nothing more to add to what @WhiteShadow said, except a slightly off-topic proposal, so feel free to ignore the following.

I think that we currently suffer from a lack of good learning material for beginners. There is a lot of documentation and a great community around Qubes OS but I don’t think it is enough, and that’s something I would like to improve by writing tutorials about the basics.

I was wondering about the possibility of providing some personal teaching lessons to new users in order to write those tutorials… If that’s something that might interest you, you can ask me more details about this “offer”.

4 Likes

Not wanting to sound rude, but the documentation is there for a reason:

I’d advise at least reading the first few pages

3 Likes

Welcome to the club! :wink:

I recommend starting with the default installation settings and then just diving in.

It’s probably best if you have a concrete goal in mind that you want to achieve using Qubes.

For me, for example, that was having a separate VM solely for accessing email and calendars.

With only a few exceptions, I was very well advised and guided through both the installation and the first steps by ChatGPT and Grok.

2 Likes

I completely agree with @WhiteShadow and @parulin.
One more tip: Try using the system as the developers intended first.
Once you feel confident and understand the basics of the operating system, you can adapt it to your needs and expectations.
And if any of your actions in the operating system (especially in dom0) require “sudo” or something similar, think carefully before pressing Enter.
That is true in every Unix-like OS (and especially in Qubes OS), because the OS assumes you know what you’re doing.
Just my two cents…

4 Likes

If your need for security is immediate. Look at using Tails OS. Which has a lot of excellent documentation on how to use it effectively. As does Whonix.

There is a been a great deal of effort, good results, in improving the documentation.

I believe the problem some have in using documentation is that only documents one narrow thing, and does not cover things that are documented elsewhere.

For a newcomer, that sometimes means they end up searching for one thing, then to understand/implement part of that, they have to go to another part of the documentation.

There is a bit of what did that term actually mean. or was it just a vague metaphor. After learning ones way around part of using Qubes. then the documentation becomes quite valuable and accurate.

There are youtube videos on how to do almost anything, although some refer to an earlier version of Qubes.

Qubes might be described as a tool kit rather than a finished Operating System.

The developers, in my opinion, and I think correctly, focus their efforts on creating a xen that is secure, minimal size Qubes of OS’s, to save RAM, and to make them more secure.

As those OS Qubes, such as, Fedora templates, Debian Template, Whonix, and their resulting app Qubes, have their updates, security, documentation accomplished those respective OS websites. Allowing our developers to focus on our security needs, and the Debian, Fedora, Whonix to focus on their own respective work that might effect, Privacy, Security, Anonymity.

Qubes can be frustrating, but, as Qubes is uniquely able, with careful operating Security, Op Sec, how you r hoose to use it. OpSec being as important can be as important to achieving you goals as Qubes, itself. You can still destroy your own, privacy, security, anonymity by using Qubes incorrectly. You can still shoot yourself in the foot.

Qubes is uniquely able to allow us to keep malware off our own computer. Minimize its effect on our life.

Perhaps the first question for a newcomer to ask themselves is what is their goal, their risk factor. Your “threat assessment.”

Burning the install, USB can be challenging. I suspect using Fedora Media Writer will likely work, from many Operating Systems, including Windows. I am vague because I have not tried all, and things keep changing.

Mostly you will be your own technical support, and the effectiveness of your Qubes install, is in your own choices. Mistakes.

Best Wishes, Have fun

3 Likes

Not rude at all, and I am slowly but surely looking through the docs. A lot of the jargon doesn’t make sense to me at this point, however.

2 Likes

I already have Tails on a USB but haven’t got around to using it yet. I have no real ‘threat assessment’ to speak of really. Just don’t like the idea of my data being harvested etc., and Qubes OS whilst seemingly difficult to get the hang of, I’m sure would be ok once I’ve been using it for a while, and the privacy element appeals in the same way that GrapheneOS does for mobile.

1 Like

Thank you for all of the advice, much appreciated.

2 Likes

Thanks. I’m such a beginner, however, that I don’t even know what sudo is/does - hence why I could find this whole thing challenging.

2 Likes

Many thanks for the reply/advice

1 Like

Yes, that’s something I’d potentially be interested in, thank you. Please tell me more!

2 Likes

Regrading all your last comments, please use heart button to say thanks instead :slightly_smiling_face:

5 Likes

Hi!

Personal recommendation about the migration from my point of view:
First of all, since you say you are note technical, the first thing I recommend you is not to jump directly into Qubes OS. First, get a global view of the things you can do with this wonderful system, and treat your candidate laptop as a playground machine until you get your desired configuration to work (you can mess things up and, if you already migrated everything to Qubes, that’s gonna be so frustrating).

Probably you will need to do tweaks to your system with the terminal. Do not be afraid of her! It’s a glorious tool that will make all of your dreams come true :slight_smile:
After a little bit of practice you will be using it with ease.

Qubes OS can feel like a very complex system at the beginning, but after you get used to it, it’s a pretty cool OS.

I switched from a full Apple ecosystem to Graphene and Qubes OS and I can’t feel more relieved and comfortable after the change.

Your hardware:
I think that lenovo is perfect for you, I’ve tested a Thinkpad T480s with Qubes OS 4.2.6 and it worked perfectly. In fact, your laptop is a very good one because it uses an Intel CPU from a generation where Intel ME can be disabled (it’s like a hardware thing for remote administration of Intel computers that can be used as a very stealthy backdoor). You can neuter it using coreboot or libreboot, although installing it will require some technical knowledge.

Also, to protect against some CPU hacks (like Spectre and Meltdown affecting Intel CPUs from your generation), you can disable Hyper-Threading in the BIOS, mitigating these vulnerabilities. Practically, they all depend on speculative execution, therefore disabling HyperThreading in BIOS will make your system defended.

I have to note that disabling that will lower the performance of the laptop. If you are not afraid of such an attack (highly complex to execute), you can leave the HyperThreading thing for more CPU speed.

I also recommend you to check out how much RAM you can add to your laptop. Add the maximum possible, Qubes relies on too much RAM because it has to run multiple VMs.

Tutorials:
I recommend you to check the official documentation here: Documentation — Qubes OS Documentation
Also there are pretty nice community guides here: Community Guides - Qubes OS Forum

For example, this community guide shows you how to create a VM with Proton VPN to route the traffic of your whole computer (of all VMs) through this VPN: Configuring a ProxyVM VPN Gateway

I recommend you to spend some hours here in the forum so you can get to know cool things created by people. Maybe you want to implement some of them to your workflow. Community Guides is a great place to start.

Have fun! :slight_smile:

TNT

3 Likes

Hi @JMP, welcome to Qubes. I hope you enjoy your time with us.

You’ve been given some good advice already, but I thought I might give
my perspective. I’ve worked with a number of new users, and this is
where I generally start.

It’s fine. You can look at the HCL as suggested. VM wont fly.

No. It’s a problem that people say that Qubes is hard to use, or
difficult to learn. It isnt. There are Qubes ways of doing
things that you have to learn, but out of the box the system is usable.
Most people are so familiar with Windows or Mac that they forget the
amount of things they had to learn with those systems.

Good enough. Grab a spare SSD, and give it a go.

There are (at least) two pages in the documentation that you should read:

Install Qubes with the default settings: qubes will be created for
you automatically. Treat it like a new car - start gently, and dont
assume you know what you’re doing. The net is full of videos of folk
totalling their new super cars - dont be like them.

So start small. Use Qubes for a while, but dont fill it with personal or
identifying data. This is just a test drive.

Install Qubes with the default options but as you are interested in
privacy, choose the options to install Whonix.
When you start the system for the first time, there are a few things
that you will want to do. Get online, start a browser, write some stuff

  • I dont know what you want to do. But you do. Break it down to
    small steps.
    Get online - there’s a network widget in the tray.
    Use a browser - look in the Menu for the WhonixWS.
    Write some stuff - look in the Menu for the personal qube, and open an
    editor. Write something and save it in the qube.
    Write some other stuff - look in the Menu for the work qube, and open an
    editor. Write something and save it in the qube.
    That is you using Qubes, and you can be pretty productive just like that.

What about everything you’ve heard about? “When do I get to impress my
friends by burning up the street?”, I hear you ask. Learn the basics
first, and then you’re good to go.

Some things to learn -
How do I install a new package? Do it in the template, and then look in
the qube settings to make it available in the Menu for that qube.
How do I move stuff between qubes? There’s a copy/paste mechanism -
Ctrl+C, Ctrl+Shift+C in one qube - Ctrl+Shift+V in the target, then
paste with Ctrl+V
For files use a file manager: Right Click, and there are options to
copy/move files to another qube.
How do I create a new qube? (Menu ->QubesTools>Create a new qube)
How do I make a qube offline? Connect it to Whonix? DONT connect it to
Whonix? (Open the qube settings and change the netvm)
Learn what is a disposable? It might be better called a single shot
qube. Anything you do there will be lost when you close the qube.

Many people are productive with just that level of knowledge. When you are
comfortable, take a while to think about what you are doing. Perhaps you
want to separate work from personal, keep school work in a separate
qube - I dont know. But you do. Once you’re clear about what Qubes can
do you can think about how you will do it. When you are clear, reinstall
Qubes, set it up as you want, and start to use it in earnest. As you go
you may find you want

Many problems that people have in Qubes are actually not Qubes specific.
You can find guides online to help with problems, and those should help
you. There are a few Qubes specific parts but you generally can pick
these up fairly quickly.

If you’re stuck, ask in the mailing lists or the Forum, with enough
detail that people wont have to guess what you have done and what you
want to do.

Enjoy.

I never presume to speak for the Qubes team.
When I comment in the Forum I speak for myself.

6 Likes

I’ve been an Apple man for as long as I can remember, typing this on a MAC, but want to come away from all that. Was nervous about Graphene firstly, but loved it as soon as I’d changed from iphone, and I would hope for the same with Qubes.

1 Like

I have qubes running on this exact laptop (4.2.4). It’s fine though pretty slow. If you already have this laptop then good but I wouldn’t buy it in 2026 for Qubes

3 Likes

I bought one second hand to try Ubuntu (not downloaded yet), as I’ve never even used a Linux-based OS to this point (and just want to get away from Apple in the first instance)! Qubes is where I want to get to!

2 Likes

I have been thinking a bit more about my “offer” and there are a lot of drawbacks (for you), that I need to mention. Especially after all those welcoming messages and advices :slight_smile:

So, my idea is the following: I write some parts of the tutorial that I send to the learner. Then, the learner sent me back any questions, comments on unclear parts, and so on. To get useful feedback, I would need the learner to read as little documentation as possible. That’s a problem because my material is not ready yet, so it will take some time to complete some basic things. I also need the learner to be able to distrust what I say and to check by themself, that’s quite contradictory to the previous assumption.

What I have in mind is basically what unman said: focus on basic tasks (connect to the internet, use USB drives, transfer files, backup, etc.). I will stay generic and avoid anything special (i.e., set up a VPN). So to be honest, that’s more about me looking for someone to test a tutorial than providing a real personalized lesson. And at the end, that’s only about learning the basics, nothing special. As you can see, the community here is active and welcoming, most of what you might want to do is already in the docs or something that you can figure out by yourself or by asking the good questions here…

5 Likes