Re: [qubes-users] Easiest way to redirect USB to a VM?

['awokd' via qubes-users]

Guerlan:

I installed android-tools and it didn't work.

Are you sure I don't need a sys-usb VM?
If you want to try, in that same link that was posted earlier 
(https://www.qubes-os.org/doc/usb-qubes/), look for the part about how 
to create one manually. Pay close attention to how to identify a free 
USB controller. Some machines only have one, in which case it is not an 
option unless you have a PS/2 keyboard.


--
- don't top post
Mailing list etiquette:
- trim quoted reply to only relevant portions
- when possible, copy and paste text instead of screenshots

--
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/db2ec3e3-b402-7625-ab50-1f9d656b5a54%40danwin1210.me.

Re: [qubes-users] Tabs mangled when copying between AppVMs

[Andrew David Wong]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2019-10-07 2:53 AM, tetrahedra via qubes-users wrote:
> When copying from AppVM to AppVM, tabs and/or spaces often get
> mangled (additional tabs/spaces inserted).
>
> For example, if I have a block of text in one AppVM that looks
> like:
>
> def my_function(): msg = "foo" othermsg = "bar" print(msg +
> othermsg)
>
>
> When I Ctrl-C (or Ctrl-Insert) and Ctrl-Shift-C this block of
> text, then Ctrl-Shift-V and Shift-Insert it into an editor in
> another VM, it sometimes comes out looking like:
>
> def my_function(): msg = "foo" othermsg = "bar" print(msg +
> othermsg)
>
> The issue does not crop up every time. Unfortunately, I haven't
> been able to figure out a pattern or logic for when it occurs vs
> when it does not occur.
>
> Any suggestions for how to stop this happening?
>

Are you, by any chance, copying into Vi/Vim? That sort of thing happens
when you have "smart indentation" (or similar) enabled in Vim.

- -- 
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAl2dN0kACgkQ203TvDlQ
MDAKJw//V+f0frDGnGwgzqP/WqyIfSszGEN4gX4i5qGBbc9QJfXsWFmJahZttMAq
dariltki6uSwtGepCp6qjMYLTephaZKzLwc3aue0VJupfuDEQw3oM0GNEv9CbqOy
BX515smS5SZISUVHTXnQ18fv3GEVHeXEAWuQ1P3CZgwzUwjaaH4iTD1PI5VdVyhW
Z5J4puy4fuA9LfcCUkg2TPerPOwWc+d/JiBBecWzLFl/HV1EgIiCqumMpYkDigtD
lV+VYJS50glxjfJ5fhlqsd8zHIKTSsYviMOKkijyZ0oVJhCQvI+Ci3p0lsMkNlYl
C6FLOTZSH9Gnh4KjAdZBNcz84roqSfMMPk3FdFs0u6dy57H6FhQb7uLZ8ZzeD6st
KklDHtx9uhleqCpLwY7q2eAKqjjYjmNyDKIda9VJZ7dSrX1EVtHZmvVRB4nHA/X6
G0g6VGjb5onCJweNcArEcsioZmMtOw4vK+p7ck9/8tEd10qAzGALO5SV+uub6gjI
b9c8Io0GXNYOOmZ4PoO/la24Y+mnd2/PnIntq9VdldS4KmWUcjPrKTO0TcEnZv3A
trOnKwiU/9IyeRmqgf4ovFdJ6czKG1BysqEtTRBSU/DBwamerpjBBYhU1SBZzw65
suXGCwDXJvAYVlPHB5Swlggpm3ebWis6FpADo8+lJRs454Q/Z10=
=NQjv
-END PGP SIGNATURE-

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/bceb8e6f-95fa-6bab-081a-e6ff8277d0f1%40qubes-os.org.

Re: [qubes-users] Easiest way to redirect USB to a VM?

[Guerlan]

I installed android-tools and it didn't work.

Are you sure I don't need a sys-usb VM?

On Tuesday, October 8, 2019 at 6:44:22 PM UTC-3, steve.coleman wrote:
>
> On 2019-10-08 17:35, Guerlan wrote: 
> > On Ubuntu it always worked out of th ebox,I only had to choose the rigth 
> > USB option in Android. 
> > 
> > How can I install things in dom0? Is it posible? 
>
> To search what is available: 
>
> dom0$ sudo qubes-dom0-update --action=search  
>
> then: 
>
> dom0$ sudo qubes-dom0-update  
>
> Be careful not to install any dangerous software that you don't actually 
> need in dom0. Its best to leave that to the VM's that will be mounting 
> the phone USB. 
>
>
> > I tried all USB modes on 2 phones and I get nothing on both qvm-usb and 
> > qvm-block 
> > 
> > I also plugged an Yubikey and it appears in lsusb (the phones appear 
> > too) but they don't appear in the devices tray icon. 
> > 
> > On Tuesday, October 8, 2019 at 6:14:39 PM UTC-3, steve.coleman wrote: 
> > 
> > On 2019-10-08 16:44, Guerlan wrote: 
> >  > I tried that too, but when I run qvm-usb I get an empty list of 
> usb 
> >  > devices. Running lsusb obviously gives me a lot of usb devices 
> (on 
> >  > dom0). So I thought sys-usb is needed for USB to work. What am I 
> > doing 
> >  > wrong? 
> > 
> > I think the trick is to: 
> > 
> > 1) Make sure your Android device presents itself as a USB drive, so 
> > that 
> > you can copy/move files between the device and the VM. 
> > 
> > Q: Have you used the phone with any other Linux/Windows machine such 
> > that you know it is configured to present the USB drive interface? 
> I'm 
> > pretty sure you need to configure that on the phone first. 
> > 
> > 2) Then Dom0 needs to have the proper tools/drivers to see that USB 
> > device as a drive, so that it can be passed/attached via the command 
> > line tools or the toolbar applet. I know that fedora-25 has a 
> > "android-tools" package that might be needed for this. 
> > 
> > Once you can see it in dom0 using qvm-usb/qvm-block you should be 
> able 
> > to pass it through to your VM with the toolbar applet or qvm-block 
> > attach. 
> > 
> > Its been a long while since I have done this, and I have not yet 
> > done it 
> > with either Qubes4.x nor my current Android phone, so your mileage 
> may 
> > vary greatly. 
> > 
> > 
> > 
> > 
> > -- 
> > 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...@googlegroups.com  
> > . 
> > To view this discussion on the web visit 
> > 
> https://groups.google.com/d/msgid/qubes-users/cbbed5fa-400a-44e6-8efc-832a5157af76%40googlegroups.com
>  
> > <
> https://groups.google.com/d/msgid/qubes-users/cbbed5fa-400a-44e6-8efc-832a5157af76%40googlegroups.com?utm_medium=email_source=footer>.
>  
>
>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/b21af873-2217-4550-9c16-d88b89ee0eea%40googlegroups.com.

Re: [qubes-users] laptop screen wont appear after closing lid

[Claudia]

Guerlan:

Whenever I close the lid of the notebook, when I open again, I see the
keyboard light lightning up but the screen never lights and I have to
reboot.

Is there a fix for it?



It sounds like suspend/resume isn't working correctly on your laptop 
under Qubes. Does the same thing happen when you click suspend from the 
logout menu?


As a workaround, open the Xfce Power Manager (Start -> System Tools -> 
Power Manager) and change the lid switch to "do nothing." This way it 
won't go into suspend when you close the lid, but it'll at least turn 
off the screen.


Something else to try: download Fedora 30 and boot into a live CD/USB, 
and try suspend/resume (by closing the lid) from there, and see if the 
screen comes back on. If it does, it probably means Qubes' dom0 (F25) is 
too old for your hardware.


Also it would help to know the make and model of your laptop. Ideally, 
you can submit an HCL report: https://www.qubes-os.org/doc/hcl/


--
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/e4ae5aaf-275b-5c5e-b384-bbcd24e231b1%40vfemail.net.

Re: [qubes-users] Re: persistance of change by iptables for portforwarding

[Chris Laprise]

On 10/6/19 5:47 PM, lik...@gmx.de wrote:

On 2019-10-05 16:42, Chris Laprise wrote:

On 10/5/19 10:35 AM, liked2-mmb7mzph...@public.gmane.org wrote:

Hi!

I found a script to ease the setup of port forwarding, which uses 
iptables:

https://gist.github.com/Joeviocoe/6c4dc0c283f6d6c5b1a3f5af8793292b

Can anyone assess how persistant these changes are? I've noticed that 
internal qube IPs as well IPs in my private networks change, so that 
I'm not sure whether the changes applied by the script above will

- survive a reboot of qubes?
- survive a reboot of netvm?
- survive a rebbot of the AppVm which is used as routing target?

Thxs in advance! Pete.



Depending on the type of VM you probably want to modify one of the 
following:


/rw/config/qubes-ip-change-hook
/rw/config/qubes-firewall.d
/rw/config/qubes-firewall-user-script

The qubes-firewall.d is a directory where you can add multiple scripts.

See https://www.qubes-os.org/doc/config-files/



This means that the used tools in the script like
- iptables-save
- iptables

are not persistent and will be gone after reboot of qubes/AppVm/NetVm, 
right? I'd like to know whether it's necessary to clean up every time or 
whether a reboot is sufficient to clear the port forwarding.


Right... no need to clean up.

Anything done from /rw/config will be swept away when the VM shuts down. 
However, if you read the doc there is also an option to use /etc (i.e. 
if you want to add the script to the template and have all the dependent 
VMs run it).


--

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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/0d589897-408a-bf81-a775-006712a46a0a%40posteo.net.

Re: [qubes-users] Easiest way to redirect USB to a VM?

[Steve Coleman]

On 2019-10-08 17:35, Guerlan wrote:
On Ubuntu it always worked out of th ebox,I only had to choose the rigth 
USB option in Android.


How can I install things in dom0? Is it posible?


To search what is available:

   dom0$ sudo qubes-dom0-update --action=search 

then:

   dom0$ sudo qubes-dom0-update 

Be careful not to install any dangerous software that you don't actually 
need in dom0. Its best to leave that to the VM's that will be mounting 
the phone USB.



I tried all USB modes on 2 phones and I get nothing on both qvm-usb and 
qvm-block


I also plugged an Yubikey and it appears in lsusb (the phones appear 
too) but they don't appear in the devices tray icon.


On Tuesday, October 8, 2019 at 6:14:39 PM UTC-3, steve.coleman wrote:

On 2019-10-08 16:44, Guerlan wrote:
 > I tried that too, but when I run qvm-usb I get an empty list of usb
 > devices. Running lsusb obviously gives me a lot of usb devices (on
 > dom0). So I thought sys-usb is needed for USB to work. What am I
doing
 > wrong?

I think the trick is to:

1) Make sure your Android device presents itself as a USB drive, so
that
you can copy/move files between the device and the VM.

Q: Have you used the phone with any other Linux/Windows machine such
that you know it is configured to present the USB drive interface? I'm
pretty sure you need to configure that on the phone first.

2) Then Dom0 needs to have the proper tools/drivers to see that USB
device as a drive, so that it can be passed/attached via the command
line tools or the toolbar applet. I know that fedora-25 has a
"android-tools" package that might be needed for this.

Once you can see it in dom0 using qvm-usb/qvm-block you should be able
to pass it through to your VM with the toolbar applet or qvm-block
attach.

Its been a long while since I have done this, and I have not yet
done it
with either Qubes4.x nor my current Android phone, so your mileage may
vary greatly.




--
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/cbbed5fa-400a-44e6-8efc-832a5157af76%40googlegroups.com 
.


--
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/60760709-8647-d9ad-f818-4701e54a9dce%40jhuapl.edu.

Re: [qubes-users] Easiest way to redirect USB to a VM?

[Guerlan]

On Ubuntu it always worked out of th ebox,I only had to choose the rigth 
USB option in Android.

How can I install things in dom0? Is it posible?

I tried all USB modes on 2 phones and I get nothing on both qvm-usb and 
qvm-block

I also plugged an Yubikey and it appears in lsusb (the phones appear too) 
but they don't appear in the devices tray icon.

On Tuesday, October 8, 2019 at 6:14:39 PM UTC-3, steve.coleman wrote:
>
> On 2019-10-08 16:44, Guerlan wrote: 
> > I tried that too, but when I run qvm-usb I get an empty list of usb 
> > devices. Running lsusb obviously gives me a lot of usb devices (on 
> > dom0). So I thought sys-usb is needed for USB to work. What am I doing 
> > wrong? 
>
> I think the trick is to: 
>
> 1) Make sure your Android device presents itself as a USB drive, so that 
> you can copy/move files between the device and the VM. 
>
> Q: Have you used the phone with any other Linux/Windows machine such 
> that you know it is configured to present the USB drive interface? I'm 
> pretty sure you need to configure that on the phone first. 
>
> 2) Then Dom0 needs to have the proper tools/drivers to see that USB 
> device as a drive, so that it can be passed/attached via the command 
> line tools or the toolbar applet. I know that fedora-25 has a 
> "android-tools" package that might be needed for this. 
>
> Once you can see it in dom0 using qvm-usb/qvm-block you should be able 
> to pass it through to your VM with the toolbar applet or qvm-block attach. 
>
> Its been a long while since I have done this, and I have not yet done it 
> with either Qubes4.x nor my current Android phone, so your mileage may 
> vary greatly. 
>
>
>
>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/cbbed5fa-400a-44e6-8efc-832a5157af76%40googlegroups.com.

Re: [qubes-users] Qubes on Dell Vostro 5581?

[Tomáš Vondra]

On Monday, October 7, 2019 at 3:42:38 PM UTC+2, Claudia wrote:
>
> Tomáš Vondra: 
> > 
> > 
> > On Saturday, October 5, 2019 at 7:45:40 PM UTC+2, Tomáš Vondra wrote: 
> >> 
> >> On Friday, October 4, 2019 at 4:36:57 PM UTC+2, Claudia wrote: 
> >> 
> > ... 
> >>   
> >> 
> >>> There is a pre-release 4.1 iso available. 
> >>> https://openqa.qubes-os.org/tests/3021 
> >>> <
> https://www.google.com/url?q=https%3A%2F%2Fopenqa.qubes-os.org%2Ftests%2F3021=D=1=AFQjCNEtwV-7EB_Hj9-89w3F8kL7XBW3pA>
>  
>
> >>> - this is a kind of old link so 
> >>> newer builds may be available. I could not get it to install on my 
> >>> machine so I couldn't test suspend on it, but it might work for you. 
> >>> 
> >>> 
> >> Thanks for the link. I gave it a try and there seems to be some 
> >> improvement compared - the installer now works out of the box, without 
> >> having to tweak it like I had to with Qubes 4.0. Unfortunately, the 
> >> suspend/resume issue is still there, although maybe it actually gets to 
> >> sleep this time (but still does not wake up). 
> >> 
> >> I've tried looking for a newer build (the one you posted is from July, 
> so 
> >> a couple of months ol), but I haven't found anything. I've been trying 
> to 
> >> build ISO locally over the past two weeks, but I keep running into 
> issues 
> >> so I haven't been successful in that. 
> >>   
> >> 
> > 
> > OK, I've noticed there actually is a link to the latest job for that 
> > scenario, leading to https://openqa.qubes-os.org/tests/3737 (which is 
> > 2019/08/22 instead of 2019/07/01). Unfortunately the suspend behavior is 
> > the same as for the older build :-( 
> > 
> > regards 
> > 
> >   
> > 
>
> You mean out of the box? Or when dom0 is brought fully up to date? Odds 
> are slim, but updating might fix the problem. Also enabling 
> testing/unstable repos might help. 
>
>
After updating dom0. Unfortunately I'm unable to switch to testing repos 
because dnf started complaining about a missing config file for some 
reason, and I haven't managed to fix that (yet).
 

> As far as building your own iso, I'm afraid I don't know anything about 
> that, but there are plenty of people on this list who could help if you 
> start a thread about the specific problems you're having. 
>
>
Yeah, I plan to try again and I'll start a new thread here (or maybe on 
qubes-devel, that seems like a better match).
 

> In general, debugging suspend/resume is quite difficult unless you're a 
> kernel developer with a serial console. However there are a couple of 
> things you can do that might get you a step further. 
>
> First, it's helpful to know if the machine is actually going into 
> suspend. Open a few terminals and run `sha256sum /dev/urandom` and wait 
> for the fans to start running. If you hear them stop, you know it 
> suspended. If, on resume, you hear them start up again, then it could be 
> that the machine is partially resuming but just the screen is not coming 
> back on (possibly indicative of a GPU or WiFi driver problem). Playing a 
> repeating sound probably has the same effect. You can also hit caps lock 
> and num lock after resume and see if the lights change. 
>   
>
Try shutting down all VMs before suspending. I think the command is 
> `qvm-shutdown --all --force --wait` or something like that. Make sure 
> they're all stopped (e.g., `qvm-ls`). This can tell you if something 
> with PCI passthru is causing a problem, such as (most likely) the NetVM 
> or UsbVM (wifi card, wifi driver, usb controller). 
>
> Another idea, try disabling VT-x and VT-d in BIOS, then boot Qubes and 
> try suspend. This might tell you if it's a Xen problem, or a firmware 
> bug related to VT-x, for example. 
>
> If the option is present, try disabling the onboard WiFi card in BIOS. 
> It's worth trying this for any other hardware too (dGPU, etc). 
>
>
Thanks, I'll do more experiments like this with it.
 

> Try upgrading your machine's firmware. On dell you can do this via 
> fwupd, Freedos, or using the boot-menu option to upgrade from USB drive. 
> On my Dell, option 3 was simply broken, so I had to do it from Freedos. 
>
>
That was the first thing I did after getting the laptop. I've managed to 
upgrade the BIOS only to 2.4.0, though. There is 2.5.0 but upgrading that 
from USB did not work. Unfortunately, fwupd does not seem to be supported 
for this laptop (at least that's my undestanding).
 

> Try installing Fedora with Xen (the basis of Qubes) and see if it 
> resumes from there. 
>
>
Hmmm? Not sure what you mean by Fedora with Xen? 
 

> There are also tons of techniques for debugging suspend on generic 
> Linux. You can play with acpi_osi=, mem_sleep_default=, `dmesg > 
> before.txt ; pm-suspend ; dmesg > after.txt`, the list goes on and on. 
> Here's a nice article to get you started: 
>
> https://01.org/blogs/rzhang/2015/best-practice-debug-linux-suspend/hibernate-issues
>  
>
> If you want to read my (thus-far unresolved) experience with suspend in 
> 

Re: [qubes-users] Easiest way to redirect USB to a VM?

[Steve Coleman]

On 2019-10-08 16:44, Guerlan wrote:
I tried that too, but when I run qvm-usb I get an empty list of usb 
devices. Running lsusb obviously gives me a lot of usb devices (on 
dom0). So I thought sys-usb is needed for USB to work. What am I doing 
wrong?


I think the trick is to:

1) Make sure your Android device presents itself as a USB drive, so that 
you can copy/move files between the device and the VM.


Q: Have you used the phone with any other Linux/Windows machine such 
that you know it is configured to present the USB drive interface? I'm 
pretty sure you need to configure that on the phone first.


2) Then Dom0 needs to have the proper tools/drivers to see that USB 
device as a drive, so that it can be passed/attached via the command 
line tools or the toolbar applet. I know that fedora-25 has a 
"android-tools" package that might be needed for this.


Once you can see it in dom0 using qvm-usb/qvm-block you should be able 
to pass it through to your VM with the toolbar applet or qvm-block attach.


Its been a long while since I have done this, and I have not yet done it 
with either Qubes4.x nor my current Android phone, so your mileage may 
vary greatly.





--
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/edf300dc-d189-62d7-0cb5-78586ec10e09%40jhuapl.edu.

Re: [qubes-users] Easiest way to redirect USB to a VM?

[Guerlan]

I tried that too, but when I run qvm-usb I get an empty list of usb 
devices. Running lsusb obviously gives me a lot of usb devices (on dom0). 
So I thought sys-usb is needed for USB to work. What am I doing wrong?

On Tuesday, October 8, 2019 at 5:39:35 PM UTC-3, Mike Keehan wrote:
>
> On Tue, 8 Oct 2019 11:40:23 -0700 (PDT) 
> Guerlan > wrote: 
>
> > Yes, I followed that topic and when I created the sys-usb VM mey 
> > keyboard and mouse got disabled and I couldn't do anything else. 
> > 
> > That's why I asked if there's an easier (possibly less secure) way to 
> > redirect the USB from dom0 directly to another VM. I can't create a 
> > sys-usb because I will be left without keyboard 
> > 
> > On Monday, October 7, 2019 at 9:06:50 AM UTC-3, Mike Keehan wrote: 
> > > 
> > > On Sun, 6 Oct 2019 22:04:05 -0700 (PDT) 
> > > Guerlan > wrote: 
> > >   
> > > > I tried to create sys-usb, and my keyboard stopped working. I 
> > > > then rebooted and couldn t use keyboard to put my LUKS password. 
> > > > I had to reinstall qubes entirely. 
> > > > 
> > > > Is there an easier way to pass USB from dom0 to a VM? I don' t 
> > > > want to create a sys-usb and I don' t care too much about 
> > > > security in this level. I just need to have my Android phone 
> > > > inside the virtual machine. 
> > > >   
>
> > > 
> > > Have you read the docs?  https://www.qubes-os.org/doc/usb-devices/ 
> > >   
> > 
>
> In the link above, the section titled "With The Command Line Tool" shows 
> how to use qvm-usb in dom0 to attach usb devices to a VM. 
>
> (I think you have been reading the usb-qubes page, and not that in the 
> link given above!). 
>
> Mike. 
>
> ps - mailing list etiquette is to post replies below the email, not 
> 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/7bd940e7-1987-4a71-aa3d-adfa12eee894%40googlegroups.com.

Re: [qubes-users] Easiest way to redirect USB to a VM?

[Mike Keehan]

On Tue, 8 Oct 2019 11:40:23 -0700 (PDT)
Guerlan  wrote:

> Yes, I followed that topic and when I created the sys-usb VM mey
> keyboard and mouse got disabled and I couldn't do anything else.
> 
> That's why I asked if there's an easier (possibly less secure) way to 
> redirect the USB from dom0 directly to another VM. I can't create a
> sys-usb because I will be left without keyboard
> 
> On Monday, October 7, 2019 at 9:06:50 AM UTC-3, Mike Keehan wrote:
> >
> > On Sun, 6 Oct 2019 22:04:05 -0700 (PDT) 
> > Guerlan > wrote: 
> >  
> > > I tried to create sys-usb, and my keyboard stopped working. I
> > > then rebooted and couldn t use keyboard to put my LUKS password.
> > > I had to reinstall qubes entirely. 
> > > 
> > > Is there an easier way to pass USB from dom0 to a VM? I don' t
> > > want to create a sys-usb and I don' t care too much about
> > > security in this level. I just need to have my Android phone
> > > inside the virtual machine. 
> > >   

> >
> > Have you read the docs?  https://www.qubes-os.org/doc/usb-devices/ 
> >  
> 

In the link above, the section titled "With The Command Line Tool" shows
how to use qvm-usb in dom0 to attach usb devices to a VM.

(I think you have been reading the usb-qubes page, and not that in the
link given above!).

Mike.

ps - mailing list etiquette is to post replies below the email, not
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/20191008213927.447a674a.mike%40keehan.net.

Re: [qubes-users] Installation on Lenovo ThinkStation P330 (2. generation)

[M]

And should I next time erase the mark in the box where there stood something 
like “save session for future login” ?

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/beeab370-1256-46b6-8021-5ffe90a2ecb1%40googlegroups.com.

Re: [qubes-users] Installation on Lenovo ThinkStation P330 (2. generation)

[M]

I have just tried to restart the pc to disable the device in UEFI 
config.

I have erased the mark in the box where there stood something like “save 
session for future login” and pressed on restart.

Then after running some code, there is just a black screen with a white cursor 
in the upper left corner.

Shall I just hold the power button in for restart and to enter bios to disable 
the device ?

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/dc17f06a-1b58-421f-b6a6-fe31dac2b48c%40googlegroups.com.

Re: [qubes-users] Installation on Lenovo ThinkStation P330 (2. generation)

['awokd' via qubes-users]

M:
> Thanks.
> 
> I should just click on OK in the error message and then click on “Continue 
> configuration” - or something similar.
> 
> I then entered “lspci” in the Dom0 Terminal when logged in as root (do not 
> know if it’s also possible to see when logged in as normal user).
> 
> I then found out that on that address is the “Ethernet controller: Intel 
> Corporation Ethernet Connection (7) I219-LM (rev 10).
> 
> Then what do I do now ?
> 
Temporarily remove it from sys-net in Qube Settings/Devices, then enter
the command to finish deploying your templates if they haven't all been
created.

-- 
- don't top post
Mailing list etiquette:
- trim quoted reply to only relevant portions
- when possible, copy and paste text instead of screenshots

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/be678345-ee76-6d14-211a-c371191b0405%40danwin1210.me.

Re: [qubes-users] Installation on Lenovo ThinkStation P330 (2. generation)

[M]

Thanks.

I should just click on OK in the error message and then click on “Continue 
configuration” - or something similar.

I then entered “lspci” in the Dom0 Terminal when logged in as root (do not know 
if it’s also possible to see when logged in as normal user).

I then found out that on that address is the “Ethernet controller: Intel 
Corporation Ethernet Connection (7) I219-LM (rev 10).

Then what do I do now ?

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/41815262-6cad-4b27-97ab-d1e1eef8470a%40googlegroups.com.

Re: [qubes-users] Easiest way to redirect USB to a VM?

[Guerlan]

Yes, I followed that topic and when I created the sys-usb VM mey keyboard 
and mouse got disabled and I couldn't do anything else.

That's why I asked if there's an easier (possibly less secure) way to 
redirect the USB from dom0 directly to another VM. I can't create a sys-usb 
because I will be left without keyboard

On Monday, October 7, 2019 at 9:06:50 AM UTC-3, Mike Keehan wrote:
>
> On Sun, 6 Oct 2019 22:04:05 -0700 (PDT) 
> Guerlan > wrote: 
>
> > I tried to create sys-usb, and my keyboard stopped working. I then 
> > rebooted and couldn t use keyboard to put my LUKS password. I had to 
> > reinstall qubes entirely. 
> > 
> > Is there an easier way to pass USB from dom0 to a VM? I don' t want 
> > to create a sys-usb and I don' t care too much about security in this 
> > level. I just need to have my Android phone inside the virtual 
> > machine. 
> > 
>
> Have you read the docs?  https://www.qubes-os.org/doc/usb-devices/ 
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/c6aa536e-12fd-4046-af68-ce0c0e91a9a0%40googlegroups.com.

Re: [qubes-users] Installation on Lenovo ThinkStation P330 (2. generation)

[M]

Maybe it is caused by a PCIe card...

I’ll try to dismount it and try again...

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/75953034-6641-4d90-9445-c0c539310dc0%40googlegroups.com.

Re: [qubes-users] Installation on Lenovo ThinkStation P330 (2. generation)

[M]

It is while it is preparing templates.

So what do I do then when I can’t log in and use the terminal... ?

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/feb0a2d7-8a9a-4625-afcb-eeeb9e1b3b55%40googlegroups.com.

Re: [qubes-users] Installation on Lenovo ThinkStation P330 (2. generation)

['awokd' via qubes-users]

M:
> Now the motherboard is changed and I have managed to begin the installation 
> of Qube OS.
>  
> But after the installation, reboot and continuing the installation process, I 
> get this error message:
> 
> [dom0] Error
> “[‘/user/bin/qvm-start’, ‘sys-firewall’] failed:
> stdout: “”
> stderr: “Start failed: internal error: Unable to reset PCI device 
> :00:1f:6 no FLR, PM reset or bus reset available, see ...
> “
> How can I drop by this so I can start Qubes OS ?
> 
Good news is you are close to having it installed. When/how do you get
this error, while it is preparing templates or once you've logged in to
Qubes? If you can get to a dom0 terminal, check "lspci" and it will tell
you what device is on :00:1f:6. The fix is similar in either case-
temporarily disable the problem device (likely a wifi card) in UEFI
config, then repeat either the full install or if you can get to a dom0
terminal "sudo /usr/libexec/initial-setup/initial-setup-graphical". Once
you are able to login without it complaining, re-enable the problem
device, and add it to sys-net with no-strict-reset per
https://www.qubes-os.org/doc/pci-devices/#pci-passthrough-issues.

-- 
- don't top post
Mailing list etiquette:
- trim quoted reply to only relevant portions
- when possible, copy and paste text instead of screenshots

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/fece7669-a38b-753d-7a87-8306c76a630f%40danwin1210.me.

Re: [qubes-users] Installation on Lenovo ThinkStation P330 (2. generation)

[M]

Now the motherboard is changed and I have managed to begin the installation of 
Qube OS.
 
But after the installation, reboot and continuing the installation process, I 
get this error message:

[dom0] Error
“[‘/user/bin/qvm-start’, ‘sys-firewall’] failed:
stdout: “”
stderr: “Start failed: internal error: Unable to reset PCI device :00:1f:6 
no FLR, PM reset or bus reset available, see ...
“
How can I drop by this so I can start Qubes OS ?

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/67877004-9a4d-48c3-8760-825cf247caef%40googlegroups.com.

[qubes-users] laptop screen wont appear after closing lid

[Guerlan]

Whenever I close the lid of the notebook, when I open again, I see the 
keyboard light lightning up but the screen never lights and I have to 
reboot.

Is there a fix for 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/ed421d19-6ac1-4e06-8f2e-102823274ead%40googlegroups.com.

[qubes-users] Salt Questions

[Johannes Graumann]

Gentlepeople,

I'm finally biting the bullet and setting out to salt my Qubes.

1) DARN is it complicated in comparison to Ansible - not least because 
of the ... interesting ... obsession with the physical characteristics 
of salty minerals (grain, pillar, ...) - just call it what if 
functionally is, for  chrissakes ... 


2) I'm unclear about whether the fedora-/debian-X-minimal template VMs 
require additional packages to be managed through salt.

https://www.qubes-os.org/doc/templates/minimal/ appears to indicate so:

Also, there are packages to provide additional services:
...
qubes-mgmt-\*: If you want to use salt management on the template and 
qubes.


If that's indeed the case, it's actually not possible to manage minimal 
template installation/customization entirely through salt, which I 
consider suboptimal.


3) I so far have managed to setup `*.sls` files for updating all 
templates as well as dom0 (THANKS unman for the example repo posted a 
while ago). Now I'm trying to get a defined package installed in a 
minimal template and fail:


flatpak.sls:
install_flatpak:
  pkg.installed:
- pkgs:
 - flatpak

*.top:
base:
  ^(.*)-flatpak$:
- match: pcre
- flatpak

when applying this to --all, everything appears to run fine, but at the 
end, the present fedora-30-minimal-flatpak template does NOT have 
flatpak installed ...

Where am I erring?

Thank you for any insight you may be able to give.

Sincerely, Joh

--
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/5b638b1e2e4ab858548f05c4b8bf6e9b%40graumannschaft.org.