On Wednesday, January 23, 2019 at 6:29:04 AM UTC-5, Mike Keehan wrote:
>
> Hi Bryce,
>
> Glad you got something working for you :)
>
> This is a good description of the changes in Qubes 4.0 :-
>https://www.qubes-os.org/doc/releases/4.0/release-notes/
>
>
On Saturday, January 19, 2019 at 6:37:47 AM UTC-5, Mike Keehan wrote:
>
> Ah, what a shame. It does seem as if your iommu is a problem.
>
> Without any other ideas, the only thing I can suggest is that you try
> the latest Qubes 3.2 just to allow you to try out Qubes. It doesn't
> require the v
> That's odd. You say you are installing 4.01, yet the qubes manager
> shows that fedora is only release 26. I thought that Qubes 4.01 had
> Fedora 29 in it.
>
> Mike.
Well Mike that could be it; you made me check when you said that, the image I
used was "Qubes-R4.0-x86_64.iso" from 11/27/18.
On Friday, January 18, 2019 at 10:31:33 AM UTC-5, Mike Keehan wrote:
> On Fri, 18 Jan 2019 07:17:00 -0800 (PST)
> scott wrote:
>
> > On Friday, January 18, 2019 at 9:16:59 AM UTC-5, unman wrote:
> > > On Fri, Jan 18, 2019 at 07:40:30AM -0500, Scott wrote:
> > > > Thanks but unfortunately I don't
On Monday, March 13, 2017 at 11:24:04 AM UTC-6, bryce.pa...@gmail.com wrote:
> Hi, I recently created a USB bootable installation media from my previous
> Windows 10 installation using a Microsoft media creation tool. In addition to
> the installation media, it contains info about my product key
On Monday, March 13, 2017 at 4:26:18 PM UTC-6, Grzesiek Chodzicki wrote:
> W dniu poniedziałek, 13 marca 2017 22:18:42 UTC+1 użytkownik
> bryce.pa...@gmail.com napisał:
> > Some additional information:
> >
> > vt-x is available and enabled in the BIOS
> > vt-d is not available
>
> Are You sure Y
Some additional information:
vt-x is available and enabled in the BIOS
vt-d is not available
--
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
Hi, I recently created a USB bootable installation media from my previous
Windows 10 installation using a Microsoft media creation tool. In addition to
the installation media, it contains info about my product key somehow. I've
done this before moving from HDD to SSD.
[dom0] mount /dev/sdd1 /mn