Re: [qubes-users] Qubes Manager / Qubes 4.0 R3 ?

[ThierryIT]

Yes it is but only if you are using as repo=testing

Le lundi 29 janvier 2018 09:30:12 UTC+2, [799] a écrit :
> Hello,
> 
>  ThierryIT wrote:
> > Hi, Not possible anymore to hide "un-running
> > VMs" ?
> 
> Ist Qubes Manager already available in 4rc3?
> I haven't read anything and thought that it will come with Qubes 4rc4.
> 
> [799]

-- 
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/47d5a9c0-782c-491e-9990-df5d65447565%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

AW: [qubes-users] Qubes Manager / Qubes 4.0 R3 ?

['[799]' via qubes-users]

Hello,

ThierryIT wrote:
> Hi, Not possible anymore to hide "un-running
> VMs" ?

Ist Qubes Manager already available in 4rc3?
I haven't read anything and thought that it will come with Qubes 4rc4.

[799]

-- 
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/tbI3qHvl8r4Cnkt-ZYbOlNTuTC3uhhV42IuLHW6M0pSyHukwQJXtNxgTatV69qsMb8se3jnMDq3-6o9ZnO1Z-fDs1Hauy3PJGnW0aXl-3XU%3D%40protonmail.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Qubes Manager / Qubes 4.0 R3 ?

[ThierryIT]

Hi,

Not possible anymore to hide "un-running VMs" ?
By the way, is it possible to create in Qubes Manager folders to be able to 
sort out VMs ?

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/86678769-44ff-4d59-887e-bb518a06ef37%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[billollib]

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

-- 
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/84d78b6f-6965-4b64-a6e5-8f8d5a1e4340%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Newbie question on KDE configuration

[billollib]

Makes sense.  Thanks.

-- 
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/c24eaa92-f04b-4f74-8e3e-6b0ea6b9f5de%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Qubed One]

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.
> 

-- 
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 

Re: [qubes-users] Newbie question on KDE configuration

['Tom Zander' via qubes-users]

On Saturday, 27 January 2018 18:14:23 CET billol...@gmail.com wrote:
> First, while KDE seems to be working well, I noticed that I can't download
> and install new themes, widgets, etc. through the KDE GUI.  It can't
> connect to the KDE server.  I'm assuming that this is because dom0
> doesn't actually have a network connection (which I think I read
> somewhere).  It's not the end of the world for me to download the stuff
> from kde.org and install it from file, but it's more convenient to use
> the gui interface.  What I need to know is if it is possible or should I
> move on and just do it by hand.

The AdminVM (dom0) indeed has no network, the reason for this is that it is 
the one completely trusted place.
I would advice against installing anything you downloaded from KDE directly, 
as that basically works around all the security you get by running qubes in 
the first place.
 
> Second, I really liked that convention in the default window manager for
> having a different color for the title bar for each domain.  That got
> lost when I moved to KDE, though the domain is still *listed* in the
> title bar.  I know how to set colors in kwin on an application by
> application basis, but I don't know how to do it on a domain basis.  Is
> there a mechanism for that in KDE?

This got readded in a recent update in the 'testing' repo, but only on the 
default window-manager decorations called Breeze.

So make sure you are up-to-date and make sure you are using Breeze.

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

[qubes-users] Re: OpenGL 4.0

[Yuraeitha]

On Thursday, January 25, 2018 at 4:35:40 AM UTC+1, Andrew Morgan wrote:
> Hello all,
> 
> I know GPU virtualization is currently not possible, so we have software
> rendering with mesa. Currently, I only seem to be able to run Open GL ES
> OpenGL ES 2.0 with Mesa 17.2.4.
> 
> I'm aware we're only able to use software drivers here, but is there a
> way to run a more up-to-date OpenGL version, such as 4.0+ within a Qube?
> 
> Thanks,
> Andrew Morgan

I've been flirting with the idea of trying out USB external graphic cards, 
which can be done via the USB protocol. Full PCI USB card passthrough already 
works in Qubes, so technically, this "should" allow full-blown graphics in 
Qubes in terms of graphic card availability. In regards whether a higher 
version of OpenGL is possible, I suspect without knowing for sure, that this is 
requiring a graphic driver to tie to? So I speculate, if USB external graphic 
card becomes available, then, so too OpenGL "should" work in higher versions?

The other means I know of that works is to pass-through the graphic card 
directly to Xen, bypassing Qubes entirely, essentially exposing dom0 and Xen. 
Currently this method works, unless it was broken again. It's just that there 
is a huge security "hole" in Qubes in order to get it to work.

Essentially, the dom0/xen exposed example shows a working graphic card, seems 
to be the missing link to make everything tie together, if I'm not mistaken. 

Now if you can get USB 3.1 type 2 with 10Gbit/s connection working, then you 
can get some pretty decent graphics. If you can get Thunderbolt working through 
USB 3.1 type, then you have access to some 40Gbit/s (they merged recently, 
although not all USB 3.1. have thunderbolt support yet). 

Regular USB 3 only offers 5Gbit/s, so it's a bit of a downside for heavy 
graphics.

It'd be cool if someone can test this out, I've been thinking of doing it for 
many months now, but I've simply never got around to it. It's also a bit 
expensive, at least currently. It's best to investigate and research before 
throwing money at something like this, it may not work after all. 

But all things considered, USB passthrough already works, so it "should" work, 
no? Especially so if you get thunderbolt working in USB 3.1. type 2. Also 
thunderbolt is only merged in USB-C ports (the new modern standard only slowly 
appearing atm), but not all USB-C ports support thunderbolt.

The question is though, would this work at all.

-- 
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/4c6f4316-b6bb-4467-879c-1e3c4c27e823%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: [qubes-project] Hosting for OpenQA instance

[Marek Marczykowski-Górecki]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Sun, Jan 28, 2018 at 09:38:17AM -0800, Yethal wrote:
> I have a spare machine I can donate. If any of the Qubes devs are 
> Warsaw-based I can even bring it over.

Thanks!

We'd prefer a machine hosted somewhere, but just hardware also could be
useful - we can look for place to host it separately. What are physical
dimensions of it? Rack case, or tower, or else?
What CPU and RAM size it have?

- -- 
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAlpuXqwACgkQ24/THMrX
1yxMsQf/V2ToVljqO92/QtUgUqPN7E7w579FOWrqedexnLYHl4Sg1KjHyvzpSMA7
hg4vHP3DxD2r7LjEmPBQ2YJM0PlS3MBubIUcbsyclQUMvUwqPOrJnBYtHV2VA8JH
w2sDMYxzRXn2BqvZxwyudrH/msp3aH+8qxmd1yUNzPpiKXwcCw87uNv+aqh3ZUeF
uLTbpuT22/7WFvpjB50kBPPC4eCvy/eEjghviKSqLClpIbLSc/Ztq1xVBvceXTGd
uElCwGEAX1Y3Kemmsz01Qz6Vld2eGGXLzPH795EBVHtGrePPKIRTkq279mUXY3qe
kTsqKijqo22OM9pGOaZ/HHJifuSfIw==
=x9o+
-END PGP SIGNATURE-

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

Re: [qubes-users] my mouse is dead

[cooloutac]

Some people have no choice since only one controller.  But there is not so much 
to worry when using mouse in sys-usb as there is for usb keyboard. 

  The only suggestion is to make screen lock when idle after a minute or two,  
to prevent someone using mouse maliciously when you are not looking.  Probably 
should do the same for wireless mouse.

Have you tried unplugging and replugging and see if the mouse proxy message 
pops up to allow it?  Make sure the mouse proxy installed and working 
correctly.  https://www.qubes-os.org/doc/usb/  
https://github.com/QubesOS/qubes-app-linux-input-proxy


-- 
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/c38db28d-4711-4408-9500-1ebc63549c34%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)

[drewshg]

On Tuesday, March 28, 2017 at 1:26:48 PM UTC-7, 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.

Have the absolutely same results but with MabBook Pro 13' Retina (mid 2015)

followed the instructions for MacBook Pro Retina, 15 inch, Mid-2015 (MacBookPro 
11,5)

Did it 4 times from scratch.

No luck...

-- 
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/2ec9946b-7199-439e-8787-abeb144bcc52%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Qubes OS screensharing

[Vít Šesták]

On January 27, 2018 7:57:02 AM GMT+01:00, Dave C  wrote:
>* VMs that can't access the conference site (i.e. bluejeans.com) or
>can't access the net at all

How can a VM without network access open a window in the X11 accessible from 
network?

>* VMs that don't have vncserver installed, or don't have a plugin
>needed to screenshare
IMHO a minor gain.

>My approach lowers security while screensharing.  But the rest of the
>time, not screensharing, the VMs are running with normal firewall
>settings.

It is likely that a VM can infect any other of the VMs (or the screensharing 
VM). There are multiple potential ways to do so:

a. Exploit some vulnerability in X11 protocol implementation.
b. Open a terminal (if not already opened) and type a command. This is 
possible, because any client can inject any input events to other client.
c. Download some file using webbrowser and run/install it (e.g., using some 
packaging system).
d. I remember I have read that X11 effectively provides no isolation between 
apps and I had an impression that any app can by design even run some code in 
another client. However, don't take this point as verified unless you verify it 
from some other source.

Regards,
Vít Šesták 'v6ak'

General note: Maybe top-posting is bad. However, quoting whole message 
(including quotes of quotes and quotes of quotes of quotes etc.) before your 
message is even worse. Please don't let others scroll extensively.

-- 
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/85D57652-4F14-41F7-9020-506468F33FEC%40v6ak.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: [qubes-project] Hosting for OpenQA instance

[Marek Marczykowski-Górecki]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Sun, Jan 28, 2018 at 10:03:09AM -0800, Frédéric Pierret (fepitre) wrote:
> Le samedi 27 janvier 2018 02:31:12 UTC+1, Andrew David Wong a écrit :
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA512
> > 
> > On 2018-01-26 09:37, Marek Marczykowski-Górecki wrote:
> > > Does anyone have some place/recommendation where to look? Hardware we
> > > need:
> > >  - CPU with VT-x + EPT, so KVM will work with reasonable performance (
> > >means a physical machine, not virtual one)
> > >  - 6-8 GB RAM (4GB for KVM + something for OpenQA itself)
> > >  - 50 GB of disk (preferably more)
> > > 
> > > Does anyone have a spare machine running somewhere, and willing to
> > > share?
> > 
> > However, I'd be surprised if there were no one in the Qubes community
> > willing to share a suitable machine for this purpose. My guess is that
> > there aren't as many readers on qubes-project as there are on
> > qubes-devel and qubes-users, so I'm CCing those other lists.
> 
> I guess it means to have a good bandwidth to download several times an ISO?

- From time to time, yes - we definitely want to test exact images we're
going to release. But I imagine most of the test builds can be done
locally, only downloading few packages from current-testing
repositories.

- -- 
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAlpuMFcACgkQ24/THMrX
1yzv1wf/c+cM/VZTv+BZSRzMURq6LfWupd80usA7eMN9eDcQeUg2vao8zAuEkvlZ
OWvMJIq3KTT+NMMqPG92gC+3oeQRKdZCf4l5myZLPWdKSwkbEXytle2IH+gLuUYX
/EJslkR1JapgzgjKWuLdAhxl5VPBlpJwm3DsXN1CyDMVl4OAMkY2MRK+oVqC06eV
wznb+v203b3LrOjkFby4DG7hGgD4+Wkntt8pjYC6gScdHRc5ZmY53kV3XxXvkktZ
I/WJGCuX94NamyzXIeC5+V0En4PiFYIjyfeQVui0aEBJoW/4r4OyxEJCkZoQLLLo
zG72jdbOitSpIDDoMN3eyEkVr72k1w==
=IrJg
-END PGP SIGNATURE-

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

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

[ludwig jaffe]

private.img is too big, the file system says its really big but it can not
be that big. I guess 4x of the size it should have as I feel it.
But I back it up to my big nas and then I say fsck.ext2 just to be sure
not to loose a thing.


On Sun, Jan 28, 2018 at 3:08 PM, ludwig jaffe 
wrote:

> it is qubes 3.2
>
> Now I found a way:
> I booted kali from usb stick,
> then I did
> cryptsetup  luksOpen /dev/sda3  green
> and mount /dev/dm-blabla  /mnt/8
>
> 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 this a way to repair your cubes without using the idiotic
> tools of qubes :-)
>
>
>
> On Sun, Jan 28, 2018 at 2:42 PM, awokd  wrote:
>
>> On Sun, January 28, 2018 5:26 pm, 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.
>>
>> 4.0? I think the "Qubes way" would be to boot from your install media,
>> pick Rescue mode, and get enough free space to be able to boot the full
>> system. 3.2 I guess you'd have to use a live image; can't remember if
>> there's a rescue mode.
>>
>> I honestly can't tell you how you'd go about attaching a NIC to dom0. USB
>> might be an easier choice, but same there- not something I've ever looked
>> into!
>>
>>
>

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

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

[ludwig jaffe]

it is qubes 3.2

Now I found a way:
I booted kali from usb stick,
then I did
cryptsetup  luksOpen /dev/sda3  green
and mount /dev/dm-blabla  /mnt/8

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 this a way to repair your cubes without using the idiotic
tools of qubes :-)



On Sun, Jan 28, 2018 at 2:42 PM, awokd  wrote:

> On Sun, January 28, 2018 5:26 pm, 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.
>
> 4.0? I think the "Qubes way" would be to boot from your install media,
> pick Rescue mode, and get enough free space to be able to boot the full
> system. 3.2 I guess you'd have to use a live image; can't remember if
> there's a rescue mode.
>
> I honestly can't tell you how you'd go about attaching a NIC to dom0. USB
> might be an easier choice, but same there- not something I've ever looked
> into!
>
>

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

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

['awokd' via qubes-users]

On Sun, January 28, 2018 5:26 pm, 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.

4.0? I think the "Qubes way" would be to boot from your install media,
pick Rescue mode, and get enough free space to be able to boot the full
system. 3.2 I guess you'd have to use a live image; can't remember if
there's a rescue mode.

I honestly can't tell you how you'd go about attaching a NIC to dom0. USB
might be an easier choice, but same there- not something I've ever looked
into!

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

Re: [qubes-users] Re: Split GPG and Emacs/mu4e: able to retrieve email but not send

[rumsey . anthony]

On Sunday, January 28, 2018 at 6:10:36 PM UTC, [799] wrote:
> Hello Rumsey, 
> 
> >> I can now send email using emacs/mu4e
> >> and Qubes split gpg
> 
> I am also interested in this setup. Can you give me some more information 
> what needs to be done to start from a plain installation?
> Something like a copy of the relevant configuration files (stripping out the 
> personal configuration of course by replacing it with something like 
> MAILSERVER.COM, logi...@domain.com, YOUR-GPG-KEY-ID etc).
> 
> Would really appreciate this, to get things up and running.
> 
> [799]

Are you asking about how to get mu4e up and running in emacs? If so, that is 
outside the scope of this message group and I'm certainly not the best place to 
go for information.

I would suggest doing your googles, as there are many guides for this process 
available scattered about.

Briefly, I have found that I'm happy with the an email setup that uses mu4e 
(https://www.djcbsoftware.nl/code/mu/mu4e.html) for interacting with email in 
emacs. I use isync/mbsync (http://isync.sourceforge.net/) for getting my mail 
from the server.

Guides like this one: 
http://www.macs.hw.ac.uk/~rs46/posts/2014-01-13-mu4e-email-client.html

...are helpful for giving you a template on how to set everything up, and it's 
just a matter of wading through the details to get it tuned to your own liking.

-- 
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/bd96a75e-255d-4e51-9e50-3a26e3ae0387%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[demiobenour]

On Wednesday, January 17, 2018 at 5:08:13 AM UTC-5, Tim W wrote:
> On Monday, January 15, 2018 at 6:23:55 PM UTC-5, demio...@gmail.com wrote:
> > My Lenovo ThinkPad fails to boot after installing Qubes.  I had to boot the 
> > USB drive via legacy boot for Qubes to install at all, but the EFI setup 
> > doesn't happen.
> 
> 
> need a model number and spec.  should not need legacy mode if hardware/cpu 
> matches tp qubes oversion 3 vs 4s

Model number is 20HH-CTO1WW

-- 
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/666999e0-4445-4651-8d26-0ed2bb576b85%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: [qubes-project] Hosting for OpenQA instance

[BePe]

Hi All,

FYI, and it in case that it can help, I have succesfully installed Qubes 
4.0 rc3 in KVM with nested virtualization and iommu enabled.
I had to hack a little bit the qemu intel_iommu.c, but now I have fully 
fonctional Qubes 4  (with all the VM in hvm mode).

The VM are not flying but they do work.

BePe - From  BKO

On 01/27/2018 01:31 AM, Andrew David Wong wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2018-01-26 09:37, Marek Marczykowski-Górecki wrote:

Hi,

Manual testing of installation is a time consuming job, so I was looking
for some tool to automate it. And found one:

http://open.qa/

This works by launching the system under test in KVM and then interact
with it as user would do (mouse clicks, keyboard etc). Then compare
screenshots (or parts of it).
The nice thing is when using new new enough KVM, qemu and hardware with
VT-x + EPT, Qubes installation works there! In theory KVM supports even
nested virtualization, so HVM should works inside such setup, but in
practice Xen and/or qemu crashes badly... But PV works fine, which is
enough for installation testing.

I've uploaded some basic tests here:
https://github.com/marmarek/openqa-tests-qubesos

The problem is we don't have a place to host it in long run. While I can
launch it from time to time on one of my testing laptops, it doesn't
scale well. And access to it is restricted, which limit who can work on
this (and on issues found by tests).

Does anyone have some place/recommendation where to look? Hardware we
need:
  - CPU with VT-x + EPT, so KVM will work with reasonable performance (
means a physical machine, not virtual one)
  - 6-8 GB RAM (4GB for KVM + something for OpenQA itself)
  - 50 GB of disk (preferably more)

Does anyone have a spare machine running somewhere, and willing to
share?

Alternatively, it looks like we can get one for ~70 EUR/month. Andrew,
Michael, could we use opencollective money for this?


The OpenCollective money is supposed to be used to pay developers to
work on the open-source version of Qubes. While this would not be a
direct payment to a developer, I can see how it would qualify, since
it's directly saving you and other devs time and work that would
otherwise have to be spent on testing. I think it would adhere to the
spirit of the rule, which is that the money should be spent on
improving the open-source version of Qubes. (Arguably, it would be
even more efficient than paying a developer directly, since Qubes
would probably benefit a lot more from the testing bought by that ~70
EUR/month than it would from the tiny amount of developer time ~70
EUR/month would pay for.)

However, I'd be surprised if there were no one in the Qubes community
willing to share a suitable machine for this purpose. My guess is that
there aren't as many readers on qubes-project as there are on
qubes-devel and qubes-users, so I'm CCing those other lists.

- -- 
Andrew David Wong (Axon)

Community Manager, Qubes OS
https://www.qubes-os.org

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlpr1ioACgkQ203TvDlQ
MDBZaA/9HZWo8gZh5UsrKEAWIC4c4b4hnL2U0NZvqi508qbr65DmqW67y/QGXA0q
EI3VNHpNrhL99jpWGlsGnN3K1Dss+NKKEk82AVsqw6in9P1LA+9CyMjf3TQB1yLn
QkWyFc0E/+wN4ExpMgUuX7kqTv9TgjPrFki+KajpsIvQpXDOqMxM6vNdYitI8fer
B1cpIn0gS17ANcvlXJU2OhLKEradX6msZJdAYWlrZPpy7XEIPtnJTugsN5fm6kr/
ChsQtGH7OTHIJkd0pEr9YODhyr/Tpp6OYDwsQL1uWW4W8K03Mhmh5q+MuKg/scvG
nv8vINL0wo010GdiqsU/bvqB7pYkOFcdsghgM3gy1jBK8E7aR4KgNrafKn22D7eu
fC0Y2LlJmGZ6s+l//sfI6YIMi/iCj+6zUHXLdcGrLI9v+iYu23/9Lz6oyKl1Vedv
+6zh0PasElJXxAgdBGN7Se16ApC8/cTLeEcHhAQ1No/Tye3TaYE1U4ouj+9d6o1l
f7LLiSs1wxmBZcRdK09yK7zqcqi92NsgwBzmKwoz6fQFljo+G3/giar0xZ+8HPXN
HTnQ0von8o22yoK7x5H9jc+Fmq32zUvmYy2R3dAkY8PVmOgVEyf5z2OY3q0HEiEK
25kYJw9tdC7ZS6kI22l4tLGaAm6ntoM/ZbFUG0wrpESunWVrZOE=
=EIwB
-END PGP SIGNATURE-




--
BePe

--
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/175a0e62-c854-d798-d86c-5585729a785d%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

AW: [qubes-users] Re: Split GPG and Emacs/mu4e: able to retrieve email but not send

['[799]' via qubes-users]

Hello Rumsey,

>> I can now send email using emacs/mu4e
>> and Qubes split gpg

I am also interested in this setup. Can you give me some more information what 
needs to be done to start from a plain installation?
Something like a copy of the relevant configuration files (stripping out the 
personal configuration of course by replacing it with something like 
MAILSERVER.COM, loginn...@domain.com, YOUR-GPG-KEY-ID etc).

Would really appreciate this, to get things up and running.

[799]

-- 
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/Sg7yaE_MsuJN4TeW35SHra2JoVzrnA5Ju4d1usmuSHjFE2zAaLQSBRiop-v-7zMqrQ3UEVwM3hk6QlfVrv9qXzHRAIZfg2_p_N24FdlhePg%3D%40protonmail.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: [qubes-project] Hosting for OpenQA instance

[fepitre]

Le samedi 27 janvier 2018 02:31:12 UTC+1, Andrew David Wong a écrit :
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> On 2018-01-26 09:37, Marek Marczykowski-Górecki wrote:
> > Hi,
> > 
> > Manual testing of installation is a time consuming job, so I was looking
> > for some tool to automate it. And found one:
> > 
> > http://open.qa/
> > 
> > This works by launching the system under test in KVM and then interact
> > with it as user would do (mouse clicks, keyboard etc). Then compare
> > screenshots (or parts of it).
> > The nice thing is when using new new enough KVM, qemu and hardware with
> > VT-x + EPT, Qubes installation works there! In theory KVM supports even
> > nested virtualization, so HVM should works inside such setup, but in
> > practice Xen and/or qemu crashes badly... But PV works fine, which is
> > enough for installation testing.
> > 
> > I've uploaded some basic tests here:
> > https://github.com/marmarek/openqa-tests-qubesos
> > 
> > The problem is we don't have a place to host it in long run. While I can
> > launch it from time to time on one of my testing laptops, it doesn't
> > scale well. And access to it is restricted, which limit who can work on
> > this (and on issues found by tests).
> > 
> > Does anyone have some place/recommendation where to look? Hardware we
> > need:
> >  - CPU with VT-x + EPT, so KVM will work with reasonable performance (
> >means a physical machine, not virtual one)
> >  - 6-8 GB RAM (4GB for KVM + something for OpenQA itself)
> >  - 50 GB of disk (preferably more)
> > 
> > Does anyone have a spare machine running somewhere, and willing to
> > share?
> > 
> > Alternatively, it looks like we can get one for ~70 EUR/month. Andrew,
> > Michael, could we use opencollective money for this?
> > 
> 
> The OpenCollective money is supposed to be used to pay developers to
> work on the open-source version of Qubes. While this would not be a
> direct payment to a developer, I can see how it would qualify, since
> it's directly saving you and other devs time and work that would
> otherwise have to be spent on testing. I think it would adhere to the
> spirit of the rule, which is that the money should be spent on
> improving the open-source version of Qubes. (Arguably, it would be
> even more efficient than paying a developer directly, since Qubes
> would probably benefit a lot more from the testing bought by that ~70
> EUR/month than it would from the tiny amount of developer time ~70
> EUR/month would pay for.)
> 
> However, I'd be surprised if there were no one in the Qubes community
> willing to share a suitable machine for this purpose. My guess is that
> there aren't as many readers on qubes-project as there are on
> qubes-devel and qubes-users, so I'm CCing those other lists.
> 
> - -- 
> Andrew David Wong (Axon)
> Community Manager, Qubes OS
> https://www.qubes-os.org
> 
> -BEGIN PGP SIGNATURE-
> 
> iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlpr1ioACgkQ203TvDlQ
> MDBZaA/9HZWo8gZh5UsrKEAWIC4c4b4hnL2U0NZvqi508qbr65DmqW67y/QGXA0q
> EI3VNHpNrhL99jpWGlsGnN3K1Dss+NKKEk82AVsqw6in9P1LA+9CyMjf3TQB1yLn
> QkWyFc0E/+wN4ExpMgUuX7kqTv9TgjPrFki+KajpsIvQpXDOqMxM6vNdYitI8fer
> B1cpIn0gS17ANcvlXJU2OhLKEradX6msZJdAYWlrZPpy7XEIPtnJTugsN5fm6kr/
> ChsQtGH7OTHIJkd0pEr9YODhyr/Tpp6OYDwsQL1uWW4W8K03Mhmh5q+MuKg/scvG
> nv8vINL0wo010GdiqsU/bvqB7pYkOFcdsghgM3gy1jBK8E7aR4KgNrafKn22D7eu
> fC0Y2LlJmGZ6s+l//sfI6YIMi/iCj+6zUHXLdcGrLI9v+iYu23/9Lz6oyKl1Vedv
> +6zh0PasElJXxAgdBGN7Se16ApC8/cTLeEcHhAQ1No/Tye3TaYE1U4ouj+9d6o1l
> f7LLiSs1wxmBZcRdK09yK7zqcqi92NsgwBzmKwoz6fQFljo+G3/giar0xZ+8HPXN
> HTnQ0von8o22yoK7x5H9jc+Fmq32zUvmYy2R3dAkY8PVmOgVEyf5z2OY3q0HEiEK
> 25kYJw9tdC7ZS6kI22l4tLGaAm6ntoM/ZbFUG0wrpESunWVrZOE=
> =EIwB
> -END PGP SIGNATURE-

I guess it means to have a good bandwidth to download several times an ISO?

-- 
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/5e859c08-f5f9-49cb-b894-04ff8cd552de%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: [qubes-project] Hosting for OpenQA instance

[Yethal]

W dniu sobota, 27 stycznia 2018 02:31:12 UTC+1 użytkownik Andrew David Wong 
napisał:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> On 2018-01-26 09:37, Marek Marczykowski-Górecki wrote:
> > Hi,
> > 
> > Manual testing of installation is a time consuming job, so I was looking
> > for some tool to automate it. And found one:
> > 
> > http://open.qa/
> > 
> > This works by launching the system under test in KVM and then interact
> > with it as user would do (mouse clicks, keyboard etc). Then compare
> > screenshots (or parts of it).
> > The nice thing is when using new new enough KVM, qemu and hardware with
> > VT-x + EPT, Qubes installation works there! In theory KVM supports even
> > nested virtualization, so HVM should works inside such setup, but in
> > practice Xen and/or qemu crashes badly... But PV works fine, which is
> > enough for installation testing.
> > 
> > I've uploaded some basic tests here:
> > https://github.com/marmarek/openqa-tests-qubesos
> > 
> > The problem is we don't have a place to host it in long run. While I can
> > launch it from time to time on one of my testing laptops, it doesn't
> > scale well. And access to it is restricted, which limit who can work on
> > this (and on issues found by tests).
> > 
> > Does anyone have some place/recommendation where to look? Hardware we
> > need:
> >  - CPU with VT-x + EPT, so KVM will work with reasonable performance (
> >means a physical machine, not virtual one)
> >  - 6-8 GB RAM (4GB for KVM + something for OpenQA itself)
> >  - 50 GB of disk (preferably more)
> > 
> > Does anyone have a spare machine running somewhere, and willing to
> > share?
> > 
> > Alternatively, it looks like we can get one for ~70 EUR/month. Andrew,
> > Michael, could we use opencollective money for this?
> > 
> 
> The OpenCollective money is supposed to be used to pay developers to
> work on the open-source version of Qubes. While this would not be a
> direct payment to a developer, I can see how it would qualify, since
> it's directly saving you and other devs time and work that would
> otherwise have to be spent on testing. I think it would adhere to the
> spirit of the rule, which is that the money should be spent on
> improving the open-source version of Qubes. (Arguably, it would be
> even more efficient than paying a developer directly, since Qubes
> would probably benefit a lot more from the testing bought by that ~70
> EUR/month than it would from the tiny amount of developer time ~70
> EUR/month would pay for.)
> 
> However, I'd be surprised if there were no one in the Qubes community
> willing to share a suitable machine for this purpose. My guess is that
> there aren't as many readers on qubes-project as there are on
> qubes-devel and qubes-users, so I'm CCing those other lists.
> 
> - -- 
> Andrew David Wong (Axon)
> Community Manager, Qubes OS
> https://www.qubes-os.org
> 
> -BEGIN PGP SIGNATURE-
> 
> iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlpr1ioACgkQ203TvDlQ
> MDBZaA/9HZWo8gZh5UsrKEAWIC4c4b4hnL2U0NZvqi508qbr65DmqW67y/QGXA0q
> EI3VNHpNrhL99jpWGlsGnN3K1Dss+NKKEk82AVsqw6in9P1LA+9CyMjf3TQB1yLn
> QkWyFc0E/+wN4ExpMgUuX7kqTv9TgjPrFki+KajpsIvQpXDOqMxM6vNdYitI8fer
> B1cpIn0gS17ANcvlXJU2OhLKEradX6msZJdAYWlrZPpy7XEIPtnJTugsN5fm6kr/
> ChsQtGH7OTHIJkd0pEr9YODhyr/Tpp6OYDwsQL1uWW4W8K03Mhmh5q+MuKg/scvG
> nv8vINL0wo010GdiqsU/bvqB7pYkOFcdsghgM3gy1jBK8E7aR4KgNrafKn22D7eu
> fC0Y2LlJmGZ6s+l//sfI6YIMi/iCj+6zUHXLdcGrLI9v+iYu23/9Lz6oyKl1Vedv
> +6zh0PasElJXxAgdBGN7Se16ApC8/cTLeEcHhAQ1No/Tye3TaYE1U4ouj+9d6o1l
> f7LLiSs1wxmBZcRdK09yK7zqcqi92NsgwBzmKwoz6fQFljo+G3/giar0xZ+8HPXN
> HTnQ0von8o22yoK7x5H9jc+Fmq32zUvmYy2R3dAkY8PVmOgVEyf5z2OY3q0HEiEK
> 25kYJw9tdC7ZS6kI22l4tLGaAm6ntoM/ZbFUG0wrpESunWVrZOE=
> =EIwB
> -END PGP SIGNATURE-

I have a spare machine I can donate. If any of the Qubes devs are Warsaw-based 
I can even bring it over.

-- 
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/c33647fa-a990-4f18-ab1c-79a920363772%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[ludwig jaffe]

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.





-- 
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/c9dedca4-2135-4f83-81a2-fc429d60a069%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Import back VM (3.2) to Qubes 4.0RC3 ?

['awokd' via qubes-users]

On Sun, January 28, 2018 4:42 pm, ThierryIT wrote:
> I have done my restore.
> Do have some bugs, will open a ticket in Github tomorrow.
> But I do have an error when trying to add "devices" for my netVM:
>
>
> Error: Device tab:
> Can't attach pci device to VM in pvh mode ??
>
>
> What is the pvh mode ?

That's one of the new remediations for Spectre/Meltdown. In order to
attach a PCI device, you have to switch your NetVM back to HVM mode. You
can do that in VM Settings GUI or dom0 command with qvm-prefs.

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

Re: [qubes-users] Import back VM (3.2) to Qubes 4.0RC3 ?

[ThierryIT]

I have done my restore.
Do have some bugs, will open a ticket in Github tomorrow.
But I do have an error when trying to add "devices" for my netVM:

Error: Device tab:
Can't attach pci device to VM in pvh mode ??

What is the pvh mode ?

Thx


Le dimanche 28 janvier 2018 16:14:52 UTC+2, Yuraeitha a écrit :
> On Sunday, January 28, 2018 at 2:58:42 PM UTC+1, ThierryIT wrote:
> > Hi,
> > 
> > I have installed Qubes 4 without any problem.
> > I have done the dom0 upgrade.
> > I am able to start the system.
> > 
> > But I do not have any "Qubes Manager" ...
> > 
> > Thx
> > 
> > Le dimanche 28 janvier 2018 14:17:54 UTC+2, awokd a écrit :
> > > On Sun, January 28, 2018 7:46 am, ThierryIT wrote:
> > > >
> > > > I am a bit lost with Qubes 4.0 RC3 ...
> > > > Before moving to 4.0, I have done my VM's backup.
> > > > How to restore them to Qubes 4.0 ?
> > > 
> > > Please check out https://www.qubes-os.org/doc/upgrade-to-r4.0/. Let me
> > > know if you have any questions; you might be the first one to try it out.
> 
> - Once fully updated, the Qubes manager should be in GUI Menu --> 
> System-tools ---> Qubes Manager. It might require a current-testing update, 
> since it's meant to be released in RC-4 version, and it doesn't seem finished 
> yet. If you can't see it in System-Tools, then you either need to wait, or 
> find it in current-testing dom0 updates.
> 
> - In addition, you may want to consider to be careful with having to re-name 
> VM's too often. This is because Qubes 4 instead of the typical plain 
> re-naming, will copy the entire VM with the new name, and thereafter delete 
> the old-named VM. I hear there is a good reason for this, but I did not look 
> up the technical reason for it. Either way, plan ahead, try avoid to have to 
> re-name in particular large VM's as it can take a while on slow drives. If 
> you got a fast NVMe drive, then it should be fast, but on a slow HDD or even 
> SDD, larger VM's can take a while. It's essentially like doing qvm-clone as 
> you probably can imagine. 
> 
> - There are still bugs to look out for in Qubes 4 RC-3 updated to this day, 
> although most are starting to be mostly minor. 
> 
> - Read the release news in detail when RC-4 is released, as with Qubes 4 the 
> developers has started advizing us whether we can keep updating between RC-X 
> releases, or whether they recommend we re-install again. Last time between 
> RC-2 and RC-3 it was fine to just keep updating. The same may or may not 
> happen between RC-3 and RC-4/final-version.
> 
> - Qubes Manager is still a bit slow and sluggish. I don't know if it'll 
> improve, but my guesses is it probably will when there is time available to 
> do so. 
> 
> - Be aware of the disk discard/trimming in Qubes 4. In Qubes 3.2. we could do 
> it manually, but it's supposed to work automatic in Qubes 4. Unfortunately it 
> doesn't always work out of the box. You may have to dig into /etc/fdisk, 
> Grub.cfg/EFI.cfg, and so forth, in order to get discard/fstrim working. Also 
> notice that dom0 discard/fstrim is not the same as the template 
> discard/fstrim. If it works in dom0, then it'll automatically adjust shown 
> available space moments after removal, if you for example remove a large 
> package in dom0, like a large template. However if you remove files in a VM 
> that doesn't have working discard/fstrim, then it'll be less noticeable and 
> you might not realize. It's a good idea to pay attention, especially if you 
> got little drive space.

-- 
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/f1bde3cd-1679-4244-82d6-f12f372d61c9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Import back VM (3.2) to Qubes 4.0RC3 ?

[Yuraeitha]

On Sunday, January 28, 2018 at 2:58:42 PM UTC+1, ThierryIT wrote:
> Hi,
> 
> I have installed Qubes 4 without any problem.
> I have done the dom0 upgrade.
> I am able to start the system.
> 
> But I do not have any "Qubes Manager" ...
> 
> Thx
> 
> Le dimanche 28 janvier 2018 14:17:54 UTC+2, awokd a écrit :
> > On Sun, January 28, 2018 7:46 am, ThierryIT wrote:
> > >
> > > I am a bit lost with Qubes 4.0 RC3 ...
> > > Before moving to 4.0, I have done my VM's backup.
> > > How to restore them to Qubes 4.0 ?
> > 
> > Please check out https://www.qubes-os.org/doc/upgrade-to-r4.0/. Let me
> > know if you have any questions; you might be the first one to try it out.

- Once fully updated, the Qubes manager should be in GUI Menu --> System-tools 
---> Qubes Manager. It might require a current-testing update, since it's meant 
to be released in RC-4 version, and it doesn't seem finished yet. If you can't 
see it in System-Tools, then you either need to wait, or find it in 
current-testing dom0 updates.

- In addition, you may want to consider to be careful with having to re-name 
VM's too often. This is because Qubes 4 instead of the typical plain re-naming, 
will copy the entire VM with the new name, and thereafter delete the old-named 
VM. I hear there is a good reason for this, but I did not look up the technical 
reason for it. Either way, plan ahead, try avoid to have to re-name in 
particular large VM's as it can take a while on slow drives. If you got a fast 
NVMe drive, then it should be fast, but on a slow HDD or even SDD, larger VM's 
can take a while. It's essentially like doing qvm-clone as you probably can 
imagine. 

- There are still bugs to look out for in Qubes 4 RC-3 updated to this day, 
although most are starting to be mostly minor. 

- Read the release news in detail when RC-4 is released, as with Qubes 4 the 
developers has started advizing us whether we can keep updating between RC-X 
releases, or whether they recommend we re-install again. Last time between RC-2 
and RC-3 it was fine to just keep updating. The same may or may not happen 
between RC-3 and RC-4/final-version.

- Qubes Manager is still a bit slow and sluggish. I don't know if it'll 
improve, but my guesses is it probably will when there is time available to do 
so. 

- Be aware of the disk discard/trimming in Qubes 4. In Qubes 3.2. we could do 
it manually, but it's supposed to work automatic in Qubes 4. Unfortunately it 
doesn't always work out of the box. You may have to dig into /etc/fdisk, 
Grub.cfg/EFI.cfg, and so forth, in order to get discard/fstrim working. Also 
notice that dom0 discard/fstrim is not the same as the template discard/fstrim. 
If it works in dom0, then it'll automatically adjust shown available space 
moments after removal, if you for example remove a large package in dom0, like 
a large template. However if you remove files in a VM that doesn't have working 
discard/fstrim, then it'll be less noticeable and you might not realize. It's a 
good idea to pay attention, especially if you got little drive space. 

-- 
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/d4c47978-bc7a-4b1f-8044-c8ee7bf737d3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Import back VM (3.2) to Qubes 4.0RC3 ?

['awokd' via qubes-users]

On Sun, January 28, 2018 1:58 pm, ThierryIT wrote:
> Hi,
>
>
> I have installed Qubes 4 without any problem.
> I have done the dom0 upgrade.
> I am able to start the system.
>
>
> But I do not have any "Qubes Manager" ...

That might be only available in the Testing repository, not in Stable yet.
In dom0, try running:

sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing

then look for Qubes Manager again. You only have to do this once,
afterwards you can go back to the regular "sudo qubes-dom0-update" for
updates.

If you don't care about having Qubes Manager, you could also run
"qubes-backup-restore" from dom0 to jump directly to the restore
interface.


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

Re: [qubes-users] Import back VM (3.2) to Qubes 4.0RC3 ?

[ThierryIT]

Hi,

I have installed Qubes 4 without any problem.
I have done the dom0 upgrade.
I am able to start the system.

But I do not have any "Qubes Manager" ...

Thx

Le dimanche 28 janvier 2018 14:17:54 UTC+2, awokd a écrit :
> On Sun, January 28, 2018 7:46 am, ThierryIT wrote:
> >
> > I am a bit lost with Qubes 4.0 RC3 ...
> > Before moving to 4.0, I have done my VM's backup.
> > How to restore them to Qubes 4.0 ?
> 
> Please check out https://www.qubes-os.org/doc/upgrade-to-r4.0/. Let me
> know if you have any questions; you might be the first one to try it out.

-- 
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/825bca3e-a741-40d4-8721-2b69ac712c58%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Import back VM (3.2) to Qubes 4.0RC3 ?

['awokd' via qubes-users]

On Sun, January 28, 2018 7:46 am, ThierryIT wrote:
>
> I am a bit lost with Qubes 4.0 RC3 ...
> Before moving to 4.0, I have done my VM's backup.
> How to restore them to Qubes 4.0 ?

Please check out https://www.qubes-os.org/doc/upgrade-to-r4.0/. Let me
know if you have any questions; you might be the first one to try it out.

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