[qubes-users] One PCI slot does not work in Qubes

2018-11-27 Thread s . w . i . m . on . qubes 
Ok so I have tried all of my network cards individually and the only ones that 
work are the GA-H110MA onboard motherboard Realtek Nic. And a StarTech 
ST2000PEXPSE, which is a PoE card with two RTL8111E Nics and a Ti XIO3130 pcie 
1.1 control chip.

Not working is
syba SY-PEX24028 with two RTL8111G nics and a Pericon Semi PI7C9X2G 304SLAFDE 
pci 2.1 chip.

Unknown brand with two intel 82576-2T nics. Unknown pci controller, the heat 
sink was stuck on there good. Mac addy references Shenzhen Lianrui Electronics 
so, you know, quality.

All devices work in windows and freebsd11. In Qubes the non working ones cry 
about pci permissive needing to be set, if set(or not) they will show up in 
qvm-pci as good. And will passthrough apprantly ok, but will not transmit data 
over the pci bus. Resulting in anything connected to them not recieving an IP 
addy(causing them to self assign one) and generally not working.

I wish I had more cards to test to isolate if its the pci controller or the nic 
chip thats at issue.

-- 
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/6440c1d8-fbaf-4f64-a6a3-19adad99e1cc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Recovering TemplateVM from boot failure caused by incorrect /etc/fstab

2018-11-27 Thread 'Fabio' via qubes-users 
Hi Ivan,

Thanks a lot for the clarification! That was indeed it, I was trying to mount 
the whole device.

I was able to fix the `/etc/fstab` and get my VM back up! (celebrations!)

Really appreciate all your help with this!


Fabio


‐‐‐ Original Message ‐‐‐
On Tuesday, November 27, 2018 6:54 AM, Ivan Mitev  wrote:

> Hi Fabio,
>
> On 11/27/18 2:33 AM, 'Fabio' via qubes-users wrote:
>
> > Thanks for the reply Ivan.
> > I was able to mount `dom0:/dev/qubes_dom0/vm-...-private vmname` 
> > successfully, however when trying to mount 
> > `dom0:/dev/qubes_dom0/vm-...-root vmname`, I still get the `wrong fs type, 
> > bad option, bad superblock...` error.
>
> You're probably mounting the wrong partition or you are trying to mount
> the whole disk.
>
> The following steps work for me:
>
> in dom0:
>
> sudo losetup /dev/loop3 /dev/qubes_dom0/vm-fedora-26-medium-bkp-root
>
> then, attach the device to some VM like you did. In that VM run `sudo dmesg` 
> and you should see a line like
>
> [timestamp_here] xvdi: xvdi1 xvdi2 xvdi3
>
> Note: it could also be xvdj, xvdk, ... if you have other devices
> attached to the VM.
>
> There are thus 3 partitions in the device/volume you attached. You can
> see what they are with `sudo sfdisk -l /dev/xvdi`:
>
> Device Start End Sectors Size Type
> /dev/xvdi1 2048 411647 409600 200M EFI System
> /dev/xvdi2 411648 415743 4096 2M BIOS boot
> /dev/xvdi3 415744 20971486 20555743 9.8G Linux filesystem
>
> Trying to mount the first two partitions will return a "bad superblock"
> error because there isn't any recognised fs on those. Trying to mount
> the whole device (/dev/xvdi) will fail for the same reason.
>
> Mount the third partition:
>
> sudo mount /dev/xvdi3 /mnt
>
> And you should be able to fix fstab there:
>
> ll /mnt/etc/fstab
>
> -rw-r--r-- 1 root root 851 May 11 2018 /mnt/etc/fstab
>
> Then, reverse the instructions: sudo unmount /mnt, detach the device in
> the tray and remove the loopback device in dom0 (losetup -d /dev/loop3).
>
> Hope this helps...
>
> > I can confirm that I get this same error message when trying to mount any 
> > `--root` suffixed volume nested under `/dev/qubes_dom0`.
> > To confirm, I am running Qubes v4.0.
> > Any reason why the `--root` volumes in particular aren't mounting? Those 
> > are where `/etc/fstab` would be located, right?
> > Thanks again for your help!
> > Fabio
> > ‐‐‐ Original Message ‐‐‐
> > On Monday, November 26, 2018 12:11 PM, Ivan Mitev i...@maa.bz wrote:
> >
> > > On 11/26/18 1:46 PM, 'Fabio' via qubes-users wrote:
> > >
> > > > I made an accidental edit to /etc/fstab which is causing my TemplateVM 
> > > > to timeout on boot with error Cannot connect to qrexec agent for 60 
> > > > seconds
> > > > Is there a way to edit a particular VM's etc/fstab without booting it 
> > > > up? Can I perhaps mount it's root filesystem?
> > >
> > > for R4:
> > > https://groups.google.com/forum/#!searchin/qubes-users/losetup|sort:date/qubes-users/rWRNIt0NOc4/VaFHp42rBgAJ
> > > Alternatively the following command will configure a loopback device
> > > automatically:
> > > qvm-start --hdisk dom0:/dev/qubes_dom0/vm-...-root vmname
> > > R3.2 uses files by default instead of LVM volumes, I can't remember
> > > where they were located (/var/lib/qubes/ or something like that) but the
> > > procedure should be more or less the same.
> > >
> > > > Attempted solutions
> > > >
> > > > 1.  I've tried adding init=/bin/bash to the kernel opts, starting the 
> > > > templateVM and then running sudo xl console TEMPLATE_NAME from Dom0 but 
> > > > I did not reach a command-prompt before fstab was read and executed.
> > > >
> > > > 2.  I tried mounting the root filesystem for the TemplateVM from Dom0 
> > > > with: sudo mount /dev/qubes_dom0/vm-fedora-26-root mnt but got error 
> > > > wrong fs type, bad option, bad superblock...
> > > >
> > >
> > > It's not recommended to access VMs' files in dom0. Once you set up a
> > > loopback device and the volume pops up in the device tray, attach it to
> > > a trusted VM and fix fstab there.
> > >
> > > 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/a303a7f7-6b8f-5ff3-7e46-13154b8edda4%40maa.bz.
> > > 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 
>

[qubes-users] Re: Screen recorder for Qubes..?

2018-11-27 Thread Fabian 
Hello everyone,
I know this topic is a bit older, but I want to give a small recommendation how 
to record the "screen" of a single VM.
I tried a lot of applications in the past to record a single window or VM 
output, but none of them worked at all.
A few weeks ago I found "Open Broadcaster Software", which is mainly used to 
live stream stuff, but it also brings a good Screen-Recording-Function, which 
surprisingly works well inside of a VM, both on Debian and Fedora.
It's completely Open Source and uses FFMPEG to handle the encoding.
https://obsproject.com/de/download

It's included in the default Debian Stable repository, so just "sudo apt 
install obs-studio" installs it.
On Fedora you need to enable the rpmfusion-free repository and then just "sudo 
dnf install obs-studio --enablerepo=rpmfusion-free"

Of course you could also use it in dom0 if you enable rpmfusion in dom0, the 
risks of that are already mentioned above.

-- 
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/7e1637dd-e52c-46db-b290-6c8ad565544f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Whonix 14 installation problem...using 4.0?

2018-11-27 Thread William Fisher 
i Just installed Qubes 4.0 without Whonix/Tor.  Now I’d like to go ahead and 
install Whonix14 Anon and Tor so I have a clean install. How can I go about 
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/c97dd4d5-0125-4942-9bb2-76cbdb36055d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Whonix GW & WS upgrade failed (Help)

2018-11-27 Thread Fidel Ramos 
‐‐‐ Original Message ‐‐‐
On Tuesday, November 27, 2018 11:08 AM,  wrote:

> I press upgrade at Whonix GW & WS and get this message, see Screnshoot, what 
> should I do? thank you in advance ;)
>
> https://ibb.co/XbCsJWQ

Did you try any of the things proposed by the error message?

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

[qubes-users] VPN-tunnels officially in Qubes. When?

2018-11-27 Thread qubes-fan 
hi all, is there any plan to add the VPN tunnels officially into the Qubes? 

https://github.com/tasket/Qubes-vpn-support 


Would be nice if less-tech people could benefit from the default setup, if 
working.

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/LSL5UzG--3-1%40tutanota.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] One PCI slot does not work in Qubes

2018-11-27 Thread s . w . i . m . on . qubes 
Dmseg had errors for the nics which indicated setting pci permissive mode might 
help.

pciback :0x:00.0: Driver tried to write to a read-only configuration...

Setting permissive mode got rid of the errors but did not actually fix the main 
issue. 

Whenever I attach a computer to these nics they are not getting an ip address 
from dhcp and cannot communicate upstream. Despite this working fine with one 
network card, and the motherboard ethernet port.

Is it possible for the one functioning card to block the pci bus for any other 
devices? I will try replacing that card too, but its a POE network card and id 
rather not have to lose 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/a03a2fbc-13a4-42a5-a6ce-5a7a3e6bf2e3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Optional: Enable AppArmor

2018-11-27 Thread qubes123456 
Could anyone help me, please ? thank you in advance ;)

-- 
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/fdb7dd60-e14d-4fc4-97da-65b3c4f82825%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Whonix GW & WS upgrade failed (Help)

2018-11-27 Thread qubes123456 
I press upgrade at Whonix GW & WS and get this message, see Screnshoot, what 
should I do? thank you in advance ;)

https://ibb.co/XbCsJWQ

-- 
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/8c69608b-127c-4cf6-9ca6-190b9eb69668%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.