Booting Qubes 4.0 on a five-year-old Core i3 laptop, it always sits for several
minutes with a grey screen, white Q logo, and slowly advancing progress bar. Is
there some textual boot report I can watch instead, to see why it takes so long?
--
You received this message because you are
On Qubes 4.0, when I try to start a dispVM, I get a popup notice that it's
starting, then a popup that it started, then a popup that it halted. I get no
error message, even when I specify --verbose:
[user@dom0 ~]$ qvm-run --verbose --autostart --dispvm=whonix-ws-dvm --service
--
‐‐‐ Original Message ‐‐‐
On Thursday, October 11, 2018 11:02 PM, 'awokd' via qubes-users
wrote:
> > On further investigation, I discovered that
> > /var/log/xen/xenstored-trace.log in dom0 was 155GB.
>
> I don't have this log on mine. Did you maybe enable it somewhere?
Yes, and then I
‐‐‐ Original Message ‐‐‐
On Monday, October 15, 2018 4:52 PM, Marek Marczykowski-Górecki
wrote:
> > Same result with qubes.StartApp+debian-xterm
> > Per your response, I verified that whonix-ws-dvm does have
> > /usr/share/applications/debian-xterm.desktop (and whonix-ws-dvm itself
>
‐‐‐ Original Message ‐‐‐
On Monday, October 15, 2018 5:29 PM, Marek Marczykowski-Górecki
wrote:
> You can add --pass-io, to see service stdout/stderr. Maybe this will
> give some hints.
vchan connection timeout
LOL. I changed qrexec-timeout for whonix-ws-dvm to 120 (from default of
‐‐‐ Original Message ‐‐‐
On Monday, October 15, 2018 3:34 PM, Marek Marczykowski-Górecki
wrote:
> > [user@dom0 ~]$ qvm-run --verbose --autostart --dispvm=whonix-ws-dvm
> > --service -- qubes.StartApp+xterm
> > Running 'qubes.StartApp+xterm' on $dispvm:whonix-ws-dvm
> > [user@dom0 ~]$
>
‐‐‐ Original Message ‐‐‐
On Monday, October 15, 2018 4:52 PM, Marek Marczykowski-Górecki
wrote:
> > Same result with qubes.StartApp+debian-xterm
> > Per your response, I verified that whonix-ws-dvm does have
> > /usr/share/applications/debian-xterm.desktop (and whonix-ws-dvm itself
>
My hard disk was 95% full, as shown by usage/size in the output of qvm-pool -i
lvm. So I decided to delete some old unneeded app qubes, each taking a few
hundred MB or a few GB of space.
Before deleting each one, I started it to check the contents, to verify there
was nothing I needed to save.
On Monday, October 1, 2018 4:32 PM, Chris Laprise wrote:
> I've submitted qubes-tunnel to Qubes with iptables commands only, with
> the intention to transition to nftables (or that other new interface in
> Linux, name escapes me just now) for Qubes 4.1.
I guess you mean BPF (Berkeley Packet
‐‐‐ Original Message ‐‐‐
On Wednesday, October 10, 2018 6:52 AM, unman
wrote:
> I admire your persistence in continuing to remove qubes.
>
> Have you tried running 'sudo fstrim -av' in dom0?
After I already trimmed / in dom0 as I mentioned (and it reported about 5GB
freed), I ran sudo
A qube window that I was using in full-screen mode died and somehow locked up
the gui in dom0 (totally unresponsive to keyboard & mouse input, except that
the mouse still moved the pointer), and I had to switch to a text console
(ctl-alt-F2) and kill xfce to force it to log out and reset the
‐‐‐ Original Message ‐‐‐
On Monday, September 24, 2018 6:03 AM, 'awokd' via qubes-users
wrote:
> All I'd know to do is reboot- don't know if there's a more elegant way.
Then does Qubes have any way yet to suspend or snapshot VM state, like vmware
can do? Most of my qubes won't be a
12 matches
Mail list logo
