On Sunday, October 14, 2018 at 7:58:49 AM UTC-6, Chris Laprise wrote:
> On 10/12/2018 01:44 AM, 'awokd' via qubes-users wrote:
> > e on 10/12/18 5:37 AM:
> >> Hello,
> >>
> >> After completing install (for my first time), I was able to login.
> >>
> >> Going to the menu, "Create Qubes VM," getting
Hello,
After completing install (for my first time), I was able to login.
Going to the menu, "Create Qubes VM," getting the dialog box titled "[Dom0]
Create new qube," the Template select drop-down control only has
"default(none)," even if I select type Standalone rather than AppVM.
Also, I don
On Monday, October 8, 2018 at 8:42:50 PM UTC-6, awokd wrote:
> @gmail.com:
> > On Monday, October 8, 2018 at 8:10:17 AM UTC-6, awokd wrote:
> >>
> >>
> >>> Now, for the actual question. :) The installer reports missing
> >>> IOMMU/VT-d/AMD-Vi, however the machine's motherboard is an Intel Celeron
On Monday, October 8, 2018 at 8:10:17 AM UTC-6, awokd wrote:
>
>
> > Now, for the actual question. :) The installer reports missing
> > IOMMU/VT-d/AMD-Vi, however the machine's motherboard is an Intel Celeron
> > N3350 which, according to
> > https://ark.intel.com/products/95598/Intel-Celeron-
Kudos to the QubesOS team for the effort and cool idea that is Qubes.
I'm new Qubes and a few days ago decided to give it a try.
After dd'ing the R4 checksum-checked iso and turning off "secure boot" on
target device, I got a printk flood of GPE errors. After being unable to
stop/mask them with
