/qubes-issues

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updating to Xen 4.8.3-8 does not take effect #3924

Closed
esote opened this Issue May 24, 2018 · 7 comments

Comments

Assignees
No one assigned
Labels
Projects
None yet
Milestone
  Ongoing
3 participants
@esote @marmarek @andrewdavidwong
@esote

esote commented May 24, 2018

Qubes OS version:

R4

Affected component(s):

Xen

Steps to reproduce the behavior:

Expected behavior:

xl dmesg shows Xen 4.8.3-8

Actual behavior:

Updated using the current-testing repo using sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing. Xen and a few other packages were updated. dnf reports Xen is 4.8.3-8 while xl dmesg reports Xen is 4.8.3-3. As such, I cannot test the new Xen update (ie for issue #3689).

General notes:

Continuing from discussion on issue #3689.

Related issues:
@esote

This comment has been minimized.

Show comment
Hide comment
@esote

esote May 24, 2018

Pinging @marmarek

esote commented May 24, 2018

Pinging @marmarek
@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek May 24, 2018

Member

Do you have xen-4.8.3.efi file there? Is it different than xen.efi?
Member

marmarek commented May 24, 2018

Do you have xen-4.8.3.efi file there? Is it different than xen.efi?
@esote

This comment has been minimized.

Show comment
Hide comment
@esote

esote May 24, 2018

Yes,

# tree
.
├── BOOT
│   ├── BOOTX64.cfg
│   ├── BOOTX64.efi
│   ├── initramfs-4.14.35-1.pvops.qubes.x86_64.img
│   ├── initramfs-4.14.41-1.pvops.qubes.x86_64.img
│   ├── vmlinuz-4.14.35-1.pvops.qubes.x86_64
│   ├── vmlinuz-4.14.41-1.pvops.qubes.x86_64
│   ├── xen-4.8.3.efi
│   └── xen.cfg.anacbak
└── qubes
    ├── initramfs-4.14.35-1.pvops.qubes.x86_64.img
    ├── initramfs-4.14.41-1.pvops.qubes.x86_64.img
    ├── vmlinuz-4.14.35-1.pvops.qubes.x86_64
    ├── vmlinuz-4.14.41-1.pvops.qubes.x86_64
    ├── xen-4.8.3.efi
    ├── xen.cfg
    ├── xen.cfg.anacbak
    └── xen.efi

xen-4.8.3.efi is different than xen.efi (and likewise BOOTX64.efi), They are nearly the same size (xen-4.8.3.efi is very slightly larger).

./BOOT:
total 61012
-rwx------ 1 root root      871 May 23 15:01 BOOTX64.cfg
-rwx------ 1 root root  2074224 May 23 15:01 BOOTX64.efi
-rwx------ 1 root root 23018390 May 23 15:01 initramfs-4.14.35-1.pvops.qubes.x86_64.img
-rwx------ 1 root root 23018865 May 23 15:01 initramfs-4.14.41-1.pvops.qubes.x86_64.img
-rwx------ 1 root root  6133696 May 23 15:01 vmlinuz-4.14.35-1.pvops.qubes.x86_64
-rwx------ 1 root root  6137408 May 23 15:01 vmlinuz-4.14.41-1.pvops.qubes.x86_64
-rwx------ 1 root root  2078490 May 23 15:01 xen-4.8.3.efi
-rwx------ 1 root root        0 May 23 15:01 xen.cfg.anacbak

./qubes:
total 61012
-rwx------ 1 root root 23018390 May 22 19:24 initramfs-4.14.35-1.pvops.qubes.x86_64.img
-rwx------ 1 root root 23018865 May 23 14:53 initramfs-4.14.41-1.pvops.qubes.x86_64.img
-rwx------ 1 root root  6133696 May 14 17:55 vmlinuz-4.14.35-1.pvops.qubes.x86_64
-rwx------ 1 root root  6137408 May 23 14:53 vmlinuz-4.14.41-1.pvops.qubes.x86_64
-rwx------ 1 root root  2078490 May 23 09:58 xen-4.8.3.efi
-rwx------ 1 root root      871 May 23 14:53 xen.cfg
-rwx------ 1 root root        0 Apr 21 22:56 xen.cfg.anacbak
-rwx------ 1 root root  2074224 Apr 21 22:56 xen.efi

Should I copy xen-4.8.3.efi to xen.efi (and to BOOTX64.efi)?

esote commented May 24, 2018 •
edited
Edited 3 times
  • @esote esote edited May 24, 2018 (most recent)
  • @esote esote edited May 24, 2018
  • @esote esote edited May 24, 2018

Yes,

# tree
.
├── BOOT
│   ├── BOOTX64.cfg
│   ├── BOOTX64.efi
│   ├── initramfs-4.14.35-1.pvops.qubes.x86_64.img
│   ├── initramfs-4.14.41-1.pvops.qubes.x86_64.img
│   ├── vmlinuz-4.14.35-1.pvops.qubes.x86_64
│   ├── vmlinuz-4.14.41-1.pvops.qubes.x86_64
│   ├── xen-4.8.3.efi
│   └── xen.cfg.anacbak
└── qubes
    ├── initramfs-4.14.35-1.pvops.qubes.x86_64.img
    ├── initramfs-4.14.41-1.pvops.qubes.x86_64.img
    ├── vmlinuz-4.14.35-1.pvops.qubes.x86_64
    ├── vmlinuz-4.14.41-1.pvops.qubes.x86_64
    ├── xen-4.8.3.efi
    ├── xen.cfg
    ├── xen.cfg.anacbak
    └── xen.efi

xen-4.8.3.efi is different than xen.efi (and likewise BOOTX64.efi), They are nearly the same size (xen-4.8.3.efi is very slightly larger).

./BOOT:
total 61012
-rwx------ 1 root root      871 May 23 15:01 BOOTX64.cfg
-rwx------ 1 root root  2074224 May 23 15:01 BOOTX64.efi
-rwx------ 1 root root 23018390 May 23 15:01 initramfs-4.14.35-1.pvops.qubes.x86_64.img
-rwx------ 1 root root 23018865 May 23 15:01 initramfs-4.14.41-1.pvops.qubes.x86_64.img
-rwx------ 1 root root  6133696 May 23 15:01 vmlinuz-4.14.35-1.pvops.qubes.x86_64
-rwx------ 1 root root  6137408 May 23 15:01 vmlinuz-4.14.41-1.pvops.qubes.x86_64
-rwx------ 1 root root  2078490 May 23 15:01 xen-4.8.3.efi
-rwx------ 1 root root        0 May 23 15:01 xen.cfg.anacbak

./qubes:
total 61012
-rwx------ 1 root root 23018390 May 22 19:24 initramfs-4.14.35-1.pvops.qubes.x86_64.img
-rwx------ 1 root root 23018865 May 23 14:53 initramfs-4.14.41-1.pvops.qubes.x86_64.img
-rwx------ 1 root root  6133696 May 14 17:55 vmlinuz-4.14.35-1.pvops.qubes.x86_64
-rwx------ 1 root root  6137408 May 23 14:53 vmlinuz-4.14.41-1.pvops.qubes.x86_64
-rwx------ 1 root root  2078490 May 23 09:58 xen-4.8.3.efi
-rwx------ 1 root root      871 May 23 14:53 xen.cfg
-rwx------ 1 root root        0 Apr 21 22:56 xen.cfg.anacbak
-rwx------ 1 root root  2074224 Apr 21 22:56 xen.efi

Should I copy xen-4.8.3.efi to xen.efi (and to BOOTX64.efi)?
@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek May 24, 2018

Member

Ok, so I guess the xen-4.8.3.efi is the new one - you can override the one you use with it and check.
It looks like the instruction in that uefi workaround needs to be updated about which file should be copied.
Member

marmarek commented May 24, 2018

Ok, so I guess the xen-4.8.3.efi is the new one - you can override the one you use with it and check.
It looks like the instruction in that uefi workaround needs to be updated about which file should be copied.

@andrewdavidwong andrewdavidwong changed the title from Updating to Xen 4.8.3-8 does not take affect to Updating to Xen 4.8.3-8 does not take effect May 24, 2018

@andrewdavidwong andrewdavidwong added bug C: xen labels May 24, 2018

@andrewdavidwong andrewdavidwong added this to the Release 4.0 updates milestone May 24, 2018

@esote

This comment has been minimized.

Show comment
Hide comment
@esote

esote May 24, 2018

@marmarek That's worked, I now see "Xen 4.8.3-8.fc25". I agree, the documentation should note the xen-*.efi file. I am now seeing "XPTI: enabled" in xl dmesg, indicating Xen's meltdown protection.

Thanks for your help.

esote commented May 24, 2018

@marmarek That's worked, I now see "Xen 4.8.3-8.fc25". I agree, the documentation should note the xen-*.efi file. I am now seeing "XPTI: enabled" in xl dmesg, indicating Xen's meltdown protection.

Thanks for your help.

@esote esote closed this May 24, 2018

@andrewdavidwong andrewdavidwong reopened this May 24, 2018

@andrewdavidwong andrewdavidwong added C: doc task and removed C: xen bug labels May 24, 2018

@andrewdavidwong andrewdavidwong modified the milestones: Release 4.0 updates, Documentation/website May 24, 2018

@andrewdavidwong andrewdavidwong added the help wanted label May 24, 2018

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong May 24, 2018

Member

@esote:

That's worked, I now see "Xen 4.8.3-8.fc25". I agree, the documentation should note the xen-*.efi file. I am now seeing "XPTI: enabled" in xl dmesg, indicating Xen's meltdown protection.

Please consider submitting a PR. (I would just fix it myself, but I don't understand how you think the documentation should be changed, since it already mentions /boot/efi/EFI/BOOT/xen.efi.)

Edit: Ah, after reading the comments above, I see that it's something about having to perform a copying step that isn't mentioned in the documentation in addition to the renaming step that is already mentioned. Still, I think you're in the best position to add the missing information in the way that makes the most sense, since you just did it. I would still have to make a lot of (potentially wrong) assumptions to simulate your experience.
Member

andrewdavidwong commented May 24, 2018 •
edited
Edited 1 time
  • @andrewdavidwong andrewdavidwong edited May 24, 2018 (most recent)

@esote:

That's worked, I now see "Xen 4.8.3-8.fc25". I agree, the documentation should note the xen-*.efi file. I am now seeing "XPTI: enabled" in xl dmesg, indicating Xen's meltdown protection.

Please consider submitting a PR. (I would just fix it myself, but I don't understand how you think the documentation should be changed, since it already mentions /boot/efi/EFI/BOOT/xen.efi.)

Edit: Ah, after reading the comments above, I see that it's something about having to perform a copying step that isn't mentioned in the documentation in addition to the renaming step that is already mentioned. Still, I think you're in the best position to add the missing information in the way that makes the most sense, since you just did it. I would still have to make a lot of (potentially wrong) assumptions to simulate your experience.
@esote

This comment has been minimized.

Show comment
Hide comment
@esote

esote May 24, 2018

@andrewdavidwong Will do, it will notify below when I've submitted the PR.

esote commented May 24, 2018 •
edited
Edited 1 time
  • @esote esote edited May 24, 2018 (most recent)

@andrewdavidwong Will do, it will notify below when I've submitted the PR.

@esote esote referenced this issue in QubesOS/qubes-doc May 24, 2018

Merged

Info about copying xen-*.cfg, example commands #656

@andrewdavidwong andrewdavidwong closed this in QubesOS/qubes-doc@a5fe27a May 25, 2018

marmarek added a commit to QubesOS/qubesos.github.io that referenced this issue May 25, 2018

@marmarek
autoupdate: _doc attachment 
_doc:
    gpg: Good signature from "Andrew David Wong (Qubes Documentation Signing Key)" [ultimate]
    object a5fe27a2bde5c2ffef70e44af500e5e854be25f0
    type commit
    tag adw_a5fe27a2
    tagger Andrew David Wong <adw@andrewdavidwong.com> 1527208754 -0500

    Tag for commit a5fe27a2bde5c2ffef70e44af500e5e854be25f0

    a5fe27a Merge branch 'esote-patch-1' (Fixes QubesOS/qubes-issues#3924)
    37ddab0 Merge branch 'patch-1' of https://github.com/esote/qubes-doc into esote-patch-1
    a7ee113 Info about copying xen-*.cfg, example commands

attachment:
    gpg: Good signature from "Andrew David Wong (Qubes Documentation Signing Key)" [ultimate]
    object 1a346f56aa55fc85e37e9d1dcf4c643b8736be05
    type commit
    tag adw_1a346f56
    tagger Andrew David Wong <adw@andrewdavidwong.com> 1527208866 -0500

    Tag for commit 1a346f56aa55fc85e37e9d1dcf4c643b8736be05

    1a346f5 Merge branch 'AlmightyLaxz-master'
    2bcfae7 Merge branch 'master' of https://github.com/AlmightyLaxz/qubes-attachment into AlmightyLaxz-master
    86da7ff New image of MAC randomiztion step
Verified
This commit was signed with a verified signature.
@marmarek marmarek Marek Marczykowski-Górecki
GPG key ID: F32894BE9684938A Learn about signing commits
Loading status checks…
a32a821
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment