My laptop has started to fail to boot my 4.0rc2 installation. This started
after doing a qubes-dom0-update, but I'm pretty sure that I had rebooted the
machine successfully at least once since then.
The computer has now gone into a bootloop, and fails to display the GRUB
screen. I can only
Before installing 4.0rc2, I did a backup of my VM's from 3.2. I've started
restoring them one-by-one and for the most part is has been a reasonably
painless operation.
However, when I tried to restore the "ssh" VM, I got the following error:
qubesadmin.backup: -> Restoring ssh...
I just installed rc2 and trying to configure the machine similar to the way
things worked in my old (3.2) installation. One of the issues I have faced is
that the timesync service doesn't seem to do the right thing.
I am in Singapore timezone (UTC+8). Typing "date" in dom0 shows that the
On Tuesday, 3 October 2017 19:26:29 UTC+8, Foppe de Haan wrote:
> > When trying to start the VM using qvm-start, a window is opened with some
> > diagnostic information scrolling past (too fast to see what's going on),
> > and then the window disappears and the VM is shut down. Trying to go to
On Tuesday, 3 October 2017 16:56:24 UTC+8, Foppe de Haan wrote:
> Did the backup restoration process work at all, or did it error and skip the
> win7 VM?
Thanks for the reply.
Please allow me to do it all from the beginning again and record all the logs.
I'll update in a day or so.
--
You
After installing Qubes 4rc1 on a new laptop, I took a backup of my Windows 7 VM
from my old 3.2 installation and loaded it onto the new laptop. This did not
work at all.
After some searching I came across a statement suggesting that Windows not work
is a known issue and will be fixed with the
Apparently ME has a HAP mode that can be enabled, which disables most of the ME
functionality.
http://blog.ptsecurity.com/2017/08/disabling-intel-me.html
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop
On Saturday, 12 August 2017 03:33:38 UTC+8, PR wrote:
> In total I ended up installing windows roughly 20 times, tweaking lots
> of settings - but if know how it can be done, you get rewarded with a
> working windows installation which is running fine in seamless mode.
>
> I can walk you
On Tuesday, 1 August 2017 13:19:21 UTC+8, Holger Levsen wrote:
> so far so very good. i'm curious whether this will also be the case with qubes
> 3.2.1 and a 4.9 kernel (so far only tried with the older 4.8 one from the
> qubes repos…)
>
> (but then, see the other mail on this list about my
On Monday, 31 July 2017 11:11:58 UTC+8, lok...@gmail.com wrote:
> > 2) Hardware that didn't work with 4.4 or 4.8 still doesn't work.
>
> I can now disable tap-to-click. Finally!
Note that I quoted the wrong question here. It didn't work in the old version,
but works with 4.9.
--
You
The machine I'm testing on is a Dell Latitude E7470.
> 1) Hardware that used to work with 4.4 or 4.8 no longer works with 4.9.
The computer now greets me with a black screen (hung? I don't know) when coming
out of sleep. Thankfully I don't usually put the machine to sleep, so I can
live with
On Thursday, 20 July 2017 20:29:11 UTC+8, Patrik Hagara wrote:
> On 07/20/2017 02:08 PM, Patrik Hagara wrote:
> > As for the Linux kernel, you want to use the earlyprintk param,
> > either "earlyprintk=vga,keep" or "earlyprintk=xen,keep" should
> > work. Again, the full (and fairly long) list of
On Thursday, 20 July 2017 16:22:22 UTC+8, Patrik Hagara wrote:
> That's a non-fatal error, I have that in my log too.
>
> What's more interesting is the last photo, in particular the line:
>
> ERR: SENTER disabled by feature control MSR (5)
>
> I _think_ this means that your
On Thursday, 20 July 2017 15:18:26 UTC+8, Patrik Hagara wrote:
> Try checking the tboot log (from dom0) for any obvious error messages:
> sudo txt-stat
Thanks. I did this, but I'm not sure how to interpret the information. It does
say "TXT measures launch: FALSE". Does that mean that TXT is
On Friday, 14 July 2017 16:16:21 UTC+8, Patrik Hagara wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On 07/14/2017 09:45 AM, loke...@gmail.com wrote:
> > On Friday, 30 June 2017 04:17:08 UTC+8, Marek Marczykowski-Górecki
> > wrote:
> >
> >> Oh, it isn't listed in
On Friday, 30 June 2017 04:17:08 UTC+8, Marek Marczykowski-Górecki wrote:
> Oh, it isn't listed in updates-status[1], so I completely forgot.
> Probably it was uploaded to testing before introducing that system. Of
> course it should be migrated to current, will do.
I updated to the latest AEM,
The AEM package was upgraded recently (probably because of this thread:
https://groups.google.com/forum/#!topic/qubes-users/3ZkmS5v7E38), and after I
installed the updated version, AEM stopped working completely.
Now, it asks me for the AEM password. I type it in, and it doesn't display my
On Thursday, 6 July 2017 06:21:01 UTC+8, Unman wrote:
> On Wed, Jul 05, 2017 at 09:20:48PM +, js...@riseup.net wrote:
> > loke...@gmail.com:
> > > I have some applications I have installed manually in /usr/local on
> > > appvms. I would like to create appmenu entries for these applications.
I have some applications I have installed manually in /usr/local on appvms. I
would like to create appmenu entries for these applications. However, the Qubes
appmenu management only deals with menus coming from templates.
Is there an official way to handle this?
--
You received this message
Thanks for the reply.
The funny thing is that I did see my secret message. That's why I thought it
was so weird.
That's why I asked for a way to force a failure so that I can double check
this.
--
You received this message because you are subscribed to the Google Groups
"qubes-users"
I enabled AEM some time ago, and so far it's worked the way I'd expect it to.
Based on what I have read here, I came to the understanding that after
upgrading the dom0 kernel I'd get an AEM error when I reboot the machine, since
the kernel is different from the last boot.
Yesterday, I
On Sunday, 18 June 2017 14:54:03 UTC+8, Vít Šesták wrote:
> BTW, I remember having such issue (including real CPU load), but that time,
> avahi-daemon was to blame, related to VPN. But it was shown in htop. Disabling
> avahi-daemon has helped.
>
> On recreating VMs (or VM templates): It might
On Saturday, 17 June 2017 18:38:10 UTC+8, Nikolai Stenfors wrote:
> Hello Qubes-users,
>
> I've made a fresh standard installation of Qubes OS on a Lenovo SL510 with
> 220 GB memory. A reclaimed all disk memory during the installation to whipe
> out my previous Debian installation.
> However,
On Saturday, 17 June 2017 18:35:39 UTC+8, Vít Šesták wrote:
> What CPU usage does Qubes Manager show? I guess is shows low CPU usage.
>
> Do you see any other symptoms of high CPU usage like heat or fan activity?
>
> I guess the Xen just allocates some CPU time for some VMs, but the time is
I noticed that my laptop fan was blowing more than usual, so I started ‘xentop’
in dom0 to see which VM was using CPU. I noticed two VM's were using 150% and
abour 70% respectively (according to ‘xentop’ output).
However, when running ‘top’ in the VM's themselves, I saw nothing using any
CPU.
On Tuesday, 13 June 2017 18:06:31 UTC+8, Alchemist wrote:
> Noor,
>
> most Http only sites work more often, but there are instances where they get
> hit by this "slowdown" and it seems to be affecting the whole appvm not just
> the browser.
>
> The problem seems to be transient, no restarts
I regularly compile the latest version of Emacs for use in my development VM. I
simply compile Emacs from the git repository and install it in /usr/local. All
works the way it's supposed to.
However, I now have more than one VM where I need to use Emacs, and I would
like to avoid having to
On Thursday, 18 May 2017 03:17:42 UTC+8, Vít Šesták wrote:
> With external GPU, be careful about additional outputs (HDMI/DVI/DP/VGA).
> They
> might be wired to the dedicated GPU, which can cause various problems with
> your
> setup. First, it is generally poorly supported with Linux. (It
On Monday, 15 May 2017 03:12:18 UTC+8, tai...@gmx.com wrote:
> I would get a laptop with AMD graphics instead, or get an older model
> like the T430 or W530 (and you can install open source init coreboot on
> that)
Thanks. I'm convinced. I'll go for a laptop with Radeon chipset.
I've been
On Sunday, 14 May 2017 00:50:01 UTC+8, Grzesiek Chodzicki wrote:
> W dniu sobota, 13 maja 2017 15:30:07 UTC+2 użytkownik lok...@gmail.com
> napisał:
> > I am about to buy a new laptop, and jst about the only requirements I have
> > is that it should be reasonably small, and that I am able to
I am about to buy a new laptop, and jst about the only requirements I have is
that it should be reasonably small, and that I am able to use the GPU in it.
The latter is because I need to do some development which requires it.
I am OK with installing Nvidia's proprietary drivers on dom0. I'm
On Saturday, 22 April 2017 07:46:28 UTC+8, Dominique St-Pierre Boucher wrote:
> I would love a big logo like the one on the Twitter post in 2015. I would
> also
> like to have a small on to cover that windows logo on the keyboard... I would
> also
> like one with "Qubes inside"...
If you
I have a Windows VM where I run Outlook for work purposes. It works great and I
keep it in a separate xfce workspace. I'm running it in desktop mode (i.e. the
Windows desktop is in a single Xfce window).
After a certain amount of time (hard to say how long, but I'd guess it's in the
30 minute
On Friday, 24 March 2017 19:34:47 UTC+8, Opal Raava wrote:
> > Ah, problem solved. In the web build documentation it says to:
> >
> > cp example-configs/qubes-os-master.conf builder.conf
> >
> > if you instead do:
> >
> > cp example-configs/qubes-os-r3.2.conf
> >
> > you get a better
On Thursday, 23 March 2017 18:23:30 UTC+8, Opal Raava wrote:
> On Thursday, March 23, 2017 at 3:27:58 AM UTC+1, lok...@gmail.com wrote:
> > On Thursday, 23 March 2017 02:45:53 UTC+8, Opal Raava wrote:
> >
> > > Which tells us that we probably really do need version 3.9.0 of
> > > qubes-tools.
On Thursday, 23 March 2017 02:45:53 UTC+8, Opal Raava wrote:
> Ok that build did not work. I'm getting the following error:
>
> ../../bin/mkpadlock.py -s 36 -c 0xcc devices/appvm-red.png
> Traceback (most recent call last):
> File "../../bin/mkpadlock.py", line 25, in
> import
I'm trying to build Qubes from source, but when following the instructions
(https://www.qubes-os.org/doc/qubes-builder/), the build fails with the message
below. Does anyone have any advice?
Regards,
Elias
make[1]: Leaving directory '/home/emartenson/qubes-builder'
make[1]: Entering directory
On Wednesday, 22 March 2017 12:29:59 UTC+8, lok...@gmail.com wrote:
> I'm trying to use qubes-builder to build an image from source. I followed the
> instructions on the web site, but I'm getting errors when running "make
> get-sources":
I did a new checkout of the source code, and then it
I'm trying to use qubes-builder to build an image from source. I followed the
instructions on the web site, but I'm getting errors when running "make
get-sources":
=
$ make get-sources
-> Updating sources for builder...
--> Fetching from https://github.com/QubesOS/qubes-builder.git
On Tuesday, 21 March 2017 21:46:25 UTC+8, Mike Keehan wrote:
> On Sun, 19 Mar 2017 21:39:15 -0700 (PDT)
> loke...@gmail.com wrote:
>
> > On Monday, 20 March 2017 12:27:43 UTC+8, lok...@gmail.com wrote:
> > > I have not been able to install Qubes 3.2 on this machine.
> > >
> > > The installer
On Tuesday, 21 March 2017 10:01:57 UTC+8, Andrew David Wong wrote:
> We almost never publish new ISOs for Qubes OS versions that have
> already been released. It's likely that the next time a new ISO will
> be published with updated drivers will be when Qubes 4.0 is released.
Thank you for the
Since Qubes cannot be easily installed if things like networking or graphics is
not available during installation, is there any plan to create a new installer
image that has newer drivers?
On my old Dell Latitude E7470, I was unable to get WLAN working until I had
performed a dom0 update. I
On Monday, 20 March 2017 12:27:43 UTC+8, lok...@gmail.com wrote:
> I have not been able to install Qubes 3.2 on this machine.
>
> The installer cannot start as the graphics card is not supported. The result
> is that you get dropped into the text-based installer which does not work.
>
> This
I have not been able to install Qubes 3.2 on this machine.
The installer cannot start as the graphics card is not supported. The result is
that you get dropped into the text-based installer which does not work.
This is kind of disappointing as this is a very light laptop that supports up
to 32
What is the best way to handle ssh in Qubes?
I have a set of machines I often log in to remotely, and I want to make sure
the sessions (as well as the private keys) are protected from vulnerabilities
in other applications.
Currently I have set of a dedicates ssh qube from which I run all my
On Wednesday, 8 March 2017 14:08:29 UTC+8, Nick Darren wrote:
> First, the commands I added to /rw/config/rc.local don't seem to run.
> Namely, it doesn't appear to be mounting the /usr/local/etc/postfix
> directory in /etc/postfix. Also postfix doesn't appear to be running on
> startup. How do
On Wednesday, 8 March 2017 02:59:18 UTC+8, cooloutac wrote:
> I think most new users want more passthrough like gpu. IMO if I want to be
> secure
> on my pc i try to avoid those things. I have a separate machine for gaming
> for
> example. But I guess the idea of qubes is to be able to do
On Tuesday, 7 March 2017 03:56:20 UTC+8, Jean-Philippe Ouellet wrote:
> https://www.qubes-os.org/news/2016/09/02/4-0-minimum-requirements-3-2-extended-support/
>
> Note that those are bare minimum requirements, and that you will
> probably want more. If you need to run windows HVMs, I'd say at
Hello,
I'm looking at getting a new laptop in the next few months. I will, of course,
run Qubes on this thing but since Qubes 4 is on the horizon I'm wondering how
easy/difficult it will be to upgrade once it's out. Has anything been said
about this?
Since I don't really need my new computer
On Thursday, 2 March 2017 03:59:39 UTC+8, Jimmy Axenhus wrote:
> I got a Python script for that. Put in dom0 and run it. Unlike Andrews
> script this one will update all VMs in parallel and is interactive
> rather than non-interactive.
Thanks a lot to both you and David for helping out with
I tend to use Qubes VM's not just for security purposes, but also as a very
convenient way to have clean, manageable VM's where I only install the stuff I
need for a specific task.
This has led me to have a large number non-template VM's, all of which needs to
be manually updated every time
On Tuesday, 21 February 2017 02:25:25 UTC+8, Francesco wrote:
> I wonder if am the only one with this issue.
You're not the only one. I have it too and I haven't been able to get past it.
It happens immediately when trying to upgrade the standard Arch template.
--
You received this message
52 matches
Mail list logo
