On my first try, I did not set x2apic=false when configuring the qubes on the second boot. I noticed, that I did not manually reboot the system and that it has started automatically.
Second try: Initial boot with x2apic=false working fine.
Second boot with x2apic=false, installation fails after setting up qubes, when do some configurations and then reboots without properly finishing the installation.
Booting again won’t get me to the installation again.
There was no error trace or something. Is there a good way to debug this?
Can you check the grub options? I think there should be something like “first_boot” option or something like this that will initiate initial setup to start. Try to remove it and boot without it.
same as before
I shuts down during the ...executing qubes configuration step of the installation. Next I try to set up qubes with “don’t configure anything” and try to continue from there.
Update: I got it booting into dom0 when choosing “don’t set up anything”.
How do I proceed from here? Can I manually execute the script step by step and see where it gets stuck?
Okay, I got it working with a fresh installation. It guess it was important to add an internet connection during the installation. There were some packages downloaded/updated which seem to be required.
Also I choose “don’t set up anything” on the second installation step.
Then I ran sudo /usr/libexec/initial-setup/initial-setup-graphical and my computer was shutting down during the network setup step.
Rebooting with qubes.skip_autostart works and I can start a qube and access the internet now.
Now I set qubes.skip_autostart for linux and x2apic=false for xen via (Custom kernel options/parameters not used - #5 by dipole).
Reboot is working without modification of kernel options. Updating VMs is working, updating dom0 is working via command line.
Remove all PCI devices (USB controllers) from sys-usb in its Qube Settings Devices tab.
Then add them one by one and try to start sys-usb to find the one that is causing this.
@Rnd3sB3g13rng how did you go with narrowing down the problem? I notice there does not appear to be an issue raised yet.
I will add another data point here: same problem with 7950X + Gigabyte X670E MB: normal installation of 4.2.0rc1 runs through to just after saying “Configuring networking”, on the second pass, then a hardware reset. Further boot attempts always hardware reset just after entering disk pass phrase. Need to add “qubes.skip_autostart” to linux boot options, boot up, untick start at boot in sys_usb, manually config networking and system is running. I found that sys_usb was OK with 4 out of 5 of the A670X USB controllers enabled - they seem to work fine. Don’t need x2apic=false at any time.
The problem is with device 37:00.0 something different about this controller in the 670 chipset?
Quick followup: I lost my MBR (not Qubes fault) so had to reload - tried the latest kernel instal, same result that problem is with just one USB controller, leaving it not passed thru to sys-usb allows the system to function normally. Yes it is pretty snappy at runnning Qubes. I have the 3D processor which has slightly lower base clock and 1/2 power consumption, typically, than 7950X.
First boot with 4.2.0rc1 bootstick (x2apic=false, tbh I don’t know if it is really required, but it’s working now and I will do a clean reinstallation anyway for 4.2.0 or 4.2.1).
Second boot (x2apic=false, just to be sure): I set the option “don’t set up anything” and clicked ok. You are forwarded to the login screen now.
Then I ran sudo /usr/libexec/initial-setup/initial-setup-graphical in dom0 and installed it qube by qube.
What is you problem in detail? I have not had any networking issues, only one of the usb controllers resulted in instant restart of the whole system when attaching it to sys-usb.
