Nested Virtualization seems to work generally well, albeit slower, even with
different hypervisors.
Despite the advice given in the install docs:
> Note: We don’t recommend installing Qubes in a virtual machine! It will
> likely not work.
I tried it an the Kernel comes up, as does the installe
Thanks!
--
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.co
MY sys info:
Custom built system using SuperMicro C7H170-m & using only onboard cpu video
which is from an Intel Core I3 6100. Qubes v3.1 official installation.
Mostly a non issue for me now (saw some of this during installation & seemed
like it disappeared during update phase like it wouldn't
Excuse if this is already asked or documented somewhere. I was not able to find.
I am 80 year old grandma and still learning computers so please dont flame me
too much. I am still learning. I ask questions so I can prevent from arriving to
error on false assumptions.
I am building Qubes from sourc
I wanted to mention this in case it helps others trying to compile Qubes.
Issue 1
I got lots of issues when trying to do qubes-builder at first. I figured out it
was because I was trying to build
Qubes 4.1 which is not stable build processes. I recommend buliding Qubes 4.0
for less compile issue
When using Qubes-Builder for making Qubes 4.0 I have one more issue
that I do not yet have solution for. I ran into other issues that I found
solution
and posted earlier here in qubes-users.
The unresolved issue is that Make failed to build 'builder'. Which can be seen
when listing with "make hel
> I used the command "make grubby-dummy" to build grubby-dummy. Then I was able
> to
> continue compiling as normal (you can type "make help" to list all the
> components that make builds,
> then list starting with where you left off at so you do not have to recompile
> the entire source tree. I
> I got this error too. The builder directory in qubes-src was empty, if I
> remember right. It didn't seem to have any impact on the ISO.
I confirm that the ISO seems to not have any issues.
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To un
For the newest security updates mention in
https://github.com/QubesOS/qubes-secpack/blob/master/QSBs/qsb-049-2019.txt how
can I install the security updates from security-testing repo but from source
code? I prefer to compile or install everything from source code. I do not
trust pre-baked bin
I was able to install Qubes from source using Qubes Builder. But how do I
install Qubes updates from source, for dom0 and the fedora and debian
templates? I do not want to have to trust precompiled binaries from the Qubes
repo.
Thank you
Sent with [ProtonMail](https://protonmail.com) Secure Em
10 matches
Mail list logo