Re: [qubes-users] New laptop for Qubes V4

2016-08-06 Thread eldorado

Thank you

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


Re: [qubes-users] AppVMs with pci devices attached don't start

2016-11-20 Thread eldorado

On 2016-11-20 15:15, Marek Marczykowski-Górecki wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Sun, Nov 20, 2016 at 01:53:30PM -0500, eldor...@riseup.net wrote:

Hi!

After upgrading dom0 and fedora-23 templates two days ago i can't run 
any

appvm that has pci devices like sys-net and sys-usb.
sys-net and sys-usb work after removing pci devices.
Download attachments for more info.
How can i fix this issue?


Is it include also automatic starting of them during system startup?
Generally starting a VM with PCI device after long system uptime is
unreliable (at least) because of how Xen handle memory for such VMs
(needs coherent memory area, which may not be available after running
many VMs).

- --
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-
Version: GnuPG v2

iQEcBAEBCAAGBQJYMgR1AAoJENuP0xzK19csy6IH/0s9v3SmPAJPrZOIopnLcwpx
de8D+7VSRMDsGwBYfRtdI0P/j3J72Jla/ju9tINXwDUZkeYHahxVGMPht389PIUt
I1EGcd58vpWIdDrSUI8PfBf4uZGnR2FMd9C7irHFAFqgI+7S8c38vMQi9HXZ5Jiq
mnw9QvCst2FjwRtOpJt2daSAPVx5X04AelfVEnl8jaIjkZ15doqgYuXXLFi5QN6u
wYUCEx8FQTmtUveOID0mR7WsZpO778LQj68ncK34llZXgv5wwbDEcT/aeRj9CP+8
iqb+Tuk7m85iRArJqFzGpa10qcXLswIqyHtMO6HuE/p9xJ9fpc9ZBf38z0YkDJA=
=yhwM
-END PGP SIGNATURE-


Yes , all of these AppVMs automatically start on boot but logs show 
failed.


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


Re: [qubes-users] AEM boot doesn't load serviceVM's since Xen 4.6.3

2016-12-07 Thread eldorado

On 2016-12-04 15:49, Lorenzo Lamas wrote:

Since upgrading to Xen 4.6.3-21 from Xen 4.6.1-20, booting with AEM
fails to start serviceVM's(netVM, usbVM, firewallVM). When the boot
process finally completes, trying to manually launch the VMs through
VM Manager doesn't work either. When I choose to boot without AEM,
everything works as expected. Problem remains with the latest Xen
4.6.3-24.
It is on a HP Elitebook 8460p with IOMMU running Qubes 3.2

I'm not very familiar with Linux, so if you want logs, please tell me
where to find them.

In case it may not be related to the new Xen version but some other
update installed at the same time, here is the update history:

Transaction ID : 13
Begin time : Tue Nov 22 19:56:34 2016
Begin rpmdb: 934:24862fb1256d9f648273fa8d88ac172b1a06d3d9
End time   :19:58:15 2016 (101 seconds)
End rpmdb  : 939:d785b8e09d66f2d440768eaa6b01d1e77e21ac7c
User   :  
Return-Code: Success
Command Line   :
--exclude=qubes-template-fedora-23,qubes-template-fedora-24,qubes-template-whonix-ws,qubes-template-whonix-gw,qubes-template-debian-8,
upgrade
Transaction performed with:
Installed dnf-1.1.10-1.fc23.noarch@anaconda/rawhide
Installed rpm-4.13.0-0.rc1.13.fc23.x86_64 @anaconda/rawhide
Packages Altered:
Upgraded glusterfs-3.7.16-1.fc23.x86_64
@qubes-dom0-cached
Upgrade3.7.17-1.fc23.x86_64
@qubes-dom0-cached
Upgraded glusterfs-api-3.7.16-1.fc23.x86_64
@qubes-dom0-cached
Upgrade3.7.17-1.fc23.x86_64
@qubes-dom0-cached
Upgraded glusterfs-client-xlators-3.7.16-1.fc23.x86_64 
@qubes-dom0-cached
Upgrade   3.7.17-1.fc23.x86_64 
@qubes-dom0-cached
Upgraded glusterfs-libs-3.7.16-1.fc23.x86_64   
@qubes-dom0-cached
Upgrade 3.7.17-1.fc23.x86_64   
@qubes-dom0-cached
Upgraded libraw1394-2.1.0-6.fc23.x86_64
@anaconda/rawhide
Upgrade 2.1.2-1.fc23.x86_64
@qubes-dom0-cached
Upgraded qubes-core-dom0-3.2.11-1.fc23.x86_64  
@qubes-dom0-cached
Upgrade  3.2.12-1.fc23.x86_64  
@qubes-dom0-cached
Upgraded qubes-core-dom0-doc-3.2.11-1.noarch   
@qubes-dom0-cached
Upgrade  3.2.12-1.noarch   
@qubes-dom0-cached
Upgraded qubes-db-3.2.1-1.fc23.x86_64  
@anaconda/rawhide
Upgrade   3.2.3-1.fc23.x86_64  
@qubes-dom0-cached
Upgraded qubes-db-dom0-3.2.1-1.fc23.x86_64 
@anaconda/rawhide
Upgrade3.2.3-1.fc23.x86_64 
@qubes-dom0-cached
Upgraded qubes-db-libs-3.2.1-1.fc23.x86_64 
@anaconda/rawhide
Upgrade3.2.3-1.fc23.x86_64 
@qubes-dom0-cached
Upgraded xfce4-datetime-plugin-0.6.2-6.fc23.x86_64 
@anaconda/rawhide
Upgrade0.7.0-1.fc23.x86_64 
@qubes-dom0-cached
Upgraded xfce4-diskperf-plugin-2.5.5-2.fc23.x86_64 
@anaconda/rawhide
Upgrade2.6.0-1.fc23.x86_64 
@qubes-dom0-cached
Upgraded xfce4-fsguard-plugin-1.0.2-2.fc23.x86_64  
@anaconda/rawhide
Upgrade   1.1.0-1.fc23.x86_64  
@qubes-dom0-cached
Upgraded xfce4-systemload-plugin-1.1.2-3.fc23.x86_64   
@anaconda/rawhide
Upgrade  1.2.0-1.fc23.x86_64   
@qubes-dom0-cached
Upgraded quota-1:4.02-5.fc23.x86_64
@anaconda/rawhide
Upgrade1:4.02-6.fc23.x86_64
@qubes-dom0-cached
Upgraded quota-nls-1:4.02-5.fc23.noarch
@anaconda/rawhide
Upgrade1:4.02-6.fc23.noarch
@qubes-dom0-cached
Upgraded libpng-2:1.6.23-1.fc23.x86_64 
@anaconda/rawhide
Upgrade 2:1.6.26-1.fc23.x86_64 
@qubes-dom0-cached
Upgraded xen-2001:4.6.1-20.fc23.x86_64 
@anaconda/rawhide
Upgrade  2001:4.6.3-21.fc23.x86_64 
@qubes-dom0-cached
Upgraded xen-hvm-2001:4.6.1-20.fc23.x86_64 
@anaconda/rawhide
Upgrade  2001:4.6.3-21.fc23.x86_64 
@qubes-dom0-cached
Upgraded xen-hypervisor-2001:4.6.1-20.fc23.x86_64  
@anaconda/rawhide
Upgrade 2001:4.6.3-21.fc23.x86_64  
@qubes-dom0-cached
Upgraded xen-libs-2001:4.6.1-20.fc23.x86_64
@anaconda/rawhide
Upgrade   2001:4.6.3-21.fc23.x86_64
@qubes-dom0-cached
Upgraded xen-licenses-2001:4.6.1-20.fc23.x86_64
@anaconda/rawhide
Upgrade   2001:4.6.3-21.fc23.x86_64
@qubes-dom0-cached
Upgraded xen-runtime-2001:4.6.1-20.fc23.x86_64 
@anaconda/rawhide
Upgrade  2001:4.6.3-21.fc23.x86_64 
@qubes-dom0-cached

Scriptlet output:
   1 sed: can't read /etc/sysconfig/prelink: No such file 

[qubes-users] How to set dns in sys-net

2017-03-15 Thread eldorado

I want to set dns in sys-net .
After installing dnscrypt-proxy in sys-net template i have access to 
internet in sys-net

via new dns address with these commands.
"sudo dnscrypt-proxy --daemonize --syslog -R dnscrypt.eu-nl -a 
127.0.0.2:53"

"dig txt opendns.com"
and dig command shows me i have access to new dns address(127.0.0.2:53).

but sys-firewall doesn't have access to internet.
How can i fix this?

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