-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Mon, Dec 05, 2016 at 03:55:45AM +, Manuel Amador (Rudd-O) wrote:
> On 12/05/2016 02:50 AM, Marek Marczykowski-Górecki wrote:
> >
> > There are also still a couple of rough edges during installation/first
> > run. For
> > example "LVM thin"
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sun, Dec 04, 2016 at 11:19:41PM -0800, Vít Šesták wrote:
> I am interested about the implications of using HVMs. I know about the
> introduced need of some CPU features, some changes under-the-hood and
> potentiially better compatibility. But I
Hi Marek,
thanks for sharing this information. I found it quite interesting!
(and wouldnt mind to see such posts every 3 months or so…)
--
cheers,
Holger
--
You received this message because you are subscribed to the Google Groups
"qubes-devel" group.
To unsubscribe from this group
I am interested about the implications of using HVMs. I know about the
introduced need of some CPU features, some changes under-the-hood and
potentiially better compatibility. But I am interested in some others:
1. What will change about performance and memory-usage characteristics? I
believe
On 12/05/2016 02:50 AM, Marek Marczykowski-Górecki wrote:
>
> There are also still a couple of rough edges during installation/first
> run. For
> example "LVM thin" storage should be used, but currently it needs to be
> selected manually (using custom partitioning option). And depending on
> the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
Most of the features of Qubes 4.0 are done, but there are few more things to do
be fully useable. Below is (not so) quick summary.
0. (Mostly) rewrite of Qubes core management scripts.
Over time, our codebase grew significantly, and the focus
