On Monday, September 26, 2016 at 2:40:51 AM UTC-5, Mara Kuenster wrote: > Yes, SOME VMs work sometimes ☺. > > I will just reinstall, it’s better anyway to have no unsupervised downtime > between installing qubes and AEM, especially since I used Windows already on > the same PC before activating AEM. > Still this is a weird issue. Maybe one of the developers could try to > reproduce by installing with UEFI then activating BIOS and confirm this > messed up system? It is especially weird since the SAME system is just fine > when booting in UEFI. > > Btw, maybe you could add a warning to the installer that UEFI will not allow > AEM to be used, this would save a lot of time. I think I am not the only one > who didn’t read the AEM documentation that carefully :D. > > Cheers > Chris > > > On 26/09/16 01:34, "Marek Marczykowski-Górecki" wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256in > > On Mon, Sep 26, 2016 at 12:02:01AM +0200, Mara Kuenster wrote: > > Hmm yeah with that I managed to boot through BIOS mode, unfortunately > the VMs don’t start (randomly, different ones fail on each boot attempt). So > basically something seems to go wrong. The disks get decrypted and I can > login with the manager etc. but the system is more or less a complete failure > ^^. When I go back and boot in UEFI mode, everything works just fine… > > > > This seems kinda odd xD. > > Just to clarify - does any VM start at all? > If not, check if Xen is started. The easiest way is to call `xl info` in > dom0. If not, make sure you select grub boot entry containing "Xen". > > - -- > 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 > > iQEcBAEBCAAGBQJX6F72AAoJENuP0xzK19csLNcIAIJry9faT2BpdtxRqthd2QuK > ZE+jWf93MBDydoMX0vvGUptFBobYfRb4Qzyu0yihXT/a+uH2UbDKI7RskGISVU3I > BlhXbRcspfG1evnykOcOWAQ5wyPXDZrwB9+cztR4FuB48n6Ib3zLrPuJzqSFDiVZ > LrEg5OvUO+I1e1Bj//PyTCYTzApNWFmVcsC1+6DOchkeoNfnHNqtZlkhNGj+3580 > 2Se3XYCgTaLQ26MEoi1HYXJe5Gf9P3XLFdmiCoc7Ehjs3Cv3jK0Xq/knILiLvuV/ > o8xGFxMHHseTVfyQUUafE4xt1PoqOp28aziWMJf6MY7EHpVNhaZmFe0zAh6oIKw= > =dsD5 > -----END PGP SIGNATURE-----
Indeed. I don't understand why AEM can't be used with UEFI. The docs should also mention the reliance on TPM for AEM and the use of AEM prevents ability to swap drives in mobo easily, such as hot swapable SATA. That is probably not an important consideration in the majority of cases I suspect. Also, the conversion process should probably discuss GPT vs MBR partitioning. I was under the impression UEFI required GPT, but even if not, I do know booting an OS that resides on a GPT drive via BIOS (i.e. legacy) mode has problems. Most BIOS / legacy code doesn't even recognize a GPT drive. Often BIOS booting on a GPT drive relies on the protected partition region which isn't recognized across the board and is far from being well recognized my all Op Systems. -- 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/680c3a7c-8cac-44c1-864c-cc5da1496f4e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
