Hello,
> > It is clear that despite ticking the check boxes from the auditor point
> of
> > view with this idea, I would be willingly violating the internal rules
> they
> > have setup, and maybe risking the company certification in case of a
> deeper
> > review after an incident. Despite
Hello,
> > > I think you may be overstating the problem of running anti-virus on
> > > Qubes. If you could find an AV that updates its virus definitions via
> > > signed RPMs, then it can be made to work without a lot of effort.
> > >
> >
> > The issue in this case is two fold: The
Hello,
> I think you may be overstating the problem of running anti-virus on
> Qubes. If you could find an AV that updates its virus definitions via
> signed RPMs, then it can be made to work without a lot of effort.
>
The issue in this case is two fold: The designated ~antivius~ endpoint
Hello!
I have been a Qubes user for 3+ years and adopted its separation-of-concern
model deeply into my day to day activities.
A year ago I started to work for a cloud company that is
seeking/re-certifying several security certifications, and among the
requirement of these certifications are
ctl enable qubes-gui-agent.service
systemctl start qubes-gui-agent.service
and from that point on, the template is operating normally.
Hope it helps!
///Pablo
El miércoles, 15 de agosto de 2018, 8:29:40 (UTC-3), tier...@gmail.com escribió:
> On Tuesday, August 14, 2018 at 4:36:29 PM UTC+1,
Further troubleshooting shows last Debian template update I did recently seems
to be the reason (I normally use Debian for sys-* service VMs)
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving
Further troubleshooting shows last Debian template seems to be the reason (I
normally use Debian for sys-* service VMs)
--
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
I updated last night to testing, and now qvm-run just hangs. Terminating it
with CTRL-C gives the same traceback.
Please note that in my case, starting any application from the dom0 menu is now
working at all. Seems there is issue with the X session.
--
You received this message because you
El martes, 1 de mayo de 2018, 19:07:35 (UTC), haaber escribió:
> it would be a nice feature to have a program like redshift
> https://doc.ubuntu-fr.org/redshift running in dom0. Did anyone have such
> software running in qubes (I am on Q4). Thank you,
I am using it since R3.0 and had no issue
Hello Ivan,
El mar., 1 may. 2018 01:13, Ivan Mitev <i...@maa.bz> escribió:
> Hi,
>
> On 05/01/2018 03:18 AM, Pablo Di Noto wrote:
> > Hello all,
> >
> > I asked this question when Qubes R3.2 was out, and solved with help from
> Andrew in a somewhat weird way
Hello all,
I asked this question when Qubes R3.2 was out, and solved with help from Andrew
in a somewhat weird way (running local scripts on each AppVM).
Now that we are at R4.0, I am again having this issue:
After install, dom0 gets proper timezone:
|[root@dom0 Desktop]# timedatectl
|
Hello,
After a normal reboot I had a working dom0 without any ServiceVM started.
Found that `sys-net` could not start because the 'vm-sys-net-private' LVM
volume was missing.
Looking around I found that the '-tmp' version of it was available, and after
mounting it I could see the contents of
> > > > You could also try to revert to earlier revision using "qvm-volume
> > revert sys-net:private" for example.
>
> Will try that tonight.
>
Unfortunately, that was not possible for the service VMs.
For the only important AppVM that had -back and -back missing, the command
`qvm-block
> > > If, as I suspect, the root cause of your problem is a lack of metadata
> > > space on pool00; you can confirm this by typing "sudo lvs" into a
> > > console. You will then need to figure out a way to enlarge that metadata
> > > volume.
> >
> > Yes, you are right, the `pool00` volume
> techg...@gmail.com
> If, as I suspect, the root cause of your problem is a lack of metadata space
> on pool00; you can confirm this by typing "sudo lvs" into a console. You
> will then need to figure out a way to enlarge that metadata volume.
Yes, you are right, the `pool00` volume metadata
And also, there is possible reason for this to happen as stated
[here](https://github.com/QubesOS/qubes-issues/issues/3809).
--
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
It seems that there are other users with similar issues:
https://github.com/QubesOS/qubes-issues/issues/3810
(not 100% sure is the same issue, but I have seen that message from UI tools
while having this problem)
--
You received this message because you are subscribed to the Google Groups
Hello,
I am running a Qubes R4.0 install on Thinkpad X250, fully `*-testing` updated,
and after restoring most of my R3.2 qubes and getting almost ready to switch
fully to the new version, something happened with `qubesd` or `qubes-db-dom0`.
Most `qvm-*` command fail with:
```
Traceback (most
> > Experiencing consistently the "no wifi after resume" which was working fine
> > with 4.4.x
>
> This can be avoided by adding "iwldvm iwlwifi" line to
> the following file in your WiFi NetVM:
> /rw/config/suspend-module-blacklist
Thanks! Found the specific thread
Thanks from Argentina, unman and magicadu!
--
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
Hello,
Running 3.2 with XFCE.
My notebook has a small SSD with Qubes boot and root/swap on it, and a larger
(and slower) SHDD mounted as /var/lib/qubes-add and configured as an additional
Xen pool.
I am running out of space (and at the same time, losing speed drastically) on
the SSD, and
El 24 dic. 2016 06:28, "thinkpad user" <somelegaldownloadu...@gmail.com>
escribió:
On Friday, March 11, 2016 at 2:45:50 AM UTC+4, Pablo Di Noto wrote:
> So far, everything works as expected
Thanks for sharing info! Have you tested graphics software yet (especially
3d edi
El domingo, 20 de noviembre de 2016, 20:11:45 (UTC), Scot Anderson escribió:
> New to Qubes (installed today!), and this is my first post, but I had this
> same problem on my Thinkpad T420 and have gotten past it. Some light google
> sleuthing led me to a Proxmox issue that was similar, and
Hello,
Never had much use for a Windows7 HVM so far.
Months ago, I installed W7 on Qubes just for the sake of testing. Got to the
point of installing qubes-windows-tools and had some success with it, but never
used it much (in fact, never activated a license on the resulting W7 install).
Now
> Bump. Its not Qubes specific. Same applies to latest Xen Hypervisor on Ubuntu
> 16.04.1.
>
> Any idea what got introduced into Xen between 3.0 and 3.1?
I am using a X250 since last february (installed R3, updated to R3.1 and full
reinstall of R3.2).
No problems with booting so far.
Let me
>
>
>>
> Well, ahem, it turned out that following the advice on
> https://www.qubes-os.org/doc/i3/
> I could install it without any issue.
>
> I swear I tried `qubes-dom0-current-testing` but it seems I did not.
> Sorry for the noise!
>
>
For future reference (including to myself, it seems) you
>
>
> On Thursday, October 20, 2016 at 3:47:56 AM UTC+2, Pablo Di Noto wrote:
>> > Hello all,
>> >
>> > I have reinstalled R3.2 and want to install Redshift (and its GUI) on
>> dom0 again.
>> > I do not recall how I did it on R3.1, and su
El miércoles, 6 de abril de 2016, 5:39:40 (UTC-3),
li...@mullvad.net escribió:
> On Tuesday, February 9, 2016 at 3:18:41 PM UTC+1, Marek Marczykowski-Górecki
> wrote:
>
> On Tue, Feb 09, 2016 at 06:06:47AM -0800, Stefan wrote:
>
> > Am Dienstag, 9. Februar 2016 14:41:57 UTC+1 schrieb Marek
>
El miércoles, 31 de agosto de 2016, 13:02:06 (UTC), Andrew David Wong escribió:
>
> On 2016-08-31 05:42, Pablo Di Noto wrote:
> > El miércoles, 31 de agosto de 2016, 12:26:42 (UTC), Andrew David Wong
> > escribió:
> >
> >> On 2016-08-31 04:48,
29 matches
Mail list logo
