Le mercredi 9 novembre 2016 07:43:28 UTC-5, Pablo Di Noto a écrit : > > Bump. Its not Qubes specific. Same applies to latest Xen Hypervisor on > > Ubuntu 16.04.1. > > > > Any idea what got introduced into Xen between 3.0 and 3.1? > > I am using a X250 since last february (installed R3, updated to R3.1 and full > reinstall of R3.2). > > No problems with booting so far. > Let me know if you want to compare BIOS versions, config, etc. > > Regards, > ///Pablo
Yep I would like to, as I was able to use 3.1 with Legacy but can't boot 3.2. Updated BIOS to 1.25, made sur vt-d and vt-x were activated. It's an i7, if it changes anything. Attempting to add Xen hypervisor to Ubuntu results in the same behavior. Will attemtpt to find debugging arguments and setup AMT to have debug logs. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/2a01b957-53b1-4bc3-857d-b13d7c38e190%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
