[qubes-users] dom0 autocomplete in dom0 terminal

[haaber]

Hi, did someone try to program qubes-* and qvm-* specific
"autocompletes" in the terminal, like

qvm-start w[TAB]  to obtain   qvm-start work
qvm-shutdown v[TAB]  to obatin qvm-shutdown vault

Since Q4 trained me to use a terminal for everything, I think that  an
autocomplete really speeds up daily life... 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/9ff7858e-2cd4-18f4-10c2-02182f356abe%40web.de.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: dd command to creat an .iso from the win7 cdrom please

[pixel fairy]

you need the device entry of the cdrom, usually /dev/sr0 or /dev/cdrom. if you 
mount the cdrom, and type "mount" you should it in the first column. its been a 
long time since doing this. you can also download the windows 7 installer from 
microsoft here, https://www.microsoft.com/en-us/software-download/windows7

the first command below makes the iso file, with sudo meaning "so this as root" 
(kinda like administrator in windows) and the second gives the iso back to you, 
cause otherwise its owned by root.

sudo dd if=/dev/cdrom of=windows7.iso
sudo chown user.user windows7.iso

-- 
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/fe69c271-7036-42e0-a15a-91dc7b53a00f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Qubes OS 4.0-rc4 has been released!

[pixel fairy]

Can you clarify which specter variants will be mitigated and how?

-- 
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/0f9d0226-8d12-4789-bbf6-51daf2dcdea6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Slow network speed outside netvm

[Jarle Thorsen]

Mike Keehan:

> It sounds a bit ambitious to run 10gb per sec from one VM through 
> another and onto the wire.  I suspect you are memory speed limited
> if you are using a straightforward desktop pc.

I'm not sure what is the limiting factor (memory speed, xen overhead?), but I 
just did an iperf test between netvm and appvm only, and I still maxed out at 4 
Gbit/s. This test takes the network card out of the equation and only tests the 
speed between the vms. Maybe somebody can do similar tests on their system?

> Do you know if anyone has achieved this?

I don't know.

-- 
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/5022b631-9a83-4c15-a240-c00d620e67f0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] dd command to creat an .iso from the win7 cdrom please

[David W. Hodgins]

On Wed, 31 Jan 2018 22:03:03 -0500,  wrote:


dd command to creat an .iso from the win7 cdrom please


dd if=/dev/cdrom of=/home/user/win7.iso bs=1M


BTW, any suggested amount of RAM or HD space to allocate in the HVM for
win7 ?


That I don't know.


I don't see any reference to bcedit  or how/where I would disable
driver signing  sigh


It's a windows command. See
https://docs.microsoft.com/en-ca/windows-hardware/drivers/devtest/bcdedit--set

Regards, Dave Hodgins

--
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/op.zdqv9krrn7mcit%40hodgins.homeip.net.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Qubes / Github bugs track ??

[Ivan Mitev]

Whatever you do, don't create a new issue when you know it's a duplicate
of the old one! That causes confusion and creates extra work, which
takes time away from working on the actual problem.



[...]



Please don't send emails to individual developers or create issues you
know are duplicates! Both are distracting and actually make it harder
for them to help you with your problem. Instead, please just add a
comment on the existing closed issue, as I explained above. We'll
receive a notification when you do.


To the OP's credit, both those [bad] suggestions were mine: without 
knowing that you get notifications when a comment to closed issue was 
post I only saw those two - non optimal - ways.


Cheers,
Ivan

--
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/bf627382-b808-46e0-1b69-34ab0cef60c7%40maa.bz.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] sudden reboot?!

[evo]

Hi all!

I have sometimes big problem with Qubes 3.2.
Just now, by writing an email... suddenly my laptop rebooted. Without
any errors. Blackscreen and reboot.

This was the second time, but after rather large period.

how can i manage it??

greets
evo

-- 
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/61abc93b-ce15-d540-94b8-bcd499a92e04%40aliaks.de.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Qubes / Github bugs track ??

[Andrew David Wong]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2018-01-31 08:25, ThierryIT wrote:
> Le mardi 30 janvier 2018 10:05:57 UTC+2, Ivan Mitev a écrit :
>> On 01/30/18 09:36, ThierryIT wrote:
>>> Hi,
>>>
>>> Why are you closing a ticket before knowing if the modification you have 
>>> made, to correct the bug, is working ? I mean, why can't you wait for the 
>>> user to add the modification and see if it is working or not ?
>>
>> Once a dev or contributor provides a fix that he/she thinks solves an 
>> issue there is usually no reason to keep the issue open, or else the 
>> issue tracker would be cluttered with fixed but open issues waiting to 
>> be confirmed/closed by their reporter.
> 
> Do not agree at all with this ...
> If taking as example my ticket, what happen:
> 
> 1) I open a ticket for a problem
> 2) The ticket is taken into account by the dev
> 3) Work on it, push the patch
> 4) close the ticket
> 5) I do the update as requested
> 6) result: not fully working
> 7) Cannot re-open my ticket, open a new ticket
> 8) The dev close my second ticket because it is duplicated ticket
> 9) re-open the first ticket
> 
> And what about:
> 
> 1) I open a ticket for a problem
> 2) The ticket is taken into account by the dev
> 3) Work on it, push the patch
> 4) Ask the user to update and give feedback
> 5) if working then close the ticket, if not then go ahead ...
> 
> What do you think ?
> 

The problem, as Ivan pointed out, is that our issue tracker would be
cluttered with open reports in which the issue is probably fixed, but
we're waiting for the reporter to confirm that it's fixed. Many
reporters wouldn't respond at all. That would make our issue tracker
much less efficient for our developers, which would in turn make them
less efficient at fixing bugs and adding features.

Instead, if you find that your issue was closed without being fixed, you
should simply say so in a comment on that issue. You could simply say,
"This is still happening. Please re-open." (However, it would be more
helpful if you could provide more detail than that. We understand that
it's not always possible, though.)

Whatever you do, don't create a new issue when you know it's a duplicate
of the old one! That causes confusion and creates extra work, which
takes time away from working on the actual problem.

>>
>>> As exemple: ticket #3501 is closed, but even if I have followed the 
>>> instruction, the problem is not solved, but the ticket is closed ... 
>> Either you're now hitting a bug that has nothing to do with your 
>> original issue or Marek thought he fixed the bug but made a mistake. If 
>> it's the former simply open another issue. If it's the latter, I'd send 
>> Marek a friendly email, or I would create a new issue pointing to the 
>> wrongly solved older one.
>>

Please don't send emails to individual developers or create issues you
know are duplicates! Both are distracting and actually make it harder
for them to help you with your problem. Instead, please just add a
comment on the existing closed issue, as I explained above. We'll
receive a notification when you do.

I've updated the Reporting Bugs page to try to clarify all of this:

https://www.qubes-os.org/doc/reporting-bugs/

>>> How to re-open it ?
>>
>> You can't, it looks like it's a github shortcoming. Had you taken 2 secs 
>> to websearch it, you'd have found:
>>
>> https://stackoverflow.com/questions/21333654/how-to-re-open-an-issue-in-github#21333938
>>
>> first hit, no need to even click the link, the answer is at the top of 
>> the search page: "you cannot re-open your own issues if a repo 
>> collaborator closed them".

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

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlpymZoACgkQ203TvDlQ
MDDgIxAAjtzKW1QtkK6HtYR+XcFpVR+sWAsT0xWzhk6eyTi5ob1yersq74h2sgzt
sZthRjz5q5x4ylWYR/6kB4jWj+Dc1aQkhieWmNKdSbpiV7fcdk94wFJQz7QaLUbq
zYjoiG8ERKSO0pS1X1ts1rUIed0EavGC5jYcnjDD9bUSqniXMhXUsv4G7Pq07I34
CSrtjd4eXBKzdQ4ky0if2XAQlQF0LpTaKjhNlMUTouOuzCcQZWAtm62/UE5VzZq6
5KKHoM9iviCjzjV3HHDvWyHbT21o75RMBf8UE3WrpZOSoQkKZDRSFZ59J8URQ6Vn
I1Q/FtAMHKCNvRr1NvspvCVglpQ7mJCh4Cf8ataCB4swIj7eUMM7GUaDE79jYIrI
y+SkRIO0b7Pd+tQHLocjx2v+lVlcKc4QQlOnCMm86hUKfrSg38KrNJrnVs4VKhsu
zds4tqD2Wx1PIQ0nUkuNg2uF1G9uV84vLop9cKN5w4bsU4/Wgm1E8Kn6mwhK0f35
OGF35PkTmp/wC3hrQxv5DW26rKM/3ejQ9cy/2U01nqxHWH4rCmMVMwPYxCQvfSrD
hkDIPJ2ba6OaZuzWjocJ1wlDT0UHYlfcF0V+dkWGhZfruSSv/v5XaKi1RmWh64GC
aWVWqNh/pYbkfjspBWDjfMLz6sjEDXhfCFiyFtYMr/locQjw8wk=
=SGK5
-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 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/17ab8ebd-101d-844a-609d-c920e601d36a%40qubes-os.org.
For more 

[qubes-users] dd command to creat an .iso from the win7 cdrom please

[yrebstv]

dd command to creat an .iso from the win7 cdrom please 

I'm trying to create a win7 HVM and am getting stuck at the magic
glowing windows logo and I discovered in the reference doc's eventually:
https://github.com/QubesOS/qubes-issues/issues/2488

only problem, Is I don't think the original doc, actually gives the dd
command arguments etc,  and somehow I'm not linuxy enough to know it. 


2)
BTW, any suggested amount of RAM or HD space to allocate in the HVM for
win7 ?

3)
Lastly, I don't think I understand step #8 
"When windows is successfully installed, disable driver signing with
bcedit (see install docs)" . 



.if these docs are meant
https://www.qubes-os.org/doc/windows-appvms/
https://www.qubes-os.org/doc/windows-appvms/ (btw  there seem to be two
different pages loading with the same URL )

https://www.qubes-os.org/doc/hvm/

I don't see any reference to bcedit  or how/where I would disable 
driver signing  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/09e933a7750c010b55bc02c13dfc5483%40riseup.net.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Qubes OS 4.0-rc4 has been released!

[Andrew David Wong]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear Qubes Community,

We're pleased to announce the fourth release candidate for Qubes 4.0!
This release contains important safeguards against the [Spectre and
Meltdown attacks][qsb-37], as well as bug fixes for many of the issues
discovered in the [previous release candidate][4.0-rc3]. A full list of
the Qubes 4.0 issues closed so far is available [here][closed-issues].
Further details about this release, including full installation
instructions, are available in the [Qubes 4.0 release
notes][release-notes]. The new installation image is available on the
[Downloads] page.

As always, we're immensely grateful to our community of testers for
taking the time to [discover and report bugs]. Thanks to your efforts,
we're able to fix these bugs *before* the final release of Qubes 4.0. We
encourage you to continue diligently testing this fourth release
candidate so that we can work together to improve Qubes 4.0 before the
stable release.

Major changes in Qubes 4.0-rc4
- --

The Qubes VM Manager is back by popular demand! The returning Qubes
Manager will be slightly different from the 3.2 version. Specifically,
it will not duplicate functionality that is already provided by the new
4.0 widgets. Specific examples include attaching and detaching block
devices, attaching and detaching the microphone, and VM CPU usage.

In addition, the default TemplateVMs have been upgraded to Fedora 26 and
Debian 9.

The Qubes 4.0 stable release
- 

If the testing of 4.0-rc4 does not reveal any major problems, we hope to
declare it the stable 4.0 release without any further significant
changes. In this scenario, any bugs discovered during the testing
process would be fixed in subsequent updates.

If, on the other hand, a major issue is discovered, we will continue
with the standard [release schedule], and Qubes 4.0 stable will be a
separate, later release.

Current Qubes 4.0 Users
- ---

Current users of Qubes 4.0-rc3 can upgrade in-place by downloading the
latest updates from the testing repositories in both
[dom0][dom0-testing] and [TemplateVMs][domU-testing]. As explained in
[QSB #37][qsb-37], Qubes 4.0-rc4 uses PVH instead of HVM for almost all
VMs without PCI devices by default as a security measure against
Meltdown, and this change will also be released as a patch for existing
Qubes 4.0 installations in the coming days. Therefore, current Qubes 4.0
users will benefit from this change whether they upgrade in-place from a
previous release candidate or perform a clean installation of 4.0-rc4.

If you wish to upgrade in-place and have manually changed your VM
settings, please note the following:

1. By default, Qubes 4.0-rc3 used kernel 4.9.x. However, PVH mode will
   require kernel >= 4.11. This is fine, because we will include kernel
   4.14 in the PVH update. However, if you have manually changed the
   kernel setting for any of your VMs, the update will not automatically
   override that setting. Those VMs will still be using an old kernel,
   so they will not work in PVH mode. Therefore, you must must either
   change their settings to use the new kernel or change the VM mode
   back to HVM.

2. If you have created a Windows VM, and you rely on it running in HVM
   mode, you must explicitly set its mode to HVM (since the default mode
   after applying the PVH update will be PVH rather than HVM). You can
   do this either through the VM Settings GUI or by using the
   `qvm-prefs` command-line tool to change the `virt_mode` property.


[qsb-37]: https://www.qubes-os.org/news/2018/01/11/qsb-37/
[4.0-rc3]: https://www.qubes-os.org/news/2017/11/27/qubes-40-rc3/
[closed-issues]: 
https://github.com/QubesOS/qubes-issues/issues?q=is%3Aissue+milestone%3A%22Release+4.0%22+is%3Aclosed
[release-notes]: https://www.qubes-os.org/doc/releases/4.0/release-notes/
[discover and report bugs]: https://www.qubes-os.org/doc/reporting-bugs/
[release schedule]: 
https://www.qubes-os.org/doc/version-scheme/#release-schedule
[4.0-bugs]: 
https://github.com/QubesOS/qubes-issues/issues?utf8=%E2%9C%93=is%3Aopen+is%3Aissue+milestone%3A%22Release+4.0%22+label%3Abug
[dom0-testing]: 
https://www.qubes-os.org/doc/software-update-dom0/#testing-repositories
[domU-testing]: 
https://www.qubes-os.org/doc/software-update-vm/#testing-repositories
[Downloads]: https://www.qubes-os.org/downloads/

This announcement is also available on the Qubes website:
https://www.qubes-os.org/news/2018/01/31/qubes-40-rc4/

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

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlpyfsUACgkQ203TvDlQ
MDDB3w/+M0JJTT1cWeQNe1fZgQXkKE9dY/lJD3E+/llFjxHrA1QpjYoo2txWHj6a
oM9pbH9qDCdhFxyU9z3wejMaMuseav5xOhg9BgtO2qeWyCCEwPap4EFgwEnn6wzF
HjNtDxkxtgenJtf9833OI5uRNiejp9zuW3NvlisAVaAYmCi+ZT3ksaJFidVpkna7

[qubes-users] Re: Ubuntu templates

[mikihonzero]

On Wednesday, January 31, 2018 at 11:56:29 PM UTC, Unman wrote:
> I'm just pushing up some PRs to remove zesty and institute build support
> for artful (17.10).
> If you cant wait there's a ready built 3.2 template you can try at:
> http://qubes.3isec.org/Templates
> 
> unman

What about Q4, are there downloads ready or does the build process work (and 
which versions)?
Regards

-- 
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/554ba66d-f3fa-4967-a94c-a9b55dcaecfb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] How to deal with Yubikey ?

[joeviocoe]

qvm-usb command shows you how to attach USB devices to VMs.  There is no GUI 
method like there is for block devices.  

Remember, Yubikey is not a storage/block device.  It is a USB that acts more 
like a HID keyboard.  

Mine works on 3.2 just fine using sys-usb, then attaching to whatever VM needs 
it.

On Wednesday, 31 January 2018 09:14:36 UTC-5, ThierryIT  wrote:
> How did you attached it ? I am trying without success ... I can attached it 
> from dom0 using: qvm-block a vm_name dom0:sdd 
> Is it correct under Qubes4.0r3 ?
> 
> 
> Le mardi 23 janvier 2018 09:51:17 UTC+2, Kushal Das a écrit :
> > On Tue, Jan 23, 2018 at 12:17 PM, ThierryIT  wrote:
> > > Hello,
> > >
> > > I have today to deal with two problems:
> > >
> > > 1) I am using Yubikey to be authentified on some web site like Github ...
> > > 2) I am using Yubikey to stock my PGP keys and to use them with mainly my 
> > > emails (Thinderbird+Enigmail)
> > >
> > > What to do under Qubes to make this possible ?
> > > I have already sys-usb running.
> > 
> > On Qubes 4.0rc3, I just attach it to the vm as required, and use it.
> > No configuratino is required.
> > 
> > Kushal
> > -- 
> > Staff, Freedom of the Press Foundation
> > CPython Core Developer
> > Director, Python Software Foundation
> > https://kushaldas.in

-- 
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/008377f5-41d4-4460-ae36-2accec859729%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Ubuntu templates

[Unman]

I'm just pushing up some PRs to remove zesty and institute build support
for artful (17.10).
If you cant wait there's a ready built 3.2 template you can try at:
http://qubes.3isec.org/Templates

unman

-- 
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/20180131235625.qwihevz3g3nm7y75%40thirdeyesecurity.org.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] HCL report - Dell Precision 5520

[Yassine]

At first couldn't install 4.0-rc3 because of some hardware issues (dual GPU and 
multicore features).
Upgraded the BIOS and modified xen configuration to blacklist nouveau and 
bochs_drm in order have a successful install

-- 
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/4d452c25-598c-4130-84e0-edece6028077%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Qubes-HCL-Dell_Inc_-Precision_5520-20180131-230512.yml
Description: Binary data

[qubes-users] Re: Slow network speed outside netvm

[Alex Dubois]

On Wednesday, 31 January 2018 12:15:01 UTC, Jarle Thorsen  wrote:
> Alex Duboise:
> > Interested to find out too. Have you tried from FirewallVM?
> 
> Same slow performance when iperf is run from a FirewallVM that is connected 
> to the netvm.
> 
> > Could you also test what happen when during the load test you start a 
> > disposable VM? Does it drop 
> 
> Running iperf in the netvm, and starting a disposable vm using the same netvm 
> there is no performance drop. (I get 8+ Gbit running one thread, and about 
> 9,5Mbit when using multiple threads)

Thanks for testing and for the SG module I didn't know before this thread. I'll 
have to dig into my pb...

-- 
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/4752302e-276b-4c1d-a60f-a7fc76a1830e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Networking unavailable on Dell XPS 9350, QubesOS 4

[Qubed One]

'awokd' via qubes-users:
> On Wed, January 31, 2018 2:39 pm, jaya...@gmail.com wrote:
>> What do you mean it is easy to do? Where do you get a compatible wireless
>> card, that is definitely supported by Qubes anyway?


You can purchase them many places online, even Amazon, for example, for
about $12 USD.


>> I somehow imagined that getting appropriate driver should be simpler :/
> 
> It's not necessarily a driver issue; more of a Xen (on which Qubes is
> based) pass-through issue. Of the subset of wireless NICs that work
> problem-free on Linux, there's a smaller subset that Xen can pass-through
> problem-free and an even smaller subset that can be passed through a
> QEMU/Xen stub-domain (which is what Qubes uses). I think it comes down to
> how virtualization friendly the hardware manufacturer laid out their BARs
> and MSI pages and whether MSI interrupts work (and who knows, maybe
> there's a QEMU or some other bug somewhere in there too).


Broadcom wireless in linux has always been a pain. That is because of
Broadcom.


> I have success with an AR9565 on R4.0 but not an AR928x. If you're going
> to be shopping for another wireless card, maybe pick one then search this
> mailing list for problem/success reports, or identify which laptops come
> with it then search https://www.qubes-os.org/hcl/ and see if those laptops
> are reported problem free with R4.0?


I can confirm that an Atheros AR9462 works great on 3.2 and 4.0. If
you're open to considering replacing the wifi card, you can email me
off-list and I can walk you through it step by step. It really is easy
to do, even the first time.


> Longer term, I wonder if a section should be added to
> https://www.qubes-os.org/hcl/ specifically to list known
> compatible/incompatible network cards under Qubes R4.0? Could be painful
> to maintain if we expand it to cover PCI devices in general...

-- 
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/b1ba1ef0-c15f-7562-1c04-0387197c6d05%40riseup.net.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Networking unavailable on Dell XPS 9350, QubesOS 4

['awokd' via qubes-users]

On Wed, January 31, 2018 2:39 pm, jaya...@gmail.com wrote:
> What do you mean it is easy to do? Where do you get a compatible wireless
> card, that is definitely supported by Qubes anyway?
>
> I somehow imagined that getting appropriate driver should be simpler :/

It's not necessarily a driver issue; more of a Xen (on which Qubes is
based) pass-through issue. Of the subset of wireless NICs that work
problem-free on Linux, there's a smaller subset that Xen can pass-through
problem-free and an even smaller subset that can be passed through a
QEMU/Xen stub-domain (which is what Qubes uses). I think it comes down to
how virtualization friendly the hardware manufacturer laid out their BARs
and MSI pages and whether MSI interrupts work (and who knows, maybe
there's a QEMU or some other bug somewhere in there too).

I have success with an AR9565 on R4.0 but not an AR928x. If you're going
to be shopping for another wireless card, maybe pick one then search this
mailing list for problem/success reports, or identify which laptops come
with it then search https://www.qubes-os.org/hcl/ and see if those laptops
are reported problem free with R4.0?

Longer term, I wonder if a section should be added to
https://www.qubes-os.org/hcl/ specifically to list known
compatible/incompatible network cards under Qubes R4.0? Could be painful
to maintain if we expand it to cover PCI devices in general...




-- 
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/8fa99630352fccb4fa0b19e7f7248272.squirrel%40tt3j2x4k5ycaa5zt.onion.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Slow network speed outside netvm

[Mike Keehan]

On Wed, 31 Jan 2018 05:23:19 -0800 (PST)
Jarle Thorsen  wrote:

> Ilpo Järvinen: 
> > Please also check that GSO (generic-segmentation-offload) is on at 
> > the sending appvm eth0 (I don't remember if the depency logic
> > causes it to get toggled off when SG was off'ed and cannot check it
> > ATM myself).  
> 
> Yes, GSO is automatically turned on when SG is enabled.
> 
> > > I'm still far away from the speed I get inside the netvm
> > > though... Maybe the netvm needs more than 2 vcpus to handle the
> > > stress from appvms?  
> > 
> > Could be.  
> 
> Going from 2 to 4 vcpu in netvm does not make any difference.
> 
> > I'm not sure how your appvm is connected to netvm if there's
> > firewall vm in between that would also be relevant.  
> 
> Appvm goes directly into the netvm without anything (no firewall) in
> between. 
> > I guess you can try e.g. vmstat 1 in all vms through which the
> > traffic passes through to see if any of them is saturating CPU.  
> 
> Appvm hardly uses any cpu at all, and netvm is below 50% cpu usage.
> 

Hi Jarle,

It sounds a bit ambitious to run 10gb per sec from one VM through 
another and onto the wire.  I suspect you are memory speed limited
if you are using a straightforward desktop pc.

Do you know if anyone has achieved this?

Mike.

-- 
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/20180131145647.2bc52f7f.mike%40keehan.net.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Networking unavailable on Dell XPS 9350, QubesOS 4

[jayarjo]

What do you mean it is easy to do? Where do you get a compatible wireless card, 
that is definitely supported by Qubes anyway?

I somehow imagined that getting appropriate driver should be simpler :/


On Wednesday, January 31, 2018 at 3:33:23 PM UTC+4, bobos wrote:
> On Wednesday, January 24, 2018 at 8:47:28 AM UTC+1, jay...@gmail.com wrote:
> > I decided to try Qubes OS 4 on my XPS 9350 laptop, from USB drive. Mostly 
> > it went ok (had to manually specify EFI file in BIOS to make it load), but 
> > networking is completely unavailable. I think the reason might be that 
> > laptop itself doesn't have ethernet adapter - it connect via a dock station 
> > (which has). I believe something has to be fixed somewhere to enable it? 
> > The dock station itself seems to be recognized somehow, since I have double 
> > external monitors connected to it and QubesOS properly spread over all 
> > three (one  of the laptop and two external).
> > 
> > I see networking icon in the system tray. But it is red with a cross in the 
> > lower right corner and when I click on it it says Ethernet Network "device 
> > not managed". What does it mean?
> > 
> > Laptop also has wireless Broadcom Limited BCM4350 [14e4:43a3] network 
> > controller, however from dmesg I see that:
> > 
> > brcmfmac: brcmf_chip_recognition: SB chip is not supported
> > brcmfmac: brcmf_pcie_probe: failed 14e4:43a3
> > 
> > ...so it probably is not supported.
> > 
> > Is there anything I can do in either direction to obtain networking in my 
> > Qubes OS 4 on this platform?
> 
> 
> 
> change your wireless card, I did the same with my XPS.
> works now.
> 
> its easy to do.

-- 
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/1cbcc9f9-6424-41f1-8936-f72e0b7eee9a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Qubes / Github bugs track ??

[ThierryIT]

Le mardi 30 janvier 2018 10:05:57 UTC+2, Ivan Mitev a écrit :
> On 01/30/18 09:36, ThierryIT wrote:
> > Hi,
> > 
> > Why are you closing a ticket before knowing if the modification you have 
> > made, to correct the bug, is working ? I mean, why can't you wait for the 
> > user to add the modification and see if it is working or not ?
> 
> Once a dev or contributor provides a fix that he/she thinks solves an 
> issue there is usually no reason to keep the issue open, or else the 
> issue tracker would be cluttered with fixed but open issues waiting to 
> be confirmed/closed by their reporter.

Do not agree at all with this ...
If taking as example my ticket, what happen:

1) I open a ticket for a problem
2) The ticket is taken into account by the dev
3) Work on it, push the patch
4) close the ticket
5) I do the update as requested
6) result: not fully working
7) Cannot re-open my ticket, open a new ticket
8) The dev close my second ticket because it is duplicated ticket
9) re-open the first ticket

And what about:

1) I open a ticket for a problem
2) The ticket is taken into account by the dev
3) Work on it, push the patch
4) Ask the user to update and give feedback
5) if working then close the ticket, if not then go ahead ...

What do you think ?

> 
> > As exemple: ticket #3501 is closed, but even if I have followed the 
> > instruction, the problem is not solved, but the ticket is closed ... 
> Either you're now hitting a bug that has nothing to do with your 
> original issue or Marek thought he fixed the bug but made a mistake. If 
> it's the former simply open another issue. If it's the latter, I'd send 
> Marek a friendly email, or I would create a new issue pointing to the 
> wrongly solved older one.
> 
> > How to re-open it ?
> 
> You can't, it looks like it's a github shortcoming. Had you taken 2 secs 
> to websearch it, you'd have found:
> 
> https://stackoverflow.com/questions/21333654/how-to-re-open-an-issue-in-github#21333938
> 
> first hit, no need to even click the link, the answer is at the top of 
> the search page: "you cannot re-open your own issues if a repo 
> collaborator closed them".

-- 
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/17348f3e-a744-41bc-9797-1e396dcf900b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] How to deal with Yubikey ?

[ThierryIT]

How did you attached it ? I am trying without success ... I can attached it 
from dom0 using: qvm-block a vm_name dom0:sdd 
Is it correct under Qubes4.0r3 ?


Le mardi 23 janvier 2018 09:51:17 UTC+2, Kushal Das a écrit :
> On Tue, Jan 23, 2018 at 12:17 PM, ThierryIT  wrote:
> > Hello,
> >
> > I have today to deal with two problems:
> >
> > 1) I am using Yubikey to be authentified on some web site like Github ...
> > 2) I am using Yubikey to stock my PGP keys and to use them with mainly my 
> > emails (Thinderbird+Enigmail)
> >
> > What to do under Qubes to make this possible ?
> > I have already sys-usb running.
> 
> On Qubes 4.0rc3, I just attach it to the vm as required, and use it.
> No configuratino is required.
> 
> Kushal
> -- 
> Staff, Freedom of the Press Foundation
> CPython Core Developer
> Director, Python Software Foundation
> https://kushaldas.in

-- 
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/4f642009-c092-4a59-963f-1b9d8728b52f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: How to deal with Yubikey ?

[ThierryIT]

There is no sys-usb and I do not have installed qubes-usb-proxy 

Le mercredi 31 janvier 2018 16:10:08 UTC+2, ThierryIT a écrit :
> Hi,
> 
> I have moved from R3.2 to 4.0R3.
> And I am still dealing with the same problem, and I don't know if for 4.0R3 
> the documentation provided is still updated.
> All my Keys are detected by dom0:
> 
> Device dom0:4-2 - Neowave_Keydo-AES_0989876... is available
> Device dom0:sdd - Keydo-AES () available
> Device dom0:sdf - Keydo-AES ()( is available
> Device dom0:sdf1 - Keydo-AES (PUBLIC) is available
> 
> This key has two fuction as auth key (github ...) and an public and an  
> encrypted folder
> 
> I am using it to log to Github and to my Registar under Windows.
> 
> So for a Qubes 4.0R3 how to do ?
> 
> Thx
> 
> Le jeudi 25 janvier 2018 13:37:56 UTC+2, rob_66 a écrit :
> > On Mon, 22 Jan 2018 22:47:55 -0800 (PST)
> > ThierryIT  wrote:
> >  
> > > I have today to deal with two problems:
> > > 
> > > 1) I am using Yubikey to be authentified on some web site like
> > > Github ... 2) I am using Yubikey to stock my PGP keys and to use them
> > > with mainly my emails (Thinderbird+Enigmail)
> > > 
> > > What to do under Qubes to make this possible ?
> > > I have already sys-usb running. 
> > 
> > Hi.
> > 
> > I studied and followed
> > https://mig5.net/content/yubikey-2fa-qubes-redux-adding-backup-key as
> > well as https://mig5.net/content/yubikey-challenge-response-mode-qubes
> > and it works perfectly fine on Qubes 3.2, Fedora 26. And my skills
> > are mediocre. 
> > 
> > (Sending *63* bits, »variable«, you'll recognize later.)
> > 
> > However, Qubes' own tutorial can, of course, work flawlessly with your
> > set-up:
> > 
> > https://www.qubes-os.org/doc/yubi-key/
> > 
> > If you like to dig in deeper, see the discussions on Github: 
> > 
> > https://www.qubes-os.org/doc/yubi-key/
> > 
> > Best regards,
> > r.

-- 
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/2c4d60cc-a503-4ed9-9987-b5e93bfcf8b5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: How to deal with Yubikey ?

[ThierryIT]

Hi,

I have moved from R3.2 to 4.0R3.
And I am still dealing with the same problem, and I don't know if for 4.0R3 the 
documentation provided is still updated.
All my Keys are detected by dom0:

Device dom0:4-2 - Neowave_Keydo-AES_0989876... is available
Device dom0:sdd - Keydo-AES () available
Device dom0:sdf - Keydo-AES ()( is available
Device dom0:sdf1 - Keydo-AES (PUBLIC) is available

This key has two fuction as auth key (github ...) and an public and an  
encrypted folder

I am using it to log to Github and to my Registar under Windows.

So for a Qubes 4.0R3 how to do ?

Thx

Le jeudi 25 janvier 2018 13:37:56 UTC+2, rob_66 a écrit :
> On Mon, 22 Jan 2018 22:47:55 -0800 (PST)
> ThierryIT  wrote:
>  
> > I have today to deal with two problems:
> > 
> > 1) I am using Yubikey to be authentified on some web site like
> > Github ... 2) I am using Yubikey to stock my PGP keys and to use them
> > with mainly my emails (Thinderbird+Enigmail)
> > 
> > What to do under Qubes to make this possible ?
> > I have already sys-usb running. 
> 
> Hi.
> 
> I studied and followed
> https://mig5.net/content/yubikey-2fa-qubes-redux-adding-backup-key as
> well as https://mig5.net/content/yubikey-challenge-response-mode-qubes
> and it works perfectly fine on Qubes 3.2, Fedora 26. And my skills
> are mediocre. 
> 
> (Sending *63* bits, »variable«, you'll recognize later.)
> 
> However, Qubes' own tutorial can, of course, work flawlessly with your
> set-up:
> 
> https://www.qubes-os.org/doc/yubi-key/
> 
> If you like to dig in deeper, see the discussions on Github: 
> 
> https://www.qubes-os.org/doc/yubi-key/
> 
> Best regards,
> r.

-- 
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/4f9b9c15-76d1-4e2e-97b8-0f1c28ff6a6a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Slow network speed outside netvm

[Jarle Thorsen]

Ilpo Järvinen: 
> Please also check that GSO (generic-segmentation-offload) is on at 
> the sending appvm eth0 (I don't remember if the depency logic causes it to 
> get toggled off when SG was off'ed and cannot check it ATM myself).

Yes, GSO is automatically turned on when SG is enabled.

> > I'm still far away from the speed I get inside the netvm though... Maybe 
> > the netvm needs more than 2 vcpus to handle the stress from appvms?
> 
> Could be.

Going from 2 to 4 vcpu in netvm does not make any difference.

> I'm not sure how your appvm is connected to netvm if there's firewall vm 
> in between that would also be relevant.

Appvm goes directly into the netvm without anything (no firewall) in between.
 
> I guess you can try e.g. vmstat 1 in all vms through which the traffic 
> passes through to see if any of them is saturating CPU.

Appvm hardly uses any cpu at all, and netvm is below 50% cpu usage.

-- 
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/547a1f87-d856-4ae0-9c79-0c3831892bda%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Slow network speed outside netvm

[Ilpo Järvinen]

On Wed, 31 Jan 2018, Jarle Thorsen wrote:

> Ilpo Järvinen: 
> > Scatter-Gather.
> > 
> > > Are you talking about enabling sg on the virtual network device in the 
> > > netvm? 
> > > 
> > > Something like "sudo ethtool -K vif12.0 sg on" ?
> > 
> > Yes. For both that and the eth0 in appvm.
> 
> This made a huge performance boost! (single threaded iperf went from 
> 1.34 Gbit/sec to 3.75 Gbit/sec in appvm after enabling SG) 

Please also check that GSO (generic-segmentation-offload) is on at 
the sending appvm eth0 (I don't remember if the depency logic causes it to 
get toggled off when SG was off'ed and cannot check it ATM myself).

> I'm still far away from the speed I get inside the netvm though... Maybe 
> the netvm needs more than 2 vcpus to handle the stress from appvms?

Could be.

I'm not sure how your appvm is connected to netvm if there's firewall vm 
in between that would also be relevant.

I guess you can try e.g. vmstat 1 in all vms through which the traffic 
passes through to see if any of them is saturating CPU.


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

Re: [qubes-users] Re: Slow network speed outside netvm

[Jarle Thorsen]

Ilpo Järvinen: 
> Scatter-Gather.
> 
> > Are you talking about enabling sg on the virtual network device in the 
> > netvm? 
> > 
> > Something like "sudo ethtool -K vif12.0 sg on" ?
> 
> Yes. For both that and the eth0 in appvm.

This made a huge performance boost! (single threaded iperf went from 1.34 
Gbit/sec to 3.75 Gbit/sec in appvm after enabling SG)

I'm still far away from the speed I get inside the netvm though... Maybe the 
netvm needs more than 2 vcpus to handle the stress from appvms?

-- 
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/d6107dd7-0152-43cc-9de9-b6cf4555a8a3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Slow network speed outside netvm

[Jarle Thorsen]

Alex Duboise:
> Interested to find out too. Have you tried from FirewallVM?

Same slow performance when iperf is run from a FirewallVM that is connected to 
the netvm.

> Could you also test what happen when during the load test you start a 
> disposable VM? Does it drop 

Running iperf in the netvm, and starting a disposable vm using the same netvm 
there is no performance drop. (I get 8+ Gbit running one thread, and about 
9,5Mbit when using multiple threads)

-- 
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/3437fe7a-49b6-4477-a1a8-3eeaf30546b5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Slow network speed outside netvm

[Ilpo Järvinen]

On Wed, 31 Jan 2018, Jarle Thorsen wrote:

> onsdag 31. januar 2018 11.12.33 UTC+1 skrev Ilpo Järvinen følgende:
> > On Wed, 31 Jan 2018, Jarle Thorsen wrote:
> > > onsdag 31. januar 2018 10.50.09 UTC+1 skrev Jarle Thorsen følgende:
> > > > My netvm (Fedora 26 template) has a 10gbe network card, and from 
> > > > within the netwm I have no problem saturating the 10Gbit link using 
> > > > iperf to an external server.
> > > > However, in any vm sending traffic through this netvm I can only get 
> > > > around 2Gbit max using the same iperf command against the same server.
> > > > 
> > > > I have this problem both with appvms using the *same* Fedora template 
> > > > as the netvm, and also in Windows HVM.
> > > > 
> > > > Anybody have experience with Qubes in a 10Gbe network?
> > > 
> > > I do notice the the process ksoftirqd in the netvm is running at 100% 
> > > cpu during the iperf test from the appvm. I'm guessing this is related 
> > > to my problem? 
> > 
> > SG being disabled for the qubes inter-vm interfaces (due to an unknown 
> > reason as Marek didn't anymore remember the details for that change) might 
> > have some(/huge?) impact on performance as it prevents using some 
> > high-speed features of the kernel.
> 
> Not quite sure what "SG" is in this context. Is there any settings I can 
> experiment with? 

Scatter-Gather.

> Are you talking about enabling sg on the virtual network device in the 
> netvm? 
> 
> Something like "sudo ethtool -K vif12.0 sg on" ?

Yes. For both that and the eth0 in appvm.


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

Re: [qubes-users] Re: Slow network speed outside netvm

[Jarle Thorsen]

onsdag 31. januar 2018 11.12.33 UTC+1 skrev Ilpo Järvinen følgende:
> On Wed, 31 Jan 2018, Jarle Thorsen wrote:
> > onsdag 31. januar 2018 10.50.09 UTC+1 skrev Jarle Thorsen følgende:
> > > My netvm (Fedora 26 template) has a 10gbe network card, and from 
> > > within the netwm I have no problem saturating the 10Gbit link using 
> > > iperf to an external server.
> > > However, in any vm sending traffic through this netvm I can only get 
> > > around 2Gbit max using the same iperf command against the same server.
> > > 
> > > I have this problem both with appvms using the *same* Fedora template 
> > > as the netvm, and also in Windows HVM.
> > > 
> > > Anybody have experience with Qubes in a 10Gbe network?
> > 
> > I do notice the the process ksoftirqd in the netvm is running at 100% 
> > cpu during the iperf test from the appvm. I'm guessing this is related 
> > to my problem? 
> 
> SG being disabled for the qubes inter-vm interfaces (due to an unknown 
> reason as Marek didn't anymore remember the details for that change) might 
> have some(/huge?) impact on performance as it prevents using some 
> high-speed features of the kernel.

Not quite sure what "SG" is in this context. Is there any settings I can 
experiment with?

Are you talking about enabling sg on the virtual network device in the netvm?

Something like "sudo ethtool -K vif12.0 sg on" ?

-- 
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/aa95bf82-c3fe-4d54-a7b6-a9ea6d0cfc3e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Networking unavailable on Dell XPS 9350, QubesOS 4

[Alex Dubois]

On Wednesday, 31 January 2018 08:28:01 UTC, jay...@gmail.com  wrote:
> So... no go?

For the wireless you could check support for it with Fedora community (netVM 
runs Fedora 26).

-- 
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/c740537f-a1cc-4d47-a037-b9b08d9efee8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Networking unavailable on Dell XPS 9350, QubesOS 4

[bobos]

On Wednesday, January 24, 2018 at 8:47:28 AM UTC+1, jay...@gmail.com wrote:
> I decided to try Qubes OS 4 on my XPS 9350 laptop, from USB drive. Mostly it 
> went ok (had to manually specify EFI file in BIOS to make it load), but 
> networking is completely unavailable. I think the reason might be that laptop 
> itself doesn't have ethernet adapter - it connect via a dock station (which 
> has). I believe something has to be fixed somewhere to enable it? The dock 
> station itself seems to be recognized somehow, since I have double external 
> monitors connected to it and QubesOS properly spread over all three (one  of 
> the laptop and two external).
> 
> I see networking icon in the system tray. But it is red with a cross in the 
> lower right corner and when I click on it it says Ethernet Network "device 
> not managed". What does it mean?
> 
> Laptop also has wireless Broadcom Limited BCM4350 [14e4:43a3] network 
> controller, however from dmesg I see that:
> 
> brcmfmac: brcmf_chip_recognition: SB chip is not supported
> brcmfmac: brcmf_pcie_probe: failed 14e4:43a3
> 
> ...so it probably is not supported.
> 
> Is there anything I can do in either direction to obtain networking in my 
> Qubes OS 4 on this platform?



change your wireless card, I did the same with my XPS.
works now.

its easy to do.

-- 
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/061ae119-4039-48a9-8438-aed53c47da6b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Slow network speed outside netvm

[Jarle Thorsen]

onsdag 31. januar 2018 10.50.09 UTC+1 skrev Jarle Thorsen følgende:
> My netvm (Fedora 26 template) has a 10gbe network card, and from within the 
> netwm I have no problem saturating the 10Gbit link using iperf to an external 
> server.
> 
> However, in any vm sending traffic through this netvm I can only get around 
> 2Gbit max using the same iperf command against the same server.
> 
> I have this problem both with appvms using the *same* Fedora template as the 
> netvm, and also in Windows HVM.
> 
> Anybody have experience with Qubes in a 10Gbe network?

I do notice the the process ksoftirqd in the netvm is running at 100% cpu 
during the iperf test from the appvm. I'm guessing this is related to my 
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/e812a2c1-29c4-48f0-bdbd-fefa1da0f00e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Slow network speed outside netvm

[Jarle Thorsen]

My netvm (Fedora 26 template) has a 10gbe network card, and from within the 
netwm I have no problem saturating the 10Gbit link using iperf to an external 
server.

However, in any vm sending traffic through this netvm I can only get around 
2Gbit max using the same iperf command against the same server.

I have this problem both with appvms using the *same* Fedora template as the 
netvm, and also in Windows HVM.

Anybody have experience with Qubes in a 10Gbe network?

-- 
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/2b2594f3-35c5-43b6-b5ac-72e68d261be2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Networking unavailable on Dell XPS 9350, QubesOS 4

[jayarjo]

So... no go?

-- 
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/a9c92d40-0989-4629-8c26-9b7f8075db3d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.