On Friday, November 17, 2017 at 6:22:03 AM UTC-7, Styles Grant wrote:
> I did see some evidence of one guy who got a ryzen to work, and another who
> got an a 10 series to work. I'd nab an a 10, but this old fx 8350 is on sale.
>
> What do you think?
I'm running on an FX-6300, and it's working
The nature of the error was deterministic, deterministic as in "stupid human."
I really appreciate all the support but I had some really similar file names
and way too much faith in my command line history.
Sorry guys.
(I had also been working 16+ hours at the time.)
--
You received this
First of all - which Qubes version?
I run Qubes 3.2.
Where is the ISO you want to attach - in dom0, or in some other VM?
I put the ISO in another VM, sys-net.
I took a look at /var/log/libvirt/libxl/libxl-driver.log for some details.
The log looked like this:
https://imgur.com/a/rK9Bq
--
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2017-11-17 19:56, Gordon Rice wrote:
>>
>> The warning is evident: Andrew's key is not signed. Questions about this
>> have been asked before, and the reason is probably that most of the
>> Qubes team are using split-gpg
>
> The warning is evident: Andrew's key is not signed. Questions about this
> have been asked before, and the reason is probably that most of the
> Qubes team are using split-gpg (www.qubes-os.org/doc/split-gpg) with
> subkeys. If you review that page then you will see that one of the
>
On Fri, Nov 17, 2017 at 11:47:06AM -0800, d5od...@gmail.com wrote:
> On Friday, September 29, 2017 at 6:31:15 PM UTC-7, Andrew David Wong wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA512
> >
> > Dear Qubes community,
> >
> > On 2017-09-12, we published Qubes Canary #13. The text of
Thank you for the answer to the first question. The back ticks took care of not
finding the file. The warning pops up for the `git describe` now though:
$ git tag -v `git describe`
object 8567fa1b877d5afa5789448a0027717a44329cd3
type commit
tag adw_8567fa1b
tagger Andrew David Wong
On Friday, November 17, 2017 at 7:49:00 AM UTC-7, toront...@gmail.com wrote:
> I intend to reinstall 3.2 which is currently running on somewhat undersized
> SSD. This time I would like to keep most of the semi-static portions of the
> OS and templates on the SSD for speed and to reduce wear on
On Fri, Nov 17, 2017 at 2:47 PM, wrote:
> On Friday, September 29, 2017 at 6:31:15 PM UTC-7, Andrew David Wong wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA512
>>
>> Dear Qubes community,
>>
>> On 2017-09-12, we published Qubes Canary #13. The text of this canary
Is it random, or deterministic?
Do you observe any signs of unstable system (e.g., freezes, app crashes, VM
crashes, system crashes…)? If you do, it might be a faulty RAM.
Regards,
Vít Šesták 'v6ak'
--
You received this message because you are subscribed to the Google Groups
"qubes-users"
On Friday, September 29, 2017 at 6:31:15 PM UTC-7, Andrew David Wong wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Dear Qubes community,
>
> On 2017-09-12, we published Qubes Canary #13. The text of this canary is
> reproduced below. This canary and its accompanying signatures
Mine is not working, it won't load VMs.
If this replace prior to scheduled release date?
When I go to the download page and click on 'version', focus changes to the
bottom of the page but I don't find anything about interim releases.
Ray
--
You received this message because you are
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Thu, Nov 16, 2017 at 06:18:00PM -0800, Person wrote:
> Whenever I try to attach an ISO to a VM, I receive an error: “internal error:
> libxenlight failed to create new domain”.
>
> I have tried running different commands on Qubes. Disabling
On Friday, November 17, 2017 at 9:49:00 AM UTC-5, toront...@gmail.com wrote:
> I intend to reinstall 3.2 which is currently running on somewhat undersized
> SSD. This time I would like to keep most of the semi-static portions of the
> OS and templates on the SSD for speed and to reduce wear on
On 11/17/2017 07:49 AM, 'Grogins' via qubes-users wrote:
Fresh install of Qubes rc2 but cannot start sys-firewall - Getting
error during dom0 setup as follows: [usr/bin/qvm-start sys-firewall]
failed stdout stderr Cannot execute qrexec daemon.
I've noticed the same issue reported on github -
On 11/17/2017 09:49 AM, torontojoh...@gmail.com wrote:
I intend to reinstall 3.2 which is currently running on somewhat undersized
SSD. This time I would like to keep most of the semi-static portions of the OS
and templates on the SSD for speed and to reduce wear on the SSD and the more
On 11/17/2017 08:22 AM, Styles Grant wrote:
I did see some evidence of one guy who got a ryzen to work, and another who got
an a 10 series to work. I'd nab an a 10, but this old fx 8350 is on sale.
What do you think?
It'll work great, unlike the first gen ryzen boards the
I intend to reinstall 3.2 which is currently running on somewhat undersized
SSD. This time I would like to keep most of the semi-static portions of the OS
and templates on the SSD for speed and to reduce wear on the SSD and the more
dynamic parts on a spinning disk. If this were a conventional
I did see some evidence of one guy who got a ryzen to work, and another who got
an a 10 series to work. I'd nab an a 10, but this old fx 8350 is on sale.
What do you think?
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from
Fresh install of Qubes rc2 but cannot start sys-firewall - Getting error during
dom0 setup as follows: [usr/bin/qvm-start sys-firewall] failed stdout stderr
Cannot execute qrexec daemon.
I've noticed the same issue reported on github - No 3153 on 8 October 2017
against Qubes4 rc1
Any solution
On Thu, Nov 16, 2017 at 11:57:44PM -0800, pandakaas...@gmail.com wrote:
> I just saw that in the directory containing my default dvm
> (/var/lib/qubes/appvms/whonix-ws-ws-dvm/) contains alot of files named like
> this:
> disp1.conf
> disp2.conf
> disp3.conf
> And it keeps going on for a while,
Hi everyone,
Following the documentation there
(https://www.qubes-os.org/doc/assigning-devices/#possible-issues) I tried to
make my PCI arbitrator less strict.
When booting the new service "qubes_pre_netvm.service", it fails with the error
:
"/bin/sh line 0 echo: write error : no peripheral
22 matches
Mail list logo