[qubes-users] Qubes-4.0rc2 restore backup error

[lokedhs]

Before installing 4.0rc2, I did a backup of my VM's from 3.2. I've started 
restoring them one-by-one and for the most part is has been a reasonably 
painless operation.

However, when I tried to restore the "ssh" VM, I got the following error:

qubesadmin.backup: -> Restoring ssh...
qubesadmin.backup: Extracting data: 105.4 MiB to restore
qubesadmin.backup: Error extracting data: retrieved backup size exceed 
expected size, if you believe this is ok, use --ignore-size-limit option
qubesadmin.backup: Continuing anyway to restore at least some VMs
qubesadmin.backup: -> Done. Please install updates for all the restored 
templates

After this, I have an "ssh" VM, but it's empty. Or rather, it contains the 
default content as if I had manually created a new VM based on some template.

I then deleted the "ssh" VM and restored using the --ignore-size-limit flag. 
The output was different, but the end result was the same:

qubesadmin.backup: -> Restoring ssh...
qubesadmin.backup: Extracting data: 0 to restore
qubesadmin.backup: -> Done. Please install updates for all the restored 
templates

Again, the "ssh" VM was created, but it just contained the default content just 
as in the first case.

-- 
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/3b1f15bd-a1a0-4ba1-aa4e-f57ae722108d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Qubes-4rc2 timezone (or clocksync service) problems

[lokedhs]

I just installed rc2 and trying to configure the machine similar to the way 
things worked in my old (3.2) installation. One of the issues I have faced is 
that the timesync service doesn't seem to do the right thing.

I am in Singapore timezone (UTC+8). Typing "date" in dom0 shows that the 
correct timezone is configured, but the time is 8 hours in the future:

[dom0]$ date
Thu Oct 26 20:09:23 +08 2017

The actual time when I typed the command was 12:09.

Running "date" in sys-net (which is the VM that runs the clocksync service) 
gives me the same output as in dom0.

Is this a problem with clocksync? Where should I start looking in order to 
figure out the cause of this 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/a8039e35-fd9e-4383-9b9e-bee88f1177fa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[derpytorp]

On Wednesday, October 25, 2017 at 1:26:51 PM UTC-4, [799] wrote:
> Hello,
> 
> As at least one other Qubes user has the same problem, that VMs won't start, 
> I'll add this as special topic.
> 
> I've made a clean install of Qubes 4-rc2 but ~70% of the time I can't boot 
> the VMs.
> This includes sys-net, sys-firewall, but also others.
> 
> I tried to check the logs but I don't get any valuable information.
> See screenshot.
> 
> I started the following command in dom0:
> 
> watch -n 1 xl list
> 
> When I try to launch a VM I can see that the VMs appears in the xl list 
> output, but the State is -- and the Time(s) is 0.0.
> After ~30sec the start is aborted with error message: Cannot execute 
> qrexec-daemon.
> 
> Questions:
> 1) is anyone running Qubes 4.0-rc2 on a Lenovo X230?
> 2) is someone additionaly running Coreboot?
> 3) I am running the Qubes Installation with the default settings, any options 
> to tweak on the Grub command line
> 
> [799]
> 
> 
> 
> 
> 
> Gesendet von ProtonMail mobile



I just tried extending the qrexec-daemon timeout by another 60 seconds and that 
worked for me.

For me, it was my vault that refused to run.

qvm-prefs -s vault qrexec_timeout 120

and that worked.

-- 
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/3d6eafc5-e19a-4c45-ac25-6f2c084a174a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Seeking a Localization Team co-leader

[Andrew David Wong]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi all,

We'd like to put out another call for volunteer Localization Team
co-leaders. Tobias is currently away from email, so if you're
interested in helping out in this area, please let me know.

Best,
Andrew

On 2017-07-08 12:12, Andrew David Wong wrote:
> Dear Qubes Community,
> 
> We're looking for someone to join Tobias  as 
> co-leader of the Qubes localization team. If you're interested in 
> this position, please let us know.
> 
> You can learn more about our ongoing localization efforts from 
> these sources:
> 
> https://www.transifex.com/otf/qubes/ 
> https://github.com/QubesOS/qubes-issues/issues/2824 
> https://github.com/QubesOS/qubes-issues/issues/2652 
> https://github.com/QubesOS/qubes-issues/issues/1452 
> https://github.com/QubesOS/qubes-issues/issues/2599 
> https://github.com/QubesOS/qubes-issues/issues/1333
> 
> Please feel free to reply to this thread with any questions, and 
> Tobias will be happy to answer them.
> 

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

iQIcBAEBCgAGBQJZ8VKcAAoJENtN07w5UDAwubMQAIwfoh27MUyHU3TKVXC/6xnf
PC+Ih3PyAyxOHGaBTU9GB3I3VHalPAMuoMZ5qTxCdD6vIxb7ypG176yTpxRU6JjJ
EJ2BobN9+WmT8WwklmlWU8exRfBB9V5wxfDFApTsqw+wokdH1SMWxOfGRSD411v/
m/LyIiTcjTojW2Bbd+fB3AcoBehbZTv5n+grftZopxkY1RBCQrN4FkiIT5X4lAoE
10aFjqDFGLxw4ECfR0PbjlaZuPW3XHv8/QkP7BdZSOBkI3lcVenXEIMzGHvRaMXn
rOnT+UPtiakwg1QxPEmEK793BhpAX3Y2Gvm62CSpKjerxPgP+6M5QgV294EwNEBg
RrcRZHhHGj1pQyE2cjRroEIrbmuPdEB9TZp9Z96mT0T/9+GaelXdlX0/lI7UTVz0
vWRQte6xKD/t5wwKROYR1ImIu6aUtXpmYgIMQhz/CpKPkOvznMajyS7h96iqa1H3
Dux+pog487aIMRAcqaP3+dltlJJOQQ0ysmYO2PrA5+npIokZLW7Pzp3woFeJSTuV
QpGo3GdnBj4U1r1qaVmwgkzejrf/skNS5UFYt3IsTFf8soBLRg8MNCTRjkNyB4AP
EqDFFGiNlEAOSF2p7d73c5Fal2yFUxhsCBRUaMehsRHxNrHDsaNr9BK+1bIDtTk+
TTUnmBDdSahEq5MZQgg/
=pu8a
-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/2a7119c9-71f4-e32c-55a8-b8dc3196ae2a%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Logitech C920 Webcam with Qubes?

[cooloutac]

On Tuesday, October 24, 2017 at 1:42:25 PM UTC-4, evo wrote:
> ... do nobody has any USB webcam in use with qubes???
> 
> it shows me on sys-usb (lsusb) that the webcam is attached, but i can
> not find it over attach/detach devices and i have no idea, how can i
> mount it on another VM.

how exactly did you attach it?  I think you have to do the single device method 
or the whole controller.

-- 
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/cbf3e41a-e166-47b1-b30c-48e69a8a441b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Sub-menus using xfce4

[cooloutac]

On Wednesday, October 25, 2017 at 8:50:56 PM UTC-4, cooloutac wrote:
> On Wednesday, October 25, 2017 at 7:53:46 PM UTC-4, Sam Hentschel wrote:
> > I am trying to make a VM that is going to have a lot of applications.  I
> > would like to be able to put these applications into groups (sub-menus)
> > in the main qubes menu using xfce4.
> > 
> > I've looked at the xfce wiki[1] on working with their menus, tried
> > everything they recommended and could not get it to work. 
> > 
> > If it is not possible in Qubes 3.2, would it be plausible in Qubes 4.0?
> > 
> > [1] https://wiki.xfce.org/howto/customize-menu
> > 
> > -- 
> > Respectfully,
> > Sam Hentschel
> > FD6A 2998 5301 B440 D26B
> > 7040 69D1 CE58 6FA5 BB5A
> 
> I've had this problem with xfce too,  something I took for granted with kde 
> which I miss now.

you could install kde,  although its not actually supported,  I don't think.

-- 
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/6f8711ea-91ba-40d4-8f23-9fa5b8796580%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Sub-menus using xfce4

[cooloutac]

On Wednesday, October 25, 2017 at 7:53:46 PM UTC-4, Sam Hentschel wrote:
> I am trying to make a VM that is going to have a lot of applications.  I
> would like to be able to put these applications into groups (sub-menus)
> in the main qubes menu using xfce4.
> 
> I've looked at the xfce wiki[1] on working with their menus, tried
> everything they recommended and could not get it to work. 
> 
> If it is not possible in Qubes 3.2, would it be plausible in Qubes 4.0?
> 
> [1] https://wiki.xfce.org/howto/customize-menu
> 
> -- 
> Respectfully,
> Sam Hentschel
> FD6A 2998 5301 B440 D26B
> 7040 69D1 CE58 6FA5 BB5A

I've had this problem with xfce too,  something I took for granted with kde 
which I miss 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 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/5fec49f9-a1d3-4364-aabf-250f644dbf16%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Sub-menus using xfce4

[Sam Hentschel]

I am trying to make a VM that is going to have a lot of applications.  I
would like to be able to put these applications into groups (sub-menus)
in the main qubes menu using xfce4.

I've looked at the xfce wiki[1] on working with their menus, tried
everything they recommended and could not get it to work. 

If it is not possible in Qubes 3.2, would it be plausible in Qubes 4.0?

[1] https://wiki.xfce.org/howto/customize-menu

-- 
Respectfully,
Sam Hentschel
FD6A 2998 5301 B440 D26B
7040 69D1 CE58 6FA5 BB5A

-- 
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/20171025235332.GA993%40Personal-Email.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: PGP signature

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

[mouerta]

can you see if this can help : 
https://github.com/QubesOS/qubes-issues/issues/3133

-- 
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/e9da6e33-071b-4c54-bd0b-91dab78d6047%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

['[799]' via qubes-users]

>> I've made a clean install of Qubes 4-rc2
>> but ~70% of the time I can't boot the VMs

After 2h troubleshooting I deleted my whole setup and reinstalled, again 
running into problems when trying to create new VMs.
... Ahrk. I. Hate. Linux. (From time to time).

Seriously, I burned now ~2h trying to get Qubes 4 running. Can't be that hard 
for a user who is running Qubes for ~2y.

Question:
Can we get an information on which laptops/Modells Qubes 4-rc2 has been tested?
Currently I don't know if I just to dumb to get things up and running or if my 
hardware has a problem.
As I have already invested lots of time in Qubes 4 rc1 before abandoning it and 
go back to 3.2, I just don't want to burn any time in case that my hardware is 
a dead horse.

Having the information on which laptops Qubes 4 "should" run or even more where 
it is running (Dev Users?) would help.
The HCL https://www.qubes-os.org/hcl/ does not help me, as it has no 
information if 4.x is ok for the X230.

As mentioned before I am running Coreboot, should I go back to stock ROM?

[799]
I need to

. > > This includes sys-net, sys-firewall, but also . > > > > I tried to check 
the logs but I don't get any valuable information. > > See screenshot. > > > > 
I started the following command in dom0: > > > > watch -n 1 xl list > > > > 
When I try to launch a VM I can see that the VMs appears in the xl list output, 
but the State is -- and the Time(s) is 0.0. > > After ~30sec the start is 
aborted with error message: Cannot execute qrexec-daemon. > > > > Questions: > 
> 1) is anyone running Qubes 4.0-rc2 on a Lenovo X230? > > 2) is someone 
additionaly running Coreboot? > > 3) I am running the Qubes Installation with 
the default settings, any options to tweak on the Grub command line > > > > 
[799] > > > > > > > > > > > > Gesendet von ProtonMail mobile > Set pci strict 
reset on sys-net and sys-usb to false and try again. If that doesn't help set 
virt_mode to pv. If that helps it means your laptop does not meet minimum 
system requirements Same for me. It worked after a lot of restarting and 
changing settings. Sys-firewall started after I set initial ram higher. The 
others on debug mode with no network-vm set in settings. Not immediately 
though, try it, even change templates, and restart the templates a few times. I 
didn't get the qrexec logs from the qubes-applet and didn't bother to check 
further since it worked after several retries. -- 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/0326dd36-a12e-45f3-ad4e-ce89ad688772%40googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/-eRgdQDQFTTwNdHXLhB497Flh6HWeMHUfuTBAA87lVz-poaDrd2zQ03XH6EDMtIkEogtZwdx9nU07fLR3bmdjeM7oBjZui01iRGyQAZ7WCA%3D%40protonmail.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Qubes Security Bulletin #35: Xen hypervisor issue related to grant tables (XSA-236)

[Marek Marczykowski-Górecki]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear Qubes Community,

We have published Qubes Security Bulletin (QSB) #35:
Xen hypervisor issue related to grant tables (XSA-236).
The text of this QSB is reproduced below. This QSB and its accompanying
signatures will always be available in the Qubes Security Pack (qubes-secpack).

View QSB #35 in the qubes-secpack:



Learn about the qubes-secpack, including how to obtain, verify, and read it:



View all past QSBs:



View XSA-236 in the XSA Tracker:





```
 ---===[ Qubes Security Bulletin #35 ]===---

  October 24, 2017


 Xen hypervisor issue related to grant tables (XSA-236)

Summary


The Xen Security Team has published Xen Security Advisory 236, which
concerns an issue with the grant tables mechanism used to share memory
between domains. The practical impact of this advisory is believed to
be denial of service only. However, privilege escalation and information
leaks are theoretically possible.

Technical details
==

Xen Security Advisory 236 [1]:

| Grant copying code made an implication that any grant pin would be
| accompanied by a suitable page reference.  Other portions of code,
| however, did not match up with that assumption.  When such a grant
| copy operation is being done on a grant of a dying domain, the
| assumption turns out wrong.
|
| A malicious guest administrator can cause hypervisor memory
| corruption, most likely resulting in host crash and a Denial of
| Service.  Privilege escalation and information leaks cannot be ruled
| out.

Compromise Recovery


Beginning with Qubes 3.2, we offer Paranoid Backup Restore Mode, which
was designed specifically to aid in the recovery of a potentially
compromised Qubes OS system. If you believe your system may be
compromised (perhaps because of the issue discussed in this bulletin),
please read and follow the procedure described here:

https://www.qubes-os.org/news/2017/04/26/qubes-compromise-recovery/

Patching
=

The specific packages that resolve the problem discussed in this
bulletin are as follows:

  For Qubes 3.2:
  - Xen packages, version 4.6.6-34

  For Qubes 4.0:
  - Xen packages, version 4.8.2-9

The packages are to be installed in dom0 via the Qubes VM Manager or via
the qubes-dom0-update command as follows:

  For updates from the stable repository (not immediately available):
  $ sudo qubes-dom0-update

  For updates from the security-testing repository:
  $ sudo qubes-dom0-update --enablerepo=qubes-dom0-security-testing

A system restart will be required afterwards.

These packages will migrate from the security-testing repository to the
current (stable) repository over the next two weeks after being tested
by the community.

If you use Anti Evil Maid, you will need to reseal your secret
passphrase to new PCR values, as PCR18+19 will change due to the new
Xen binaries.

Credits


See the original Xen Security Advisory.

References
===

[1] https://xenbits.xen.org/xsa/advisory-236.html

- --
The Qubes Security Team
https://www.qubes-os.org/security/
```

- -- 
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBCAAGBQJZ8CgsAAoJENuP0xzK19csZuMH/3UJBpIVxZVbeX+x+dwpehjo
EBREIxWAFsJmygOHTgjgmu0RZEY1j3993BV4+O4oX7mAn8cLmpwTb/mYqVK3G2La
adMX4PKKBBaQPOsBL44QWGJjOQeZQm9Q9uvl41H1mThvOsfk8s0kVWnENdPOm6t6
gx8Oy4BklD/2z6TkWDilxkF+8I24QuMR1UMAjwEuKZdD37jO9k4vEaD9fjIUWuxt
hze20DgQypbDj1nm8VeINN3QULTNMv9LcItwnJ5v949VYW+actopaBaFmsv2lDrw
Jvb2ipB+XXDSe4zRQZsgGsY9KfJkvdTCGVRhHGOMeocncyRKm48j5NWAZRp5iLE=
=GPn4
-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/20171025210951.GE2882%40mail-itl.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Qubes 4.0rc2

[Roy Bernat]

On Wednesday, 25 October 2017 16:26:47 UTC-4, Jon Solworth  wrote:
> Clock not set correctly.  Isn't qubes supposed
> to run ntp?
> 
> thanks,
> Jon

you can set it by your self . right click on the clock and properties and 
choose your country . 

Roy

-- 
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/18d01feb-db7a-4961-9a66-f05fd5a0a62c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Qubes 4.0rc2

[Jon Solworth]

Clock not set correctly.  Isn't qubes supposed
to run ntp?

thanks,
Jon

-- 
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/c8aa351e-4140-42e5-981d-091129a4c33c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Windows 10 guest support

[Roy Bernat]

On Tuesday, 24 October 2017 10:11:23 UTC-4, tine@gmail.com  wrote:
> Hello,
> 
> I would like to know if there are any plans for better Windows (10) support 
> in the upcoming 4.X version?
> 
> I really appreciate your work, but currently this is preventing me to use 
> Qubes as the daily driver.
> 
> Best regards, Tine

In my point of view bring you own laptop inside secure lan is the worst thing 
as CTO i will want .  
1. email - browser
2. rdp - remmina 
3. libre office doing the job . 


you will create appvm that will be completely isolate from the internet with 
all the apps i mentioned with specific sys-net and firewall for the office only 
. 

Moving from windows at start seems to be very hard . after you will do your 
first step you will never want to go back .:) 

Roy 

-- 
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/3c1320b3-d84e-42cb-9f3c-a0aa7a252b58%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Windows 10 guest support (in Qubes 4.x)?

[joeviocoe]

On Wednesday, 25 October 2017 15:59:47 UTC-4, Yethal  wrote:
> 
> Code is on GitHub, nothing's stopping you from forking/sending a pull request

Please refrain from "just do it yourself" responses in the Qubes-Users group 
forum.  
People here are not developers, which has its own group forum.  This is why the 
original post ended with, "...raise some funding so that a capable developer 
can work on this topic."

-- 
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/d60b506e-201c-4042-ba6b-e66799ed9950%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Windows 10 guest support (in Qubes 4.x)?

[Yethal]

W dniu środa, 25 października 2017 20:13:17 UTC+2 użytkownik Ted Brenner 
napisał:
> On Wed, Oct 25, 2017 at 2:01 AM, '[799]' via qubes-users 
>  wrote:
> Hello Tine,
> 
> >> I would like to know if there are any plans for
> >> better Windows (10) support in the
> >> upcoming 4.X version? 
> 
> I have the same question regarding the future strategy for windows support:
> 
> - will we see Windows 10 support in Qubes 3.2?
> (Not relevant as Qubes 3.2 will become EOL)
> 
> - what about windows 7 and 10 support in Qubes 4.0?
> 
> With "supported" I mean that we'll have Qubes Tools available and maybe the 
> option to use seamless mode.
> 
> In the past I read about Windows Support for windows 8.1 which I think is not 
> relevant as most people run either Windows 7 or 10.
> Looking at my customers I have not a single customer who is running windows 
> 8.x (for a good reason).
> 
> To Qubes Dev's
> 
> I really think the Qubes Dev-Team should be honest and transparent about 
> Qubes Windows Support - maybe answering the question if they are working on 
> this at all, or if Windows on Qubes is more like another project which is out 
> of scope of the Qubes Dev Team as they are mainly focussing on the Qubes 
> (Core) OS themselves (which I would totally understand).
> 
> >> I really appreciate your work, but currently
> >> this is preventing me to use Qubes as the
> >> daily driver
> 
> As you said I need to run windows for my daily workflow and would really like 
> to do so in Qubes.
> I guess there are more users who work in Enterprise environments (as 
> non-developers) where windows is basically the default OS where lots of 
> applications are running.
> One example is that lots of my work is done on Outlook (Exchange 2016) and I 
> have not been able to get this done with Linux.
> 
> I think it would be good to know how many users are asking for windows on 
> Qubes and maybe raise some funding so that a capable developer can work on 
> this topic.
> 
> [799]
> 
> 
> 
> 
> 
> -- 
> 
> You received this message because you are subscribed to the Google Groups 
> "qubes-users" group.
> 
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to qubes-users...@googlegroups.com.
> 
> To post to this group, send email to qubes...@googlegroups.com.
> 
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/qubes-users/akE3h9OJmfmidm58UyS7FxK0sCUVtgRK__X6rHkfGjTeIQhvEp-ac2FROHm42zpJw5VLDDEeAj6PiXJP4-IBerWOnS46Pmzv_FbRadShsg0%3D%40protonmail.com.
> 
> For more options, visit https://groups.google.com/d/optout.
> 
> 
> I strongly suspect there isn't any work going on as I never see replies from 
> qubes dev on Windows questions, and there are a lot of them. Or at least it 
> is tabled for now till 4.0 is done. Perhaps it would be nice to open support 
> of the code to the community rather than having the Qubes team working on it 
> exclusively?
> 
> 
> -- 
> 
> Sent from my Desktop

Code is on GitHub, nothing's stopping you from forking/sending a pull request

-- 
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/0fb41fb3-4a28-4395-b6a2-4aced6a48cc4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: HCL Asrock AB350 Pro4 + Ryzen 5 1600 (Qubes R4)

[tjc . cornelius]

On Sunday, October 22, 2017 at 2:15:29 PM UTC+2, ma...@krysoft.cz wrote:
> Dne sobota 2. září 2017 11:32:04 UTC+2 Foppe de Haan napsal(a):
> > works
> 
> Hi, works with this gpu card out-of-the-box?

Hi, have you gotten it to work? I'm stuck with " X startup failed, aborting 
installation " message. :(

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/5d7ee6b9-d969-4eec-8704-2d6cf144f3f1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: HCL Asrock AB350 Pro4 + Ryzen 5 1600 (Qubes R4)

[tjc . cornelius]

On Saturday, September 2, 2017 at 11:32:04 AM UTC+2, Foppe de Haan wrote:
> works

Hoi Foppe,

Zou je mij kunnen helpen.. Het werkt niet bij.
Ik zie een melding " X startup failed, aborting installation" 

Alvast bedankt
Timo

-- 
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/343efc75-a5d7-4d95-84d3-133fcab66348%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Windows 10 guest support

[Roy Bernat]

On Tuesday, 24 October 2017 10:11:23 UTC-4, tine@gmail.com  wrote:
> Hello,
> 
> I would like to know if there are any plans for better Windows (10) support 
> in the upcoming 4.X version?
> 
> I really appreciate your work, but currently this is preventing me to use 
> Qubes as the daily driver.
> 
> Best regards, Tine

why it is prevent ?
90% i can do from qubes . 

next 10 % use remote machine . 

-- 
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/e8558443-ea4c-4ad6-8e0b-53e5b8dbf313%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Qubes 4.0 RC1/2, USB VM Pool Shows Up In Device Tray:

[tharrisone]

I have setup an external drive as a vm pool, and it has a vm setup as well. I 
have /etc/fstab setup to automount the drive. Even though the drive is mounted 
by dom0 it still shows up in the device tray list.

How can I make this device off limits to everything but dom0 so it does not 
show up in the device list?

-- 
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/f15813b6-a3e7-4e6a-856e-3ccaf532bb9a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Windows 10 guest support (in Qubes 4.x)?

[msgheap]

On Thursday, October 26, 2017 at 1:13:17 AM UTC+7, Ted Brenner wrote:
> On Wed, Oct 25, 2017 at 2:01 AM, '[799]' via qubes-users 
>  wrote:
> Hello Tine,
> 
> >> I would like to know if there are any plans for
> >> better Windows (10) support in the
> >> upcoming 4.X version? 
> 
> I have the same question regarding the future strategy for windows support:
> 
> - will we see Windows 10 support in Qubes 3.2?
> (Not relevant as Qubes 3.2 will become EOL)
> 
> - what about windows 7 and 10 support in Qubes 4.0?
> 
> With "supported" I mean that we'll have Qubes Tools available and maybe the 
> option to use seamless mode.
> 
> In the past I read about Windows Support for windows 8.1 which I think is not 
> relevant as most people run either Windows 7 or 10.
> Looking at my customers I have not a single customer who is running windows 
> 8.x (for a good reason).
> 
> To Qubes Dev's
> 
> I really think the Qubes Dev-Team should be honest and transparent about 
> Qubes Windows Support - maybe answering the question if they are working on 
> this at all, or if Windows on Qubes is more like another project which is out 
> of scope of the Qubes Dev Team as they are mainly focussing on the Qubes 
> (Core) OS themselves (which I would totally understand).
> 
> >> I really appreciate your work, but currently
> >> this is preventing me to use Qubes as the
> >> daily driver
> 
> As you said I need to run windows for my daily workflow and would really like 
> to do so in Qubes.
> I guess there are more users who work in Enterprise environments (as 
> non-developers) where windows is basically the default OS where lots of 
> applications are running.
> One example is that lots of my work is done on Outlook (Exchange 2016) and I 
> have not been able to get this done with Linux.
> 
> I think it would be good to know how many users are asking for windows on 
> Qubes and maybe raise some funding so that a capable developer can work on 
> this topic.
> 
> [799]
> 
> 
> 
> 
> 
> -- 
> 
> You received this message because you are subscribed to the Google Groups 
> "qubes-users" group.
> 
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to qubes-users...@googlegroups.com.
> 
> To post to this group, send email to qubes...@googlegroups.com.
> 
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/qubes-users/akE3h9OJmfmidm58UyS7FxK0sCUVtgRK__X6rHkfGjTeIQhvEp-ac2FROHm42zpJw5VLDDEeAj6PiXJP4-IBerWOnS46Pmzv_FbRadShsg0%3D%40protonmail.com.
> 
> For more options, visit https://groups.google.com/d/optout.
> 
> 
> I strongly suspect there isn't any work going on as I never see replies from 
> qubes dev on Windows questions, and there are a lot of them. Or at least it 
> is tabled for now till 4.0 is done. Perhaps it would be nice to open support 
> of the code to the community rather than having the Qubes team working on it 
> exclusively?
> 
> 
> -- 
> 
> Sent from my Desktop

https://github.com/QubesOS/qubes-issues/issues/1861#issuecomment-284584315

-- 
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/3ee683a8-4ddb-4d91-8f89-96434cafc83b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Windows 10 guest support (in Qubes 4.x)?

[Ted Brenner]

On Wed, Oct 25, 2017 at 2:01 AM, '[799]' via qubes-users <
qubes-users@googlegroups.com> wrote:

> Hello Tine,
>
> >> I would like to know if there are any plans for
> >> better Windows (10) support in the
> >> upcoming 4.X version?
>
> I have the same question regarding the future strategy for windows support:
>
> - will we see Windows 10 support in Qubes 3.2?
> (Not relevant as Qubes 3.2 will become EOL)
>
> - what about windows 7 and 10 support in Qubes 4.0?
>
> With "supported" I mean that we'll have Qubes Tools available and maybe
> the option to use seamless mode.
>
> In the past I read about Windows Support for windows 8.1 which I think is
> not relevant as most people run either Windows 7 or 10.
> Looking at my customers I have not a single customer who is running
> windows 8.x (for a good reason).
>
> To Qubes Dev's
> 
> I really think the Qubes Dev-Team should be honest and transparent about
> Qubes Windows Support - maybe answering the question if they are working on
> this at all, or if Windows on Qubes is more like another project which is
> out of scope of the Qubes Dev Team as they are mainly focussing on the
> Qubes (Core) OS themselves (which I would totally understand).
>
> >> I really appreciate your work, but currently
> >> this is preventing me to use Qubes as the
> >> daily driver
>
> As you said I need to run windows for my daily workflow and would really
> like to do so in Qubes.
> I guess there are more users who work in Enterprise environments (as
> non-developers) where windows is basically the default OS where lots of
> applications are running.
> One example is that lots of my work is done on Outlook (Exchange 2016) and
> I have not been able to get this done with Linux.
>
> I think it would be good to know how many users are asking for windows on
> Qubes and maybe raise some funding so that a capable developer can work on
> this topic.
>
> [799]
>
> --
> You received this message because you are subscribed to the Google Groups
> "qubes-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to qubes-users+unsubscr...@googlegroups.com.
> To post to this group, send email to qubes-users@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/qubes-users/akE3h9OJmfmidm58UyS7FxK0sCUVtgRK__X6rHkfGjTeIQhvEp-
> ac2FROHm42zpJw5VLDDEeAj6PiXJP4-IBerWOnS46Pmzv_FbRadShsg0%3D%
> 40protonmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

I strongly suspect there isn't any work going on as I never see replies
from qubes dev on Windows questions, and there are a lot of them. Or at
least it is tabled for now till 4.0 is done. Perhaps it would be nice to
open support of the code to the community rather than having the Qubes team
working on it exclusively?

-- 
Sent from my Desktop

-- 
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/CANKZutwyw7%2BZY3JUtyf-GXgMM%3D_HypyUKs4%2BxgrZjmSzTJCFvw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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

[mikihonzero]

On Wednesday, October 25, 2017 at 5:48:38 PM UTC, Yethal wrote:
> W dniu środa, 25 października 2017 19:26:51 UTC+2 użytkownik [799] napisał:
> > Hello,
> > 
> > As at least one other Qubes user has the same problem, that VMs won't 
> > start, I'll add this as special topic.
> > 
> > I've made a clean install of Qubes 4-rc2 but ~70% of the time I can't boot 
> > the VMs.
> > This includes sys-net, sys-firewall, but also others.
> > 
> > I tried to check the logs but I don't get any valuable information.
> > See screenshot.
> > 
> > I started the following command in dom0:
> > 
> > watch -n 1 xl list
> > 
> > When I try to launch a VM I can see that the VMs appears in the xl list 
> > output, but the State is -- and the Time(s) is 0.0.
> > After ~30sec the start is aborted with error message: Cannot execute 
> > qrexec-daemon.
> > 
> > Questions:
> > 1) is anyone running Qubes 4.0-rc2 on a Lenovo X230?
> > 2) is someone additionaly running Coreboot?
> > 3) I am running the Qubes Installation with the default settings, any 
> > options to tweak on the Grub command line
> > 
> > [799]
> > 
> > 
> > 
> > 
> > 
> > Gesendet von ProtonMail mobile
> Set pci strict reset on sys-net and sys-usb to false and try again. If that 
> doesn't help set virt_mode to pv. If that helps it means your laptop does not 
> meet minimum system requirements

Same for me. It worked after a lot of restarting and changing settings.
Sys-firewall started after I set initial ram higher. The others on debug mode 
with no network-vm set in settings. Not immediately though, try it, even change 
templates, and restart the templates a few times.
I didn't get the qrexec logs from the qubes-applet and didn't bother to check 
further since it worked after several retries.

-- 
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/0326dd36-a12e-45f3-ad4e-ce89ad688772%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

['[799]' via qubes-users]

Hello,

>> Set pci strict reset on sys-net and sys-usb to
>> false and try again. If that doesn't help set
>> virt_mode to pv

qvm-prefs -s sys-usb pci_strictreset false

Results in:

qvm-prefs: error: no such property: 'pci_strictreset'

Has the setting be changed in Qubes 4? Same question has been asked by me for 
the internal setting, which hides VM from the menu.

[799]

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/9xauEp9fAThnlIDOtfnH7OJUBjhrIT3yaFh_ICk5vN8BtRZP0rLLQ3SicgLoKw9O0gRYZw_e1ZJnxESd6cshQlynsclsTJqCVCRkRzz2Awk%3D%40protonmail.com.
For more options, visit https://groups.google.com/d/optout.

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

[Yethal]

W dniu środa, 25 października 2017 19:26:51 UTC+2 użytkownik [799] napisał:
> Hello,
> 
> As at least one other Qubes user has the same problem, that VMs won't start, 
> I'll add this as special topic.
> 
> I've made a clean install of Qubes 4-rc2 but ~70% of the time I can't boot 
> the VMs.
> This includes sys-net, sys-firewall, but also others.
> 
> I tried to check the logs but I don't get any valuable information.
> See screenshot.
> 
> I started the following command in dom0:
> 
> watch -n 1 xl list
> 
> When I try to launch a VM I can see that the VMs appears in the xl list 
> output, but the State is -- and the Time(s) is 0.0.
> After ~30sec the start is aborted with error message: Cannot execute 
> qrexec-daemon.
> 
> Questions:
> 1) is anyone running Qubes 4.0-rc2 on a Lenovo X230?
> 2) is someone additionaly running Coreboot?
> 3) I am running the Qubes Installation with the default settings, any options 
> to tweak on the Grub command line
> 
> [799]
> 
> 
> 
> 
> 
> Gesendet von ProtonMail mobile
Set pci strict reset on sys-net and sys-usb to false and try again. If that 
doesn't help set virt_mode to pv. If that helps it means your laptop does not 
meet minimum system requirements

-- 
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/fd020f3a-7eae-4c5f-84e4-b2f0055d41d0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] R4rc2 libvirt error when attaching PCI USB controller using no-strict-reset=true

[Sonny Horton]

This thread shows where I started: 
https://groups.google.com/forum/#!topic/qubes-users/5IurMRKaViU

Original issue related to inability to start sys-net with PCI USB controllers 
attached.

Hardware info:
Dell Latitude E6420 - i5 that previously worked using R3.2
VT-x and VT-d are properly enabled
BRCM WiFi is disabled in BIOS


Attempting to attach both PCI USB controllers to sys-net using instructions 
provided in the other thread yields partial results.

qvm-pci a sys-net -o no-strict-reset=true --persistent dom0:00_1a.0

completes without error, but

qvm-pci a sys-net -o no-strict-reset=true --persistent dom0:00_1d.0

returns "Got empty response from qubesd.  See journalctl in dom0 for details."

The pertinent lines in journalctl are as follows:

-- Logs begin at Tue 2017-10-24 16:59:49 MST, end at Wed 2017-10-25 09:17:44 
MST. --
Oct 25 09:17:44 dom0 libvirtd[1468]: 2017-10-25 16:17:44.129+: 1495: error 
: libxlDomainAttachHostPCIDevice:3250 : internal error: libxenlight failed to 
attach pci device :00:1d.0
Oct 25 09:17:44 dom0 qubesd[1419]: unhandled exception while calling 
src=b'dom0' meth=b'admin.vm.device.pci.Attach' dest=b'sys-net' 
arg=b'dom0+00_1d.0' len(untrusted_payload)=36
Oct 25 09:17:44 dom0 qubesd[1419]: Traceback (most recent call last):
Oct 25 09:17:44 dom0 qubesd[1419]:   File 
"/usr/lib/python3.5/site-packages/qubes/api/__init__.py", line 262, in respond
Oct 25 09:17:44 dom0 qubesd[1419]: untrusted_payload=untrusted_payload)
Oct 25 09:17:44 dom0 qubesd[1419]:   File 
"/usr/lib64/python3.5/asyncio/futures.py", line 381, in __iter__
Oct 25 09:17:44 dom0 qubesd[1419]: yield self  # This tells Task to wait 
for completion.
Oct 25 09:17:44 dom0 qubesd[1419]:   File 
"/usr/lib64/python3.5/asyncio/tasks.py", line 310, in _wakeup
Oct 25 09:17:44 dom0 qubesd[1419]: future.result()
Oct 25 09:17:44 dom0 qubesd[1419]:   File 
"/usr/lib64/python3.5/asyncio/futures.py", line 294, in result
Oct 25 09:17:44 dom0 qubesd[1419]: raise self._exception
Oct 25 09:17:44 dom0 qubesd[1419]:   File 
"/usr/lib64/python3.5/asyncio/tasks.py", line 240, in _step
Oct 25 09:17:44 dom0 qubesd[1419]: result = coro.send(None)
Oct 25 09:17:44 dom0 qubesd[1419]:   File 
"/usr/lib/python3.5/site-packages/qubes/api/admin.py", line 1109, in 
vm_device_attach
Oct 25 09:17:44 dom0 qubesd[1419]: yield from 
self.dest.devices[devclass].attach(assignment)
Oct 25 09:17:44 dom0 qubesd[1419]:   File 
"/usr/lib/python3.5/site-packages/qubes/devices.py", line 255, in attach
Oct 25 09:17:44 dom0 qubesd[1419]: device=device, 
options=device_assignment.options)
Oct 25 09:17:44 dom0 qubesd[1419]:   File 
"/usr/lib/python3.5/site-packages/qubes/events.py", line 229, in 
fire_event_async
Oct 25 09:17:44 dom0 qubesd[1419]: kwargs, pre_event=pre_event)
Oct 25 09:17:44 dom0 qubesd[1419]:   File 
"/usr/lib/python3.5/site-packages/qubes/events.py", line 164, in _fire_event
Oct 25 09:17:44 dom0 qubesd[1419]: effect = func(self, event, **kwargs)
Oct 25 09:17:44 dom0 qubesd[1419]:   File 
"/usr/lib/python3.5/site-packages/qubes/ext/pci.py", line 235, in 
on_device_pre_attached_pci
Oct 25 09:17:44 dom0 qubesd[1419]: device=device, vm=vm, options=options))
Oct 25 09:17:44 dom0 qubesd[1419]:   File 
"/usr/lib/python3.5/site-packages/qubes/app.py", line 94, in wrapper
Oct 25 09:17:44 dom0 qubesd[1419]: return attr(*args, **kwargs)
Oct 25 09:17:44 dom0 qubesd[1419]:   File 
"/usr/lib64/python3.5/site-packages/libvirt.py", line 563, in attachDevice
Oct 25 09:17:44 dom0 qubesd[1419]: if ret == -1: raise libvirtError 
('virDomainAttachDevice() failed', dom=self)
Oct 25 09:17:44 dom0 qubesd[1419]: libvirt.libvirtError: internal error: 
libxenlight failed to attach pci device :00:1d.0


Here's the output of qmv-pci ls:

dom0:00_00.0  Host bridge: Intel Corporation 2nd Generation Core Processor 
Family DRAM Controller
dom0:00_01.0  PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core 
Processor Family PCI Express Root Port  
dom0:00_16.0  Communication controller: Intel Corporation 6 Series/C200 Series 
Chipset Family MEI Controller #1  
dom0:00_19.0  Ethernet controller: Intel Corporation 82579LM Gigabit Network 
Connection (Lewisville) sys-net
dom0:00_1a.0  USB controller: Intel Corporation 6 Series/C200 Series Chipset 
Family USB Enhanced Host Controller #2  sys-net (no-strict-reset=true)
dom0:00_1b.0  Audio device: Intel Corporation 6 Series/C200 Series Chipset 
Family High Definition Audio Controller   
dom0:00_1c.0  PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family 
PCI Express Root Port 1  
dom0:00_1c.2  PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family 
PCI Express Root Port 3  
dom0:00_1c.3  PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family 
PCI Express Root Port 4  
dom0:00_1c.5  PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family 
PCI 

[qubes-users] Re: R4rc2 fresh install - sys-net won't start with PCI USB controllers attached.

[Sonny Horton]

On Wednesday, October 25, 2017 at 9:14:48 AM UTC-7, Darcy Brown wrote:
> On Wednesday, October 25, 2017 at 12:06:21 PM UTC-4, Sonny Horton wrote:
> > On Wednesday, October 25, 2017 at 8:34:04 AM UTC-7, Foppe de Haan wrote:
> > > On Wednesday, October 25, 2017 at 5:22:13 PM UTC+2, Sonny Horton wrote:
> > > > Hardware:  Dell Latitude E6420 - i5
> > > > BRCM on-board WiFi disabled in BIOS
> > > > VT-x and VT-d properly enabled in BIOS
> > > > Machine worked great with R3.2, including USB WiFi using Edimax/Realtek
> > > > 
> > > > Symptoms:
> > > > USB WiFi adapters (tried two) not properly detected during install
> > > > 
> > > > Attempting to start sys-net qube with either PCI USB controller 
> > > > attached results in error: "Start failed: internal error: libxenlight 
> > > > failed to create new domain 'sys-net'"
> > > > 
> > > > Actions taken:
> > > > Removed both PCI USB controllers from sys-net and sys-net will then 
> > > > start.  Tried adding them back singly (there are two) and sys-net will 
> > > > not start.
> > > > 
> > > > My issue appears to be closely related to this:  
> > > > https://www.qubes-os.org/doc/user-faq/#i-created-a-usbvm-and-assigned-usb-controllers-to-it-now-the-usbvm-wont-boot
> > > > 
> > > > The last several lines of my output of xl dmesg is identical to that 
> > > > noted on the FAQ page linked above, but adds more lines showing failure 
> > > > to attach either of the two controllers to a number of xen domains.
> > > > 
> > > > However, the FAQ says it is likely a USB3.0 issue, but this machine 
> > > > does not have USB3.0 and note that the controllers worked fine in R3.2.
> > > > 
> > > > I have not tried this solution: "qvm-prefs usbVM -s pci_strictreset 
> > > > false"  as my error message is different and, as noted above, these USB 
> > > > controllers worked fine in R3.2.  I also don't want to open up 
> > > > additional risks.
> > > > 
> > > > Thanks in advance for any assistance.  I am *somewhat* new to Qubes, 
> > > > but love it.
> > > > 
> > > > Sonny Horton
> > > 
> > > please disconnect them from the usbVM, then start the VM, and (re)attach 
> > > them using 'qvm-pci a usbVM -o no-strict-reset=true --persistent 
> > > dom0:0x_yy.z'
> > 
> > 
> > 
> > On Wednesday, October 25, 2017 at 8:34:04 AM UTC-7, Foppe de Haan wrote:
> > > On Wednesday, October 25, 2017 at 5:22:13 PM UTC+2, Sonny Horton wrote:
> > > > Hardware:  Dell Latitude E6420 - i5
> > > > BRCM on-board WiFi disabled in BIOS
> > > > VT-x and VT-d properly enabled in BIOS
> > > > Machine worked great with R3.2, including USB WiFi using Edimax/Realtek
> > > > 
> > > > Symptoms:
> > > > USB WiFi adapters (tried two) not properly detected during install
> > > > 
> > > > Attempting to start sys-net qube with either PCI USB controller 
> > > > attached results in error: "Start failed: internal error: libxenlight 
> > > > failed to create new domain 'sys-net'"
> > > > 
> > > > Actions taken:
> > > > Removed both PCI USB controllers from sys-net and sys-net will then 
> > > > start.  Tried adding them back singly (there are two) and sys-net will 
> > > > not start.
> > > > 
> > > > My issue appears to be closely related to this:  
> > > > https://www.qubes-os.org/doc/user-faq/#i-created-a-usbvm-and-assigned-usb-controllers-to-it-now-the-usbvm-wont-boot
> > > > 
> > > > The last several lines of my output of xl dmesg is identical to that 
> > > > noted on the FAQ page linked above, but adds more lines showing failure 
> > > > to attach either of the two controllers to a number of xen domains.
> > > > 
> > > > However, the FAQ says it is likely a USB3.0 issue, but this machine 
> > > > does not have USB3.0 and note that the controllers worked fine in R3.2.
> > > > 
> > > > I have not tried this solution: "qvm-prefs usbVM -s pci_strictreset 
> > > > false"  as my error message is different and, as noted above, these USB 
> > > > controllers worked fine in R3.2.  I also don't want to open up 
> > > > additional risks.
> > > > 
> > > > Thanks in advance for any assistance.  I am *somewhat* new to Qubes, 
> > > > but love it.
> > > > 
> > > > Sonny Horton
> > > 
> > > please disconnect them from the usbVM, then start the VM, and (re)attach 
> > > them using 'qvm-pci a usbVM -o no-strict-reset=true --persistent 
> > > dom0:0x_yy.z'
> > 
> > 
> > 
> > On Wednesday, October 25, 2017 at 8:34:04 AM UTC-7, Foppe de Haan wrote:
> > > On Wednesday, October 25, 2017 at 5:22:13 PM UTC+2, Sonny Horton wrote:
> > > > Hardware:  Dell Latitude E6420 - i5
> > > > BRCM on-board WiFi disabled in BIOS
> > > > VT-x and VT-d properly enabled in BIOS
> > > > Machine worked great with R3.2, including USB WiFi using Edimax/Realtek
> > > > 
> > > > Symptoms:
> > > > USB WiFi adapters (tried two) not properly detected during install
> > > > 
> > > > Attempting to start sys-net qube with either PCI USB controller 
> > > > attached results in error: "Start failed: internal error: libxenlight 
> > > > failed to create new domain 'sys-net'"

[qubes-users] R4rc2 debian-9 template not working at all

[Chris Laprise]

The debian-9 template appears to install OK, but neither it nor VMs 
based on it will start properly. The menu list contains only the "VM 
Settings" entry. Starting in debug mode the last thing I see in the 
console window is "Probing EDD...ok" then a much larger blank window 
opens. Then it will just sit like that forever.


The vm-debian-9.log says:
Starting debian-9
Setting Qubes DB info for the VM
Starting Qubes DB
Activating the debian-9 VM

In addition, all VMs (any template) are not starting consistently. There 
is < 50% success rate and I often have to try starting a second or third 
time.


--

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

--
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/f44a670d-85d3-58a3-794c-4c613a0b271b%40posteo.net.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: R4rc2 fresh install - sys-net won't start with PCI USB controllers attached.

[darcy]

On Wednesday, October 25, 2017 at 12:06:21 PM UTC-4, Sonny Horton wrote:
> On Wednesday, October 25, 2017 at 8:34:04 AM UTC-7, Foppe de Haan wrote:
> > On Wednesday, October 25, 2017 at 5:22:13 PM UTC+2, Sonny Horton wrote:
> > > Hardware:  Dell Latitude E6420 - i5
> > > BRCM on-board WiFi disabled in BIOS
> > > VT-x and VT-d properly enabled in BIOS
> > > Machine worked great with R3.2, including USB WiFi using Edimax/Realtek
> > > 
> > > Symptoms:
> > > USB WiFi adapters (tried two) not properly detected during install
> > > 
> > > Attempting to start sys-net qube with either PCI USB controller attached 
> > > results in error: "Start failed: internal error: libxenlight failed to 
> > > create new domain 'sys-net'"
> > > 
> > > Actions taken:
> > > Removed both PCI USB controllers from sys-net and sys-net will then 
> > > start.  Tried adding them back singly (there are two) and sys-net will 
> > > not start.
> > > 
> > > My issue appears to be closely related to this:  
> > > https://www.qubes-os.org/doc/user-faq/#i-created-a-usbvm-and-assigned-usb-controllers-to-it-now-the-usbvm-wont-boot
> > > 
> > > The last several lines of my output of xl dmesg is identical to that 
> > > noted on the FAQ page linked above, but adds more lines showing failure 
> > > to attach either of the two controllers to a number of xen domains.
> > > 
> > > However, the FAQ says it is likely a USB3.0 issue, but this machine does 
> > > not have USB3.0 and note that the controllers worked fine in R3.2.
> > > 
> > > I have not tried this solution: "qvm-prefs usbVM -s pci_strictreset 
> > > false"  as my error message is different and, as noted above, these USB 
> > > controllers worked fine in R3.2.  I also don't want to open up additional 
> > > risks.
> > > 
> > > Thanks in advance for any assistance.  I am *somewhat* new to Qubes, but 
> > > love it.
> > > 
> > > Sonny Horton
> > 
> > please disconnect them from the usbVM, then start the VM, and (re)attach 
> > them using 'qvm-pci a usbVM -o no-strict-reset=true --persistent 
> > dom0:0x_yy.z'
> 
> 
> 
> On Wednesday, October 25, 2017 at 8:34:04 AM UTC-7, Foppe de Haan wrote:
> > On Wednesday, October 25, 2017 at 5:22:13 PM UTC+2, Sonny Horton wrote:
> > > Hardware:  Dell Latitude E6420 - i5
> > > BRCM on-board WiFi disabled in BIOS
> > > VT-x and VT-d properly enabled in BIOS
> > > Machine worked great with R3.2, including USB WiFi using Edimax/Realtek
> > > 
> > > Symptoms:
> > > USB WiFi adapters (tried two) not properly detected during install
> > > 
> > > Attempting to start sys-net qube with either PCI USB controller attached 
> > > results in error: "Start failed: internal error: libxenlight failed to 
> > > create new domain 'sys-net'"
> > > 
> > > Actions taken:
> > > Removed both PCI USB controllers from sys-net and sys-net will then 
> > > start.  Tried adding them back singly (there are two) and sys-net will 
> > > not start.
> > > 
> > > My issue appears to be closely related to this:  
> > > https://www.qubes-os.org/doc/user-faq/#i-created-a-usbvm-and-assigned-usb-controllers-to-it-now-the-usbvm-wont-boot
> > > 
> > > The last several lines of my output of xl dmesg is identical to that 
> > > noted on the FAQ page linked above, but adds more lines showing failure 
> > > to attach either of the two controllers to a number of xen domains.
> > > 
> > > However, the FAQ says it is likely a USB3.0 issue, but this machine does 
> > > not have USB3.0 and note that the controllers worked fine in R3.2.
> > > 
> > > I have not tried this solution: "qvm-prefs usbVM -s pci_strictreset 
> > > false"  as my error message is different and, as noted above, these USB 
> > > controllers worked fine in R3.2.  I also don't want to open up additional 
> > > risks.
> > > 
> > > Thanks in advance for any assistance.  I am *somewhat* new to Qubes, but 
> > > love it.
> > > 
> > > Sonny Horton
> > 
> > please disconnect them from the usbVM, then start the VM, and (re)attach 
> > them using 'qvm-pci a usbVM -o no-strict-reset=true --persistent 
> > dom0:0x_yy.z'
> 
> 
> 
> On Wednesday, October 25, 2017 at 8:34:04 AM UTC-7, Foppe de Haan wrote:
> > On Wednesday, October 25, 2017 at 5:22:13 PM UTC+2, Sonny Horton wrote:
> > > Hardware:  Dell Latitude E6420 - i5
> > > BRCM on-board WiFi disabled in BIOS
> > > VT-x and VT-d properly enabled in BIOS
> > > Machine worked great with R3.2, including USB WiFi using Edimax/Realtek
> > > 
> > > Symptoms:
> > > USB WiFi adapters (tried two) not properly detected during install
> > > 
> > > Attempting to start sys-net qube with either PCI USB controller attached 
> > > results in error: "Start failed: internal error: libxenlight failed to 
> > > create new domain 'sys-net'"
> > > 
> > > Actions taken:
> > > Removed both PCI USB controllers from sys-net and sys-net will then 
> > > start.  Tried adding them back singly (there are two) and sys-net will 
> > > not start.
> > > 
> > > My issue appears to be closely related to this:  
> > > 

[qubes-users] Re: R4rc2 fresh install - sys-net won't start with PCI USB controllers attached.

[Sonny Horton]

On Wednesday, October 25, 2017 at 9:06:21 AM UTC-7, Sonny Horton wrote:
> On Wednesday, October 25, 2017 at 8:34:04 AM UTC-7, Foppe de Haan wrote:
> > On Wednesday, October 25, 2017 at 5:22:13 PM UTC+2, Sonny Horton wrote:
> > > Hardware:  Dell Latitude E6420 - i5
> > > BRCM on-board WiFi disabled in BIOS
> > > VT-x and VT-d properly enabled in BIOS
> > > Machine worked great with R3.2, including USB WiFi using Edimax/Realtek
> > > 
> > > Symptoms:
> > > USB WiFi adapters (tried two) not properly detected during install
> > > 
> > > Attempting to start sys-net qube with either PCI USB controller attached 
> > > results in error: "Start failed: internal error: libxenlight failed to 
> > > create new domain 'sys-net'"
> > > 
> > > Actions taken:
> > > Removed both PCI USB controllers from sys-net and sys-net will then 
> > > start.  Tried adding them back singly (there are two) and sys-net will 
> > > not start.
> > > 
> > > My issue appears to be closely related to this:  
> > > https://www.qubes-os.org/doc/user-faq/#i-created-a-usbvm-and-assigned-usb-controllers-to-it-now-the-usbvm-wont-boot
> > > 
> > > The last several lines of my output of xl dmesg is identical to that 
> > > noted on the FAQ page linked above, but adds more lines showing failure 
> > > to attach either of the two controllers to a number of xen domains.
> > > 
> > > However, the FAQ says it is likely a USB3.0 issue, but this machine does 
> > > not have USB3.0 and note that the controllers worked fine in R3.2.
> > > 
> > > I have not tried this solution: "qvm-prefs usbVM -s pci_strictreset 
> > > false"  as my error message is different and, as noted above, these USB 
> > > controllers worked fine in R3.2.  I also don't want to open up additional 
> > > risks.
> > > 
> > > Thanks in advance for any assistance.  I am *somewhat* new to Qubes, but 
> > > love it.
> > > 
> > > Sonny Horton
> > 
> > please disconnect them from the usbVM, then start the VM, and (re)attach 
> > them using 'qvm-pci a usbVM -o no-strict-reset=true --persistent 
> > dom0:0x_yy.z'
> 
> 
> 
> On Wednesday, October 25, 2017 at 8:34:04 AM UTC-7, Foppe de Haan wrote:
> > On Wednesday, October 25, 2017 at 5:22:13 PM UTC+2, Sonny Horton wrote:
> > > Hardware:  Dell Latitude E6420 - i5
> > > BRCM on-board WiFi disabled in BIOS
> > > VT-x and VT-d properly enabled in BIOS
> > > Machine worked great with R3.2, including USB WiFi using Edimax/Realtek
> > > 
> > > Symptoms:
> > > USB WiFi adapters (tried two) not properly detected during install
> > > 
> > > Attempting to start sys-net qube with either PCI USB controller attached 
> > > results in error: "Start failed: internal error: libxenlight failed to 
> > > create new domain 'sys-net'"
> > > 
> > > Actions taken:
> > > Removed both PCI USB controllers from sys-net and sys-net will then 
> > > start.  Tried adding them back singly (there are two) and sys-net will 
> > > not start.
> > > 
> > > My issue appears to be closely related to this:  
> > > https://www.qubes-os.org/doc/user-faq/#i-created-a-usbvm-and-assigned-usb-controllers-to-it-now-the-usbvm-wont-boot
> > > 
> > > The last several lines of my output of xl dmesg is identical to that 
> > > noted on the FAQ page linked above, but adds more lines showing failure 
> > > to attach either of the two controllers to a number of xen domains.
> > > 
> > > However, the FAQ says it is likely a USB3.0 issue, but this machine does 
> > > not have USB3.0 and note that the controllers worked fine in R3.2.
> > > 
> > > I have not tried this solution: "qvm-prefs usbVM -s pci_strictreset 
> > > false"  as my error message is different and, as noted above, these USB 
> > > controllers worked fine in R3.2.  I also don't want to open up additional 
> > > risks.
> > > 
> > > Thanks in advance for any assistance.  I am *somewhat* new to Qubes, but 
> > > love it.
> > > 
> > > Sonny Horton
> > 
> > please disconnect them from the usbVM, then start the VM, and (re)attach 
> > them using 'qvm-pci a usbVM -o no-strict-reset=true --persistent 
> > dom0:0x_yy.z'
> 
> 
> 
> On Wednesday, October 25, 2017 at 8:34:04 AM UTC-7, Foppe de Haan wrote:
> > On Wednesday, October 25, 2017 at 5:22:13 PM UTC+2, Sonny Horton wrote:
> > > Hardware:  Dell Latitude E6420 - i5
> > > BRCM on-board WiFi disabled in BIOS
> > > VT-x and VT-d properly enabled in BIOS
> > > Machine worked great with R3.2, including USB WiFi using Edimax/Realtek
> > > 
> > > Symptoms:
> > > USB WiFi adapters (tried two) not properly detected during install
> > > 
> > > Attempting to start sys-net qube with either PCI USB controller attached 
> > > results in error: "Start failed: internal error: libxenlight failed to 
> > > create new domain 'sys-net'"
> > > 
> > > Actions taken:
> > > Removed both PCI USB controllers from sys-net and sys-net will then 
> > > start.  Tried adding them back singly (there are two) and sys-net will 
> > > not start.
> > > 
> > > My issue appears to be closely related to this:  
> > > 

[qubes-users] Re: R4rc2 fresh install - sys-net won't start with PCI USB controllers attached.

[Sonny Horton]

On Wednesday, October 25, 2017 at 8:34:04 AM UTC-7, Foppe de Haan wrote:
> On Wednesday, October 25, 2017 at 5:22:13 PM UTC+2, Sonny Horton wrote:
> > Hardware:  Dell Latitude E6420 - i5
> > BRCM on-board WiFi disabled in BIOS
> > VT-x and VT-d properly enabled in BIOS
> > Machine worked great with R3.2, including USB WiFi using Edimax/Realtek
> > 
> > Symptoms:
> > USB WiFi adapters (tried two) not properly detected during install
> > 
> > Attempting to start sys-net qube with either PCI USB controller attached 
> > results in error: "Start failed: internal error: libxenlight failed to 
> > create new domain 'sys-net'"
> > 
> > Actions taken:
> > Removed both PCI USB controllers from sys-net and sys-net will then start.  
> > Tried adding them back singly (there are two) and sys-net will not start.
> > 
> > My issue appears to be closely related to this:  
> > https://www.qubes-os.org/doc/user-faq/#i-created-a-usbvm-and-assigned-usb-controllers-to-it-now-the-usbvm-wont-boot
> > 
> > The last several lines of my output of xl dmesg is identical to that noted 
> > on the FAQ page linked above, but adds more lines showing failure to attach 
> > either of the two controllers to a number of xen domains.
> > 
> > However, the FAQ says it is likely a USB3.0 issue, but this machine does 
> > not have USB3.0 and note that the controllers worked fine in R3.2.
> > 
> > I have not tried this solution: "qvm-prefs usbVM -s pci_strictreset false"  
> > as my error message is different and, as noted above, these USB controllers 
> > worked fine in R3.2.  I also don't want to open up additional risks.
> > 
> > Thanks in advance for any assistance.  I am *somewhat* new to Qubes, but 
> > love it.
> > 
> > Sonny Horton
> 
> please disconnect them from the usbVM, then start the VM, and (re)attach them 
> using 'qvm-pci a usbVM -o no-strict-reset=true --persistent dom0:0x_yy.z'



On Wednesday, October 25, 2017 at 8:34:04 AM UTC-7, Foppe de Haan wrote:
> On Wednesday, October 25, 2017 at 5:22:13 PM UTC+2, Sonny Horton wrote:
> > Hardware:  Dell Latitude E6420 - i5
> > BRCM on-board WiFi disabled in BIOS
> > VT-x and VT-d properly enabled in BIOS
> > Machine worked great with R3.2, including USB WiFi using Edimax/Realtek
> > 
> > Symptoms:
> > USB WiFi adapters (tried two) not properly detected during install
> > 
> > Attempting to start sys-net qube with either PCI USB controller attached 
> > results in error: "Start failed: internal error: libxenlight failed to 
> > create new domain 'sys-net'"
> > 
> > Actions taken:
> > Removed both PCI USB controllers from sys-net and sys-net will then start.  
> > Tried adding them back singly (there are two) and sys-net will not start.
> > 
> > My issue appears to be closely related to this:  
> > https://www.qubes-os.org/doc/user-faq/#i-created-a-usbvm-and-assigned-usb-controllers-to-it-now-the-usbvm-wont-boot
> > 
> > The last several lines of my output of xl dmesg is identical to that noted 
> > on the FAQ page linked above, but adds more lines showing failure to attach 
> > either of the two controllers to a number of xen domains.
> > 
> > However, the FAQ says it is likely a USB3.0 issue, but this machine does 
> > not have USB3.0 and note that the controllers worked fine in R3.2.
> > 
> > I have not tried this solution: "qvm-prefs usbVM -s pci_strictreset false"  
> > as my error message is different and, as noted above, these USB controllers 
> > worked fine in R3.2.  I also don't want to open up additional risks.
> > 
> > Thanks in advance for any assistance.  I am *somewhat* new to Qubes, but 
> > love it.
> > 
> > Sonny Horton
> 
> please disconnect them from the usbVM, then start the VM, and (re)attach them 
> using 'qvm-pci a usbVM -o no-strict-reset=true --persistent dom0:0x_yy.z'



On Wednesday, October 25, 2017 at 8:34:04 AM UTC-7, Foppe de Haan wrote:
> On Wednesday, October 25, 2017 at 5:22:13 PM UTC+2, Sonny Horton wrote:
> > Hardware:  Dell Latitude E6420 - i5
> > BRCM on-board WiFi disabled in BIOS
> > VT-x and VT-d properly enabled in BIOS
> > Machine worked great with R3.2, including USB WiFi using Edimax/Realtek
> > 
> > Symptoms:
> > USB WiFi adapters (tried two) not properly detected during install
> > 
> > Attempting to start sys-net qube with either PCI USB controller attached 
> > results in error: "Start failed: internal error: libxenlight failed to 
> > create new domain 'sys-net'"
> > 
> > Actions taken:
> > Removed both PCI USB controllers from sys-net and sys-net will then start.  
> > Tried adding them back singly (there are two) and sys-net will not start.
> > 
> > My issue appears to be closely related to this:  
> > https://www.qubes-os.org/doc/user-faq/#i-created-a-usbvm-and-assigned-usb-controllers-to-it-now-the-usbvm-wont-boot
> > 
> > The last several lines of my output of xl dmesg is identical to that noted 
> > on the FAQ page linked above, but adds more lines showing failure to attach 
> > either of the two controllers to a number of xen 

[qubes-users] Re: R4rc2 fresh install - sys-net won't start with PCI USB controllers attached.

[Sonny Horton]

Thank you for the fast response.  I seem to need some help with the syntax of 
the device ID at the end of the command.

lspci shows me IDs of 00:1a.0 and 00:1d.0 for the controllers, but the qvm-pci 
command doesn't accept that ID prefaced with dom0: (i.e.: dom0:00:1a.0)...  I 
get the error "qvm-pci: error: backend vm 'dom0' doesn't expose device 
'00:1a.0'". 

I am sure I am misunderstanding something.

Thanks again for the help!

-- 
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/8a71edda-60c0-45b9-be6c-91fc8b152054%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Qubes Release 4.0-rc2 installation acpi error firmware bug

[mouerto]

i tried to install qubes 4.0 rc2 on Lenovo T440s thinkpad but i got errors ( i 
was using qubes 3.2 before with no problems ) here is the screenshots :

https://imgur.com/a/Lylq5

-- 
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/c4093c87-7692-44a6-9093-f697bd9bf535%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Wifi problems on recent updates

[dan]

On Tuesday, October 24, 2017 at 8:50:18 PM UTC-7, d...@mindstab.net wrote:
> I upgraded my netbook from Linux 4.4.67 to 4.9.35 and lost wifi ability on 
> it. I believe it was an Atheros chip using the ath9k driver. At least with it 
> I've been able to boot the old 4.4.67 kernel and retain wireless. 
> 
> This week I upgraded my laptop to 4.9.45 and it also lost wifi ability with 
> an Intel iwlwifi driver. And worse, booting old 4.4 kernels is not working 
> for it.
> 
> What data do I need to gather to help troubleshoot this and fix it?

On Net the NetworkManager log shows

(wlp0s0): using nl80211 for WiFi device Control
device (wlp0s0): driver supports Access Point (AP) mode
manager: (wlp0s0): new 802.11 WiFi device
device (wlp0s0): state change: unmanaged -> unavailable (reason 'managed') [10 
20 2]

More interestingly

# wpa_supplicant -Dnl80211 -iwlps0s0 -c/etc/wpa_supplicant/wpa_supplicant.conf
Succesfully initialized wpa_supplicant
rfkill: WLAN hard blocked

So, on my netbook, when it turned on, the wifi was always not quite right and I 
had to toggle via the via function keyboard key it to 'off' and then 'on' 
again. That not working could have been part of the problem under 4.9.35? 
But for this laptop, that had never been a problem, the wifi worked.
Still, I've tried now toggling it using the Wifi function key and no success

Sadly the rfkill command doesn't seem to be available in my dom0 or net vm

In net tried (after chmod u+w hard)
# echo 0  >  /sys/class/rfkill/rfkill0/hard
Error while writing to stdout
write_loop: Input/output error

-- 
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/7e2bb665-b5ab-4c88-818d-2661e1b7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: R4rc2 fresh install - sys-net won't start with PCI USB controllers attached.

[Foppe de Haan]

On Wednesday, October 25, 2017 at 5:22:13 PM UTC+2, Sonny Horton wrote:
> Hardware:  Dell Latitude E6420 - i5
> BRCM on-board WiFi disabled in BIOS
> VT-x and VT-d properly enabled in BIOS
> Machine worked great with R3.2, including USB WiFi using Edimax/Realtek
> 
> Symptoms:
> USB WiFi adapters (tried two) not properly detected during install
> 
> Attempting to start sys-net qube with either PCI USB controller attached 
> results in error: "Start failed: internal error: libxenlight failed to create 
> new domain 'sys-net'"
> 
> Actions taken:
> Removed both PCI USB controllers from sys-net and sys-net will then start.  
> Tried adding them back singly (there are two) and sys-net will not start.
> 
> My issue appears to be closely related to this:  
> https://www.qubes-os.org/doc/user-faq/#i-created-a-usbvm-and-assigned-usb-controllers-to-it-now-the-usbvm-wont-boot
> 
> The last several lines of my output of xl dmesg is identical to that noted on 
> the FAQ page linked above, but adds more lines showing failure to attach 
> either of the two controllers to a number of xen domains.
> 
> However, the FAQ says it is likely a USB3.0 issue, but this machine does not 
> have USB3.0 and note that the controllers worked fine in R3.2.
> 
> I have not tried this solution: "qvm-prefs usbVM -s pci_strictreset false"  
> as my error message is different and, as noted above, these USB controllers 
> worked fine in R3.2.  I also don't want to open up additional risks.
> 
> Thanks in advance for any assistance.  I am *somewhat* new to Qubes, but love 
> it.
> 
> Sonny Horton

please disconnect them from the usbVM, then start the VM, and (re)attach them 
using 'qvm-pci a usbVM -o no-strict-reset=true --persistent dom0:0x_yy.z'

-- 
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/e15c5e7d-4569-4526-8a5b-bd5c3a8fc621%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] R4rc2 fresh install - sys-net won't start with PCI USB controllers attached.

[Sonny Horton]

Hardware:  Dell Latitude E6420 - i5
BRCM on-board WiFi disabled in BIOS
VT-x and VT-d properly enabled in BIOS
Machine worked great with R3.2, including USB WiFi using Edimax/Realtek

Symptoms:
USB WiFi adapters (tried two) not properly detected during install

Attempting to start sys-net qube with either PCI USB controller attached 
results in error: "Start failed: internal error: libxenlight failed to create 
new domain 'sys-net'"

Actions taken:
Removed both PCI USB controllers from sys-net and sys-net will then start.  
Tried adding them back singly (there are two) and sys-net will not start.

My issue appears to be closely related to this:  
https://www.qubes-os.org/doc/user-faq/#i-created-a-usbvm-and-assigned-usb-controllers-to-it-now-the-usbvm-wont-boot

The last several lines of my output of xl dmesg is identical to that noted on 
the FAQ page linked above, but adds more lines showing failure to attach either 
of the two controllers to a number of xen domains.

However, the FAQ says it is likely a USB3.0 issue, but this machine does not 
have USB3.0 and note that the controllers worked fine in R3.2.

I have not tried this solution: "qvm-prefs usbVM -s pci_strictreset false"  as 
my error message is different and, as noted above, these USB controllers worked 
fine in R3.2.  I also don't want to open up additional risks.

Thanks in advance for any assistance.  I am *somewhat* new to Qubes, but love 
it.

Sonny Horton

-- 
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/e81464c1-67f5-4f92-833f-f9d71d88153b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Laptop 2nd Drive Qubes VM

[Andrew]

Outback Dingo:
> I have a complete 1TB SSD with Fedora 27 installed on my second disk
> would there be a way to launch that inside of Qubes as an AppVM?
> 
> I could ask about the 3rd drive also, being a full windows 10 install
> 

Did you try creating a standalone HVM, then replacing its root.img with
a symlink to /dev/sdb1?

Andrew

-- 
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/2fc50aeb-c5ce-d6b4-54b2-3c7168caac58%40riseup.net.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Laptop 2nd Drive Qubes VM

[blacklight]

As far as i know, you cannot boot them(unless thet are vms created in another 
qubes installation), you should be able to mount their drives and access the 
files though

-- 
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/8f9544e6-edda-46b1-b891-2ccf6ddf0688%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Use another Window Manager (awesome) with Qubes OS

[Outback Dingo]

On Friday, September 29, 2017 at 3:13:35 AM UTC-4, Jarle Thorsen wrote:
> torsdag 28. september 2017 20.09.10 UTC+2 skrev One7two99 følgende:
> > Hello Holger,
> > 
> > 
> > 
> > > I"ve been using awesome for almost 10 years and when I switched to Qubes
> > 
> > > half a year ago I wanted to continue using awesome, saw these 
> > > instructions and
> > 
> > > gave i3 a try. (Which is a simple as "sudo qubes-dom0-update 
> > > qubes-i3-settings", 
> > 
> > > logout, changing to i3 in the login manager and login in again.)
> > 
> > 
> > 
> > Thank you for the tip, I've watched some i3 videos and it looks good.
> > 
> > I'll give it a try. Just for info, the installation of i3 is possible via
> 
> As a former Awesome user I also now prefer the "simplicity" of i3.

Any possibilities Xmonad would also work i wonder, its quite nice

-- 
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/f85d66f7-e7fc-47c0-a4ef-c55c76acebee%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Laptop 2nd Drive Qubes VM

[Outback Dingo]

I have a complete 1TB SSD with Fedora 27 installed on my second disk
would there be a way to launch that inside of Qubes as an AppVM?

I could ask about the 3rd drive also, being a full windows 10 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/ebe5c7f1-2ea4-4106-8049-be5ce9bc2bf8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] HCL MetaBox P650RE / Clevo

[Outback Dingo]

working with wireless, no onboard nic pci conflicts someplace

-- 
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/286cc09f-279e-40a1-b730-60b9cafe774f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Qubes-HCL-Notebook-P65_P67RGRERA-20171025-082409.yml
Description: Binary data

AW: [qubes-users] Windows 10 guest support (in Qubes 4.x)?

['[799]' via qubes-users]

Hello Tine,

>> I would like to know if there are any plans for
>> better Windows (10) support in the
>> upcoming 4.X version?

I have the same question regarding the future strategy for windows support:

- will we see Windows 10 support in Qubes 3.2?
(Not relevant as Qubes 3.2 will become EOL)

- what about windows 7 and 10 support in Qubes 4.0?

With "supported" I mean that we'll have Qubes Tools available and maybe the 
option to use seamless mode.

In the past I read about Windows Support for windows 8.1 which I think is not 
relevant as most people run either Windows 7 or 10.
Looking at my customers I have not a single customer who is running windows 8.x 
(for a good reason).

To Qubes Dev's

I really think the Qubes Dev-Team should be honest and transparent about Qubes 
Windows Support - maybe answering the question if they are working on this at 
all, or if Windows on Qubes is more like another project which is out of scope 
of the Qubes Dev Team as they are mainly focussing on the Qubes (Core) OS 
themselves (which I would totally understand).

>> I really appreciate your work, but currently
>> this is preventing me to use Qubes as the
>> daily driver

As you said I need to run windows for my daily workflow and would really like 
to do so in Qubes.
I guess there are more users who work in Enterprise environments (as 
non-developers) where windows is basically the default OS where lots of 
applications are running.
One example is that lots of my work is done on Outlook (Exchange 2016) and I 
have not been able to get this done with Linux.

I think it would be good to know how many users are asking for windows on Qubes 
and maybe raise some funding so that a capable developer can work on this topic.

[799]

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/akE3h9OJmfmidm58UyS7FxK0sCUVtgRK__X6rHkfGjTeIQhvEp-ac2FROHm42zpJw5VLDDEeAj6PiXJP4-IBerWOnS46Pmzv_FbRadShsg0%3D%40protonmail.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Qubes 4.0-rc2 :: how to hide VMs from menu

['[799]' via qubes-users]

Hello,

Thanks to the Qubes-Team for releasing v4.0-rc2.
After having problems with my Lenovo X230 and 4.0rc1 I decided to wait for the 
next release and gave it a try yesterday.

I went through the installation process and booting up was fine, even when 
running Coreboot.

Some feedback:

1) I had to boot 2 times until the sys-net VM could launch network manager.

2) it feels like the starting of VMs is a slower than on Qubes 3.2.
My X230 has 16GB RAM and a 500GB SSD, i5-CPU, so I don't understand the light 
performance loss.

3) starting VMs fails occasionally:
The auto start of sys-firewall fails. I tried to manually start it and run a 
terminal with:

qvm-start sys-firewall && qvm-run --gui sys-firewall Gnome-Terminal

I see that the VM seems to start up (Qubes Icon on top right corner, shows a 
"progress circle icon" behind sys-firewall, but the start is aborted and I get 
an error message:
"cannot execute qrexec-daemon"

3) missing Feature:
It seems that is not possible to hide VMs from the startmenu as before.
In Qubes 3.2 there was the option in Qubes Manager "Internal" which would hide 
the VM.
It was also possible to use "qvm-prefs -s  internal true"
Please bring back this feature as it allows me to keep my list of VMs in the 
menu "clean and lean"

Any idea what I can do to fix 2)?

[799]

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/n_iu0nSlMteG489F6wQyfQIYYQRCtZEDHFzE_OmJuNONk82qzLBAa8wQMTJ5G68IILSCusUc4oEXGep2K3tLvWxyIKTuVsRYFjRSt1l9ytM%3D%40protonmail.com.
For more options, visit https://groups.google.com/d/optout.