Re: [qubes-users] dispVM shuts down immediately after starting (I'm trying to run xterm)

2018-10-15 Thread 'floasretch' via qubes-users
‐‐‐ 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 60), 
and that fixed it.

Thanks.

A bit disturbing that 60 seconds isn't enough, though. It's a reasonably modern 
system. Intel Core i3 (Haswell generation) with 16GB RAM, and not overloaded. 
(CPU and disk are idle until I start the DVM, and not too many qubes are 
running.)

-- 
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 email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/H8gakPcWZ7TBrGWs5t2gX_9m6WZGbi9XnmvpWjnzMnHM8ITc-SIMd_j0rkEgtwP9VsIAt6a7VrFx4tMZPOUP1mgUOaSQHjCFeUP-qr-YykU%3D%40protonmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] dispVM shuts down immediately after starting (I'm trying to run xterm)

2018-10-15 Thread 'floasretch' via qubes-users
‐‐‐ 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 
> > starts and runs with no problem).
>
> I've tried the same command on my whonix-ws-14-dvm and it works...
> Is your whonix-ws-dvm Whonix 13, or updated to Whonix 14?

Whonix 14. Originally was 13 (installed with Qubes 4.0), then updated when 14 
was released.

I verified /etc/whonix_version in both whonix-ws and whonix-ws-dvm. They're 
both 14.

BTW, I haven't been using disposable VMs at all for the past couple months, so 
I have no idea whether my problem is recent or old. In fact, the last time I 
did was with the Fedora DVM, and I've deleted it since then. Today was the 
first time I ever tried using any DVM other than Fedora.

Qubes and all templates are fully updated.

Is there a log somewhere?

-- 
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 email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/BwyMdQWJbx539y8b38BsOOWGP91fzLzfpgus2IrcCl6R5Nva4Gg3SzSavKx9AZ_H6fFoPXeyWdG8PdmPenM446iLiU6rx-Q9k1mwayMKMl4%3D%40protonmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] dispVM shuts down immediately after starting (I'm trying to run xterm)

2018-10-15 Thread 'floasretch' via qubes-users
‐‐‐ 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 
> > starts and runs with no problem).
>
> I've tried the same command on my whonix-ws-14-dvm and it works...
> Is your whonix-ws-dvm Whonix 13, or updated to Whonix 14?

Whonix 14. Originally was 13 (installed with Qubes 4.0), then updated when 14 
was released.

I verified /etc/whonix_version in both whonix-ws and whonix-ws-dvm. They're 
both 14.

BTW, I haven't been using disposable VMs at all for the past couple months, so 
I have no idea whether my problem is recent or old. In fact, the last time I 
did was with the Fedora DVM, and I've deleted it since then. Today was the 
first time I ever tried using any DVM other than Fedora.

Qubes and all templates are fully updated.

Is there a log somewhere?

-- 
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 email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/L12HKlT8NzJAbW9X0R6BX881TfFARiB5wi8M24Dng1U2-fNJihUQWhDH9Od3BoL1f5aR0XmaCATI-BJcFpMnWP6oSZOd8DleRMu8tcb_UCU%3D%40protonmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] dispVM shuts down immediately after starting (I'm trying to run xterm)

2018-10-15 Thread 'floasretch' via qubes-users
‐‐‐ 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 ~]$
> > Is there a log somewhere to tell me what's going wrong?
>
> The +xterm part should be a base name of .desktop file in
> /usr/share/applications (or other directory per XDG standard). xterm on
> Debian happens to have debian-xterm.desktop, so it should be
> qubes.StartApp+debian-xterm.

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 starts 
and runs with no problem).

-- 
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 email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/1YkWrPit5VaYwhB41JfX0zXdYL78wu_VH4f6ucS3TI68kkjWctOT2K5Pp4y8-FADu7_G75LmEku-FAAWqzVmo6hiJeOIOlzZru4NA8B0bLA%3D%40protonmail.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] dispVM shuts down immediately after starting (I'm trying to run xterm)

2018-10-15 Thread 'floasretch' via qubes-users
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 
-- qubes.StartApp+xterm
Running 'qubes.StartApp+xterm' on $dispvm:whonix-ws-dvm
[user@dom0 ~]$

Is there a log somewhere to tell me what's going wrong?

-- 
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 email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/cYnO-Vk2RuiJZhGOZg80tuu_ERnO0KGVuat06JeY2aZdUkiKGpn-Pf2ubPF3f2xcnJzar-t_qqnGyaD6M0dBmJPQo6xzcdiAyPPSk-bWwJU%3D%40protonmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Deleting app VMs in Qubes 4.0 doesn't free up disk space

2018-10-14 Thread 'floasretch' via qubes-users
‐‐‐ 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 forgot to disable it when I was done with it. Then the extreme 
growth of the log coincidentally (!) canceled out the space freed up by 
deleting qubes, which accounted for the surprising behavior I was seeing.

> > But qvm-pool -vi lvm still reports 99% HD usage (468GB used out of 473GB 
> > size for pool00)! The HD is 500GB, so trimming 80.7GiB should have freed 
> > 17%.
> > OTOH, sudo lvs did report that pool00 data% dropped from 99 to 67, and 
> > meta% dropped from 55 to 39. So the problem is clearly with Qubes, not LVM.
>
> Have you rebooted since cleaning up? Maybe qvm-pool just hasn't caught
> up yet.

I noticed some hours later that qv-pool finally caught up. Don't know what 
triggered it (but not a reboot). Also don't know why lvs and qvm-pool should 
ever report different free space values, but anyway my immediate problem is 
solved.

-- 
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 email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/zuBknMcgNe8RRjZUeHaFZWft_6YVlFeB6KtnrMGXdeP1UqtGi9uJ4oWNKbViLaQMN_3SBbyxzplsm68nzW5Ks9bt9_7gd5gqO0WQim_i_F8%3D%40protonmail.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] How to see what Qubes is doing during boot?

2018-10-11 Thread 'floasretch' via qubes-users
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 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 email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/QDkOtIM__Fk8UwwKui7CzMYdG3NcEjvSOyxb0rmGzfY2hqNoUEgAgTcO24lhKC3VMInKpZCpnuoFWs9RWr4bQ-YTI1-1EyNEOGBCs4VIiYQ%3D%40protonmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Deleting app VMs in Qubes 4.0 doesn't free up disk space

2018-10-10 Thread 'floasretch' via qubes-users
‐‐‐ 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 fstrim -av per your suggestion, and it reported 0 bytes 
trimmed.

On further investigation, I discovered that /var/log/xen/xenstored-trace.log in 
dom0 was 155GB.

So I did sudo truncate /var/log/xen/xenstored-trace.log --size 0
Then again sudo fstrim -av, and this time for / it reported 80.7GiB trimmed. (I 
don't know why not all 155GB trimmed.)

But qvm-pool -vi lvm still reports 99% HD usage (468GB used out of 473GB size 
for pool00)! The HD is 500GB, so trimming 80.7GiB should have freed 17%.

OTOH, sudo lvs did report that pool00 data% dropped from 99 to 67, and meta% 
dropped from 55 to 39. So the problem is clearly with Qubes, not LVM.

-- 
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 email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/Uctl60dNAdJXbXjsu9e_CZ4TGoxk3DuHN5p6EtbOqdccB2T7WwNAmf0ywtBjO79rcTBXYA7UgUTxCarucLldOW93S5zo_Gqx33PkJ3go0kw%3D%40protonmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] nftables vs iptables

2018-10-10 Thread 'floasretch' via qubes-users
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 Filter).

-- 
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 email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/h4m5HXxy0LpeW92e2R0ZdfpFDUA04H-5J7f5E_WpUY121foawKFep0dJ6mdgOzx5jpJKHGRLnH0hGevy9hdWJjhQFCwGyuWNtfed5Vg1dsw%3D%40protonmail.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Deleting app VMs in Qubes 4.0 doesn't free up disk space

2018-10-10 Thread 'floasretch' via qubes-users
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. HD usage crept up a little, then a little more 
after I killed the qube. But surprisingly, HD usage crept up a little more 
after I deleted the qube, instead of decreasing!

I guessed it was a fluke, so I did the same with the next qube. The same thing 
happened! Then again with the third and fourth qubes. At this point, my HD is 
99% full. I ran fstrim / in dom0, and it reported about 5GB freed, but HD is 
still 99% full.

I'm starting to panic, since I know Linux fails badly when an LVM pool that's 
over-committed with thin volumes (as Qubes 4.0 is designed) fills up.

I know the qubes were deleted successfully, since lvs | grep  no 
longer shows them.

No running qubes are writing any significant data to disk. Now that I'm not 
deleting any more qubes, HD usage is holding steady at 99%.

Why isn't my HD usage decreasing when I delete qubes? How can I free up some 
space?

Sent with [ProtonMail](https://protonmail.com) Secure Email.

-- 
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 email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/vm9YVHYoyXt1OPnO_FVawYii5BuvTCngkd99DNizLqcfVa6ub_7_dZJ9FndNb9cKm1vb6bK6jAOlLh4WydV8MDQYQVnGOcI7pLs0m4o8Ba4%3D%40protonmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Help! qvm-start-gui won't restart properly, so my qube windows are invisible

2018-09-24 Thread 'floasretch' via qubes-users
‐‐‐ 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 problem to reboot after I reboot the 
system, but I have one qube in particular with running state that would be a 
big hassle to re-initialize if I have to reboot the qube.

-- 
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 email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/7N5BlhcjLTldJdHqiy6Fk2Cp6fvrlLvCts1DEs2OdAbv3LY89BawFUBo0euxwS-f6SwH4dHjBcwqE02lRS37oUmON8dhX3Rvm4cerQqktNc%3D%40protonmail.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Help! qvm-start-gui won't restart properly, so my qube windows are invisible

2018-09-23 Thread 'floasretch' via qubes-users
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 gui.
That worked, but when I logged back in, all of my qube windows (and all the 
dom0 windows I had open, including some terminal emulators) momentarily flashed 
on screen one at a time in rapid succession, then disappeared. Alt-tab doesn't 
show them.

I can, however, start new dom0 windows, e.g. terminal emulator, qube manager, 
etc, and they work properly.
xl list shows all my running qubes are still running, and I can access them 
using xl console, then within them I can use xlsclients and see that everything 
is still running. But if I try to create a new window, e.g. by running xterm, 
nothing appears.

https://github.com/QubesOS/qubes-issues/issues/3147 for an unrelated issue has 
instructions to fix invisible windows:
kill qvm-start-gui process and start it again: qvm-start-gui --all --watch &
But when I do that, all my windows just flash momentarily again, and disappear, 
same as happened when I logged back in.

Using Qubes 4.0 final release, fully updated.

Please help! How can I get my windows back?

Sent with [ProtonMail](https://protonmail.com) Secure Email.

-- 
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 email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/Fjl1AZKeU-zBDzd21-v23nM70l4T6cMT9zbSVVeMsKRC-7dpaHSjaUeKeRO_5EoBQ_Z_EqH7Csal6W2vHCX68vGFAZTnjmuVq2g-aRm46dY%3D%40protonmail.com.
For more options, visit https://groups.google.com/d/optout.