[qubes-users] Recover broken bootloader

2017-10-30 Thread lokedhs 
My laptop has started to fail to boot my 4.0rc2 installation. This started 
after doing a qubes-dom0-update, but I'm pretty sure that I had rebooted the 
machine successfully at least once since then.

The computer has now gone into a bootloop, and fails to display the GRUB 
screen. I can only assume that the bootloader is crashing. However, nothing is 
displayed on the screen.

Is there a recommended procedure to reinstall GRUB when booting from the 
installation media?

Regards,
Elias

-- 
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/1c7696e0-7a58-4913-b9df-266593aac15b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Anyone have any luck setting up KDE Connect or another Android-sync tool?

2017-10-30 Thread Sudomain 
@[799] Thank you for the links. I've read through them and I understand 
iptables a bit better now, but unfortunately I still haven't been able to get 
this to work. I've created rules for both tcp and udp on ports 1714:1764 (per 
the KDEConnect troubleshooting doc I originally linked to). I tried doing this 
by following the Qubes documentation on port forwarding to appvm's, but 
substituting ip addresses that sys-net and sys-firewall gave me using:
ifconfig | grep -i cast

I'm positive that I used the correct ip's and interface names. There's just so 
many moving parts to this (sys-net, sys-firewall, iptables, KDEConnect, my 
router and phone) that it's hard to tell where it's breaking. Is there a way to 
tell if sys-net (and also sys-firewall) is routing the packets properly?
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/b535b7aa-af7a-4c35-ae34-952afca05422%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Qubes 4.0-rc2 :: VMs fail to start

2017-10-30 Thread Chris Laprise 

On 10/30/17 16:29, Roy Bernat wrote:

On Wednesday, 25 October 2017 13:26:51 UTC-4, [799]  wrote:

Hello,

As at least one other Qubes user has the same problem, that VMs won't start, 
I'll add this as special topic.

I've made a clean install of Qubes 4-rc2 but ~70% of the time I can't boot the 
VMs.
This includes sys-net, sys-firewall, but also others.

I tried to check the logs but I don't get any valuable information.
See screenshot.

I started the following command in dom0:

watch -n 1 xl list

When I try to launch a VM I can see that the VMs appears in the xl list output, 
but the State is -- and the Time(s) is 0.0.
After ~30sec the start is aborted with error message: Cannot execute 
qrexec-daemon.

Questions:
1) is anyone running Qubes 4.0-rc2 on a Lenovo X230?
2) is someone additionaly running Coreboot?
3) I am running the Qubes Installation with the default settings, any options 
to tweak on the Grub command line

[799]





Gesendet von ProtonMail mobile

no one has any idea ?  i tried to look for some logs with no solution .

what i have found that it happen mpre if i update the dom0 before i am updating 
the templates .

maybe 

Roy



Over the past couple days, this has usually worked:

1. Close any appVMs that appear to be using lots of RAM and are not 
giving it back.


2. Start an isolated (network setting is "none") appVM... it should 
start up. Leave it running...


3. Start the VMs you intend to use; they should also start now.

--

Chris Laprise, tas...@posteo.net
https://github.com/tasket
https://twitter.com/ttaskett
PGP: BEE2 20C5 356E 764A 73EB  4AB3 1DC4 D106 F07F 1886

--
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/c17cfc69-9019-9cff-30ae-5b1584af2ba1%40posteo.net.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Rc2 hangs on install -- Dell Inspiron i5759-8835SLV

2017-10-30 Thread billollib 
On Monday, October 30, 2017 at 7:29:55 PM UTC-4, bill...@gmail.com wrote:
> Don't know what this means, but I downloaded the new 4.0 RC2, put it on a 
> flash drive, and tried to install it on my new Dell laptop.  It froze early 
> on, with the messages:
> 
> 
> Firmware Bug:  TSC_DEADLINE disabled due to errate.  Please update microcode 
> to version 0xb2 (or later)
> 
> 2.035271  Could not get size 0x8000e
> 
> Anyway, just a data point.  
> 
> I tried the "troubleshooting" option.  It froze again, but I didn't write 
> down the step.  I believe it was after discovering/creating /dev/sdd
> 
> Good luck!  I'll try again once the final version comes out.  I'll monitor 
> this if someone has an idea of how to get beyond this, but it's just an early 
> hang for me.
> 
> billo

Er, that's "errata" not "errate."  Sigh.

-- 
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/d9a7e860-d23f-450a-b078-961cb3ea9ca9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Rc2 hangs on install -- Dell Inspiron i5759-8835SLV

2017-10-30 Thread billollib 
Don't know what this means, but I downloaded the new 4.0 RC2, put it on a flash 
drive, and tried to install it on my new Dell laptop.  It froze early on, with 
the messages:


Firmware Bug:  TSC_DEADLINE disabled due to errate.  Please update microcode to 
version 0xb2 (or later)

2.035271  Could not get size 0x8000e

Anyway, just a data point.  

I tried the "troubleshooting" option.  It froze again, but I didn't write down 
the step.  I believe it was after discovering/creating /dev/sdd

Good luck!  I'll try again once the final version comes out.  I'll monitor this 
if someone has an idea of how to get beyond this, but it's just an early hang 
for me.

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/7c8ea9be-ad7b-4f08-919d-c866573b4554%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] How to Setup Wireless

2017-10-30 Thread donoban 
On 10/30/2017 03:29 PM, donoban wrote:
> On 10/30/2017 12:53 AM, Ray Joseph wrote:
>> How do I enter my password?  In Debian9, I installed wpa_supplicant to 
>> include a key in network/interfaces.  Should this same method be used for 
>> sys-net?
>>
>> Where would I find this type of information.  Searching the Qubes-OS doc, I 
>> only found one reference to wireless and that was how to unload and load the 
>> wirel drivers.
>>
>> BTW, I had cloned sys-net vm to experiment.  But it would not start.  Andrew 
>> pointed to developer docs where it was stated that a vm that would use a 
>> device already in use will not start.
>> https://github.com/QubesOS/qubes-issues/issues?q=is%3Aopen+is%3Aissue+label%3A%22C%3A+doc%22
>>  
>> Just for the record, since I will probably forget that.
>>
>> Thanks,
>> Ray
>>
> 
> Hi,
> 
> Did you check if your wireless card is attached to your sys-net? Try
> running "sudo lspci" on sys-net and look something like:
> 
> 00:01.0 Network controller: Intel Corporation Wireless 7265 (rev 61)
> 
> If you don't see it try to attach it using the Qubes VM Manager (on
> version 3.2).
> 
> If the device is right, check your dmesg log (running "sudo dmesg") on
> sys-net and check if you are missing some proprietary firmware or it
> complains about another problem.
> 

Sorry, I didn't read your other mail. It seems that your card is
properly loaded.

What do you see when you click on network manager icon?
Does "iwlist scan" give some results?

-- 
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/e4a23ef4-8da1-de07-0317-d09dc8847861%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] Re: really no support

2017-10-30 Thread Desobediente 
I don't use Qubes 4, I wasn't even aware of that option. The page I
mentioned should be updated in the 4.x docs


-- 
iuri.neocities.org

-- 
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/CAF0bz4RHXzDcfiQVZ6Ygim%3DDrOw5R%2B-M-D-emnY_VSy1dvwpUA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: really no support

2017-10-30 Thread Foppe de Haan 
On Monday, October 30, 2017 at 9:43:53 PM UTC+1, Outback Dingo wrote:
> seriously still seems there is very little support ive sent multiple
> emails to the list and received no response, so let me ask again ?
> 
> how do i enlarge a vm file system with 4.0RC2
> basically my personal vm is out of space..

why not use the GUI? Every VM's menu has an entry called 'VM settings' (can 
also be called via terminal -> qubes-vm-settings VMNAME), from which you can 
increase the size of the private image.

-- 
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/291529e1-9785-4620-9b18-aee0734cc584%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] really no support

2017-10-30 Thread Desobediente 
Two considerations:

1 - The size is the target size - total size you want - not how much more
size you want to add. The example I gave would resize the AppVM to 105GB

2 - I'm a Qubes OS user, I'm not from the support team, nor I believe there
is such a thing in this mailing list, or at all. This is what is called a
open source community.

-- 
iuri.neocities.org

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

Re: [qubes-users] really no support

2017-10-30 Thread Desobediente 
https://www.qubes-os.org/doc/resize-disk-image/

on dom0 terminal: qvm-grow-private personal 104857MB

-- 
iuri.neocities.org

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

AW: Re: AW: [qubes-users] Reinstalled Qubes 3.2 -> /grub2/i386-pc/normal.mod not found

2017-10-30 Thread '[799]' via qubes-users 
Hello,

> Try repeating the Qubes install but when you
> get to the custom partitioning step, make sure
> to specify the appropriate partitions for boot
> and /. You will probably want to re-enable the
> boot flag on your hda1 partition as well

Thank you for the feedback, I have meanwhile installed a fresh installation of 
Fedora 26 and could boot up fine, I reinstalled Qubes 3.2 afterwards and got 
the same result.

Can't boot, tried to setup the partitions manually and made sure that the Boot 
partition is installed correctly.
I also set the Boot flag to the first partition.
It doesn't matter ... Can't boot.
Totally annoyed that I tried Qubes 4 which can't boot any VMs and that I can't 
go back to Qubes 3.2 without deleting all partitions including my windows setup.

I think I'll try to reboot into windows when Fedora is installed, make a backup 
of my windows partition and then reinstall Qubes from scratch.
Have invested so much time already in this Qubes upgrade/downgrade topic that I 
am done for the year.

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

[qubes-users] HCL - Lenovo G580 20150

2017-10-30 Thread tq3otj9qer0o9uq34toighwfglk 
Model:  Lenovo G580 20150 (Intel i7-3612QM, 2.10GHz, 3rd Gen.)
BIOS:   5ECN96WW(V9.01)
HVM:YES - Intel VT-x
IOMMU:  NO
SLAT:   YES - Intel VT-x
TPM:UNKNOWN
Qubes:  R3.2
Kernel: 4.9.45-21
Remark: CPU upgraded to i7-3612QM. NOT WORKING: port for SD card;
touch-pad "hotkeys". UNKNOWN/UNTESTED: camera; microphone. WORKING: Fn
keys; audio; everything else not listed as not working or
unknown/untested.
Credit: PG

-- 
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/bded6e4197f7f2b5ff199487392dc68c%40riseup.net.
For more options, visit https://groups.google.com/d/optout.
---
layout:
  'hcl'
type:
  'notebook'
hvm:
  'yes'
iommu:
  'no'
slat:
  'yes'
tpm:
  'unknown'
remap:
  'no'
brand: |
  LENOVO
model: |
  20150
bios: |
  5ECN96WW(V9.01)
cpu: |
  Intel(R) Core(TM) i7-3612QM CPU @ 2.10GHz
cpu-short: |
  FIXME
chipset: |
  Intel Corporation 3rd Gen Core processor DRAM Controller [8086:0154] (rev 09)
chipset-short: |
  FIXME
gpu: |
  Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
gpu-short: |
  FIXME
network: |
  Qualcomm Atheros AR8162 Fast Ethernet (rev 10)
  Qualcomm Atheros AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
memory: |
  16252
scsi: |
  WDC WD10JPVX-16J Rev: 1A02
  SanDisk SD8SB8U5 Rev: 
usb: |
  3
versions:

- works:
'FIXME:yes|no|partial'
  qubes: |
R3.2
  xen: |
4.6.6
  kernel: |
4.9.45-21
  remark: |
FIXME
  credit: |
FIXAUTHOR
  link: |
FIXLINK

---

[qubes-users] really no support

2017-10-30 Thread Outback Dingo 
seriously still seems there is very little support ive sent multiple
emails to the list and received no response, so let me ask again ?

how do i enlarge a vm file system with 4.0RC2
basically my personal vm is out of 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/CAKYr3zyfe7A%2BST3GwvFY5njKEuhf80HksCnCD-268fxLuRm0OQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] How to Setup Wireless

2017-10-30 Thread donoban 
On 10/30/2017 12:53 AM, Ray Joseph wrote:
> How do I enter my password?  In Debian9, I installed wpa_supplicant to 
> include a key in network/interfaces.  Should this same method be used for 
> sys-net?
> 
> Where would I find this type of information.  Searching the Qubes-OS doc, I 
> only found one reference to wireless and that was how to unload and load the 
> wirel drivers.
> 
> BTW, I had cloned sys-net vm to experiment.  But it would not start.  Andrew 
> pointed to developer docs where it was stated that a vm that would use a 
> device already in use will not start.
> https://github.com/QubesOS/qubes-issues/issues?q=is%3Aopen+is%3Aissue+label%3A%22C%3A+doc%22
>  
> Just for the record, since I will probably forget that.
> 
> Thanks,
> Ray
> 

Hi,

Did you check if your wireless card is attached to your sys-net? Try
running "sudo lspci" on sys-net and look something like:

00:01.0 Network controller: Intel Corporation Wireless 7265 (rev 61)

If you don't see it try to attach it using the Qubes VM Manager (on
version 3.2).

If the device is right, check your dmesg log (running "sudo dmesg") on
sys-net and check if you are missing some proprietary firmware or it
complains about another problem.

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/540e845c-b742-7246-4ac9-0d3dce5edeea%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

Re: AW: [qubes-users] Reinstalled Qubes 3.2 -> /grub2/i386-pc/normal.mod not found

2017-10-30 Thread awokd 
On Mon, October 30, 2017 18:42, '[799]' via qubes-users wrote:
> Additional information:
> I found out that Qubes didn't boot into /dev/sda3 but in /dev/sda5 which
> can't be started as this is not primary partition.
> See also my attached screenshot.
>
> I have mounted both partition with a live Linux and copied all files from
> /dev/sda5 to /dev/sda3.
> I have also edited in /dev/sda3 grub2/grub.cfg and edited all entries
> which said msdos5 and changed it to msdos3.
> Not sure if I need to changes some more lines and what to do afterwards.
>
> As far as I know there are also references which are referenced to with a
> UUID (some weirds long numbers/characters) - do I need to change them
> also?
>
> Also do I need to run a specific Grub command to apply the manually
> modified grub.cfg?
>
> I tried to boot up, but run into the same error.
> How can I reinstalled Qubes 3.2 and force it to use dev/sda3 as boot not a
> logical partition?
>
> [799]
>
> Gesendet von ProtonMail mobile
>
>  Original-Nachricht 
> An 30. Okt. 2017, 19:27, '[799]' via qubes-users schrieb:
>
>> Hello,
>>
>> After Qubes 4 wasn't working for me I reinstalled Qubes 3.2 but on the
>> first boot I get the following error message:
>>
>> error: file '/grub2/i386-pc/normal.mod' not found.
>> Entering rescue mode...
>>
>> I had 4 partitions before:
>>
>> /dev/hda1 = windows boot
>> /dev/hda1 = windows 10
>> /dev/hda3 = Qubes boot
>> /dev/hda4 = logical partition
>> /dev/hda5 = Qubes LUKS partition
>>
>> I tried to install Qubes a second time but iI get the same Error
>> message.
>>
>> I booted with a gparted Live disk and changed to boot flag from
>> /dev/hda1 to /dev/hda3 still the same problem.
>>
>> Any idea where to go from here?
>>
>> [799]
>>

Try repeating the Qubes install but when you get to the custom
partitioning step, make sure to specify the appropriate partitions for
boot and /.
You will probably want to re-enable the boot flag on your hda1 partition
as well.


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

AW: [qubes-users] Re: Qubes 4.0-rc2 :: VMs fail to start

2017-10-30 Thread '[799]' via qubes-users 
Hello Rob,

>> So what is the solution ? Every reboot I am
>> struggle to Start the vm’s

As I haven't seen any good solution for this yet, I recommend going back to 
Qubes 3.2 until 4.0 has been updated to fix this or until we know what is 
causing the problems (hardware?).

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

AW: [qubes-users] Reinstalled Qubes 3.2 -> /grub2/i386-pc/normal.mod not found

2017-10-30 Thread '[799]' via qubes-users 
Additional information:
I found out that Qubes didn't boot into /dev/sda3 but in /dev/sda5 which can't 
be started as this is not primary partition.
See also my attached screenshot.

I have mounted both partition with a live Linux and copied all files from 
/dev/sda5 to /dev/sda3.
I have also edited in /dev/sda3 grub2/grub.cfg and edited all entries which 
said msdos5 and changed it to msdos3.
Not sure if I need to changes some more lines and what to do afterwards.

As far as I know there are also references which are referenced to with a UUID 
(some weirds long numbers/characters) - do I need to change them also?

Also do I need to run a specific Grub command to apply the manually modified 
grub.cfg?

I tried to boot up, but run into the same error.
How can I reinstalled Qubes 3.2 and force it to use dev/sda3 as boot not a 
logical partition?

[799]

Gesendet von ProtonMail mobile

 Original-Nachricht 
An 30. Okt. 2017, 19:27, '[799]' via qubes-users schrieb:

> Hello,
>
> After Qubes 4 wasn't working for me I reinstalled Qubes 3.2 but on the first 
> boot I get the following error message:
>
> error: file '/grub2/i386-pc/normal.mod' not found.
> Entering rescue mode...
>
> I had 4 partitions before:
>
> /dev/hda1 = windows boot
> /dev/hda1 = windows 10
> /dev/hda3 = Qubes boot
> /dev/hda4 = logical partition
> /dev/hda5 = Qubes LUKS partition
>
> I tried to install Qubes a second time but iI get the same Error message.
>
> I booted with a gparted Live disk and changed to boot flag from /dev/hda1 to 
> /dev/hda3 still the same problem.
>
> Any idea where to go from here?
>
> [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/_3tyghg4Vw7vQiie4gA8Cs_QidAzs5OPKo4fMNymrggMbS58D02Y_ebWic8ohUb1xEDvHOlVckWi-mwiflRNVVWcyJJ6_2Zndo2sJzJ-vPE%3D%40protonmail.com](https://groups.google.com/d/msgid/qubes-users/_3tyghg4Vw7vQiie4gA8Cs_QidAzs5OPKo4fMNymrggMbS58D02Y_ebWic8ohUb1xEDvHOlVckWi-mwiflRNVVWcyJJ6_2Zndo2sJzJ-vPE%3D%40protonmail.com?utm_medium=email_source=footer).
> 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/9Z-_5gdft3mPG077MWS4gN1oJ_j6IVye-zYcny__ZVUlpSfTliMOgDYjm-dAokXO6-g7BsNoVxwMaNZLOQk_AKEseMFZL3vbP627l2dg43s%3D%40protonmail.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Reinstalled Qubes 3.2 -> /grub2/i386-pc/normal.mod not found

2017-10-30 Thread '[799]' via qubes-users 
Hello,

After Qubes 4 wasn't working for me I reinstalled Qubes 3.2 but on the first 
boot I get the following error message:

error: file '/grub2/i386-pc/normal.mod' not found.
Entering rescue mode...

I had 4 partitions before:

/dev/hda1 = windows boot
/dev/hda1 = windows 10
/dev/hda3 = Qubes boot
/dev/hda4 = logical partition
/dev/hda5 = Qubes LUKS partition

I tried to install Qubes a second time but iI get the same Error message.

I booted with a gparted Live disk and changed to boot flag from /dev/hda1 to 
/dev/hda3 still the same problem.

Any idea where to go from here?

[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/_3tyghg4Vw7vQiie4gA8Cs_QidAzs5OPKo4fMNymrggMbS58D02Y_ebWic8ohUb1xEDvHOlVckWi-mwiflRNVVWcyJJ6_2Zndo2sJzJ-vPE%3D%40protonmail.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Qubes 4.0-rc2 :: VMs fail to start

2017-10-30 Thread Roy Bernat 
And now the sys firewall don’t start anymore .  Someone 

Hel

-- 
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/e0f6f2dc-c470-4ceb-be7d-fd4156f6bcd6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Qubes 4.0-rc2 :: VMs fail to start

2017-10-30 Thread Roy Bernat 
So what is the solution ? Every reboot I am struggle to 
Start the vm’s 

-- 
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/9c5485d4-bbde-4fc4-936a-ad046ff5fe44%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Qubes 4.0rc2 install on corebooted Lenovo G505s (AMD)

2017-10-30 Thread awokd 
On Thu, October 26, 2017 12:37, awokd wrote:
> On Wed, October 25, 2017 20:32, awokd wrote:
>> Few issues on this attempt am hoping someone might have some insight
>> into.
>>
>> 1) Installer warns "interrupt remapping" is not supported.
>> qubes-hcl-report shows IOMMU as enabled but "Remapping" is not. What
>> exactly are they looking for?
>>
>> 2) Install completes and reboots successfully after that but it only
>> gets
>> part way through the first default template installation (whonix-gw)
>> then
>> hard locks- no mouse or keyboard response. Is there a way to force these
>> to install in compatible mode or something so I can work on fixing them
>> later?
>>
>> 3) I can choose Do not configure anything and get logged in and to a
>> terminal window, but without any templates or VMs am pretty lost on how
>> to
>> setup from scratch. qubes-template-fedora-25.noarch is listed in dnf but
>> when I try to create an AppVM there's nothing in the template dropdown.
>>
>> When I boot debian stretch on the same machine, I see AMD-Vi enabling
>> interrupt remapping. xl dmesg under 4.0 shows (Xen) enabling interrupt
>> remapping. Qubes 3.2 worked fine on this too.
>>
>> Suggestions welcomed!
>
> 1) I found https://github.com/QubesOS/qubes-issues/issues/3208 which seems
> to address this case and see "(XEN) Interrupt remapping enabled" [with
> lowercase "r"] in my xl dmesg output too.
>
> 2) This might be related but I'm having trouble finding if this patch has
> made it into the version of Xen Qubes uses.
> http://xen.1045712.n5.nabble.com/Xen-4-6-0-Dom0-freezes-at-creation-of-HVM-domain-with-activated-IOMMU-td5731709.html
>
> 3) I see what seem to be partially installed templates under
> /var/lib/qubes/vm-templates but fedora-25 for example has 4.5 1GB
> root.img.part.0? files and no root.img.

Any suggestions where to begin troubleshooting 2 or 3? Is there a way to
repeat the initial template setup step (or any built in template
deployment) from the command line with logging enabled, for example?
I've used 3.2 since it shipped but have exhausted the search engines on
this one and am facing a blank wall with no toeholds.

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

[qubes-users] Re: Clearly expose --mem option in HVM docs

2017-10-30 Thread Ryan Tate 
By the way, it looks like this was suggested previously, see number 3 in the 
ordered list under “Steps to reproduce” here:

https://github.com/QubesOS/qubes-issues/issues/3089

-- 
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/C8FA8A2C-30EE-42E1-9F3C-FC6AD212C913%40ryantate.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Message signed with OpenPGP

Re: [qubes-users] Why is there no qubes manager in V4.0?

2017-10-30 Thread David Hobach 

On 10/30/2017 12:40 AM, Ray Joseph wrote:

On Sunday, October 29, 2017 at 1:52:53 PM UTC-5, David Hobach wrote:

On 10/29/2017 03:36 PM, Sergio da Matta wrote:

Dear David, Thank you for your information. I did not know conky. I liked
it but I did not find the repo. Did you installed on dom0?


Yes, sudo qubes-dom0-update conky does it.
I attached my config for your convenience.


P.S.: Just found out about xentop yesterday thanks to a guy mentioning 
it on github. Basically it displays CPU usage etc. for your VMs.


This line should get you going with that in conky:
-- apparently xentop doesn't get the CPU % in the first run, so we do two
${execp xentop -f -b -i2 -d0 | tail -n+2 | sed -r -n '/NAME/,$ p' |  sed 
-r -n 's/^\s*([^ ]+)\s+([^ ]+)\s+([^ ]+)\s+([^ ]+)\s+([^ ]+)\s+([^ 
]+)\s+([^ ]+)\s+([^ ]+)\s+([^ ]+)\s+.*$/\1${goto 140}\4${goto 
220}\9${goto 300}\6${goto 400}\8/p'}


Happy to hear that you guys find it useful as well. :-)

--
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/0124b36b-711b-48df-bb6d-ab0b9ed45a21%40hackingthe.net.
For more options, visit https://groups.google.com/d/optout.


smime.p7s
Description: S/MIME Cryptographic Signature

Re: [qubes-users] Re: Properly setup a qube dns cache server

2017-10-30 Thread nicholas roveda 
I'm already in the process of implementing this feauture (method A) in R4.0.

> dom0 doesn't store any DNS settings. Each VM forwards packets to the
> next upstream VM and the DNS decision is made at your netvm resolv.conf.
> Dynamic firewalls (iptables in 3.2, netfilter or so in 4.0) managed by
> the dom0 qvm-firewall in your proxsy & firewall VMs ensure only allowed
> traffic is going through. DNS uses dnat rules...
>

I'm aware of the Qubes networking mechanisms.


What I'm trying to achieve is the following:

1) New fields in 'Qubes Global Settings' menu, under 'System defaults' (Dom0) 
that let the user choose the default primary and secondary DNS (now 
'10.139.1.1' and '10.139.1.2').

How this is will be implemented?
Dom0 will inform the first NetVM backends ('sys-firewall', 'sys-net' or a 
VpnVM) of the change though a rpc service and this will trigger 
`qubes-dnat-to-ns` which will procede to update the (NAT) iptables.
-> All the DNS requests destinated to '10.139.1.1' and '10.139.1.2'   DNAT   to 
the new DNS backend specified by the user <-
This method doesn't require any changes to the Templates or the AppVMs, but 
only to install a rpc service and a custom `qubes-dnat-to-ns` script in the VMs 
that provide network (ProxyVMs and NetVMs).


2) New fields in 'VM Settings' menu (Dom0) that let the user choose the primary 
and secondary DNS for each VM, if the machine has network.

How this is will be implemented?
Dom0 will inform the NetVM backend to which the VM is attached and the (NAT) 
iptables will be modified to DNAT all the DNS requests from a the specific VM 
vif interface (-i vifX.0) to the new addresses provided.
Again, no changes are required to the Templates or the AppVMs, but only to the 
VMs that provide network (ProxyVMs and NetVMs).



ISSUES:
1) I solved the first issue and I discovered how to retrieve vif names from xen 
database,

2) I still don't know how to make all VMs that provide network launch a script 
when a new vif interface came up.
As I said before, I've found the this file 
'/etc/udev/rules.d/99-qubes-network.rules' that I believed was the solution, 
but it seem not to work at all,

3) My code still rely on files, because the Qubes API and Qubesadmin API has 
confused me a lot.
I need to add:
- the attributes 'default_primary_dns' and 'default_secondary_dns' to 
'qubesadmin.app.QubesBase' and
- the properties 'primary_dns' and 'secondary_dns' to the base Class that 
represent a VM object.
I don't know if I have to modify 'Qubes' or 'Qubesadmin' and if this is enough 
for the `qubesd` calls or if it's not possible to add new properties at all.


I really need help from the developers, expecially for the point n.3.
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/38f7121d-b047-431d-b4c2-aedc2b68a9fb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Properly setup a qube dns cache server

2017-10-30 Thread nicholas roveda 
I'm already in the process of implementing this feauture (method A) in R4.0.

> dom0 doesn't store any DNS settings. Each VM forwards packets to the 
> next upstream VM and the DNS decision is made at your netvm resolv.conf. 
> Dynamic firewalls (iptables in 3.2, netfilter or so in 4.0) managed by 
> the dom0 qvm-firewall in your proxsy & firewall VMs ensure only allowed 
> traffic is going through. DNS uses dnat rules...

I'm aware of the Qubes networking mechanisms.


What I'm trying to achieve is the following:

1) New fields in 'Qubes Global Settings' menu, under 'System defaults' (Dom0) 
that let the user choose the default primary and secondary DNS (now 
'10.139.1.1' and '10.139.1.2').

How this is will be implemented?
Dom0 will inform the first NetVM backends ('sys-firewall', 'sys-net' or a 
VpnVM) of the change though a rpc service and this will trigger 
`qubes-dnat-to-ns` which will procede to update the (NAT) iptables.
-> All the DNS requests destinated to '10.139.1.1' and '10.139.1.2'   DNAT   to 
the new DNS backend specified by the user <-
This method doesn't require any changes to the Templates or the AppVMs, but 
only to install a rpc service and a custom `qubes-dnat-to-ns` script in the VMs 
that provide network (ProxyVMs and NetVMs).


2) New fields in 'VM Settings' menu (Dom0) that let the user choose the primary 
and secondary DNS for each VM, if the machine has network.

How this is will be implemented?
Dom0 will inform the NetVM backend to which the VM is attached and the (NAT) 
iptables will be modified to DNAT all the DNS requests from a the specific VM 
vif interface (-i vifX.0) to the new addresses provided.
Again, no changes are required to the Templates or the AppVMs, but only to the 
VMs that provide network (ProxyVMs and NetVMs).



ISSUES:
1) I solved the first issue and I discovered how to retrieve vif names from xen 
database,

2) I still don't know how to make all VMs that provide network launch a script 
when a new vif interface came up.
As I said before, I've found the this file 
'/etc/udev/rules.d/99-qubes-network.rules' that I believed was the solution, 
but it seem not to work at all,

3) My code still rely on files, because the Qubes API and Qubesadmin API has 
confused me a lot.
I need to add:
- the attributes 'default_primary_dns' and 'default_secondary_dns' to 
'qubesadmin.app.QubesBase' and 
- the properties 'primary_dns' and 'secondary_dns' to the base Class that 
represent a VM object.
I don't know if I have to modify 'Qubes' or 'Qubesadmin' and if this is enough 
for the `qubesd` calls or if it's not possible to add new properties at all.


I really need help from the developers, expecially for the point n.3.
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/126d08c0-9846-4c50-832f-b0636a35e973%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Clearly expose --mem option in HVM docs

2017-10-30 Thread Ryan Tate 
Right now the HVM documentation does not prominently disclose that initial 
memory/RAM may be configured on creation of the HVM domain via --mem option 
(https://www.qubes-os.org/doc/hvm/ ).

This is mentioned only in "Converting VirtualBox VM to HVM” which is way down 
the page and on a tangential topic. Under the main prominent "Creating an HVM 
domain” it is not mentioned.

Given that the default memory allocation is a very meagre 512MB, it would be 
helpful to include a mention of the --mem option in a prominent place, 
especially since Windows is a major use case for HVM, and this page is linked 
from the Qubes Windows documentation, and this allocation will be insufficient 
for the Qubes supported version of Windows (Windows 7) not to mention any 
successors.

I’d be willing to submit a patch if people think this makes sense. The project 
guidelines discuss patches for errors in the docs but it’s not clear to me if 
patches to improve the docs are also welcome. 
(https://www.qubes-os.org/doc/doc-guidelines/ 
)

-- 
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/BF82DE3E-095E-43A6-A70D-5B9F2D227331%40ryantate.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Message signed with OpenPGP

Re: [qubes-users] Installing screen-recorder in Dom0

2017-10-30 Thread corpknut 
mandag 30. oktober 2017 14.55.16 UTC+1 skrev Ilpo Järvinen følgende:
> On Mon, 30 Oct 2017, @gmail.com wrote:
> 
> >I am aware of the security risks, but I need to be able to do screen 
> > recordings of my work in Qubes OS. And as I understand it, the recorder 
> > needs to run out of Dom 0.
> > 
> > I have tried to use the following command to copy the installation files 
> > from an AppVM to Dom0:
> > 
> > qvm-run --pass-io personal '/home/user/Downloads/kazam.tar.gz' > 
> > /home/myuser/Downloads/kazam.tar.gz
> 
> cat is missing:
> 
> qvm-run --pass-io personal 'cat /home/user/Downloads/kazam.tar.gz' > ...
>  
> 
> -- 
>  i.

Ah, I must be going blind...  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/906df818-b4d1-4436-a076-254a716dc58a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Installing screen-recorder in Dom0

2017-10-30 Thread Ilpo Järvinen 
On Mon, 30 Oct 2017, corpk...@gmail.com wrote:

>I am aware of the security risks, but I need to be able to do screen 
> recordings of my work in Qubes OS. And as I understand it, the recorder needs 
> to run out of Dom 0.
> 
> I have tried to use the following command to copy the installation files from 
> an AppVM to Dom0:
> 
> qvm-run --pass-io personal '/home/user/Downloads/kazam.tar.gz' > 
> /home/myuser/Downloads/kazam.tar.gz

cat is missing:

qvm-run --pass-io personal 'cat /home/user/Downloads/kazam.tar.gz' > ...
 

-- 
 i.

-- 
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/alpine.DEB.2.20.1710301554240.3749%40whs-18.cs.helsinki.fi.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Installing screen-recorder in Dom0

2017-10-30 Thread corpknut 
Hi,

   I am aware of the security risks, but I need to be able to do screen 
recordings of my work in Qubes OS. And as I understand it, the recorder needs 
to run out of Dom 0.

I have tried to use the following command to copy the installation files from 
an AppVM to Dom0:

qvm-run --pass-io personal '/home/user/Downloads/kazam.tar.gz' > 
/home/myuser/Downloads/kazam.tar.gz

I get this error:

sh: 1: /home/user/Downloads/kazam.tar.gz: Permission Denied


I have Googled for hours, but I have not found anything that can help me with 
this problem.

Any help would be very much appreciated :)

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/395c4fe4-ac82-4b41-bcc4-6c3ac0b3b84e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: DaVinci Resolve 14 - Possible to run in a Windows VM on Qubes OS?

2017-10-30 Thread Eric 
On Sunday, October 29, 2017 at 12:38:40 PM UTC-7, lemond...@gmail.com wrote:
> I'd really like to use Qubes.  The last time I tried it was on an Ultrabook 
> and the install and setup was straightforward and painless.  However, when I 
> tried to view a YouTube video in a browser window, I noticed the video 
> playback wasn't perfectly smooth and there was NO AUDIO.
> 
> I'd like to revisit Qubes OS and see if it's feasible to use as my primary OS 
> again, but this time I'd like to know if DaVinci Resolve 14 (there are 
> Windows, Mac, and Linux versions) can be installed either to run under Linux 
> or under a Windows VM.  People have gotten Resolve 14 to install and run 
> under CentOS, Debian, Ubuntu, and other distributions.
> 
> I'd need audio to work.
> 
> If I could get youtube working with no performance or audio issues and 
> DaVinci Resolve working on Qubes, I would gladly move to it full time.

There's no hardware acceleration in any Qubes VM, so I doubt Photoshop and 
DaVinci Resolve will work. Additionally, I have no idea how this unholy mash of 
Xen/Fedora/Windows would manage color, if it would be end to end, or if you can 
even calibrate your display to get an accurate reproduction. No matter what, 
each virtual machine is essentially using the software renderer to talk to a 
fake output device, so performance is going to be very very limited and likely 
very poor.

There's currently no way to do PCI passthrough of graphics card to fix this, 
either, but that is an architectural and security decision and less of a 
software quality issue.

Short answer: I doubt that it works now, and I also doubt that it will work any 
time soon.

-- 
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/2fd70305-67c9-4c64-9491-47d4d4916e3e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.