dom0 update in Qubes 4.0

38 views
Skip to first unread message

gro...@gmail.com

unread,
Dec 7, 2017, 10:17:21 PM12/7/17
to qubes-users
Although a long-time user of Qubes 3.2, I'm a novice in the sense of not having much understanding under the hood yet, and also am quite new to this group. If I've overlooked some FAQ or relevant posting, apologies in advance; terse pointers welcome.

With the old VM Manager in Qubes 3.2, when a "dom0 updates are available" notification appeared, I would dutifully update and reboot. On my new machine with a fresh Qubes 4.0-rc3 install, in a dom0 terminal I did "sudo qubes-dom0-update" got myself into trouble. After reboot, sys-net would not start and of course life is difficult after that. I found it easiest to just re-install from scratch.

question 1: Is there something else I should have done, besides take more careful notes about how I got myself wedged?

question 2: Is there a standard way one is supposed to sign up for VM update availability notices in the new world?

Chris Laprise

unread,
Dec 7, 2017, 11:01:48 PM12/7/17
to gro...@gmail.com, qubes-users
On 12/07/2017 10:17 PM, gro...@gmail.com wrote:
> Although a long-time user of Qubes 3.2, I'm a novice in the sense of not having much understanding under the hood yet, and also am quite new to this group. If I've overlooked some FAQ or relevant posting, apologies in advance; terse pointers welcome.
>
> With the old VM Manager in Qubes 3.2, when a "dom0 updates are available" notification appeared, I would dutifully update and reboot. On my new machine with a fresh Qubes 4.0-rc3 install, in a dom0 terminal I did "sudo qubes-dom0-update" got myself into trouble. After reboot, sys-net would not start and of course life is difficult after that. I found it easiest to just re-install from scratch.
>
> question 1: Is there something else I should have done, besides take more careful notes about how I got myself wedged?

That's the way you update in rc3. But you might want to update with
--enablerepo=qubes*testing to see if that resolves the sys-net issue. Of
course, it might bring the problem back.

You could try to snapshot your dom0 LVM volume (called 'pool00/root')
before the update and then restore the snapshot if something goes wrong.

> question 2: Is there a standard way one is supposed to sign up for VM update availability notices in the new world?

I'm not aware of an update notifier (yet) in R4.0.

--

Chris Laprise, tas...@posteo.net
https://github.com/tasket
https://twitter.com/ttaskett
PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886

Reply all
Reply to author
Forward
0 new messages