Qubes R3.2 Rc1 feedback
192 views
Skip to first unread message
Alex
Jun 22, 2016, 4:32:53 AM6/22/16
to qubes-users
Hello everybody,
here's some feedback from the migration of a working 3.1 to 3.2 rc1.
First, hardware and situation:
assembled pc with asus Z97 motherboard, 32GB ram, integrated video,
intel i5 processor, 500GB hard disk. Three monitors, each with different
cable (one VGA, one DVI, one HDMI) all connected to the onboard internal
video adapter. Two monitors 1280x1024, one 768x1440 (it's a rotated 16:9).
Had a working Qubes 3.1 installation, and the only problem was that it
could NOT be used with UEFI (even if the motherboard supports it, and
the Qubes installer does boot and starts in EFI mode), because during an
EFI setup the computer completely freezes at the "Installing bootloader"
step. Text mode log says that it hangs at the second stage installation,
last message is something like "Installing stage2 on target device
/dev/sda2" (which should be the EFI partition). I'd like to have
anti-evil-maid out of curiosity.
Done a full backup (I do backup templates too; did that error of not
backing them up once - never again), downloaded Qubes 3.2 just to see if
the EFI bootloader installation worked, and - it did not. I start to
think it is a problem with my hardware that will never be fixed
upstream. I don't know if an existing installation can be "converted" to
EFI, and found very little online :(
Anyway, installed Qubes 3.2 non-efi, XFCE is my desktop environment, at
the beginning there are some glitches with icons missing - turns out
XFCE has to "index" or "preload" them, because they start appearing
after a few minutes. In the meantime, I removed the RPM templates (that
were installed even if unselected during setup!), reinstalled
kernel-qubes-vm that was automatically uninstalled when removing the
last template RPM but I think it's needed, and restored the backup.
The full restore brought back everything - dom0 settings, xrandr
settings, and the dependencies between VMs (who is the netvm of who).
The only problem here was that firewallVM was not marked anymore as
having ntpd enabled, and the clock could not sync. Enabled that,
restarted firewallVM, clock could sync again.
TL;DR: everything seems to work - audio, video, network, storage, except
for EFI whose bootloader continues to be unable to be installed on my
pc. Deselecting debian/whonix templates during setup has no effect (they
are installed anyway). Removing all RPM templates removes an unrelated
package that I think should be kept (kernel-qubes-vm). Data restore
works perfectly, apart from the ntpd service in firewallvm (may or may
not have been enabled in the original, I think so, can't I check anymore?).
Wrapping up, works for me. Thank you all for your good work!
--
Alex
here's some feedback from the migration of a working 3.1 to 3.2 rc1.
First, hardware and situation:
assembled pc with asus Z97 motherboard, 32GB ram, integrated video,
intel i5 processor, 500GB hard disk. Three monitors, each with different
cable (one VGA, one DVI, one HDMI) all connected to the onboard internal
video adapter. Two monitors 1280x1024, one 768x1440 (it's a rotated 16:9).
Had a working Qubes 3.1 installation, and the only problem was that it
could NOT be used with UEFI (even if the motherboard supports it, and
the Qubes installer does boot and starts in EFI mode), because during an
EFI setup the computer completely freezes at the "Installing bootloader"
step. Text mode log says that it hangs at the second stage installation,
last message is something like "Installing stage2 on target device
/dev/sda2" (which should be the EFI partition). I'd like to have
anti-evil-maid out of curiosity.
Done a full backup (I do backup templates too; did that error of not
backing them up once - never again), downloaded Qubes 3.2 just to see if
the EFI bootloader installation worked, and - it did not. I start to
think it is a problem with my hardware that will never be fixed
upstream. I don't know if an existing installation can be "converted" to
EFI, and found very little online :(
Anyway, installed Qubes 3.2 non-efi, XFCE is my desktop environment, at
the beginning there are some glitches with icons missing - turns out
XFCE has to "index" or "preload" them, because they start appearing
after a few minutes. In the meantime, I removed the RPM templates (that
were installed even if unselected during setup!), reinstalled
kernel-qubes-vm that was automatically uninstalled when removing the
last template RPM but I think it's needed, and restored the backup.
The full restore brought back everything - dom0 settings, xrandr
settings, and the dependencies between VMs (who is the netvm of who).
The only problem here was that firewallVM was not marked anymore as
having ntpd enabled, and the clock could not sync. Enabled that,
restarted firewallVM, clock could sync again.
TL;DR: everything seems to work - audio, video, network, storage, except
for EFI whose bootloader continues to be unable to be installed on my
pc. Deselecting debian/whonix templates during setup has no effect (they
are installed anyway). Removing all RPM templates removes an unrelated
package that I think should be kept (kernel-qubes-vm). Data restore
works perfectly, apart from the ntpd service in firewallvm (may or may
not have been enabled in the original, I think so, can't I check anymore?).
Wrapping up, works for me. Thank you all for your good work!
--
Alex
Andrew David Wong
Jun 23, 2016, 3:39:00 AM6/23/16
to Alex, qubes-users
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 2016-06-22 01:32, Alex wrote:
> Hello everybody, here's some feedback from the migration of a
> working 3.1 to 3.2 rc1.
Thanks for the feedback!
> First, hardware and situation: assembled pc with asus Z97
> motherboard, 32GB ram, integrated video, intel i5 processor, 500GB
> hard disk. Three monitors, each with different cable (one VGA, one
> DVI, one HDMI) all connected to the onboard internal video adapter.
> Two monitors 1280x1024, one 768x1440 (it's a rotated 16:9).
>
> Had a working Qubes 3.1 installation, and the only problem was that
> it could NOT be used with UEFI (even if the motherboard supports
> it, and the Qubes installer does boot and starts in EFI mode),
> because during an EFI setup the computer completely freezes at the
> "Installing bootloader" step. Text mode log says that it hangs at
> the second stage installation, last message is something like
> "Installing stage2 on target device /dev/sda2" (which should be the
> EFI partition).
I think this is to be expected. R3.1 does not support EFI.
> I'd like to have anti-evil-maid out of curiosity.
>
> Done a full backup (I do backup templates too; did that error of
> not backing them up once - never again), downloaded Qubes 3.2 just
> to see if the EFI bootloader installation worked, and - it did not.
> I start to think it is a problem with my hardware that will never
> be fixed upstream. I don't know if an existing installation can be
> "converted" to EFI, and found very little online :(
>
Bummer. :(
> Anyway, installed Qubes 3.2 non-efi, XFCE is my desktop
> environment, at the beginning there are some glitches with icons
> missing - turns out XFCE has to "index" or "preload" them, because
> they start appearing after a few minutes. In the meantime, I
> removed the RPM templates (that were installed even if unselected
> during setup!),
Noted, thank you:
https://github.com/QubesOS/qubes-issues/issues/2105
> reinstalled kernel-qubes-vm that was automatically uninstalled
> when removing the last template RPM but I think it's needed, and
> restored the backup.
>
> The full restore brought back everything - dom0 settings, xrandr
> settings, and the dependencies between VMs (who is the netvm of
> who). The only problem here was that firewallVM was not marked
> anymore as having ntpd enabled, and the clock could not sync.
> Enabled that, restarted firewallVM, clock could sync again.
>
Also noted, thanks:
https://github.com/QubesOS/qubes-issues/issues/2106
> TL;DR: everything seems to work - audio, video, network, storage,
> except for EFI whose bootloader continues to be unable to be
> installed on my pc. Deselecting debian/whonix templates during
> setup has no effect (they are installed anyway). Removing all RPM
> templates removes an unrelated package that I think should be kept
> (kernel-qubes-vm).
Tracking:
https://github.com/QubesOS/qubes-issues/issues/2107
> Data restore works perfectly, apart from the ntpd service in
> firewallvm (may or may not have been enabled in the original, I
> think so, can't I check anymore?).
>
> Wrapping up, works for me. Thank you all for your good work!
>
Thanks for the detailed report!
- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-----BEGIN PGP SIGNATURE-----
iQIcBAEBCgAGBQJXa5IEAAoJENtN07w5UDAwhUkP/3MHj1KshLfUFL2/nnQUGGhE
WeVlSEwgo1yb638hAGIg3UfRg76jDeS0WasQQhXmrGbqXyPfL7z5bRnLGWdLPUna
M9aXIaZXb5Bah6Q1fQk6fXy02AUV/1MGJyWGajXSI4+5NvFOgO83iVuxOyVcU8TD
245zHaFyfKEOmmk37JfqWF7j7yY2bLDhvB+NlrebfhKQZVikcskP2FdL1A452fUS
QMJ97+AF6IKv0n/XVqphpiEv8jEU792Gfq2wRLnS2YwlTiSkFNQ76jFn6Ilc3g8B
Zffsdpes6h7KXoYX6dskghFEeM6V2mJF5opeDM2/pK5J9O7ZB38uwP/9VXVWjcFs
ZDQufpcgwnQZlyvHRcSfzD1HbPOKG0aXo6IO/FjS/6KGsGQy2TI2ungYnK0fvjFr
dX8Yk/TpW3qxViUbAqfFMysXi5rEVdhGdQp2ws9fM8MibNTstMCJF4LInMYz7GBj
0i/PqWjqacdySG2x9ZTaC1pLuE9QaPlmssxdKQ2q4MVRCEwSBT2iHjPZWA30MHyr
1b0luI3rtDsjDjVFHMptacIWQHVuaQZTC9DuJZpAYHM277kT19AOmLWXjpYPDRZV
foi9M9CofuvqUPZZIhLsCG8NAZz6bCjc3yhY2HbHZnCR7jXTiGeqPXUtPaS2wd07
eO2FhOkCAvmn05R/8aPK
=bPfA
-----END PGP SIGNATURE-----
Hash: SHA512
On 2016-06-22 01:32, Alex wrote:
> Hello everybody, here's some feedback from the migration of a
> working 3.1 to 3.2 rc1.
> First, hardware and situation: assembled pc with asus Z97
> motherboard, 32GB ram, integrated video, intel i5 processor, 500GB
> hard disk. Three monitors, each with different cable (one VGA, one
> DVI, one HDMI) all connected to the onboard internal video adapter.
> Two monitors 1280x1024, one 768x1440 (it's a rotated 16:9).
>
> Had a working Qubes 3.1 installation, and the only problem was that
> it could NOT be used with UEFI (even if the motherboard supports
> it, and the Qubes installer does boot and starts in EFI mode),
> because during an EFI setup the computer completely freezes at the
> "Installing bootloader" step. Text mode log says that it hangs at
> the second stage installation, last message is something like
> "Installing stage2 on target device /dev/sda2" (which should be the
> EFI partition).
> I'd like to have anti-evil-maid out of curiosity.
>
> Done a full backup (I do backup templates too; did that error of
> not backing them up once - never again), downloaded Qubes 3.2 just
> to see if the EFI bootloader installation worked, and - it did not.
> I start to think it is a problem with my hardware that will never
> be fixed upstream. I don't know if an existing installation can be
> "converted" to EFI, and found very little online :(
>
> Anyway, installed Qubes 3.2 non-efi, XFCE is my desktop
> environment, at the beginning there are some glitches with icons
> missing - turns out XFCE has to "index" or "preload" them, because
> they start appearing after a few minutes. In the meantime, I
> removed the RPM templates (that were installed even if unselected
> during setup!),
https://github.com/QubesOS/qubes-issues/issues/2105
> reinstalled kernel-qubes-vm that was automatically uninstalled
> when removing the last template RPM but I think it's needed, and
> restored the backup.
>
> The full restore brought back everything - dom0 settings, xrandr
> settings, and the dependencies between VMs (who is the netvm of
> who). The only problem here was that firewallVM was not marked
> anymore as having ntpd enabled, and the clock could not sync.
> Enabled that, restarted firewallVM, clock could sync again.
>
https://github.com/QubesOS/qubes-issues/issues/2106
> TL;DR: everything seems to work - audio, video, network, storage,
> except for EFI whose bootloader continues to be unable to be
> installed on my pc. Deselecting debian/whonix templates during
> setup has no effect (they are installed anyway). Removing all RPM
> templates removes an unrelated package that I think should be kept
> (kernel-qubes-vm).
https://github.com/QubesOS/qubes-issues/issues/2107
> Data restore works perfectly, apart from the ntpd service in
> firewallvm (may or may not have been enabled in the original, I
> think so, can't I check anymore?).
>
> Wrapping up, works for me. Thank you all for your good work!
>
- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-----BEGIN PGP SIGNATURE-----
iQIcBAEBCgAGBQJXa5IEAAoJENtN07w5UDAwhUkP/3MHj1KshLfUFL2/nnQUGGhE
WeVlSEwgo1yb638hAGIg3UfRg76jDeS0WasQQhXmrGbqXyPfL7z5bRnLGWdLPUna
M9aXIaZXb5Bah6Q1fQk6fXy02AUV/1MGJyWGajXSI4+5NvFOgO83iVuxOyVcU8TD
245zHaFyfKEOmmk37JfqWF7j7yY2bLDhvB+NlrebfhKQZVikcskP2FdL1A452fUS
QMJ97+AF6IKv0n/XVqphpiEv8jEU792Gfq2wRLnS2YwlTiSkFNQ76jFn6Ilc3g8B
Zffsdpes6h7KXoYX6dskghFEeM6V2mJF5opeDM2/pK5J9O7ZB38uwP/9VXVWjcFs
ZDQufpcgwnQZlyvHRcSfzD1HbPOKG0aXo6IO/FjS/6KGsGQy2TI2ungYnK0fvjFr
dX8Yk/TpW3qxViUbAqfFMysXi5rEVdhGdQp2ws9fM8MibNTstMCJF4LInMYz7GBj
0i/PqWjqacdySG2x9ZTaC1pLuE9QaPlmssxdKQ2q4MVRCEwSBT2iHjPZWA30MHyr
1b0luI3rtDsjDjVFHMptacIWQHVuaQZTC9DuJZpAYHM277kT19AOmLWXjpYPDRZV
foi9M9CofuvqUPZZIhLsCG8NAZz6bCjc3yhY2HbHZnCR7jXTiGeqPXUtPaS2wd07
eO2FhOkCAvmn05R/8aPK
=bPfA
-----END PGP SIGNATURE-----
Alex
Jun 23, 2016, 7:46:03 AM6/23/16
to qubes...@googlegroups.com
On 06/23/2016 09:38 AM, Andrew David Wong wrote:
> On 2016-06-22 01:32, Alex wrote:
>
>> Had a working Qubes 3.1 installation, and the only problem was that
>> it could NOT be used with UEFI (even if the motherboard supports
>> it, and the Qubes installer does boot and starts in EFI mode),
>> [...]
> On 2016-06-22 01:32, Alex wrote:
>
>> Had a working Qubes 3.1 installation, and the only problem was that
>> it could NOT be used with UEFI (even if the motherboard supports
>> it, and the Qubes installer does boot and starts in EFI mode),
>
> I think this is to be expected. R3.1 does not support EFI.
>
Actually it should, at least per the release notes:
> I think this is to be expected. R3.1 does not support EFI.
>
https://www.qubes-os.org/doc/releases/3.1/release-notes/ (new features
since 3.0, it says "UEFI support") and I remember following the github
ticket for this very bullet point, and it was completed successfully.
I suspect this would happen with any plain linux distro, and suspect it
to be a bug in grub-efi, but since it takes a lot of time to trash a
system just to test with partitions/boot sectors/boot loaders I can't
invest more time on this specific workstation. I do apologize for this;
I'd like to help.
If details are needed:
- partitions have been decided autonomously by the installer
- it decided to put a 500MB /boot partition (/dev/sda1), followed by a
200MB /boot/efi partition (/dev/sda2), followed by the lvm container
(/dev/sda3)
- During boot loader installation, I can see three messages in the
anaconda log, but cannot remember them exactly. The first is "I'm gonna
install the bootloader!", the second says "Installing stage1 in
/dev/sda1" and the third says "Installing stage2 in /dev/sda2" - the
system freezes as soon as the third message appears.
- Checking online, two potential issues were mentioned:
* There may not be enough space on the EFI partition
* There may be older GPT data that may be picked up
- To try and debug the first issue, I let the installer set up the
partition tables and forced the EFI partition (/dev/sda2) to be 600MB
instead of 200 - same freeze on the same log message
- To try and debug the second, I "dd'ed" from /dev/zero to /dev/sda for
~8GB, and tried again reinstalling - same freeze on the same log message
- I don't know how grub-efi is supposed to work, but I do know grub
(stages/menu/etc) - is it right for an EFI installation to put a stage2
in the EFI partition?
That's everything in detail; hope this helps!
--
Alex
Andrew David Wong
Jun 23, 2016, 9:15:39 AM6/23/16
to Alex, qubes...@googlegroups.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hash: SHA512
On 2016-06-23 04:45, Alex wrote:
> On 06/23/2016 09:38 AM, Andrew David Wong wrote:
>> On 2016-06-22 01:32, Alex wrote:
>>
>>> Had a working Qubes 3.1 installation, and the only problem was
>>> that it could NOT be used with UEFI (even if the motherboard
>>> supports it, and the Qubes installer does boot and starts in
>>> EFI mode), [...]
>>
>> I think this is to be expected. R3.1 does not support EFI.
>>
> Actually it should, at least per the release notes:
> https://www.qubes-os.org/doc/releases/3.1/release-notes/ (new
> features since 3.0, it says "UEFI support") and I remember
> following the github ticket for this very bullet point, and it was
> completed successfully.
>
My mistake. You are correct.
> On 06/23/2016 09:38 AM, Andrew David Wong wrote:
>> On 2016-06-22 01:32, Alex wrote:
>>
>>> Had a working Qubes 3.1 installation, and the only problem was
>>> that it could NOT be used with UEFI (even if the motherboard
>>> supports it, and the Qubes installer does boot and starts in
>>> EFI mode), [...]
>>
>> I think this is to be expected. R3.1 does not support EFI.
>>
> Actually it should, at least per the release notes:
> https://www.qubes-os.org/doc/releases/3.1/release-notes/ (new
> features since 3.0, it says "UEFI support") and I remember
> following the github ticket for this very bullet point, and it was
> completed successfully.
>
- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-----BEGIN PGP SIGNATURE-----
rB0XRKc0yrY7cp641EH8SiIPGz1Z1tExE904Vo1lb7uvnbQqc/5WxTNcbQ/x1OVd
euQOMub+8rQ0pov4rTMJH7W0E8LGbd3Tq+7FVwC9WMEJlyRozbz9eI/2Yp78Kbdx
1YfDrjABzFOVwXhmlVT3/xuBwxuxiZVythLGz4945n9V2Pzdsjtf5R4RPatSblnO
DygTRSqPWX2o6yZqCCm2LihQf2jPi0cj8smCVolPUv1KAFMLp7OhqSYPSvj2aKTz
3nf9pDZUAxsM4NQUplv0r5HdzoWbqXglcz82D8u+80cwY3uACWms5/SdJEBCan9+
MQralmdpIHFmuZWpK+IJksFDjYBfskOzRrlGgO9NsPp7ZexqddaLxqLgGZA4TdlW
ktAnUmZLDU/rwOvA1gnvlZzd8UR7dipaED9eiJfJSD09etwE6AT5/kZwbVxtwwc0
uT3nclR0BGlEqiEa+dMsR5/wyeqqnsdQlIjMKq9+cg8ZWxJIEnGNskERj2eks4CO
HZOTUtqFQ9ZHzNEDhVKlShva/vclpg1I3wZtuSGSVcP9e+yd5QpaYCsuFuDvx3Xu
iYqQv9zhmfH5glNS3OXZecCqEsy5/AOge84JE/phsgkZ2ocFOxs92lo93+V5LRHa
uaCmSFo2qBKToQztMQhC
=BKlG
-----END PGP SIGNATURE-----
Marek Marczykowski-Górecki
Jun 29, 2016, 7:28:43 PM6/29/16
to Alex, qubes...@googlegroups.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
We don't use grub2-efi on installed system at all - Qubes (xen.efi to be
precise) is started directly from EFI. And in theory, in EFI
installation, Qubes doesn't need to have separate /boot (only
/boot/efi).
But as for debugging the freeze - have you tried options mentioned here:
https://www.qubes-os.org/doc/uefi-troubleshooting/
?
Symptoms are not exactly the same, but maybe it will help too...
- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQEcBAEBCAAGBQJXdFmbAAoJENuP0xzK19cseCMH/0e+S0kmcTp5zPR8AHxNexLv
MZMO3Vx93RZ+AwNjPIrweqtwyZ6IrK+v/A2MbSB6lFcK1C1w/8R2p7oDofipuEOB
Y0s1VQhUxRx0HMOWb0IV/xX5rayYn4dytaufQMBPieKKbEI3clsrcl73G5+ZBr5N
uLuz1f/q9yUl/qMkaNxB1c6wSyCCgKfXLxntMMFK+w4nJnemI/HV95KcHdOatE/H
BoOtYQ6JZ6jFK4AJfVTn2NKpF4Lfmj4JtGoPUSicfcy8iJ10WGNDNAaP/nB1Ik/5
yrvXwQucGOD1e0iFSz2eBSZP/jJnebfaJnDeDRLHDp0ISMlgQnp7l/mxTzqRhT0=
=KflT
-----END PGP SIGNATURE-----
Hash: SHA256
precise) is started directly from EFI. And in theory, in EFI
installation, Qubes doesn't need to have separate /boot (only
/boot/efi).
But as for debugging the freeze - have you tried options mentioned here:
https://www.qubes-os.org/doc/uefi-troubleshooting/
?
Symptoms are not exactly the same, but maybe it will help too...
- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQEcBAEBCAAGBQJXdFmbAAoJENuP0xzK19cseCMH/0e+S0kmcTp5zPR8AHxNexLv
MZMO3Vx93RZ+AwNjPIrweqtwyZ6IrK+v/A2MbSB6lFcK1C1w/8R2p7oDofipuEOB
Y0s1VQhUxRx0HMOWb0IV/xX5rayYn4dytaufQMBPieKKbEI3clsrcl73G5+ZBr5N
uLuz1f/q9yUl/qMkaNxB1c6wSyCCgKfXLxntMMFK+w4nJnemI/HV95KcHdOatE/H
BoOtYQ6JZ6jFK4AJfVTn2NKpF4Lfmj4JtGoPUSicfcy8iJ10WGNDNAaP/nB1Ik/5
yrvXwQucGOD1e0iFSz2eBSZP/jJnebfaJnDeDRLHDp0ISMlgQnp7l/mxTzqRhT0=
=KflT
-----END PGP SIGNATURE-----
Marek Marczykowski-Górecki
Jun 29, 2016, 7:35:16 PM6/29/16
to Alex, qubes-users
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hash: SHA256
On Wed, Jun 22, 2016 at 10:32:47AM +0200, Alex wrote:
> I don't know if an existing installation can be "converted" to
> EFI, and found very little online :(
Short answer: not easily.
> I don't know if an existing installation can be "converted" to
> EFI, and found very little online :(
> Anyway, installed Qubes 3.2 non-efi, XFCE is my desktop environment, at
> the beginning there are some glitches with icons missing - turns out
> XFCE has to "index" or "preload" them, because they start appearing
> after a few minutes. In the meantime, I removed the RPM templates (that
> were installed even if unselected during setup!),
available during installation (not first boot). And there you can
disable Debian and/or Whonix. But not Fedora, which is always installed.
What you can see during first boot, is only about creating default VMs,
based on those already installed templates.
- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
f4XAjdHDE+YRcQbr2rOxyCLvLtwWLGJ5Xdst48PWZQwOiNLVJCLzBam4vrmcUN3y
KVfnHdvzOtZOo2dONKRnzjPlwkI3mYQYuqoF7JTmIn8gJrG/4eP0OIxEaJOxoLVk
IVxS00/+uSGWZDLVEK2G3pDww5khQ9+UuXXHMvxSZdxCO9KdTKjqicGeNbOt1+mP
1TY/F6Yf89g0U4ASP2nZAOvx2uEmKaWgZZqwBBLa7Txrk6ySErbztyEF9L0OlQnx
AJwLCuZTbhuCqVq43H1Q8BuuJQq9O/+kXgWyqqWrfRmZzZTWkVVwpJDRTOkrVGI=
=tnw2
-----END PGP SIGNATURE-----
Alex
Jun 30, 2016, 2:51:12 AM6/30/16
to qubes...@googlegroups.com
On 06/30/2016 01:28 AM, Marek Marczykowski-Górecki wrote:
> On Thu, Jun 23, 2016 at 01:45:57PM +0200, Alex wrote:
>> On 06/23/2016 09:38 AM, Andrew David Wong wrote:
>>> On 2016-06-22 01:32, Alex wrote:
>>>
>>>> Had a working Qubes 3.1 installation, and the only problem was that
>>>> it could NOT be used with UEFI (even if the motherboard supports
>>>> it, and the Qubes installer does boot and starts in EFI mode),
>>>> [...]
>>>
>>> I think this is to be expected. R3.1 does not support EFI.
>>>
>
> On Thu, Jun 23, 2016 at 01:45:57PM +0200, Alex wrote:
>> On 06/23/2016 09:38 AM, Andrew David Wong wrote:
>>> On 2016-06-22 01:32, Alex wrote:
>>>
>>>> Had a working Qubes 3.1 installation, and the only problem was that
>>>> it could NOT be used with UEFI (even if the motherboard supports
>>>> it, and the Qubes installer does boot and starts in EFI mode),
>>>> [...]
>>>
>>> I think this is to be expected. R3.1 does not support EFI.
>>>
>
> We don't use grub2-efi on installed system at all - Qubes (xen.efi to be
> precise) is started directly from EFI. And in theory, in EFI
> installation, Qubes doesn't need to have separate /boot (only
> /boot/efi).
>
> But as for debugging the freeze - have you tried options mentioned here:
> https://www.qubes-os.org/doc/uefi-troubleshooting/
> ?
> Symptoms are not exactly the same, but maybe it will help too...
I'm afraid that those suggestion do not apply to my case - the problem
> precise) is started directly from EFI. And in theory, in EFI
> installation, Qubes doesn't need to have separate /boot (only
> /boot/efi).
>
> But as for debugging the freeze - have you tried options mentioned here:
> https://www.qubes-os.org/doc/uefi-troubleshooting/
> ?
> Symptoms are not exactly the same, but maybe it will help too...
is that when the installer has successfully installed all the packages
then proceeds with "post installation tasks", one of these tasks is
"Installing bootloader", and that's when it freezes completely if booted
in EFI mode.
The suggestions on the page you kindly link are related to the
bootloader (I understand it's xen.efi) is already installed, and not
when it's being installed...
Which software does the actual EFI boot component installation? Is it a
script of yours or some off-the-shelf program?
--
Alex
Alex
Jun 30, 2016, 2:54:13 AM6/30/16
to qubes...@googlegroups.com
On 06/30/2016 01:35 AM, Marek Marczykowski-Górecki wrote:
> On Wed, Jun 22, 2016 at 10:32:47AM +0200, Alex wrote:
>> I don't know if an existing installation can be "converted" to
>> EFI, and found very little online :(
>
> Short answer: not easily.
Aww. I guess it's ok this way.
> On Wed, Jun 22, 2016 at 10:32:47AM +0200, Alex wrote:
>> I don't know if an existing installation can be "converted" to
>> EFI, and found very little online :(
>
> Short answer: not easily.
>> Anyway, installed Qubes 3.2 non-efi, XFCE is my desktop environment, at
>> the beginning there are some glitches with icons missing - turns out
>> XFCE has to "index" or "preload" them, because they start appearing
>> after a few minutes. In the meantime, I removed the RPM templates (that
>> were installed even if unselected during setup!),
>
> Where exactly have you unselected them? The package selection is
> available during installation (not first boot). And there you can
> disable Debian and/or Whonix. But not Fedora, which is always installed.
>
> What you can see during first boot, is only about creating default VMs,
> based on those already installed templates.
same screen where I selected Qubes+XFCE instead of Qubes+KDE.
On the right pane there are three checkboxes, I suppose for the default
template packages. I unselected the three of them and then selected
Qubes+XFCE before clicking "Done" and continuing with other settings
(timezone, partitioning)
--
Alex
Marek Marczykowski-Górecki
Jun 30, 2016, 5:18:56 AM6/30/16
to Alex, qubes...@googlegroups.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hash: SHA256
installed and just installed system. And on Lenovo systems it is to
workaround a BIOS bug in functions accessing EFI variables. Those
variables are read during system startup (this is where original bug
manifests itself on Lenovo), but are written exactly where you
experience the freeze. So it may be applicable.
> Which software does the actual EFI boot component installation? Is it a
> script of yours or some off-the-shelf program?
- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
MN0ZJu1LmRnns5UZWpZBG6esQ9SI3yGgGVjn5nOZ3KzkHILDfnpU10xupIQp812Z
JGnpKYLa7Ge9xrVqoP/2vx7R/ehduixiXaNGsZELh3JD1MgxJRgV7xMXaU26aglD
NRnBj2C9DJi2GwsyV4ufNVRZXxwcbzZyp8ZunYr4zctwESEsk6o6MyeuKTDcvYDe
SQBM6lAapUrtNMsA6dN4xarN3oG1RHF6CXlq2qV2I5yaNjW+Lr+VqNL/XDBNt9/A
xydanj8vnNkSAvFKJXRKcd/57bKMzQBNlOP365jumI7YHQHf21dbL2CLi/dSMAc=
=6QTT
-----END PGP SIGNATURE-----
Alex
Jun 30, 2016, 5:23:07 AM6/30/16
to Marek Marczykowski-Górecki, qubes...@googlegroups.com
On 06/30/2016 11:18 AM, Marek Marczykowski-Górecki wrote:
> On Thu, Jun 30, 2016 at 08:51:09AM +0200, Alex wrote:
>> The suggestions on the page you kindly link are related to the
>> bootloader (I understand it's xen.efi) is already installed, and
>> not when it's being installed...
>
> Not necessary. That options (/mapbs /noexitboot) are applicable for
> both installed and just installed system. And on Lenovo systems it is
> to workaround a BIOS bug in functions accessing EFI variables. Those
> variables are read during system startup (this is where original bug
> manifests itself on Lenovo), but are written exactly where you
> experience the freeze. So it may be applicable.
Thank you, I will try to set these options as additional parameters in
> On Thu, Jun 30, 2016 at 08:51:09AM +0200, Alex wrote:
>> The suggestions on the page you kindly link are related to the
>> bootloader (I understand it's xen.efi) is already installed, and
>> not when it's being installed...
>
> Not necessary. That options (/mapbs /noexitboot) are applicable for
> both installed and just installed system. And on Lenovo systems it is
> to workaround a BIOS bug in functions accessing EFI variables. Those
> variables are read during system startup (this is where original bug
> manifests itself on Lenovo), but are written exactly where you
> experience the freeze. So it may be applicable.
the EFI boot menu before starting installation.
>> Which software does the actual EFI boot component installation? Is
>> it a script of yours or some off-the-shelf program?
>
> It is efibootmgr tool.
--
Alex
Marek Marczykowski-Górecki
Jul 1, 2016, 5:57:07 AM7/1/16
to Alex, qubes-users
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hash: SHA256
On Wed, Jun 22, 2016 at 10:32:47AM +0200, Alex wrote:
> In the meantime, I removed the RPM templates (that
> were installed even if unselected during setup!), reinstalled
> kernel-qubes-vm that was automatically uninstalled when removing the
> last template RPM but I think it's needed, and restored the backup.
Did you used dnf or yum to remove template rpms?
> were installed even if unselected during setup!), reinstalled
> kernel-qubes-vm that was automatically uninstalled when removing the
> last template RPM but I think it's needed, and restored the backup.
I can't reproduce the problem... But it may be related to dnf feature
enabled with clean_requirements_on_remove option, which is something
like automatic `apt-get autoremove`.
- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
SK+zQ90GXrSAixumqmNwfYYONRq+g3Oz7RAaOrtHwdWMlPqRxudYRcy+B7vlNtgj
aF9J2nobYXLyFM/f2J+6JkJHWIckvmEu/eb2yLKOQm1cd6JoiqK1/XoJNirNcn3G
GqUzEfk+gokHv1Fqjix3pF3r1L9gtylRGyJqukUVNGMdZKLdAwl6LjHV58YwKoKm
qnjFl155JHd01LN9SOfNOoJL14V8tLfDu7/QdIdG8ztGJSQS5R9IZ/83kZ+7Cb/E
/WmABpF2pEC/xj2EADXYG+/uIWLh95NskgTtki3EVpe2miePbLo8h647DGN2Up8=
=vvBI
-----END PGP SIGNATURE-----
Alex
Jul 1, 2016, 6:08:50 AM7/1/16
to qubes...@googlegroups.com
On 07/01/2016 11:56 AM, Marek Marczykowski-Górecki wrote:
> On Wed, Jun 22, 2016 at 10:32:47AM +0200, Alex wrote:
>> In the meantime, I removed the RPM templates (that
>> were installed even if unselected during setup!), reinstalled
>> kernel-qubes-vm that was automatically uninstalled when removing the
>> last template RPM but I think it's needed, and restored the backup.
>
> Did you used dnf or yum to remove template rpms?
> I can't reproduce the problem... But it may be related to dnf feature
> enabled with clean_requirements_on_remove option, which is something
> like automatic `apt-get autoremove`.
I'm sorry I don't really remember exactly what I did :/
> On Wed, Jun 22, 2016 at 10:32:47AM +0200, Alex wrote:
>> In the meantime, I removed the RPM templates (that
>> were installed even if unselected during setup!), reinstalled
>> kernel-qubes-vm that was automatically uninstalled when removing the
>> last template RPM but I think it's needed, and restored the backup.
>
> Did you used dnf or yum to remove template rpms?
> I can't reproduce the problem... But it may be related to dnf feature
> enabled with clean_requirements_on_remove option, which is something
> like automatic `apt-get autoremove`.
But straight from my dom0:/root/.bash_history,
# dnf remove qubes-template-debian-8
# dnf remove qubes-template-fedora-23 qubes-template-whonix-gw
# dnf remove qubes-template-fedora-23 qubes-template-whonix-ws
# dnf install kernel-qubes-vm
# dnf remove qubes-template-whonix-ws
# dnf install kernel-qubes-vm
# qubes-dom0-update kernel-qubes-vm
I can try to understand: when I gave the third dnf remove, it prompted
me that it would also remove kernel-qubes-vm, and I stopped it. So I
tried to set the package as manually installed somehow, hoping that it
would not be automatically removed, but since I'm not that expert with
dnf it may just have said "gee hee, that's already installed you dumb",
so I opted for the obvious way: removing both (whonix and kernel-qubes)
and reinstalling only the latter. I don't know why I later tried to use
qubes-dom0-update on the very same package.
I restored a dom0 backup shortly after, and I usually remove the
directory with contents that were in the user home before restore, so I
can't check now what was in the bash_history of the user (e.g. some
sudo-command), but I'm pretty confident that there would be nothing
related to this specific issue.
--
Alex
Marek Marczykowski-Górecki
Jul 1, 2016, 6:20:14 AM7/1/16
to Alex, qubes...@googlegroups.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hash: SHA256
On Fri, Jul 01, 2016 at 12:08:42PM +0200, Alex wrote:
> On 07/01/2016 11:56 AM, Marek Marczykowski-Górecki wrote:
> > On Wed, Jun 22, 2016 at 10:32:47AM +0200, Alex wrote:
> >> In the meantime, I removed the RPM templates (that
> >> were installed even if unselected during setup!), reinstalled
> >> kernel-qubes-vm that was automatically uninstalled when removing the
> >> last template RPM but I think it's needed, and restored the backup.
> >
> > Did you used dnf or yum to remove template rpms?
> > I can't reproduce the problem... But it may be related to dnf feature
> > enabled with clean_requirements_on_remove option, which is something
> > like automatic `apt-get autoremove`.
>
> I'm sorry I don't really remember exactly what I did :/
>
> But straight from my dom0:/root/.bash_history,
> # dnf remove qubes-template-debian-8
> # dnf remove qubes-template-fedora-23 qubes-template-whonix-gw
> # dnf remove qubes-template-fedora-23 qubes-template-whonix-ws
> # dnf install kernel-qubes-vm
> # dnf remove qubes-template-whonix-ws
> # dnf install kernel-qubes-vm
> # qubes-dom0-update kernel-qubes-vm
>
> I can try to understand: when I gave the third dnf remove, it prompted
> me that it would also remove kernel-qubes-vm, and I stopped it. So I
> tried to set the package as manually installed somehow,
dnf mark
> On 07/01/2016 11:56 AM, Marek Marczykowski-Górecki wrote:
> > On Wed, Jun 22, 2016 at 10:32:47AM +0200, Alex wrote:
> >> In the meantime, I removed the RPM templates (that
> >> were installed even if unselected during setup!), reinstalled
> >> kernel-qubes-vm that was automatically uninstalled when removing the
> >> last template RPM but I think it's needed, and restored the backup.
> >
> > Did you used dnf or yum to remove template rpms?
> > I can't reproduce the problem... But it may be related to dnf feature
> > enabled with clean_requirements_on_remove option, which is something
> > like automatic `apt-get autoremove`.
>
> I'm sorry I don't really remember exactly what I did :/
>
> But straight from my dom0:/root/.bash_history,
> # dnf remove qubes-template-debian-8
> # dnf remove qubes-template-fedora-23 qubes-template-whonix-gw
> # dnf remove qubes-template-fedora-23 qubes-template-whonix-ws
> # dnf install kernel-qubes-vm
> # dnf remove qubes-template-whonix-ws
> # dnf install kernel-qubes-vm
> # qubes-dom0-update kernel-qubes-vm
>
> I can try to understand: when I gave the third dnf remove, it prompted
> me that it would also remove kernel-qubes-vm, and I stopped it. So I
> tried to set the package as manually installed somehow,
> hoping that it
> would not be automatically removed, but since I'm not that expert with
> dnf it may just have said "gee hee, that's already installed you dumb",
> so I opted for the obvious way: removing both (whonix and kernel-qubes)
> and reinstalling only the latter. I don't know why I later tried to use
> qubes-dom0-update on the very same package.
download it again.
So it looks like my guess was right. And kernel-qubes-vm needs to be
marked as needed regardless of template rpms.
- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
oXqaUR4wQtNgfxbhrD+McIuid52MHUWCUQJZl/AlsSHbFnjR+l8XKGajHdxoymVS
hRLOIsVDWyUQetX4O3SvXDHa47YSjY1CApNvrqeEsDfH2LkIciwR1s0gE8/lQfUL
dilUiVJwoeYULHoWQjozpyI+OFyQMq7FL4V65WsaEMzX0IBXS/VYRRZi7ZkmHa93
fD6+6qgSVXeFUOacbc6x3mPJGIrDp20kh9HeDQRcy8GEW4QqvU1YcryGB5Q7ASLD
crhivYm9UHlLYgASedGjWaXKaWf+BNcNmNHnYSInW8pFSvxhrTXmFlprsEtue3I=
=brpg
-----END PGP SIGNATURE-----
ni...@kobschaetzki.net
Jul 1, 2016, 6:22:29 AM7/1/16
to Marek Marczykowski-Górecki, Alex, qubes-users
On July 1, 2016 at 11:56 AM Marek Marczykowski-Górecki <marm...@invisiblethingslab.com> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256On Wed, Jun 22, 2016 at 10:32:47AM +0200, Alex wrote:
In the meantime, I removed the RPM templates (that
were installed even if unselected during setup!), reinstalled
kernel-qubes-vm that was automatically uninstalled when removing the
last template RPM but I think it's needed, and restored the backup.
Did you used dnf or yum to remove template rpms?
I can't reproduce the problem... But it may be related to dnf feature
enabled with clean_requirements_on_remove option, which is something
like automatic
apt-get autoremove.
In my experience dnf has pretty much always this behavior.
Niels
Reply all
Reply to author
Forward
0 new messages