update dom0 offline?

61 views
Skip to first unread message

Sven Semmler

unread,
Dec 7, 2017, 5:00:33 PM12/7/17
to qubes-users
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

My problem: new computer (ThinkPad P51) comes with Intel networking
hardware which requires kernel 4.9 to be detected. When installing
Qubes 3.2 one starts of with kernel 4.4.

I can see on my other computer that is already running Qubes 3.2 that
Dom0 is meanwhile at kernel 4.9 - how can I update dom0 on my new
machine? Is there some way I could download the packets on my old
computer, transfer them to the new and update dom0?

I am aware that Qubes 4 has kernel 4.9 from the start. But I am also
aware that it is still an RC and doesn't (yet) support Windows VMs.

/Sven



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJaKbn7AAoJENpuFnuPVB+28LMQAM+crCLrTRutFAGyPI7aUXFN
r2x0TD6AIh7tMhxOS6sFmBACEhDe3nL35HBW2S33pdnuZxL5f1L5bmoikSvy4Ypj
Hu8HsK9Mvg2VLJo4UmjdS4MvjqQpIegipKu4O4MunFyzaU9qK/UyWZ4lQQp3XXar
M1R2Yg/3WVaMiqzIHpvkp2TIrKtGCwmIerVoO0tPhDCC5I8bFxe8jlyS01aN4FZ2
VKiJHXQkJ2ohK2HKkoZixdyGgxU3vIFBZh5WPVQoTiEZjOOKvSxq9z7o9uTKbwT0
lLp8n+ANXYyxRKnNBjWzelOeeCIE4BeHC4dxoOrJ+un2Z45FKuKbi+EEy5FA/AXa
su44Waw9uBlwxVrdqtCOjFbaCOKJiCJs98ilmpqtbQ8y+MC2Z2jWrE08ftBgkLAL
pvWG/ULyRAZ/mvigGZ8zWo97hK9km3Dlu0YTJL7XZnWeMVYIeBVJyGIaVoRXblUm
8zQb7FtTXS2bTNI6hNDIOBQ7624EuXTI3TRTGhdvnCM7OCb08aDlXlWf53N7O0Dh
NpOX1tyg8AiB7OA6RBR9bPRwETKeh+YopjlUrvdYUnUreWvzhELTtlmX0PEvxdzr
b1ICRvX01RWH2SYr60KninRdyvNdZ0uegAc8uG7lZMNSoH9v6x25qgRofkpX12Nc
QsiGyY/0XnZ+Q0qS/frc
=oEXD
-----END PGP SIGNATURE-----

Unman

unread,
Dec 7, 2017, 7:37:43 PM12/7/17
to Sven Semmler, qubes-users
On Thu, Dec 07, 2017 at 04:00:27PM -0600, Sven Semmler wrote:
> My problem: new computer (ThinkPad P51) comes with Intel networking
> hardware which requires kernel 4.9 to be detected. When installing
> Qubes 3.2 one starts of with kernel 4.4.
>
> I can see on my other computer that is already running Qubes 3.2 that
> Dom0 is meanwhile at kernel 4.9 - how can I update dom0 on my new
> machine? Is there some way I could download the packets on my old
> computer, transfer them to the new and update dom0?
>
> I am aware that Qubes 4 has kernel 4.9 from the start. But I am also
> aware that it is still an RC and doesn't (yet) support Windows VMs.
>
> /Sven
>
Sven

You can always grab the files from yum.qubes-os.org on the old computer.
Then you can copy them in to a qube, and transfer to dom0 on the
new computer.
The transfer TO dom0 is covered here:
www.qubes-os.org/doc/copy-from-dom0/

Rather than iterate over the files, I would tar them in the qube, and
untar in dom0

To make sure you have the right files, don't forget to check them with
rpm -K before installing them on your new system.

unman

Ro...@tuta.io

unread,
Dec 7, 2017, 7:57:50 PM12/7/17
to qubes-users
Im not sure how easy it is for your hardware. I just had an issue with my new desktop and not wanting to run v4.

What i did was take out the drive on the desktop and install on the laptop i have that runs 3.2 just fine. Then i updated the kernel there and changed the boot files since it doesnt pick it up on new one and then swapped the drive back to the desktop. Was actually alot easier then expected this way but i can swap a drive in a couple mins on my laptop.

Sven Semmler

unread,
Dec 10, 2017, 11:58:37 AM12/10/17
to qubes-users
On Dec 7, 2017, at 6:37 PM, Unman <un...@thirdeyesecurity.org> wrote:

You can always grab the files from yum.qubes-os.org on the old computer.


All of them? There seem to be different versions. If I copy all of them, is there a way to tell dnf to just upgrade the packets that are already installed?

Here is what I already tried:

- installed R4rc3 and confirmed that kernel 4.9 supports my hardware 

- on my old R3.2 machine uname -r returns 4.9 both in dom0 and the fedora-25 template

- I copied that template to the new machine now running R3.2 freshly installed and both dom0 and the template report kernel 4.4 (expected for dom0 but would have thought the template would continue to report 4.9)

- I then downloaded and transferred and installed the dom0 kernel 4.9 rpm from yum.qubes-os.org. Now dom0 reports 4.9 but the fedora-25 template still reports 4.4 ??? 

- when trying to install kernel-qubes-vm-4.9.56-21.pvops.qubes.x86_64.rpm I get dependency errors. 

Do I just download all rpms and let dnf sort it out? 

Thank you for your time and support!

/Sven





Unman

unread,
Dec 10, 2017, 8:06:43 PM12/10/17
to Sven Semmler, qubes-users
The repo contains all the old versions of files as well, so if you are
downloading manually you only need to pull the most recent versions.

An alternative approach might be to try this in your network connected
box:
sudo qubes-dom0-update --action=download <pkg-name>
I *think* that dnf will do the right thing and resolve dependencies for
you. This should download the packages to the current directory, then
you can transfer them to the offline box and install them manually.
dnf will select the most recent version if you only give a package name -
if you want a specific version you can specify that.





Sven Semmler

unread,
Dec 11, 2017, 12:06:19 PM12/11/17
to qubes...@googlegroups.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 12/07/2017 06:57 PM, Ro...@tuta.io wrote:
> Im not sure how easy it is for your hardware.

I looked into it. My old computer runs SATA and legacy BIOS, the new
one M.2 PCIe SSD and UEFI ... I tried imaging the one and using it on
the other with Clonezilla but that didn't work.

Also my M2 memory uses "M key" and I have not been able to locate any
M2-SATA adapters that would work.

So thanks for the hint, but I am afraid it won't work out.

/Sven


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJaLrrmAAoJENpuFnuPVB+2w5sQAKpqu/mtoY0W+vPIQjA/P6K0
JP2K5ELkeb+WRwiujyupltpreSBmxGultsTPKe9PybNQCax9UZwlstlQHz64ISY4
su4klVKgb79Z22RGlRj6YVr6muXRW/EzeN+IduMs4dml6205aDqCyLBV6jp5eHqS
fnO81LEoTFpa3OQS8E3ALnin7bAdz3UOPWIKxIiUflDjwwIOLTFpTTU0yKDfOXGZ
0ZPIHmUEg6Ab3igNRzzuUwrP9gsYIfvxhWIVBs047OJ3RRoeRuHsAXmnMC1uLPkj
iZHZOb76YTGi7i2RxQjdHaSHUyxjXZE8+GXKb7aoDo26+/A0C3+mS/frGEbWqZPB
bv/1LTid6DpmIxg/nxWflOHqa9/wUsLm0xXCzeCkPk7aSH4CCwb07f471JZyu3ZM
wIftO0sSVcMNZ8MK9X4gBFGBlqTEoVRId8y+5o/kI2lf/9Xc//dhVlFSCu522YXh
QOOj1JF2QUUl8bLcxs3yhxk/cAEtQPWhEFzB901AKCZwi3UQ8DQhejp1MzGTgsxL
H27oYMTl4gatRy5rPRAAoeuf/+b8T78gn2vnnLAMB7Qx1Kmfns+19E5KUD60dh+Q
JtXCZqU1N+jCnyKkOxp9md25iQpqihRFlX42Fpcm8GwoEjOOyoNiLEC6GyYocgy4
fTNiuWt8EzMuUxMivWdl
=W3Nn
-----END PGP SIGNATURE-----

Sven Semmler

unread,
Dec 11, 2017, 12:25:03 PM12/11/17
to qubes-users
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 12/10/2017 07:06 PM, Unman wrote:
> sudo qubes-dom0-update --action=download <pkg-name> I *think* that
> dnf will do the right thing and resolve dependencies for you. This
> should download the packages to the current directory, then you
> can transfer them to the offline box and install them manually. dnf
> will select the most recent version if you only give a package name
> - if you want a specific version you can specify that.

Thank you! Although I couldn't get it to work. My original plan was to
go with R4 for the new computer and that's what I will do now. Once
everything is setup, I'll reformat the old one and make it a Windows
machine for those few use cases I can't solve on Linux.

I'll also give installing Windows on R4 a try. As long as I can get
networking to work, I should be fine even without qubes-windows-tools
for now.

/Sven

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJaLr9nAAoJENpuFnuPVB+2t/gQAIm6ni7geic89xAGV/D1Xrxv
jeNs38CXBa2dU946NpVnzxs0qTJhalxPV3Zulyk0MN3QEjXg/IUTkfKJXKcr5sRs
JJnz2i+KXYZYB/RxyiP9X1zuXeqGPf4QLAF/lmgwMcw4pCOl/IFttTzNrlgvCElM
7V6lhgMreWvLnkurkNfZWHhy3UDfum6S7f7g0ddTAM14GFUI9wZbfYOnbWSVY9Y9
N7YmkOrECobuYj+YHy9Z5GpVMtiOkz+ZbvFl7GN61FPUz+CAH/kat4QcQx7gErar
dq+j/gUjFhUqywLwh3Uql0nT9AvpeojnpXrEQblcJ+JzsC2wk6M3fYnQ2EZ428E3
QB/Uy+qYpTFyA9WIuqNN5BB2fEu6SQV59sgP/URkC0y7xafmdRLvMf96ArIuem4I
3i9vbKQMdF7qLNqLsLCJqIppBJgcVyWwMJKUWJCDxiuJBpXKCDo408yzK5sKDd82
fj1OEglzjgqQ2YrepS9GLP8qyfxtZh0DB8f1e72JDk11tpVinYy5n/GgU0NmblaI
n+7pvyAIWgv61GnpAcVnhf/79bRY2Fb/qc9OVEM+T6ueFY/qWX9tVmHeBph3//Mz
TugfOWY8WID0AhXI9Pyb/KJV5GJDfYI9Y1WsA04VYzn2HTWHv/Bq9h6BZvLsi9P/
idV6Fr3/ahtNnFo7+J7w
=2/CP
-----END PGP SIGNATURE-----
Reply all
Reply to author
Forward
0 new messages