Attempting to move from v4.2 to 4.3 as an in-place upgrade. Not looking to go back to square one with a clean install.
Following the directions provided:
Nothing is happening. Ran 4 time verifying no typos. Can someone please advise how to get this upgrade accomplished without wiping the current v4.2.
Thank you.
Before folk are able to help you, I’m sure you’re going to have to give some details on the point in the install that’s failing.
Personally, I’d recommend (even if you’re clear it’s not the path you want) to do a clean install and then restore your own Qubes from back up. It would probably be quicker and cleaner than troubleshooting.
It seems like you’re more interested in keeping your settings than saving time. If that’s the case, you should learn how to salt your Qubes install; you can basically save your settings as a set of YAML files and transfer them anywhere.
It’s a time investment, but if you don’t have anything too wild, then it’s really pretty easy. unman’s shaker on GitHub has examples. It’s worth it IMO so you don’t lose your settings, and backups are smaller and easier since you only have to backup data.
In my case I believe the failure happened because I had non-standard qubes installed, like Alpine and Arch. Running the batch sripts did not work or give clear feedback.
Running the scripts one by one seemed to work, though I think there were failures with the non-standard templates.
The result was a broken upgrade in place requiring a clean install.
Whatever you do back up everything first.
Reading elsewhere a workaround was to backup any non-standard qubes, then delete them, and running the in-place update scripts on your system which only has standard templates. I don’t know if this works.
Good luck.
While that may be the path, the key issue being missed is for Qubes to gain traction in use, the continuing obsticals need to be addressed and removed. For me at this point is the increasing amount of effort for each upgrade will lead to abandoning Qubes.
Having started with computers in 1969 there is little I haven’t seen or played with. That includes writing a countless number of install/upgrade/implementation scripts for standalone through global environments. Not bragging or boasting. Just life.
Since the upgrade is locked down to a 4.2 to 4.3 jump a simple clean multi-step implementation script should have been simple.
For those way smarter than me w1th systems for more complex there would understandably be more cleanup involved.
While not the sharpest tack in the box, I have installed about 20 Qubes systems. My fee is the same, make a donation to the Qubes community. My payback.
I love Qubes and really hope the growing pains can be addressed.
Thanks for the reminder to finally start automating Qubes installation.
Just a quick question: I am already familiar and happy with Ansible and would like to not learn yet another configuration management tool. Is Ansible + Qubes 4.3 mature enough to substitute salt stack, incl. configuring both VMs and dom0 controller itself? Since there is no official guide yet (or is it?), GitHub - QubesOS/qubes-ansible: Ansible module and connection plugin for Qubes OS Install + usage instructions probably seem to be the best docs for now.
I would say Salt is definitely more mature, but I have no clue how mature Ansible is. I use and recommend Salt because I know it, but if you know Ansible, your time is probably better spent using that even if it means a wait.
TLDR: I don’t know.
@shantyspruce My bad, that question wasn’t targeted solely to you.
Found QOSS '25 - Ansible in Qubes OS presentation to be very interesting.
I would say that’s a conservative estimate.
7 posts were split to a new topic: Qubes 4.3: what are the new disposables that start in the background?