[qubes-users] Qubes / Github bugs track ??

[ThierryIT]

Hi,

Why are you closing a ticket before knowing if the modification you have made, 
to correct the bug, is working ? I mean, why can't you wait for the user to add 
the modification and see if it is working or not ?
As exemple: ticket #3501 is closed, but even if I have followed the 
instruction, the problem is not solved, but the ticket is closed ... How to 
re-open it ?

Thx 

-- 
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/2301adfc-63e5-4d02-9c19-67b57755e5b1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Qubes 3.2 installation will not boot on Dell Inspiron 7000 Gaming series laptop

[freddycribbs17]

I have installed Qubes OS 3.2 to a secondary SSD in an attempt at dual-booting 
Windows and Qubes. The installation finishes successfully but will not boot 
after the system restarts following the installation. The UEFI entry is 
successfully created by the installer, but upon selecting it, tells me that no 
Operating System has been found, giving me the option to retry, or reboot into 
the boot menu. I have tried disabling my primary Windows SSD from BIOS prior to 
installation, and I have followed the steps outlined on the Troubleshooting 
page. Let me add that the boot folder on the Qubes SSD is appears to be empty, 
and I cannot follow the instructions on the Troubleshooting page instructing me 
to copy and rename the xen.cfg and xen.efi. As the folder structure within my 
Qubes SSD and the installation media do not appear to correspond to the path 
referenced on the page in question.

Any help with regards to this matter would be greatly appreciated.

Cheers. :)

-- 
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/1aecfdd7-87dd-4aa6-a11b-9e98fe63627f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Fresh 3.2 Installation can't find updates

[Fabian Wloch]

Hello,

I just made a new installation of Qubes 3.2 and tried to update dom0 in 
it, without success.


It always says there is no update, over CLI aswell as over the Qubes VM 
Manager.


1.
   [fabian@dom0 ~]$ sudo qubes-dom0-update
2.
   Using sys-firewall as UpdateVM to download updates for Dom0; this
   may take some time...
3.
   Running command on VM: 'sys-firewall'...
4.
   Checking for dom0 updates...
5.
   No new updates available
6.
   No updates avaliable


1.
   [fabian@dom0 ~]$ sudo qubes-dom0-update --clean --check-only
2.
   Using sys-firewall as UpdateVM to download updates for Dom0; this
   may take some time...
3.
   Running command on VM: 'sys-firewall'...
4.
   13 files removed
5.
   Checking for dom0 updates...
6.
   No new updates available
7.
   No updates avaliable


1.
   [fabian@dom0 ~]$ sudo qubes-dom0-update --enablerepo=qubes-dom0-current
2.
   Using sys-firewall as UpdateVM to download updates for Dom0; this
   may take some time...
3.
   Running command on VM: 'sys-firewall'...
4.
   Checking for dom0 updates...
5.
   No new updates available
6.
   No updates avaliable


1.
   [fabian@dom0 ~]$ sudo qubes-dom0-update qubes-template-fedora-26
2.
   Using sys-firewall as UpdateVM to download updates for Dom0; this
   may take some time...
3.
   Running command on VM: 'sys-firewall'...

It's not the internet connection, surfing over DispVM is working fine 
and VM Updates are working fine aswell. I can also ping yum.qubes-os.org 
from sys-firewall aswell as from sys-net.


I also tried to just update the fedora 23 template to the most recent 
version so the sys-net and sys-firewall VMs are as "up2date" as 
possible, but doesn't work aswell.


I first used a "old" M-Disc I burned when 3.2 was released, and 
afterwards tried it with a few downloaded image, ended in the same 
result, so its probably not a broken image.


Any ideas?

-Fabian

--
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/2bd2f3be-6e55-77d7-3078-d25e06b984ea%40posteo.de.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Qubes 4.0-rc3 not installing on Lenovo P71

[joeh9617]

On Monday, January 29, 2018 at 10:11:12 AM UTC+8, Qubed One wrote:
> Yuraeitha:
> > On Sunday, January 28, 2018 at 3:13:47 AM UTC+1, joeh...@gmail.com
> > wrote:
> >> I burned the ISO to USB stick then started to install Qubes but got
> >> the following:
> >> 
> >> [0.093375] ACPI Error: [\SB_.PCIO.XHC_.RHUB.HS11] Namespace
> >> lookup failure, AE_NOT_FOUND (20170531/dswload-210) [0.093383]
> >> ACPI Exception: AE_NOT_FOUND, During name lookup/catalog
> >> (20170531/psobject-252) [0.093539] ACPI Exception:
> >> AE_NOT_FOUND, (SSDT:ProjSsdt) while loading table
> >> (20170531/tbxfload-220) [0.098243] ACPI Error: 1 table load
> >> failures, 12 successful (20170531/tbxfload-246) [2.376031]
> >> Couldn't get size: 0x800e [  137.216201]
> >> dracut-initqueue[566]: Warning: Dracut-initqueue timeout - starting
> >> timeout scripts [  137.779207] dracut-initqueue[566]: Warning:
> >> Dracut-initqueue timeout - starting timeout scripts [  138.324711]
> >> dracut-initqueue[566]: Warning: Dracut-initqueue timeout - starting
> >> timeout scripts [  138.852226] dracut-initqueue[566]: Warning:
> >> Dracut-initqueue timeout - starting timeout scripts [  139.395971]
> >> dracut-initqueue[566]: Warning: Dracut-initqueue timeout - starting
> >> timeout scripts . . .
> >> 
> >> This went on for some time, so I switched off and wrote this
> >> message. I hope there are no serious typos coz I typed this off of
> >> a picture taken of the screen.
> >> 
> >> Any hints? Thanks
> > 
> > I'm by no means an expert on the kernel, but dracut "looks" like
> > kernel errors, and "ACPI" (Advanced Configuration and Power
> > Interface) looks like a firmware/kernel support mismatch, either by a
> > lack of features, lack of development, firmware-bug, kernel-bug, or
> > possibly an un-updated firmware. The firmware should be the
> > motherboard (BIOS/UEFI).
> > 
> > You could start looking in your BIOS/UEFI after settings that may be
> > wrong and require adjustments. Is VT-d enabled? Is there a second
> > "Virtualization" that needs enabling, for exaple under "Advanced -->
> > CPU" UEFI settings? There can be other settings too, it's hard to
> > mention them all, but those two are the most important ones, which is
> > sometimes only 1 merged setting.
> > 
> > Does your hardware support VT-d and other Qubes hardware
> > requirements? Does Qubes 3.2. run on this hardware? Qubes 4 is known
> > to be more strict to hardware requirements and may not work smoothly
> > or may not even install if the hardware requirements or security is
> > not correct. Qubes 3.2. is less an issue when missing VT-d and
> > similar. This might also be a place to look and confirm. If you got
> > Qubes 3.2. running on the machine, then try run in dom0
> > "qubes-hcl-report" to see if you meet the requirements.
> > 
> > However, dracut/ACPI errors doesn't strike me as errors that appear
> > if there are issues with the Qubes 4 specific requirements.
> > 
> > You may want to try install with LegacyBIOS/Grub if you tried
> > UEFI/EFI, or vice versa, whichever you did not try yet. You can also
> > update your BIOS/UEFI to the newest version, however be sure you
> > don't brick your machine. Make sure you know any pitfalls as it may
> > make your motherboard break and become useless.
> > 
> > The kernel contains drivers too, the most essential ones, while the
> > modules contain extra drivers for the kernel. These errors could also
> > be driver issues, for example you may have to edit the EFI or the
> > Grub to pick a different driver before starting. Unfortunately I
> > believe you need to edit the /boot/efi/EFI.cfg file on the install
> > media, but you can more easily change it live on Grub by hovering
> > over the install menu, and thne press "E" key to edit the install
> > menu in grub. Here you can change ACPI settings, drivers,
> > virtulization states, hide/unhide hardware, and so on.
> 
> 
> Maybe try this: hit e at this point as directed, then add:
> acpi=off
> to the end of the long line that begins with:
> module /vmlinuz-4...
> 
> then boot in to the installer from there.
> 
> 
> > I'm not sure if it even is a driver issue, I can't see that from the
> > logs, whether it can be found there or not. But it's some clues to go
> > with, and maybe you can google some up to trial and error. Just be
> > careful, for example few of the ACPI settings can be dangerous to
> > your hardwaree, so double-check any recommendations you find on the
> > internet.
> > 
> > Also it may be worth if you can find any ACPI settings in your
> > UEFI/BIOS too.
> > 
> > At any rate, I usually solve these kind of problems with trial and
> > errors through experiments. Someone more knowledgeable might drop by
> > with a better advice. For now though, some clues you can try start
> > with if you did not do them already.
> >

Thanks for the suggestion.
I pressed  after putting the cursor on 'test image then start qubes' and 
got a line:
/ubnkern 

Re: [qubes-users] after update no VM 'starts' apps anymore.

['awokd' via qubes-users]

On Tue, January 30, 2018 12:05 am, 'Tom Zander' via qubes-users wrote:
> Is this a known issue?
>
>
> I can start a VM using qvm-start, but when I use qvm-run nothing happens,
> it hangs forever. Even commands that don't need a X server. For any qube of
> the various OSs I run.

qvm-run works on both powered on and off VMs on my 4.0 on testing repo.
qvm-run works on powered on (only) VMs on my 3.2 stable.

I did notice some weirdness starting things on a recent update but a
reboot cleared it up.

> Is there any way to connect to the VM and get a tty? Think serial-line
> fallback.

Enable Debug mode? Sorry, don't know about your other questions.


-- 
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/5d3b226f9ae90d84f64ab8b6164df003.squirrel%40tt3j2x4k5ycaa5zt.onion.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: qubes 3.2: qubes-vm-manager not consistent

[ludwig jaffe]

Hi thanks,

I edited
/var/lib/qubes/qubes.xml
and removed the lines with the names of the VMs I deleted by hand before,
and needed to kill qubes-manager and to restart it, so the file gets read
and parsed.

Now my system behaves like before.

But there should be a warning if one configures the private.img size bigger
than the disk array holding the /var/lib/qubes stuff.
So qubes-manager should summarize the space used by the private.img and
warn the user not to take more space then the disk array can provide.


On Mon, Jan 29, 2018 at 6:01 PM, awokd  wrote:

> On Mon, January 29, 2018 10:53 pm, ludwig jaffe wrote:
> > Yes, I want to repair my qubes-vm-manager.
>
> Did you In Qubes Manager, go to the View menu and click Show/Hide Inactive
> VMs?
>
> > made a back-up and I want to modify config files by hand so the tools do
> > what they should do. So I need to de-register the vms I deleted by hand,
> > and I need to tell qubes-vm-manager which vms are there. I wonder if it
> > uses the tools qvm- in order to do its work.
>
> If you are sure you want to manually edit the qubes config, it's in
> /var/lib/qubes/qubes.xml. Make sure to make a backup of it first.
>
>

-- 
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/CAP7JdrJnbbXyhjmCPWjMTj8%3DA1gyrQ2xZkR8erJ5SGeTUYGjmQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] connect to other VMs in qubes by using vm name

['Tom Zander' via qubes-users]

On Saturday, 27 January 2018 15:45:27 CET Yoganandam Marava wrote:
> by adding forward rules at sysfirewall we can ping each other VM through
> ip address but not using VM name. Is this some thing possible with Qubes
> 4? I am naive in networking.please suggest if there is a way?

Each VM has a static IP address that won't change.
What you could do is add a line to your /etc/hosts for each VM to match its 
name to the IP.

-- 
Tom Zander
Blog: https://zander.github.io
Vlog: https://vimeo.com/channels/tomscryptochannel

-- 
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/3027465.EVIPjTjbbe%40cherry.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] after update no VM 'starts' apps anymore.

['Tom Zander' via qubes-users]

Is this a known issue?

I can start a VM using qvm-start, but when I use qvm-run nothing happens, it 
hangs forever. Even commands that don't need a X server.
For any qube of the various OSs I run.

The Qubes icons also no longer show in my system-tray.
I can still update dom0 via yum, though. Thats a relief.
Is this a known issue? Can I expect a fix soon?


If not,  are there any log files anywhere I can look at?
The only relevant part I found was in qrexec.Work.log some lines saying 
"Unable to connect to X server".
Trial and error shows this is due to some timeout, as it only appears after 
a substantial amount of seconds.


Would be really happy to get my system properly working again as this is my 
work workstation :(


Some related questions;

what is 'anaconda' ? I thought it was the installer, but if it is then why 
is it running on dom0?

Is there any way to connect to the VM and get a tty? Think serial-line 
fallback.

is it known that grubs advanced menu doesn't get updated when new kernels 
are installed?

-- 
Tom Zander
Blog: https://zander.github.io
Vlog: https://vimeo.com/channels/tomscryptochannel

-- 
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/5091490.V4NiCZqDXe%40cherry.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: qubes 3.2: qubes-vm-manager not consistent

['Tom Zander' via qubes-users]

On Tuesday, 30 January 2018 00:19:58 CET ludwig jaffe wrote:
> Ok I found the file, backed it up and want to edit it.
> Do you know an xml ediitor with folding to edit this with more comfort,
> as there is no  in the xml, just spaghetti.
> A vim for xml with folding or something like that with curses text gui
> woud be best.

$ xmllint -format < in.xml > out.xml
$ vim out.xml
:set foldmethod=syntax

-- 
Tom Zander
Blog: https://zander.github.io
Vlog: https://vimeo.com/channels/tomscryptochannel

-- 
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/20247273.4H386KnXkH%40cherry.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Lenovo ThinkPad, won't boot

[Tim W]

Here is a thread with steps to get uefi install of 3.2 working on the p51 from 
a few weeks ago

https://groups.google.com/forum/m/#!topic/qubes-users/4VsKdxnKHBk

Cbeers,

Tim

-- 
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/2040e8e3-e440-4df4-9098-fa7d9376a7a8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: qubes 3.2: qubes-vm-manager not consistent

[ludwig jaffe]

Oh thank you I am a bit stupid,
I did not try the show hide button! Shame on me :-)

But still I have that zombie-VMs that I removed the hard way.
So I need to de-register them.

Ok I found the file, backed it up and want to edit it.
Do you know an xml ediitor with folding to edit this with more comfort,
as there is no  in the xml, just spaghetti.
A vim for xml with folding or something like that with curses text gui woud
be best.


On Mon, Jan 29, 2018 at 6:01 PM, awokd  wrote:

> On Mon, January 29, 2018 10:53 pm, ludwig jaffe wrote:
> > Yes, I want to repair my qubes-vm-manager.
>
> Did you In Qubes Manager, go to the View menu and click Show/Hide Inactive
> VMs?
>
> > made a back-up and I want to modify config files by hand so the tools do
> > what they should do. So I need to de-register the vms I deleted by hand,
> > and I need to tell qubes-vm-manager which vms are there. I wonder if it
> > uses the tools qvm- in order to do its work.
>
> If you are sure you want to manually edit the qubes config, it's in
> /var/lib/qubes/qubes.xml. Make sure to make a backup of it first.
>
>

-- 
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/CAP7Jdr%2BMGrtPu0CXe0EJks1Ago_HzZ3bE6BA9HXGnNc22kG3%2Bw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: qubes 3.2: qubes-vm-manager not consistent

['awokd' via qubes-users]

On Mon, January 29, 2018 10:53 pm, ludwig jaffe wrote:
> Yes, I want to repair my qubes-vm-manager.

Did you In Qubes Manager, go to the View menu and click Show/Hide Inactive
VMs?

> made a back-up and I want to modify config files by hand so the tools do
> what they should do. So I need to de-register the vms I deleted by hand,
> and I need to tell qubes-vm-manager which vms are there. I wonder if it
> uses the tools qvm- in order to do its work.

If you are sure you want to manually edit the qubes config, it's in
/var/lib/qubes/qubes.xml. Make sure to make a backup of it first.

-- 
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/3723801e0c6818e9f6f21d36da068386.squirrel%40tt3j2x4k5ycaa5zt.onion.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: qubes 3.2: qubes-vm-manager not consistent

[ludwig jaffe]

Yes, I want to repair my qubes-vm-manager.
When I say at dom0:
qvm-ls, then I see my VMs also the vms that I deleted in order to get space
by saying rm -rf /var/lib/qubes/appvm/asterisk-now (some stupid appliance,
I tested,
and wanted to dispose, in order to free up space, which was not successfull
because
of file system errors.
So I cleaned the file system and made a back-up and I want to modify config
files
by hand so the tools do what they should do.
So I need to de-register the vms I deleted by hand,
and I need to tell qubes-vm-manager which vms are there. I wonder if it
uses the tools qvm- in order to do its work.

So I want to fix my old qubes 3.2 and then see if qubes 4 is really stable.
So any help is welcome on fixing my qubes 3.2 to give it the last polish to
remove the last traces of the disaster

Thanks,

Ludwig


On Mon, Jan 29, 2018 at 5:43 PM, awokd  wrote:

> On Mon, January 29, 2018 10:25 pm, ludwig jaffe wrote:
> > On Monday, January 29, 2018 at 9:14:38 AM UTC-5, Yuraeitha wrote:
> >
> >> On Monday, January 29, 2018 at 1:06:13 PM UTC+1, ludwig jaffe wrote:
>
> >>> The Qubes-VM-Manager only shows running VMs and not all the VMs that
> >>> are there, but from the menue button one can start the shells of these
> >>> VMs,
> >>> which causes the vms to be started.
> >>>
> >>> Also I can not change the disk size of private.img in the shutdown
> >>> personal vm. And maybe others.
>
> > Hi, as there is RC-4 of something, it is clever to stick with qubes3.2
> > until there will be 4.1. Also I would like to know how the qubes manager
> > works, in order to fix it my self (maybe, I need to edit some XML), if
> > nobody wants to help.
>
> I'm sticking with 3.2 on my primary system until 4.0 is released, but rc4
> is looking like it will be pretty close to ready.
>
> Are you talking about your two questions above?
> In Qubes Manager, go to the View menu and click Show/Hide Inactive VMs.
> If you are trying to enter a smaller number to shrink it, I don't think
> you can. Back up the personal VM's data, delete the VM, create a new one,
> and restore the data.
>
>
>

-- 
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/CAP7JdrK35L0OjNTTPuibRvm7SKyTYa7s5fFqwcLjiAu62Lv9mQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: qubes 3.2: qubes-vm-manager not consistent

['awokd' via qubes-users]

On Mon, January 29, 2018 10:25 pm, ludwig jaffe wrote:
> On Monday, January 29, 2018 at 9:14:38 AM UTC-5, Yuraeitha wrote:
>
>> On Monday, January 29, 2018 at 1:06:13 PM UTC+1, ludwig jaffe wrote:

>>> The Qubes-VM-Manager only shows running VMs and not all the VMs that
>>> are there, but from the menue button one can start the shells of these
>>> VMs,
>>> which causes the vms to be started.
>>>
>>> Also I can not change the disk size of private.img in the shutdown
>>> personal vm. And maybe others.

> Hi, as there is RC-4 of something, it is clever to stick with qubes3.2
> until there will be 4.1. Also I would like to know how the qubes manager
> works, in order to fix it my self (maybe, I need to edit some XML), if
> nobody wants to help.

I'm sticking with 3.2 on my primary system until 4.0 is released, but rc4
is looking like it will be pretty close to ready.

Are you talking about your two questions above?
In Qubes Manager, go to the View menu and click Show/Hide Inactive VMs.
If you are trying to enter a smaller number to shrink it, I don't think
you can. Back up the personal VM's data, delete the VM, create a new one,
and restore the data.


-- 
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/c4a2e17023ecf8f03db6c43d79d33902.squirrel%40tt3j2x4k5ycaa5zt.onion.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: qubes 3.2: qubes-vm-manager not consistent

[ludwig jaffe]

On Monday, January 29, 2018 at 9:14:38 AM UTC-5, Yuraeitha wrote:
> On Monday, January 29, 2018 at 1:06:13 PM UTC+1, ludwig jaffe wrote:
> > Problem after some diskfull errors:
> > see my post: "data panic (disc full) / want to mount nas with nfs and 
> > backup all in /var/lib/cubes", where I managed to recover the data and to 
> > repair the file systems.
> > --
> > the box is up and running, but 
> > --
> > The Qubes-VM-Manager only shows running VMs and not all the VMs that are
> > there, but from the menue button one can start the shells of these VMs,
> > which causes the vms to be started.
> > 
> > Also I can not change the disk size of private.img in the shutdown 
> > personal vm. And maybe others.
> > 
> > What happened to qubes-vm manager?
> > -> Disk got full and maybe, it could not write configs correncty
> > -> I deleted some not needed VMs by hand 
> > rm -rf /var/lib/qubes/appvm/some_stupid_appliance in order to get space,
> > before I started the recovery with the nas and kali linux
> > 
> > 
> > so could be, that qubes vm manager did not like this.
> > 
> > How to fix qubes vm manager?!
> 
> Now I know you're talking about Qubes 3.2. here, but this issue might 
> possibly be related to Qubes 4. The Qubes VM Manager was originally planned 
> to be out-phased in Qubes 4 and was supposed to become a relic of the past. 
> But due to many people having an easier time having a visual GUI that the VM 
> Manager provides, the Qubes developers brought it back recently in Qubes 4. 
> However it still needs some updates and fixes before it can run a bit more 
> smooth.
> 
> So here's thhe thing. Due to limited time and busy schedules to make 
> everything for Qubes, I suspect that some of the updates designed for Qubes 4 
> has also arrived and mixed in with Qubes 3.2. to some extent. For example 
> updates in qvm-usb, updates to the Qubes-tools, and so forth.
> 
> Now that doesn't mean all packages that resides on both Qubes 3.2. and Qubes 
> 4 are equally updated. All I'm suspecting here, is that "some" might slip 
> through to Qubes 3.2.
> 
> Basically, in Qubes 4 the Qubes mechanics has become so different, that the 
> VM-Manager will take major re-work to make it work properly again. However 
> it's already been brought back to a state where it's useful, albeit a bit 
> slow. But the cool thing with the Qubes 4 VM-Manager is that the window now 
> can be re-sized, although it doesn't yet remember the previous window size, 
> but hopefully that's fixed sometime soon.
> 
> Either way, this could be a possible explanation, but I'm no expert, and this 
> is only and merely a suspicion. Qubes 4 required a lot of work, and they're 
> not quite done yet either. They're busy with it, and it's probably taken 
> longer than anyone ever expected, although it has brought about some really 
> good results so it's imho been well worth it.
> 
> Thing is though, Qubes 3.2. was probably not meant to be around this long, 
> and it might be starting to show. But that's just be postulating, there might 
> be another possible explanation.
> 
> But for what it's worth, having used Qubes 4 since RC-2, it's actually become 
> quite stable now. If RC-4 is not out soon, then maybe upgrade to Qubes 4 
> RC-3? Also updates meant for RC-4 has been posted to Qubes 4 RC-3 
> current-testing too. Although it reamins to be seen whether a re-install is 
> recommended between RC-3 and the yet to be released RC-4, the developers will 
> tell us on the release day in the release news article, if any of the 
> previous releases procedures is to go by.

Hi, as there is RC-4 of something, it is clever to stick with qubes3.2 until 
there will be 4.1.
Also I would like to know how the qubes manager works, in order to fix it my 
self (maybe, I need to edit some XML), if nobody wants to help.

-- 
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/57e31bba-5070-49d1-87fb-03a58e58e987%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] how to show menu bar in qubes VM Manager

[jerry57]

i clicked view and hide something i think

-- 
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/abb5c4084b5ed4e0c755a0ed975b846a%40disroot.org.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Qubes OS won't boot after fresh install on Macbook Air 4,2 (mid 2011)

[Yuraeitha]

On Tuesday, March 28, 2017 at 10:26:48 PM UTC+2, zii...@gmail.com wrote:
> Hello
> 
> I'm having issues with installing Qubes OS besides my Mac OS X on my MacBook 
> Air 4,2 (mid 2011). 
> At first I tried to follow this guide because it's the exact same model I 
> have:
> https://www.qubes-os.org/doc/macbook-troubleshooting/#macbook-air-13-mid-2011-macbookair-42
> 
> But I had a hard time just getting the installer to work, at first it wasn't 
> able to run any of the commands listed in the very simple GUI installer. Then 
> when I "forced" the USB to boot in legacy mode by installing rEFInd and 
> choosing legacy boot it finally booted into the normal menu which then lead 
> me to the main installer setup.
> Then I stumbled upon another problem in the partitioning part, it kept giving 
> me this error:
> "sda may not have enough space for grub2 to embed core.img using the ext4 
> file system on partition"
> I then tried to install grub manually by going into the system console with 
> CTRL+ALT+F2, which resulted in another error that I found out was because I 
> needed a "BIOS Boot" partition, so I created one and voíla, grub was 
> installed and I was able to go back into the installer setup and partitioning 
> went and everything installed fine.
> 
> But now whenever I boot it just goes to a halt and reboots when booting with 
> the "Boot vmlinuz-4.1.13-6.pvops.qubes.x86_64 from 500 MiB ext4 volume" 
> option from rEFInd.
> I believe that the error which is causing it to start the reboot is:
> "dracut> FATAL: No or empty root= argument"
> 
> Here is an image I found of someone having the same issue I am. This is 
> almost exactly what appears on my screen before it stops working:
> http://imgur.com/a/2xbuk#rFJ4kYJ
> 
> 
> I've tried googling and trying to find a solution but I can't seem to find 
> anything that works.
> 
> 
> Thank you for reading and in advance for any help,
> 
> Cheers.

Although someone having same results with Mac's, might exclude any of what I 
said above. There must be other Mac users who can share if they got this 
working which you can learn from. Hopefully someone posts.

-- 
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/f49db754-2842-49c9-a475-f9e88d960002%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Qubes OS won't boot after fresh install on Macbook Air 4,2 (mid 2011)

[Yuraeitha]

On Tuesday, March 28, 2017 at 10:26:48 PM UTC+2, zii...@gmail.com wrote:
> Hello
> 
> I'm having issues with installing Qubes OS besides my Mac OS X on my MacBook 
> Air 4,2 (mid 2011). 
> At first I tried to follow this guide because it's the exact same model I 
> have:
> https://www.qubes-os.org/doc/macbook-troubleshooting/#macbook-air-13-mid-2011-macbookair-42
> 
> But I had a hard time just getting the installer to work, at first it wasn't 
> able to run any of the commands listed in the very simple GUI installer. Then 
> when I "forced" the USB to boot in legacy mode by installing rEFInd and 
> choosing legacy boot it finally booted into the normal menu which then lead 
> me to the main installer setup.
> Then I stumbled upon another problem in the partitioning part, it kept giving 
> me this error:
> "sda may not have enough space for grub2 to embed core.img using the ext4 
> file system on partition"
> I then tried to install grub manually by going into the system console with 
> CTRL+ALT+F2, which resulted in another error that I found out was because I 
> needed a "BIOS Boot" partition, so I created one and voíla, grub was 
> installed and I was able to go back into the installer setup and partitioning 
> went and everything installed fine.
> 
> But now whenever I boot it just goes to a halt and reboots when booting with 
> the "Boot vmlinuz-4.1.13-6.pvops.qubes.x86_64 from 500 MiB ext4 volume" 
> option from rEFInd.
> I believe that the error which is causing it to start the reboot is:
> "dracut> FATAL: No or empty root= argument"
> 
> Here is an image I found of someone having the same issue I am. This is 
> almost exactly what appears on my screen before it stops working:
> http://imgur.com/a/2xbuk#rFJ4kYJ
> 
> 
> I've tried googling and trying to find a solution but I can't seem to find 
> anything that works.
> 
> 
> Thank you for reading and in advance for any help,
> 
> Cheers.

The missing "root=" argument some 3/4 down the code from the top, is pretty bad 
from what I can tell. I can't say with certainty if this is the "cause", it 
might just be that it can't post "root=" while "root=" is still correct, but if 
there truly is no root, then no system-files will load up and this obviously 
will make you unable to boot up. 

Presumably, you have no "root=", which as hinted above may explain that you can 
only get as far as to load the kernel (I think it halts at that point?), but no 
system-files. I'm not an expert, but it looks like only the kernel loaded, so 
it may be a correct assumption, possibly. Maybe someone knows more/better?

Which filesystem format did you install? EXT4, ZFS, BRTFS? 

If you use BTRFS, then it has a design that goes wrong with Qubes. Qubes's code 
here is correct, but the BTRFS design makes it tricky to match. Though, it's 
easy to fix manually. Since BTRFS uses sub-folders, you need to either edit 
/etc/fstab to include the correct =subfolder or something (google the exact 
attribute spelling). Then it should work. You can also change the the subfolder 
level in BTRFS instead. Either should work. 

If you don't use BTRFS, then perhaps it's something else messing up the 
rootflag. I can only guess here as to what that might be, or if this even is 
the true issue.

- Which file-system format did you use?
- Did you manually change the partition setup during install or did you pick 
the automatic setup?

-- 
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/441b9993-dcf9-4e02-848b-594d8df7da06%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: I think I've mounted my iny internal hard drive exactly wrong...

[Yuraeitha]

On Monday, January 29, 2018 at 3:30:40 AM UTC+1, bill...@gmail.com wrote:
> I have installed Qubes 4 rc3 on a usb external hard drive.  I have Neon linux 
> and Windows on my internal hard drive.  I decided I wanted to copy some files 
> from my home directory on my internal hard drive to my Qubes home directory 
> in the fedora26vm.
> 
> Unfortunately, I simply can't figure out how to make my internal drive 
> visible to my FedoraVM template.  
> 
> Oddly, I can go to dom0 and find /dev/sda8 and mount it there, making all the 
> stuff on the internal drive accessible to dom0 -- but I still can't see it in 
> the template vms.  This seems to me to be exactly wrong with respect to 
> security, at least after reading the docmentation about making it as hard as 
> possible to copy files to and from dom0.  Any bad stuff on my old internal 
> hard drive is easily accessible to dom0, but not to the templates.
> 
> I clearly don't get it.  So, what do I need to do?  How can I make /dev/sda8 
> visible to my template VM, but not have to mount it on dom0?  Or, if I have 
> to mount it on dom0, how do I then make it visible to the templates?
> 
> Thanks,
> billo

oh btw, only VM's that are currently running will appear in the widget, and 
only devices that are currently visible to Qubes will appear too. So any 
turned-off VM's, or any devices not working or blocked from Qubes, will not 
appear. Start the needed VM first, before you tie the device to the VM.

-- 
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/0a1899cd-ebd7-4ac6-a92a-5a10054faa24%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: I think I've mounted my iny internal hard drive exactly wrong...

[Yuraeitha]

On Monday, January 29, 2018 at 3:30:40 AM UTC+1, bill...@gmail.com wrote:
> I have installed Qubes 4 rc3 on a usb external hard drive.  I have Neon linux 
> and Windows on my internal hard drive.  I decided I wanted to copy some files 
> from my home directory on my internal hard drive to my Qubes home directory 
> in the fedora26vm.
> 
> Unfortunately, I simply can't figure out how to make my internal drive 
> visible to my FedoraVM template.  
> 
> Oddly, I can go to dom0 and find /dev/sda8 and mount it there, making all the 
> stuff on the internal drive accessible to dom0 -- but I still can't see it in 
> the template vms.  This seems to me to be exactly wrong with respect to 
> security, at least after reading the docmentation about making it as hard as 
> possible to copy files to and from dom0.  Any bad stuff on my old internal 
> hard drive is easily accessible to dom0, but not to the templates.
> 
> I clearly don't get it.  So, what do I need to do?  How can I make /dev/sda8 
> visible to my template VM, but not have to mount it on dom0?  Or, if I have 
> to mount it on dom0, how do I then make it visible to the templates?
> 
> Thanks,
> billo

It may be important not to mount in dom0 when using the widget explained below. 
Just to be safe, dismount it in dom0 first so nothing happens (no eject though, 
need it to be visible still). Although I believe the widget-tool can do this 
itself automated, but it might not be implemented yet similar to how it's not 
automated on VM shutdown. I suspect this might be automated in the future? 
Anyhow.

Do you see the little yellow icon up near notifications/clock/sound-widget 
icons? If you click on that, does your internal drives partition and partition 
appear here? If it does not, then perhaps there is a design-flaw/bug that 
disrupts this new Qubes 4 tool when installed on an external drive. IF the bug 
is there, then my guess is that it was not taken into account in the 
considerations when designing the tool.

However, whether it's a bug or not remains to be seen first. Try check if you 
can see the internal drive in the little widget. 

If it indeed turns out to be either a bug or design flaw that disallows 
connecting to internal devices when system is installed on an external drive, 
then, go to github, find the Qubes OS group in seach. Search in issues and see 
if you can find a similar issue. If you can, then post your results in the same 
post you found. If you don't find any, post a new one and explain the issue 
first briefly so an overview can be established of the issue, and then all the 
details below.

Having it on github in this way allow the developers to easier find this issue, 
track it, and over time get it fixed. It might? get a lot priority though, if 
there are many things more critical to work on than getting internal SATA 
devices to work while the system is installed on an external drive. After all, 
Qubes is first and foremost about security, it might take a while to fix 
something like this that may be considered lower priority. But then again, who 
knows, and it may even be quite quick and fast to fix, at which point, it might 
be fixed quickly.

Also this widget is still being developed and updated too, this bug may be 
caused by another bug, which may be be updated for another reason althother (a 
possibility). The widget still has some quirks, although it works somewhat 
nicely after being fully updated compared to its first version. 

Currently you need to reverse the process before you can move it to another VM, 
and it seems to "bug" if you just shutdown the VM without reversing the proces 
first, at which point the only solution is unplug the device, and if not 
possible to unplug then restart all of Qubes. I think this might be fixed in 
the future, i.e. when shutting down a VM, perhaps it'll reverse the proces 
automatically. 

Also I believe there is a way to automate the mounting to an AppVM/Template in 
Qubes 4, but I haven't had the need yet, so I did not explore this yet. It 
might not be developed yet either? 

But in any case, you can easily write a script, place it in dom0, keybind it in 
dom0 in System-Tools --> keyboard ---> Shortcuts tab --> "Add". Then in the 
keybind, execute a script located in dom0. (This is important, dom0 first). 
In the dom0 script, write the command the widget uses, to tie the drive. Then 
put a timer, so it doesn't execute the next step too fast. Thereafter write 
something like "qvm-run 'AppVM-name' bash path-to-your-scrupt-in-the-VM", which 
will mount the drive inside the VM you tied the drive to in the previous step. 

If done properly, this should work pretty nicely. You can make a keybind/script 
for each drive or external devices you got, it's easy to copy once you got the 
first one down, and you can back it up so you can easily set it up again if you 
ever re-install Qubes.

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.

[qubes-users] Re: qubes 3.2: qubes-vm-manager not consistent

[Yuraeitha]

On Monday, January 29, 2018 at 1:06:13 PM UTC+1, ludwig jaffe wrote:
> Problem after some diskfull errors:
> see my post: "data panic (disc full) / want to mount nas with nfs and backup 
> all in /var/lib/cubes", where I managed to recover the data and to repair the 
> file systems.
> --
> the box is up and running, but 
> --
> The Qubes-VM-Manager only shows running VMs and not all the VMs that are
> there, but from the menue button one can start the shells of these VMs,
> which causes the vms to be started.
> 
> Also I can not change the disk size of private.img in the shutdown 
> personal vm. And maybe others.
> 
> What happened to qubes-vm manager?
> -> Disk got full and maybe, it could not write configs correncty
> -> I deleted some not needed VMs by hand 
> rm -rf /var/lib/qubes/appvm/some_stupid_appliance in order to get space,
> before I started the recovery with the nas and kali linux
> 
> 
> so could be, that qubes vm manager did not like this.
> 
> How to fix qubes vm manager?!

Now I know you're talking about Qubes 3.2. here, but this issue might possibly 
be related to Qubes 4. The Qubes VM Manager was originally planned to be 
out-phased in Qubes 4 and was supposed to become a relic of the past. But due 
to many people having an easier time having a visual GUI that the VM Manager 
provides, the Qubes developers brought it back recently in Qubes 4. However it 
still needs some updates and fixes before it can run a bit more smooth.

So here's thhe thing. Due to limited time and busy schedules to make everything 
for Qubes, I suspect that some of the updates designed for Qubes 4 has also 
arrived and mixed in with Qubes 3.2. to some extent. For example updates in 
qvm-usb, updates to the Qubes-tools, and so forth.

Now that doesn't mean all packages that resides on both Qubes 3.2. and Qubes 4 
are equally updated. All I'm suspecting here, is that "some" might slip through 
to Qubes 3.2.

Basically, in Qubes 4 the Qubes mechanics has become so different, that the 
VM-Manager will take major re-work to make it work properly again. However it's 
already been brought back to a state where it's useful, albeit a bit slow. But 
the cool thing with the Qubes 4 VM-Manager is that the window now can be 
re-sized, although it doesn't yet remember the previous window size, but 
hopefully that's fixed sometime soon.

Either way, this could be a possible explanation, but I'm no expert, and this 
is only and merely a suspicion. Qubes 4 required a lot of work, and they're not 
quite done yet either. They're busy with it, and it's probably taken longer 
than anyone ever expected, although it has brought about some really good 
results so it's imho been well worth it.

Thing is though, Qubes 3.2. was probably not meant to be around this long, and 
it might be starting to show. But that's just be postulating, there might be 
another possible explanation.

But for what it's worth, having used Qubes 4 since RC-2, it's actually become 
quite stable now. If RC-4 is not out soon, then maybe upgrade to Qubes 4 RC-3? 
Also updates meant for RC-4 has been posted to Qubes 4 RC-3 current-testing 
too. Although it reamins to be seen whether a re-install is recommended between 
RC-3 and the yet to be released RC-4, the developers will tell us on the 
release day in the release news article, if any of the previous releases 
procedures is to go by.

-- 
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/cd373c07-d7c5-493e-93a0-456df31fc429%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: qubes 3.2: qubes-vm-manager not consistent

[ludwig jaffe]

On Monday, January 29, 2018 at 7:06:13 AM UTC-5, ludwig jaffe wrote:
> Problem after some diskfull errors:
> see my post: "data panic (disc full) / want to mount nas with nfs and backup 
> all in /var/lib/cubes", where I managed to recover the data and to repair the 
> file systems.
> --
> the box is up and running, but 
> --
> The Qubes-VM-Manager only shows running VMs and not all the VMs that are
> there, but from the menue button one can start the shells of these VMs,
> which causes the vms to be started.
> 
> Also I can not change the disk size of private.img in the shutdown 
> personal vm. And maybe others.
> 
> What happened to qubes-vm manager?
> -> Disk got full and maybe, it could not write configs correncty
> -> I deleted some not needed VMs by hand 
> rm -rf /var/lib/qubes/appvm/some_stupid_appliance in order to get space,
> before I started the recovery with the nas and kali linux
> 
> 
> so could be, that qubes vm manager did not like this.
> 
> How to fix qubes vm manager?!

Also there is a bug in the qubes-vm manager:
The dom0 disk can become full, as one can set a size for private.img that is 
bigger then the size of dom0 disk!
So if one is not careful, a bigger download in one of the app-vms can render
the qubes-os box unusable and one has to recover the data using kali and 
mounting the file system images.

-- 
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/a1bb83b5-ed91-4d97-b3f1-5a16619c5b69%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] qubes 3.2: qubes-vm-manager not consistent

[ludwig jaffe]

Problem after some diskfull errors:
see my post: "data panic (disc full) / want to mount nas with nfs and backup 
all in /var/lib/cubes", where I managed to recover the data and to repair the 
file systems.
--
the box is up and running, but 
--
The Qubes-VM-Manager only shows running VMs and not all the VMs that are
there, but from the menue button one can start the shells of these VMs,
which causes the vms to be started.

Also I can not change the disk size of private.img in the shutdown 
personal vm. And maybe others.

What happened to qubes-vm manager?
-> Disk got full and maybe, it could not write configs correncty
-> I deleted some not needed VMs by hand 
rm -rf /var/lib/qubes/appvm/some_stupid_appliance in order to get space,
before I started the recovery with the nas and kali linux


so could be, that qubes vm manager did not like this.

How to fix qubes vm manager?!

-- 
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/898f33b2-a936-4256-9efc-92b63f5f6504%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: PANIC!!! data panic (disc full) / want to mount nas with nfs and backup all in /var/lib/cubes

[ludwig jaffe]

On Sunday, January 28, 2018 at 12:26:44 PM UTC-5, ludwig jaffe wrote:
> Hi some systems got too big and now my dom0 is full.
> 
> data panic (disc full) / want to mount nas with nfs and backup all in 
> /var/lib/cubes
> 
> In a normal system I would setup an insulated air gap network and take a big 
> nas server mount nfs to the root-fs of dom0 and say as root cp -a 
> /var/lib/cubes /net/nas/bck.
> And then I would clean up and remove some VMs with rm -rf as I could undo it 
> when I got the VMs booted and cleaned of all the shit that got downloaded.
> 
> Now I can not connect the dom0 to a nic.
> Is there a trick to do it?
> booting a rescue linux from a stick would be a way but I first want to try 
> using qubes-os and changing a thing in the configs.
> 
> Thanks for your help.

Now I fixed nearly all. 
I did as follows:
boot kali-linux (or some other linux with enough tools -> Kali)  
from usb stick

cryptsetup  luksOpen /dev/sda3  greensda was the disk with the system and 
sda3 holds the encrypted qubes-os installation.

and mount /dev/dm-blabla  /mnt/8  (I have always mount points /mnt/{0-9} ready)

also I mounted my nas to nfs (no file security) in air gapped network
mount 192.0.123:/bigsasdrives/bakup /net/nas
and copied /var/lib/cubes to it
cp -av /var/lib/qubes /net/nas

this is running.

The disk to full problem is found:
I went to
/var/lib/qubes/personal
said file private.img
and file was so nice to tell me that private.img needs fsck.

but as there is important data on this private.img,
I first copy it to the nas and then say e2fsck private.img

so after back-up of the important stuff, i said e2fsck -f private.img
for all the app-vms and service-vms in the directory structure of 
/var/lib/qubes/

then I went to the vms like
cd /var/lib/qubes/appvms/banking1
said
mount -o loop,ro,noatime private.img /mnt/9
and I copied the important stuff here to the encrypted nas

in /var/lib/qubes/appvms/personal
I also copied the important stuff to the encrypted nas, and then I
deleted all the bloody videos I downloaded from the private.img in
personal and there is now room on the disk.

Videos are to be watched from nas from now on :-)

--
Only one Problem remains:
The Qubes-VM-Manager only shows running VMs and not all the VMs that are
there, but from the menue button one can start the shells of these VMs,
which causes the vms to be started.

Also I can not change the disk size of private.img in the shutdown 
personal vm. And maybe others.

How to fix qubes vm manager?!

-- 
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/7b384e53-bdbb-429b-91b1-5a79b737bafd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.