On 9/20/20 3:10 PM, Rusty Bird wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 9/20/20 2:03 PM, Marek Marczykowski-Górecki wrote:
In the meantime, I could use some help with debugging suspend issues[2]
which I consider one of the very few blockers before I switch to R4.1
myself :)
Oh shit, I'm like the least qualified person to help with this. I've
never even attempted to suspend any OS to RAM or to disk in my life.
Debugging suspend is hard, no? If the system goes catatonic and doesn't
wake up...
Anyway, it does not appear to be working on my Thinkpad T14 AMD.
If you have suggestions for gathering debug info I'll try them.
Chris Laprise:
* Allocating a thin lvm pool and then using the plain file pool type
Can you expand on what you're trying to do and how it's going wrong?
After building the iso and storing it on usb flash, I boot it using
additional xen parameters 'dom0_max_vcpus=1 dom0_vcpus_pin'. This is
necessary to get the installer running on a Ryzen 4000 system.
In the GUI, I choose my keyboard layout, then I click on the Install
Destination icon, leave it on automatic, click Done then enter a luks
passphrase. Next it says I need more space so I click on Reclaim Space
and then the Delete All button. Finally, I choose User Creation and give
it a simple user name+pwd.
The result is that Qubes domUs are using qcow image files, despite the
installer having setup lvm with a pool for root (which is being used by
dom0) and a large lvm pool for domUs (which is NOT being used at all).
Installing templates and creating new vms creates img files in
/var/lib/qubes (i.e. using the small root volume).
I didn't check the output of `qvm-pool` etc. but its obvious that its
using the wrong Qubes pool driver.
I could give you more info about how I configured qubes-builder, but all
I did really was copy the 'qubes-os-master.conf' example and change the
dom0 kernel to v5.8.5, and excluded any templates except fc30 to save
space and time.
(BTW, running qubes-builder in fc32 instead of fc30 results in an iso
with an invalid grub config).
* Incompatibility with a popular Intel wifi card
AX200? Then at least it's not a regression from R4.0.3.
Yes.
--
Chris Laprise, [email protected]
https://github.com/tasket
https://twitter.com/ttaskett
PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886
--
You received this message because you are subscribed to the Google Groups
"qubes-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-devel/e4736b69-8568-9486-3f07-f8c95e6a9d80%40posteo.net.
