On Saturday, April 8, 2017 at 3:26:58 AM UTC+9:30, john.c...@ucdconnect.ie
wrote:
> On Friday, 16 September 2016 08:09:46 UTC+1, almigh...@gmail.com wrote:
> > Qubes was working flawlessly on my GTX 670, recently upgraded to a GTX 1070
> > and now I can't even load the installer
>
> What
On Sunday, January 1, 2017 at 2:21:49 PM UTC+10:30, WillyPillow wrote:
> In short, there's not really an "one and only FirewallVM" in the system, but
> FirewallVMs that are assigned to each AppVM.
I see now, thanks. Each ProxyVM acts as the FirewallVM for whichever VMs use it
as a NetVM.
--
Hi,
>From my understanding, the FirewallVM is where the firewall rules are put into
>place from the Qubes VM Manager. The sys-firewall VM acts as the FirewallVM by
>default but what decides which VM gets that role? Is it automatically the
>first ProxyVM connected through the NetVM? Does naming
On Monday, December 19, 2016 at 4:33:06 PM UTC+10:30, Andrew David Wong wrote:
> How did you perform this step? Did you manually edit qubes.xml?
The VM Manager allowed me to 'remove' the VM. Because the VM was renamed, as
far as I can tell it just removed it from qubes.xml.
On Monday, December
So I made a HVM Template and renamed it through VM Manager, something went
wrong and the VM Manager did not reflect the name change. (Can't seem to
reproduce this bug)
I was just wondering if I've successfully removed the HVM Template manually.
The process I went through was:
1. Remove
I have been doing some tests using a GTX 1070, on Qubes R3.2, I think it is
fair to say GTX 900 and 1000 series cards are unusable right now going by user
reports.
Booting in BIOS mode without self-test:
Starting installer, one moment...
*black screen*
Booting in BIOS mode with self-test:
> > Qubes was working flawlessly on my GTX 670,
>
> So why did you change anything if things were working?
>
>
> Achim
Qubes isn't my main OS and I wanted an upgrade
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this
Qubes was working flawlessly on my GTX 670, recently upgraded to a GTX 1070 and
now I can't even load the installer
--
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
Update:
I have invented a temporary workaround.
Requirements:
Another usb or harddrive of 32gb (qubes system requirement)
Qubes installer or another *nix system
1. Install normally onto a USB or harddrive
2. Use the qubes installer (ctrl+alt+f2) or another *nix system to dd the
installed OS
Hi,
I am also having problems installing Qubes R3.1 to the Samsung T3 External SSD
500GB. Using a pgp and hash verified iso that passes the media verification
test. Running on a Intel Core i5-4570 @ 3.20GHz.
The install fails on the "creating swap" step with an "unknown error".
devices.py
10 matches
Mail list logo
