On Wednesday, January 25, 2017 at 7:12:56 PM UTC-8, jkitt wrote:
> On Tuesday, 24 January 2017 11:54:34 UTC, qmast...@gmail.com wrote:
>
> > I was sad when installed VirtualBox, tried launching it and it said that
> > something like "not supported on Xen hosts"
>
> But why would you want to do
On Tuesday, 24 January 2017 11:54:34 UTC, qmast...@gmail.com wrote:
> I was sad when installed VirtualBox, tried launching it and it said that
> something like "not supported on Xen hosts"
But why would you want to do that? You already have virtual machines at your
disposal..
--
You
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2017-01-25 17:26, Oleg Artemiev wrote:
> I'm lazy enough to still use old Qubes. Is it possible to assign
> fixed start desktop (or range) for a VM in new Qubes? Ability to
> bind last window position for next session start is also a good
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2017-01-25 14:22, Pietro Speroni di Fenizio wrote:
> On Wednesday, January 25, 2017 at 11:13:54 PM UTC+1, Andrew David Wong wrote:
> On 2017-01-25 13:27, Pietro Speroni di Fenizio wrote:
Hello, we just installed a Qubes in a linux machine I
I'm lazy enough to still use old Qubes. Is it possible to assign fixed
start desktop (or range) for a VM in new Qubes? Ability to bind last
window position for next session start is also a good motivation to
upgrade. Qubrs VM manager may appear on diffrent desktop and this is
annoying.
It would be
On Wednesday, January 25, 2017 at 11:13:54 PM UTC+1, Andrew David Wong wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> On 2017-01-25 13:27, Pietro Speroni di Fenizio wrote:
> > Hello, we just installed a Qubes in a linux machine I had.
> >
> > Unfortunately the system seem to be
On Wednesday, January 25, 2017 at 6:22:14 PM UTC+1, raah...@gmail.com wrote:
> On Tuesday, January 24, 2017 at 9:15:10 AM UTC-5, Kopimi Security wrote:
> > On Monday, January 23, 2017 at 8:38:56 PM UTC+1, Reg Tiangha wrote:
> > > Yeah, I tried it myself leaving my laptop turned on and on learning
> If you run lspci in dom0 you will get the list of devices and their bus
> numbers. If you look for devices on :03:00 this should give clues about
> what is going on.
Thank you. So apparently the 03:00.2 is the Ethernet controller,
the 03:00.0 is a PCI express card reader.
In any case I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2017-01-25 13:27, Pietro Speroni di Fenizio wrote:
> Hello, we just installed a Qubes in a linux machine I had.
>
> Unfortunately the system seem to be unable to start any VM.
>
> I always get the same error: ERROR: internal error: unable to
Chris Bensch wrote:
> I'm running Qubes 3.2. I have a Debian HVM that works perfect when using the
> default sys-firewall as the netvm. If I change the netvm to another proxyvm
> such as a VPN (https://github.com/Rudd-O/qubes-vpn) or change it to the
> default sys-whonix, I lose all
Hello,
we just installed a Qubes in a linux machine I had.
Unfortunately the system seem to be unable to start any VM.
I always get the same error:
ERROR: internal error: unable to reset PCI device :03:00.2
internal error: Active :03:00.0 devices on bus with
000:03:00.2, not doing bus
On Wednesday, January 25, 2017 at 12:39:07 PM UTC-5, Reg Tiangha wrote:
> On 2017-01-25 10:24 AM, raahe...@gmail.com
> wrote:
>
> >
> > It should tell you what rbac is blocking in dmesg or journal no? it will
> > say gradm I believe. You should also be seeing grsec and pax messages in
> >
On 2017-01-25 10:24 AM, raahe...@gmail.com
wrote:
>
> It should tell you what rbac is blocking in dmesg or journal no? it will say
> gradm I believe. You should also be seeing grsec and pax messages in there
> as well.
>
It probably did, although sometimes it'll say what was killed, but
On Wednesday, January 25, 2017 at 12:24:57 PM UTC-5, raah...@gmail.com wrote:
> On Tuesday, January 24, 2017 at 10:32:18 AM UTC-5, Reg Tiangha wrote:
> > On 2017-01-24 7:15 AM, Kopimi Security wrote:
> > > On Monday, January 23, 2017 at 8:38:56 PM UTC+1, Reg Tiangha wrote:
> > >> Yeah, I tried it
On Tuesday, January 24, 2017 at 9:15:10 AM UTC-5, Kopimi Security wrote:
> On Monday, January 23, 2017 at 8:38:56 PM UTC+1, Reg Tiangha wrote:
> > Yeah, I tried it myself leaving my laptop turned on and on learning mode
> > for three weeks straight, but it didn't catch everything and certain
> >
On Friday, July 15, 2016 at 3:34:12 PM UTC+2, Chris Laprise wrote:
> On 07/13/2016 11:15 AM, Chris Laprise wrote:
> > On 07/12/2016 11:15 AM, Chris Laprise wrote:
> >> On 07/12/2016 01:48 AM, Chris Laprise wrote:
> >>> On 07/05/2016 02:21 PM, Marek Marczykowski-Górecki wrote:
> -BEGIN PGP
On Tuesday, January 24, 2017 at 7:16:54 PM UTC+1, Jimmy Axenhus wrote:
> Den 2017-01-24 kl. 18:34, skrev ms.amne...@donotusemy.info:
> > On Monday, January 23, 2017 at 4:22:56 PM UTC+1, Kopimi Security wrote:
> >
> > The only "tweak" I still need is the mouse pointer, as it is unaffected by
> >
I'm running Qubes 3.2. I have a Debian HVM that works perfect when using the
default sys-firewall as the netvm. If I change the netvm to another proxyvm
such as a VPN (https://github.com/Rudd-O/qubes-vpn) or change it to the default
sys-whonix, I lose all connectivity. Can someone point me
you can specify your modified config copy in qvm-start
--custom-config=/path/to/config vm-name
--
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
On 24/01/2017 23:30, Ángel wrote:
> Bernhard wrote:
>> Hello, I bricked my system a bit. Yesterady I decided to follow the
>> ..onion update procedure. For dom0 all went well (after reading that I
>> must change to whonix-net),but I had to modify the debian-8 and
>> fedora-24 repo-files "by
20 matches
Mail list logo
