--
My Thinkpad also runs 3.2 with no issues minus the well known Nvidia issue. I was concerned as well trying the 4 prerelease, but I believe Joanna posted recently how Quebes 4 architecture is significantly different from all prior builds, not to mention new kernel. Many current users may require a completely new hardware. I think you are right many would benefit from a dedicated thread.
When I was able to get some sort of functionally I understood where most common tasks in 3.2 where relocated to in dom0. But I could not figure out how/where to go to restore my backups. Which brings me to the subject of 4 strictly using HVMs if I'm correct. Is there a process for app VMs to smoothly transition to HVMs? I have to assume these will all run in seamless mode? Lots of questions on top of the Thinkpad specific ones. I'm in no hurry for answers, they will come in time.
That being said, I can't begin to say how appreciative I am for the developers' hard work over the last two years to bring us a prerelease. And everyone should keep in mind that is exactly what it is, a prerelease. I'm not discouraged having to revert to 3.2 temporarily.
Cheers!
Pen
Many current users may require a completely new hardware. I think you are right many would benefit from a dedicated thread.
I've installed Qubes 4 from USB with VT-d disabled which works but throws an error in the end and which doesn't allow to start an AppVM:Start failed: internal error: libxenlight failed to create new domain 'sys-firewall'I have also tried to create a new Fedora 25 based AppVM (HVM and non-HVM) and run into the same error.I have enabled VT-d in the BIOS and rebooted, same error. I have enabled/disabled iommu=igfx / no-igfx same problem.Unfortunately it seems that I can't enable VT-d during Qubes installation as the installer will halt with a black screen when VT-d is enabled.See here for the hint regarding the Installation of Qubes 3.2 (?):As I didn't have any trouble installing and running Qubes 3.2 on the X200 (with 8 GB RAM) I don't understand what is the problem with Qubes 4.
(...)
I don't know enough to answer your question, but do you get any useful additional information when you remove 'rhgb quiet' from the xen boot parameters (which I assume is there)?
I have a Yoga S1 and I had the same problem. I was only able to install Qubes R3.2, also without Virtualization. After installing it, I'm able to use it though. I've already posted about this here: https://github.com/QubesOS/qubes-issues/issues/3001
Meanwhile, I'd do what I did - stick to R3.2