Re: [qubes-users] New install R3.2 - All VMs fail with libxenlight error

2017-11-21 Thread pr0xy
On 2017-11-21 10:21, pr0xy wrote:
> I have a new workstation, 128GB RAM, Xeon with 10 cores, 1TB SSD, and
> I'm trying to get R3.2 running on it. VT-x and VT-d are enabled in the
> BIOS along with TPM. Had to set the machine to Legacy boot and turn off
> UEFI to install Qubes though.
> 
> I've tried reinstalling Qubes a few times, but I get the same results.
> When trying to open any AppVM, and even the Fedora and Debian Templates,
> I get the error:
> 
> internal error: libxenlight failed to create new domain
> 
> In one of my tests I was able to get the default anon-whonix VM to work,
> but after a subsequent reinstall that is not working any longer.
> 
> I'd really like to get Qubes working on this machine, but I'm not sure
> where to look.

I see in these threads I see Marek suggesting:
https://groups.google.com/forum/#!topic/qubes-users/LU5WrTPfbZs
https://groups.google.com/d/msg/qubes-devel/jeAsPQjImlU/420g-sYzBAAJ

 - if you get "internal error: libxenlight failed ...", look into
   /var/log/libvirt/libxl/libxl-driver.log in dom0 

However, the entire /var/log/libvirt/ folder is empty on my machine. Bu
those instructions may just be for R4, not my R3.2.

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


Re: [qubes-users] Can not use Realtek RTS525A PCI Express Card : Unsigned class [ff00]

2017-11-21 Thread Laurent
Le mardi 21 novembre 2017 21:33:24 UTC+1, awokd a écrit :
> On Tue, November 21, 2017 07:39, Laurent wrote:
> > Oups !!! Sorry for this mistake ..
> 
> No problem! The only network card I see in that list is the same one you
> already found-
> 02:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a)
> 
> Is Ethernet built in? Do you need to enable it in your BIOS? Are you using
> a USB Ethernet adapter?

Yes, I use an USB Ethernet adapter (USB type C):
https://www.amazon.com/Dell-Dbqbcbc064-Adapter-Usb-C-Ethernet/dp/B01BQ8RU2U
 

I've the same issue with my hub USB (type C also) : 
(https://shop.hardware.fr/fiche/AR201511130055.html?gclid=EAIaIQobChMI_4bM8tHR1wIVdSjTCh2HWQSyEAQYASABEgLnqfD_BwE)


My USB flash drive works fine when directly plugged on my laptop. When using my 
Hub, the same USB flash drive is not detected.
Same for an external USB Disk Drive.

-- 
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/1abd6be4-4f14-47f0-85ed-035199d75b56%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] R4.0, Ubuntu, and Salt

2017-11-21 Thread viq
https://www.qubes-os.org/doc/salt/#debugging is what I found so far

On 19 Nov 2017 10:27 p.m., "rysiek"  wrote:

> On Saturday, November 18, 2017 10:30:49 PM UTC Marek Marczykowski-Górecki
> wrote:
> > On Sat, Nov 18, 2017 at 06:36:17PM +, rysiek wrote:
> > > Also, started playing with Salt, wrote a nice sls file to install all
> the
> > > stuff I need in the Kubuntu VM, but... each time I run it I get an
> > > "ERROR". I am guessing this is related to the less-than-stellar support
> > > for Ubuntu templates in Qubes R4.0.
> >
> > Run qubesctl with --show-output, or check /var/log/qubes/mgmt-*.log for
> > details.
>
> Thanks. This only gives me this error:
> 2017-11-19 22:06:19,000 calling 'state.highstate'...
> 2017-11-19 22:06:55,812 output: qubuntu:
> 2017-11-19 22:06:55,813 output: --
> 2017-11-19 22:06:55,813 output: _error:
> 2017-11-19 22:06:55,814 output: Failed to return clean data
> 2017-11-19 22:06:55,814 output: retcode:
> 2017-11-19 22:06:55,814 output: 1
> 2017-11-19 22:06:55,814 output: stderr:
> 2017-11-19 22:06:55,814 output: stdout:
> 2017-11-19 22:06:55,814 exit code: 20
>
> is tehre any way to enable more debug output?
>
> --
> Pozdrawiam,
> Michał "rysiek" Woźniak
>
> Zmieniam klucz GPG :: http://rys.io/pl/147
> GPG Key Transition :: http://rys.io/en/147
>
> --
> 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/1905541.GLcTUDNXif%40qubuntu.
> For more options, visit https://groups.google.com/d/optout.
>

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


Re: [qubes-users] Local network access when using ProxyVM as VPN gateway using iptables and CLI scripts?

2017-11-21 Thread Michael Siepmann
On 11/16/2017 09:50 PM, Michael Siepmann wrote:
> On 11/16/2017 08:11 AM, Chris Laprise wrote:
>> On 11/15/2017 10:17 PM, Michael Siepmann wrote:
>>> I've followed the instructions to "Set up a ProxyVM as a VPN gateway
>>> using iptables and CLI scripts" at https://www.qubes-os.org/doc/vpn/
>>> and it's working well so far but I need to be able to access my local
>>> network 192.168.x.x. That worked when I was connecting to the VPN
>>> with Network Manager in my NetVM. Is there a way to configure that
>>> when using a ProxyVM as a VPN gateway? I'm guessing I need to do
>>> something in /rw/config/qubes-firewall-user-script in my VPN ProxyVM
>>> to configure iptables to allow bypassing the VPN for 192.168.x.x but
>>> I'm not sure how to do that. Any help will be greatly appreciated!
>>>
>> Hi Michael,
>>
>> You're not the first to ask about LAN access via a VPN VM. Various
>> posters in qubes-users have found ways around the anti-leak
>> configuration to access particular nets directly.
>>
>> What I usually advise is to think of VPN proxy, sys-firewall or any
>> other proxyVM as Qubes network primitives: Let the VPN VM do its thing
>> in guarding against non-tunnel access, and use sys-firewall or
>> specific proxyVM to access the LAN. This implies that any given appVM
>> can have access to only one type of network (or, only one type at a
>> time). This IMHO is the best way.
>>
>> OTOH, yes you can make the compromise in the VPN VM and allow
>> non-tunnel traffic. In the firewall script, you can start by
>> commenting-out these two lines:
>>
>> iptables -I FORWARD -o eth0 -j DROP
>> iptables -I FORWARD -i eth0 -j DROP
>>
>> This removes almost all leak protection, but should suffice for
>> initial testing. You may also have to add a route pointing to your
>> local net (see Linux "ip route" documentation) because the VPN may
>> have added its route as a default. If you wish to eventually reinstate
>> the above anti-leak rules you can try adding exceptions after those
>> two (so they will be listed _first_ in the FORWARD chain), for instance:
>>
>> iptables -I FORWARD -o eth0 -d 192.168.0.0/16 -j ACCEPT
>> iptables -I FORWARD -i eth0 -s 192.168.0.0/16 -j ACCEPT
>>
>> A word of caution: Once you start modifying rules like this its easy
>> to make mistakes that compromise security, even if you generally know
>> what you're doing. That's one reason to use the Qubes-oriented net
>> security model I mentioned initially. Another reason is, of course,
>> that even creating correct exceptions to tunnel enforcement opens you
>> up to certain kinds of threats. If your use case does not call for an
>> appVM accessing both VPN and LAN at the same time then there should be
>> no reason to make the compromise.
>>
> Hi Chris,
>
> Thank you! I will try this and report back. My main use case here is
> automatically doing an encrypted backup (with Borg Backup) of my files
> once an hour to a NAS device, which in turn automatically copies the
> backups to cloud storage at night, when I don't have competing needs for
> the upload bandwidth. Another use case is file sync, e.g. with SyncThing
> (which can work over the Internet, but much slower of course). However,
> I can certainly see the security advantages of only letting an appVM
> have access to one type of network, or only one type at a time.

Hi Chris,

I got it working! The changes I've made (to allow access only to
192.168.9.x, not 192.168.x.x) are:

In my "sys-vpn" VPN Proxy VM...

...added the following lines to /rw/config/qubes-firewall-user-script,
after the "Block forwarding of connections through upstream network
device (in case the tunnel breaks)" section:

  #    Allow forwarding of connections through upstream network device
  #    if they're to 192.168.9.x
  iptables -I FORWARD -o eth0 -d 192.168.9.0/24 -j ACCEPT
  iptables -I FORWARD -i eth0 -s 192.168.9.0/24 -j ACCEPT

...added the following lines to /rw/config/vpn/qubes-vpn-handler.sh, at
the end of the "up)" case:

  # Allow access to home network for backup, etc.
  ip route add 192.168.9.0/24 via 10.137.1.1 dev eth0

...where 10.137.1.1 is the gateway for my "sys-vpn" VPN ProxyVM.

Please let me know if you see any problems with what I've done other
than the general security caveat you mentioned before.

Many thanks for your help!  I really appreciate it.



-- 
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/1f12b2c7-17b6-69a3-44fb-b6f247dc3f84%40TechDesignPsych.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature


Re: [qubes-users] Possible privacy concerns with Qubes 4 and the transition away from paravirtualization?

2017-11-21 Thread qubesos
On 11/21/2017 02:23 PM, taii...@gmx.com wrote:
> On 11/20/2017 06:08 PM, Jean-Philippe Ouellet wrote:
> 
>> On Mon, Nov 20, 2017 at 5:59 PM, taii...@gmx.com  wrote:
>>> On 11/19/2017 07:17 PM, riggedegg...@gmail.com wrote:
>>>
>>> Does this hold any water? Does the switch from paravirtualization to
>>> HVM/SLAT degrade privacy by allowing easier hardware fingerprinting?
>>>
>>> It holds no water.
>>>
>>> There is no such thing as "hardware fingerprinting"
>> Then what do you call checking e.g. clock drift, disk bandwidth, etc.?
> I consider hardware fingerprinting to be something permanent, those are
> not and are limited to finding out that two VM's are on the same PC.

Well, the clock drift in an intrinsic feature of your processor clock,
disk bandwidth of your disks, etc.

This kind of hardware fingerprinting is something permanent. And
preventing it requires willfully slow things down, things I don't expect
a general-purpose OS like Qubes to do.

Actually this kind of hardware fingerprinting can even be done in
javascript, thanks to all the optimizations performed. Basically, the
faster (hence closer to the metal) the attacking program runs, the
better it can fingerprint your hardware, usually.

HTH,
Leo

PS: Yes, I'm making things look simpler than they are, I know, but it
has to fit in an email.

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/cf7cb182-7a0d-bc4b-079f-cf6046be1de5%40gaspard.ninja.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Re: Last dom0 update broke 3.2

2017-11-21 Thread Franz
On Sun, Nov 12, 2017 at 5:18 PM, Yuraeitha  wrote:

> On Sunday, November 12, 2017 at 7:52:10 PM UTC, Francesco wrote:
> > After last dom0 update it properly restarted but gave some qubes manager
> errors.
> >
> >
> > Second restart keeps restarting on a loop Every time giving the enclosed
> screen.
> >
> >
> > Best
> > Fran
>
> I'd suspect you can probably bypass it by selecting your old kernel before
> the update. I've had that issue a few times my self on Qubes and various
> other Linux systems. If you run Grub, then instead select "Advanced" and go
> in and select the second kernel instead of the top one (which is the newly
> installed and now default kernel).
> The lowest kernel is the one installed before the one that worked before.
> Qubes saves up to 3 kernels by default, if needed it can be extended
> indefinitely, but 3 is usually enough.
>

It worked. Many thanks. I had to use supergrubdisk.org USB booting key and
with that was able to choose which kernel to boot on.

Many thanks it saved my work.
Best
Fran

>
> If you installed Qubes over EFI/UEFI instead of Legacy BIOS, then you'll
> need to pick a live boot medium, or use the Qubes installer to enter rescue
> mode, and then navigate to your /boot/efi/'somewhere here abouts' and find
> your xen.cfg file. In this file you can edit which kernel EFI boot mode
> should boot with.
>
> If any of the associated kernel/module updates broke something else, like
> for example a hardware like Wifi/networking, then it becomes much more
> tricky. It's often, in my experence at least, typically easy to recover
> from bad kernels and at least boot it up. The question is more, if
> something else stopped working too, albeit in my experience it's typically
> enough to just pick the last kernel.
>
> Also, if you succesfully get into Qubes again, then I'd recommend you
> increase your max saved kernels with 'sudo nano /etc/dnf/dnf.conf' and
> locate the line called Installonly_limit=3 to 5 or abouts.
>
> The reasoning for this, is because if another future kernel upgrade also
> fails, then you'll get no more chances of easy recovery if all working
> kernels were automatically deleted during the update. If you set it to 5,
> it'll then save 5 kernels.
>
> Just be sure your kernel partition has enough disk space to house older
> kernels associated with the number of kernels you choose to save.
>
> --
> 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/ms
> gid/qubes-users/0db23e3e-aa44-4e91-85f3-4eacb4467abd%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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


Re: [qubes-users] Copying file from Debian8(or Whonix) to a Fedora VM?

2017-11-21 Thread awokd
On Tue, November 21, 2017 20:52, vel...@tutamail.com wrote:
> Thank you both for taking the time to help...
>
> Managed to upgrade the template, also managed to get my wifi working on
> debian-8 template(seems faster now to boot!).

Good work, it's not always a very intuitive process.

> Sorry for the basic question but how do I select "GNOME" in this window?(I
> saw a "*" by googling but no keys seems to work.

Make sure you're doing "sudo tasksel" and try 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/aa766e6860816d90bda1c496f6c59c29%40elude.in.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Copying file from Debian8(or Whonix) to a Fedora VM?

2017-11-21 Thread velcro
Thank you both for taking the time to help...

Managed to upgrade the template, also managed to get my wifi working on 
debian-8 template(seems faster now to boot!).

I found this post with instructions:
1) sudo apt install firmware-iwlwifi
2) sudo apt update && sudo apt upgrade

However I am struggling with getting the Gnome desktop installed.

I run 'sudo tasksel' and get the option to scroll down to GNOME, the red cursor 
seems to move however I am unable to select GNOME, I tried just leaving the red 
cursor on GNOME, hit enter(or OK) but nothing happens?? It simply closes and I 
go back to the terminal with user@debian...

Sorry for the basic question but how do I select "GNOME" in this window?(I saw 
a "*" by googling but no keys seems to work.

Thank you again...unfortunately I have been the target of an ongoing attack and 
having been hacked with Microsoft, then Apple I decided to go with Qubes as it 
is the most secure. But it has been a huge learning curve!



 
 

-- 
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/a678c02b-9332-4cda-aa5d-18d37ed53390%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Can not use Realtek RTS525A PCI Express Card : Unsigned class [ff00]

2017-11-21 Thread awokd
On Tue, November 21, 2017 07:39, Laurent wrote:
> Oups !!! Sorry for this mistake ..

No problem! The only network card I see in that list is the same one you
already found-
02:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a)

Is Ethernet built in? Do you need to enable it in your BIOS? Are you using
a USB Ethernet adapter?



-- 
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/68172521a45a308a4e244fa8ed8d40a4%40elude.in.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Fwd: Us congress hearing of maan alsaan Money laundry قضية الكونغجرس لغسيل الأموال للمليادير معن الصانع

2017-11-21 Thread Sabah A
YouTube videos of



 U.S. Congress money laundering hearing


of

Saudi Billionaire  " Maan  Al sanea"

 with *bank of America*


and  The  owner of Saad Hospital and  Schools

 in the Eastern Province in *Saudi Arabia*



and the Chairman of the Board of Directors of Awal Bank  in *Bahrain*


With Arabic Subtitles





*موقع اليوتيوب الذي عرض جلسة استماع الكونجرس الأمريكي *

* لمتابعة نشاطات غسل الأموال ونشاطات*



*السعودي معن عبدالواحد الصانع*



*مالك مستشفى  وشركة سعد  ومدارس سعد بالمنطقة الشرقية بالسعودية   ورئيس مجلس
ادارة بنك اوال البحريني*



*مترجم باللغة العربية*



http://www.youtube.com/watch?v=mIBNnQvhU8s

-- 
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/CA%2BQeeU1q7%3Dm%3D5vyc-Mz-ZWHH38vS26QxVvGX_xdMvKUdFF1QWg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Possible privacy concerns with Qubes 4 and the transition away from paravirtualization?

2017-11-21 Thread taii...@gmx.com

On 11/20/2017 06:10 PM, Jean-Philippe Ouellet wrote:


On Mon, Nov 20, 2017 at 6:04 PM,taii...@gmx.comwrote:

On 11/20/2017 04:36 AM, Jean-Philippe Ouellet wrote:


That statement is demonstrably false. For example, we don't filter
CPUID vendor IDs in either mode.

How come?

See discussion athttps://github.com/QubesOS/qubes-issues/issues/1142

That is pretty silly reasoning from the "closedwontfix" camp.

Saying CPU model 5xxx is much different than saying CPU model 5412, 
libvirt already supports that so I see no reason not to.


--
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/832c8c18-e33d-5614-a934-369ee66ba181%40gmx.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Possible privacy concerns with Qubes 4 and the transition away from paravirtualization?

2017-11-21 Thread taii...@gmx.com

On 11/20/2017 06:08 PM, Jean-Philippe Ouellet wrote:


On Mon, Nov 20, 2017 at 5:59 PM,taii...@gmx.comwrote:

On 11/19/2017 07:17 PM,riggedegg...@gmail.com  wrote:

Does this hold any water? Does the switch from paravirtualization to
HVM/SLAT degrade privacy by allowing easier hardware fingerprinting?

It holds no water.

There is no such thing as "hardware fingerprinting"

Then what do you call checking e.g. clock drift, disk bandwidth, etc.?
I consider hardware fingerprinting to be something permanent, those are 
not and are limited to finding out that two VM's are on the same PC.


--
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/2a1be472-717d-82cc-19e6-e9e3b8c2648d%40gmx.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] A lot of trouble with qubes 4.0 rc2

2017-11-21 Thread Bernhard
On 11/20/2017 09:34 PM, Chris Laprise wrote:
>
> If possible, you should try doing a full update with testing release:
>
> qubes-dom0-update --enablerepo=qubes*testing
Thank you for helping me. I'll try this out quickly & tell (all of) you
on this list.
>> 2) I created a large (150G) personal appvm. The "max system storage" is
>> still 10G and I don't see how/where this could be changed.   When
>> playing back backups, the fs is de facto limited to these 10G - so rsync
>> fails at some stage;  from this moment on reboots fail as well (with
>> qrexec-error). journalctl gives no help (the journal keeps silent while
>> launching "qvm-start personal" in the neighbour terminal).
>
> System storage (the template) is different than private storage, and I
> believe its the latter you should be concerned about. Not sure just
> how you are using rsync... a lot depends on what your source and
> target are.
>
Here is my procedure: I have a usb disc. I attach it to the appvm, loop
the luks container to /dev/loopX, cryptsetup luksOpen it, and mount then
the /dev/mapper/backup . Then I use (as root)   rsync -auv
/backup/appvm-name  /home/user/. The data is 140G so I gave 150G to
the appvm as private storage. The rsync fails after ~6GB of data
transferred. Is this possble since the (standard install) LVM-thin
cannot provide  quickly enough disc space??

Alternatively I can start the appvm,  pause it, attach its private.img
to sys-usb and follow then the above procedure as root in sys-usb (this
is how I made the backups, since I prefer doing them by hand).

Is there some flaw in my procedure? Thank you, Bernhard

-- 
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/755eb516-14e5-8d93-e456-8bd8e0e73682%40web.de.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] New install R3.2 - All VMs fail with libxenlight error

2017-11-21 Thread pr0xy
I have a new workstation, 128GB RAM, Xeon with 10 cores, 1TB SSD, and
I'm trying to get R3.2 running on it. VT-x and VT-d are enabled in the
BIOS along with TPM. Had to set the machine to Legacy boot and turn off
UEFI to install Qubes though.

I've tried reinstalling Qubes a few times, but I get the same results.
When trying to open any AppVM, and even the Fedora and Debian Templates,
I get the error:

internal error: libxenlight failed to create new domain

In one of my tests I was able to get the default anon-whonix VM to work,
but after a subsequent reinstall that is not working any longer.

I'd really like to get Qubes working on this machine, but I'm not sure
where to look.

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


[qubes-users] Help? Support?

2017-11-21 Thread riggedeggcam
Well, there's the subreddit, this site, and qubes-issues on Github. There's 
also a fairly prominent "join the community" section on the qubes-os.org 
homepage. Not sure what else you're looking for?

-- 
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/3600c36f-d4f1-4570-a656-d79787a43e21%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Help? Support?

2017-11-21 Thread riggedeggcam
Well, there's the subreddit, this site, and qubes-issues on Github.

-- 
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/fe52f05f-250a-4ab3-aa6c-345686f9fc8a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.