On Wednesday, May 25, 2016 at 12:05:28 PM UTC-4, Niels Kobschätzki wrote:
> > On May 25, 2016 at 2:20 PM Andrew David Wong <[email protected]> wrote:
> > 
> > On 2016-05-25 03:40, Niels Kobschätzki wrote:
> > > Hi,
> > > 
> > > I hope for the last time today ;)
> > > 
> > > For online P&P-role playing sessions and for podcasting I need to 
> > > use a usb-webcam and usb-microphone. If I understand it correctly 
> > > the only way to get those working is to use a usbvm. So I
> > > activated it and Cheese and Audacity are showing the expected
> > > results.
> > > 
> > > But I would need to use both in Chrome as well for Hangouts and 
> > > WebRTC-sessions. But the usbvm doesn't seem to have access to the 
> > > internet. In the VM settings I cannot choose a NetVM (probably 
> > > because it is a NetVM itself if I understand it correctly). There 
> > > is the NetworkManager to check though in Services. When I do an
> > > "ip addr list" in the usbvm there is only a loopback-interface.
> > > 
> > > What would be the best way to approach my problem?
> > > 
> > 
> > Any AppVM can be a USBVM (by adding the USB controllers in the
> > "Devices" tab in "VM settings"), so if a USBVM-as-NetVM doesn't work
> > (can't test this myself at the moment), then a USBVM-as-AppVM should
> > be able to get network access by assigning sys-firewall as its NetVM.
> 
> Ok, I got that to work. When I tried it the first time I could add only one 
> controller but ran into the problem that the AppVM wouldn't start with an 
> error that the device driver is already in use by xendlight. I didn't get 
> that in the end the pci_strictreset False would be the solution to that 
> problem. The reason was that sys-usb worked with both controllers but the 
> appvm didn't work with just one (after fiddling around, it worked with both). 
> I ran into one wall after another. Now it seems to work.
> 
> P.s.: Is there some sort of documentation wiki? I can only find the
> > > "Docs" which are ok-ish for the beginning and the archive of this
> > > mailing list.
> > 
> > All of our documentation is here:
> > 
> > https://www.qubes-os.org/doc/
> > 
> > I'm not sure what you mean by "for the beginning." As you can see,
> > some pages go quite in depth, and there's also a section for
> > developers, most of which is here:
> > 
> > https://www.qubes-os.org/doc/system-doc/
> 
> Yes, I know that documentation and I mean exactly that. It is not very 
> beginner friendly imho but maybe I am just spoiled by the Arch- and 
> FreeBSD-documentation.
> The problem I have that when I google for errors, you might find the mailing 
> list. In the documentation problems are described but typical concrete error 
> messages are not mentioned that occur in those cases, thus throwing error 
> messages into google do not lead to the documentation.
>  
> > > I.e. is there a place where I could add the stuff I found out so 
> > > far by myself or asking in this mailing list, so it is easier to 
> > > find for others?
> > 
> > Yes, there's an "Edit This Page" button on every page of the
> > documentation. It's all written in Markdown, managed under Git, and
> > hosted on GitHub. We happily accept pull requests containing quality
> > contributions. :)
> 
> I will see what I can do. I find the "create a pull request on github"-method 
> just harder than a wiki (that's why I asked about a wiki), where I can easily 
> add pages. I am not really a developer and I rarely create pull requests. I 
> will look into it :)
> 
> > If you'd prefer just to send out some informal notes, then this
> > mailing list is the right place to do it (and would also be
> > appreciated!).
> 
> Yeah, that's the thing. I am not sure where I put something like: "For 
> getting the teamviewer-client to work, don't use the offered packages but use 
> the tar.gz and start the binary" (in a a bit more detailled way for people 
> who do not know tar-options by heart). The documentation kind of looks that 
> such a thing doesn't fit there and a mailing list is also nothing where short 
> how-tos should be posted because of discoverability.
> 
> I will learn the ways of this community :) So far you all are very helpful 
> and this is a real delight after my experiences in the Arch-community :)
> 
> Niels

I've been wondering about that specific xenlight error when trying to do the 
same thing too. Glad to know the pci_strictset false is how you fixed it. 

Curious though why you couldn't add a netvm to the usbvm.

-- 
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/71c8d3b5-5369-4de6-914a-9e441ab602d0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to