[qubes-users] BIOS

2016-12-25 Thread Drew White 
Where would I put a BIOS for a VM?

I've tried to get one working, but I've been unsuccessful getting it to work.
I placed it with the other bios.bin and called it instead, but it did not 
appear to work.

Is it possible to use a ROM file instead?

-- 
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/f1e5a6c3-788b-4a1e-99c7-07ff14a607a9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Strategy: Qubes needs flexible automation more than other OSes due to its security-by-separation architecture: Should we initiate a cross-platform project?

2016-12-25 Thread @LeeteqXV (Twitter) 

On 23/12/16 09:43, Andrew David Wong wrote:

(Copying my reply from the other thread.)
You can simply change sys-firewall's NetVM to "none," restart sys-net,
then switch it back again. Sample script:

```
#!/bin/bash
echo "Restarting sys-net..."
qvm-prefs -s sys-firewall netvm none
sleep 3
qvm-shutdown sys-net
sleep 3
qvm-start sys-net
sleep 3
qvm-prefs -s sys-firewall netvm sys-net
sleep 1
echo "Done."
```

We don't need AI-level automation to solve this one. :)


Heh, so that was a bad example to throw into this suggestion, ok. :-)
Thanks for the script sample, will come in handy I think.

Regardless of this bad example, my suggestion stands:
I think there are good reasons / perspectives for why Qubes should 
consider taking this kind of initiative.


--
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/ae8dcdba-762e-04da-1b64-d604d5e33f09%40leeteq.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] How to Backup Qubes Using New USB Hard Drive

2016-12-25 Thread mojosam 
How to Backup Qubes Using New USB Hard Drive

I'd like to backup my VMs to an external USB hard drive.  I have a couple of 
questions not answered by these pages:


and


The drive is a new Seagate 1.5TB hard drive.  It's a tiny thing that gets its 
power off of the USB bus.  Apparently Seagate has already installed their 
backup program, which runs in both Mac and Windows.

If I'm going to use this drive, I assume that I want to delete that program and 
any other crapware that Seagate might have put on there.  Also, I don't know 
which disk format they're using.  I doubt it's something that Qubes or Linux 
would find ideal.

To start, where do I want to attach the drive?  Qubes has automatically 
attached it to Dom0, but I doubt that I want to format it from there.

Does one of the other VMs already have something like gparted installed, or 
will I need to download that?

What file format should I use?

I think that's the extent of my questions.  I might think of some more as I 
work through this process the first time.  Thank you for any insight or 
enlightenment you can provide.

-- 
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/9914fd12-378b-474a-8b28-f768fffe157e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] installing windows-tools inside React OS

2016-12-25 Thread a . mcwheel 
Well, windows-tools utility supports only Windows 7 at the moment. It doesn't 
support even Windows 8/10
Besides, ReactOS is NOT opensource Windows (I don't think it's gonna happened, 
Microsoft would never open sources for Windows) . It is binary-compartible with 
software and drivers made for Windows Server 2003.
I'm afraid for windows-tools to support ReactOS you should send feature request 
for windows-tools developers.
Probably, it is better idea to send feature request to ResctOS developers, to 
ask them to integrate ReactOS as Qubes TemplateVM.

On December 24, 2016 5:01:29 AM AEDT, tnt_bom_...@keemail.me wrote:
>i think most of us heard about React OS (which is like saying
>opensource windows) 
>
>the installation of React OS succeeded 
>torifying React OS with whonix-gw succeeded
>installing windows-tools failed (which is the only thing needed for it
>to complete the image)
>
>here is the log of windows-tools:- (also uploaded inside the text file)
>
>`[02FC:0300][2016-12-23T15:27:00]i001: Burn v3.9.1208.0, Windows v5.2
>(Build 3790: Service Pack 2), path: D:\qubes-tools-WIN7x64-3.2.2.3.exe,
>cmdline: ''
>[02FC:0300][2016-12-23T15:27:00]i000: Setting string variable
>'WixBundleLog' to value
>'C:\DOCUME~1\DEFAUL~1\LOCALS~1\Temp\Qubes_Windows_Tools_3.2.2.3_20161223152700.log'
>[02FC:0300][2016-12-23T15:27:00]i000: Setting string variable
>'WixBundleOriginalSource' to value 'D:\qubes-tools-WIN7x64-3.2.2.3.exe'
>[02FC:0300][2016-12-23T15:27:00]i000: Setting string variable
>'WixBundleOriginalSourceFolder' to value 'D:\'
>[02FC:0300][2016-12-23T15:27:00]i000: Setting string variable
>'WixBundleName' to value 'Qubes Windows Tools 3.2.2.3'
>[02FC:030C][2016-12-23T15:27:00]i000: Setting version variable
>'WixBundleFileVersion' to value '3.2.2.3'
>[02FC:0300][2016-12-23T15:27:00]i100: Detect begin, 2 packages
>[02FC:0300][2016-12-23T15:27:00]i101: Detected package:
>vcredist_x64.exe, state: Absent, cached: None
>[02FC:0300][2016-12-23T15:27:00]i101: Detected package:
>qubes_tools_WIN7x64_3.2.2.3.msi, state: Absent, cached: None
>[02FC:0300][2016-12-23T15:27:00]i104: Detected package:
>qubes_tools_WIN7x64_3.2.2.3.msi, feature: DisableUac, state: Absent
>[02FC:0300][2016-12-23T15:27:00]i104: Detected package:
>qubes_tools_WIN7x64_3.2.2.3.msi, feature: Common, state: Absent
>[02FC:0300][2016-12-23T15:27:00]i104: Detected package:
>qubes_tools_WIN7x64_3.2.2.3.msi, feature: Complete, state: Absent
>[02FC:0300][2016-12-23T15:27:00]i104: Detected package:
>qubes_tools_WIN7x64_3.2.2.3.msi, feature: XenBase, state: Absent
>[02FC:0300][2016-12-23T15:27:00]i104: Detected package:
>qubes_tools_WIN7x64_3.2.2.3.msi, feature: XenPvDrivers, state: Absent
>[02FC:0300][2016-12-23T15:27:00]i104: Detected package:
>qubes_tools_WIN7x64_3.2.2.3.msi, feature: XenDisk, state: Absent
>[02FC:0300][2016-12-23T15:27:00]i104: Detected package:
>qubes_tools_WIN7x64_3.2.2.3.msi, feature: XenNetwork, state: Absent
>[02FC:0300][2016-12-23T15:27:00]i104: Detected package:
>qubes_tools_WIN7x64_3.2.2.3.msi, feature: CoreAgent, state: Absent
>[02FC:0300][2016-12-23T15:27:00]i104: Detected package:
>qubes_tools_WIN7x64_3.2.2.3.msi, feature: MoveProfiles, state: Absent
>[02FC:0300][2016-12-23T15:27:00]i104: Detected package:
>qubes_tools_WIN7x64_3.2.2.3.msi, feature: GuiAgentWindows, state:
>Absent
>[02FC:0300][2016-12-23T15:27:00]i199: Detect complete, result: 0x0
>[02FC:030C][2016-12-23T15:27:02]i000: Setting numeric variable
>'EulaAcceptCheckbox' to value 1
>[02FC:0300][2016-12-23T15:27:02]i200: Plan begin, 2 packages, action:
>Install
>[02FC:0300][2016-12-23T15:27:02]w321: Skipping dependency registration
>on package with no dependency providers: vcredist_x64.exe
>[02FC:0300][2016-12-23T15:27:02]i000: Setting string variable
>'WixBundleLog_vcredist_x64.exe' to value
>'C:\DOCUME~1\DEFAUL~1\LOCALS~1\Temp\Qubes_Windows_Tools_3.2.2.3_20161223152700_0_vcredist_x64.exe.log'
>[02FC:0300][2016-12-23T15:27:02]i204: Plan 10 msi features for package:
>qubes_tools_WIN7x64_3.2.2.3.msi
>[02FC:0300][2016-12-23T15:27:02]i203: Planned feature: DisableUac,
>state: Absent, default requested: Unknown, ba requested: Unknown,
>execute action: None, rollback action: None
>[02FC:0300][2016-12-23T15:27:02]i203: Planned feature: Common, state:
>Absent, default requested: Unknown, ba requested: Unknown, execute
>action: None, rollback action: None
>[02FC:0300][2016-12-23T15:27:02]i203: Planned feature: Complete, state:
>Absent, default requested: Unknown, ba requested: Unknown, execute
>action: None, rollback action: None
>[02FC:0300][2016-12-23T15:27:02]i203: Planned feature: XenBase, state:
>Absent, default requested: Unknown, ba requested: Unknown, execute
>action: None, rollback action: None
>[02FC:0300][2016-12-23T15:27:02]i203: Planned feature: XenPvDrivers,
>state: Absent, default requested: Unknown, ba requested: Unknown,
>execute action: None, rollback action: None
>[02FC:0300][2016-12-23T15:27:02]i203: Planned feature: XenDisk, state:
>Absent, default

Re: [qubes-users] Unable to change timezone?

2016-12-25 Thread Jodie 
On Sunday, December 25, 2016 at 4:32:16 AM UTC-10, john.david.r.smith wrote:
> > I have already tried that, and it fails with "Failed to set time zone: Unit 
> > systemd-timedated.service is masked".
> >
> 
> I just tried it and it works for me (it even updates the time instantly).
> 
> did you change stuff in dom0?

No, I didn't. But that gives me a few avenues to explore. Thanks!

-- 
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/048db1db-bd4d-455b-bd38-435da817d7fa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Qubes OS Live?

2016-12-25 Thread Niely Boyken 
Hi

This page [https://www.qubes-os.org/doc/live-usb/] says that Qubes OS Live
is still in Beta-version.

I'm wondering if this is than safe to use. Will I have the same
security-benefits if I use the Live-version than when I use the normal
version?

If no,
would it be possible to install it on an USB and not on the default
harddrive?

And when does it quit the beta?
I think a Live-option would be a good thing this OS needs.

Thanks!

-- 
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/CA%2B2vtj1-FOzFnv-uNQ2%3DeP-1XgiVwixG%3DWxpP9BnY-mH009Svw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Sleep Verb Not Supported

2016-12-25 Thread mojosam 
My computer doesn't go to sleep.

I have XFCE Power Manager set to Hibernate the system after one hour.  When I 
come back to the system after that time, the screen is blank (but not off) and 
the system seems to be fully powered up (the fan seems to be running at the 
same speed as when I'm using the computer).  So I move the mouse, log back in, 
the Qubes desktop reappears, and there is a message from the Power Manager:

GDBus.Error:org.freedesktop.login1.SleepVerbNotSupported:Sleep verb not 
supported

If it matters, this is a desktop machine (HP Compaq 8200 Elite SFF).

Anyone know how I can solve or troubleshoot this?  Thanks!

-- 
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/033c8268-de47-4343-810b-48b45e936d13%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Template updates: "cannot execute qrexec-deamon" for sys-net - Documentation improvement/addition (or just link update?)

2016-12-25 Thread @LeeteqXV (Twitter) 
For the record; my shift from Fedora-23 to Fedora-24 went 
painlessly/successfully, thanks to the existing, good documentation.


Only thing I had to figure out logically (by experience, luckily, or I 
would have started wasting time unnecessarily) was that I should try to 
reboot when sys-* failed to start afterwards, which then worked, and all 
was fine.


*Suggested documentation addition:**
*

So I think the main docs page should have a top-level link both in the 
"Upgrade guides" section to "updating template association for 
sys-net/sys-firewall" and also from the existing Fedora 23-to-24 doc 
page, especially for some time now that Fedora-23 is EoL/End-of-Life. As 
this is not specific to any particular version number, it should be easy 
to find regardless of which upgrade one is performing, therefore I think 
it should have its own page and be linked from the Upgrades section.


In particular, it should be easy to spot the information about the need 
to reboot the computer immediately after changing the template 
association for sys-firewall and sys-net, as that is not entirely 
obvious for everyone.


The existing page does not mention sys-firewall/sys-net , neither does 
it link to any other page that deals with that:


https://www.qubes-os.org/doc/template/fedora/upgrade-23-to-24/

And, if someone is coming to those pages AFTER having bravely tried to 
update the system without searching (sufficiently?) through all the docs 
(...), they just might be searching for this error message: "cannot 
execute qrexec-deamon", which also should offer a hit to this suggested 
new page among the top search results...


(I seached briefly myself, but did not find a page describing this 
template switch for sys-net/sys-firewall .)


In case there is such a page that I did not find, here is some info that 
it 'should' include:



*Doc text suggestion:*

Disable both sys-firewall and sys-net so that only dom0 is running, then 
change the template association to the new template in each one's VM 
settings. Restart the computer.


PS. If you do not restart the computer right afterwards, but instead try 
to start either one of them, you may get this error:


"Error starting VM 'sys-firewall'" / "Error starting VM 'sys-net'": 
"cannot execute qrexec-deamon"


(This may also be the error you get if running the commands 'qvm-start 
sys-firewall' / 'qvm-start sys-net' in this scenario)




Happy xmas everyone :-)

@LeeteqXV

--
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/d6463f45-e9b7-4c29-2ecf-0b57f4b23e94%40leeteq.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Thunderbolt Dockingstation: PCI bridges and nested PCI devices

2016-12-25 Thread Benjamin Richter 
Hi,

as I described earlier 
(https://groups.google.com/forum/#!msg/qubes-users/uk11tSeu5yU/XtNtOErgDQAJ) 
I'm using an Asus Transformer Pro 3 with the Thunderbolt 3 docking station, but 
I cannot get the docks Ethernet device inside a qube.

I've not made any headway in solving this, but I noticed something that might 
be the reaseon:

/sys/bus/usb/devices/
├── 1-0:1.0 -> ../../../devices/pci:00/:00:14.0/usb1/1-0:1.0
├── 1-1 -> ../../../devices/pci:00/:00:14.0/usb1/1-1
├── 1-1.1 -> ../../../devices/pci:00/:00:14.0/usb1/1-1/1-1.1
├── 1-1:1.0 -> ../../../devices/pci:00/:00:14.0/usb1/1-1/1-1:1.0
├── 1-1.1:1.0 -> 
../../../devices/pci:00/:00:14.0/usb1/1-1/1-1.1/1-1.1:1.0
├── 1-1.1:1.1 -> 
../../../devices/pci:00/:00:14.0/usb1/1-1/1-1.1/1-1.1:1.1
├── 1-1.1:1.2 -> 
../../../devices/pci:00/:00:14.0/usb1/1-1/1-1.1/1-1.1:1.2
├── 1-1.1:1.3 -> 
../../../devices/pci:00/:00:14.0/usb1/1-1/1-1.1/1-1.1:1.3
├── 1-4 -> ../../../devices/pci:00/:00:14.0/usb1/1-4
├── 1-4:1.0 -> ../../../devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0
├── 1-4:1.1 -> ../../../devices/pci:00/:00:14.0/usb1/1-4/1-4:1.1
├── 1-7 -> ../../../devices/pci:00/:00:14.0/usb1/1-7
├── 1-7:1.0 -> ../../../devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0
├── 1-7:1.1 -> ../../../devices/pci:00/:00:14.0/usb1/1-7/1-7:1.1
├── 1-8 -> ../../../devices/pci:00/:00:14.0/usb1/1-8
├── 1-8:1.0 -> ../../../devices/pci:00/:00:14.0/usb1/1-8/1-8:1.0
├── 1-8:1.1 -> ../../../devices/pci:00/:00:14.0/usb1/1-8/1-8:1.1
├── 1-8:1.2 -> ../../../devices/pci:00/:00:14.0/usb1/1-8/1-8:1.2
├── 2-0:1.0 -> ../../../devices/pci:00/:00:14.0/usb2/2-0:1.0
├── 2-1 -> ../../../devices/pci:00/:00:14.0/usb2/2-1
├── 2-1:1.0 -> ../../../devices/pci:00/:00:14.0/usb2/2-1/2-1:1.0
├── 3-0:1.0 -> 
../../../devices/pci:00/:00:1c.0/:01:00.0/:02:02.0/:39:00.0/usb3/3-0:1.0
├── 3-1 -> 
../../../devices/pci:00/:00:1c.0/:01:00.0/:02:02.0/:39:00.0/usb3/3-1
├── 3-1.1 -> 
../../../devices/pci:00/:00:1c.0/:01:00.0/:02:02.0/:39:00.0/usb3/3-1/3-1.1
├── 3-1:1.0 -> 
../../../devices/pci:00/:00:1c.0/:01:00.0/:02:02.0/:39:00.0/usb3/3-1/3-1:1.0
├── 3-1.1:1.0 -> 
../../../devices/pci:00/:00:1c.0/:01:00.0/:02:02.0/:39:00.0/usb3/3-1/3-1.1/3-1.1:1.0
├── 3-1.1.2 -> 
../../../devices/pci:00/:00:1c.0/:01:00.0/:02:02.0/:39:00.0/usb3/3-1/3-1.1/3-1.1.2
├── 3-1.1.2:1.0 -> 
../../../devices/pci:00/:00:1c.0/:01:00.0/:02:02.0/:39:00.0/usb3/3-1/3-1.1/3-1.1.2/3-1.1.2:1.0
├── 3-1.1.2:1.1 -> 
../../../devices/pci:00/:00:1c.0/:01:00.0/:02:02.0/:39:00.0/usb3/3-1/3-1.1/3-1.1.2/3-1.1.2:1.1
├── 3-1.1.2:1.2 -> 
../../../devices/pci:00/:00:1c.0/:01:00.0/:02:02.0/:39:00.0/usb3/3-1/3-1.1/3-1.1.2/3-1.1.2:1.2
├── 3-1.1.2:1.3 -> 
../../../devices/pci:00/:00:1c.0/:01:00.0/:02:02.0/:39:00.0/usb3/3-1/3-1.1/3-1.1.2/3-1.1.2:1.3
├── 3-1.1.4 -> 
../../../devices/pci:00/:00:1c.0/:01:00.0/:02:02.0/:39:00.0/usb3/3-1/3-1.1/3-1.1.4
├── 3-1.1.4:1.0 -> 
../../../devices/pci:00/:00:1c.0/:01:00.0/:02:02.0/:39:00.0/usb3/3-1/3-1.1/3-1.1.4/3-1.1.4:1.0
├── 3-1.1.4:1.1 -> 
../../../devices/pci:00/:00:1c.0/:01:00.0/:02:02.0/:39:00.0/usb3/3-1/3-1.1/3-1.1.4/3-1.1.4:1.1
├── 4-0:1.0 -> 
../../../devices/pci:00/:00:1c.0/:01:00.0/:02:02.0/:39:00.0/usb4/4-0:1.0
├── 4-1 -> 
../../../devices/pci:00/:00:1c.0/:01:00.0/:02:02.0/:39:00.0/usb4/4-1
├── 4-1.1 -> 
../../../devices/pci:00/:00:1c.0/:01:00.0/:02:02.0/:39:00.0/usb4/4-1/4-1.1
├── 4-1:1.0 -> 
../../../devices/pci:00/:00:1c.0/:01:00.0/:02:02.0/:39:00.0/usb4/4-1/4-1:1.0
├── 4-1.1.1 -> 
../../../devices/pci:00/:00:1c.0/:01:00.0/:02:02.0/:39:00.0/usb4/4-1/4-1.1/4-1.1.1
├── 4-1.1:1.0 -> 
../../../devices/pci:00/:00:1c.0/:01:00.0/:02:02.0/:39:00.0/usb4/4-1/4-1.1/4-1.1:1.0
├── 4-1.1.1:1.0 -> 
../../../devices/pci:00/:00:1c.0/:01:00.0/:02:02.0/:39:00.0/usb4/4-1/4-1.1/4-1.1.1/4-1.1.1:1.0
├── usb1 -> ../../../devices/pci:00/:00:14.0/usb1
├── usb2 -> ../../../devices/pci:00/:00:14.0/usb2
├── usb3 -> 
../../../devices/pci:00/:00:1c.0/:01:00.0/:02:02.0/:39:00.0/usb3
└── usb4 -> 
../../../devices/pci:00/:00:1c.0/:01:00.0/:02:02.0/:39:00.0/usb4


USB3 and USB4 are the USB devices on the docking station, as you can see those 
are nested deeper in the structure, below several PCI bridges.
I suppose this might be the reason I cannot assign those devices correctly to a 
qube. Neither assigning the USB device alone, nor all superordinate devices 
works.
Also I cannot enable permissive mode for these devices, it always says "no such 
device":

sudo sh

Re: [qubes-users] Unable to change timezone?

2016-12-25 Thread john.david.r.smith 



I have already tried that, and it fails with "Failed to set time zone: Unit 
systemd-timedated.service is masked".



I just tried it and it works for me (it even updates the time instantly).

did you change stuff in dom0?

--
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/73a8750d-eca6-ee11-6733-4439d29c756d%40openmailbox.org.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Unable to change timezone?

2016-12-25 Thread Jodie 
On Sunday, December 25, 2016 at 12:06:25 AM UTC-10, Andrew David Wong wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> On 2016-12-25 01:56, Jodie wrote:
> > That's what I figured the issue was, but I am indeed attempting to
> > change dom0's settings from within dom0. I'm attempting to change
> > time zone in the date and time settings module in the GUI.
> > 
> > This is after a fresh update to 3.2 and reboot.
> > 
> 
> (Please don't top-post.)
> 
> You could try it this way:
> 
> $ sudo timedatectl set-timezone 
> 
> You can view a list of available timezones with:
> 
> $ timedatectl list-timezones
> 
> You may want to narrow down the list with grep. If you're in Europe,
> for example:
> 
> $ timedatectl list-timezones | grep Europe
> Europe/Amsterdam
> Europe/Andorra
> Europe/Athens
> Europe/Belgrade
> Europe/Berlin
> Europe/Bratislava
> ...
> 
> > On Saturday, December 24, 2016 at 11:51:57 PM UTC-10, Andrew David
> > Wong wrote: On 2016-12-24 23:42, Jodie wrote:
>  Hi all,
>  
>  I seem to be unable to change the time zone. The option to
>  set date and time automatically is greyed out. When I select
>  the time zone tab of the date and time settings module and
>  try to change the time zone to where I currently am right
>  now, I get multiple pop up windows, each with an OK button in
>  the corner. The first one states "Unable to change NTP
>  settings", the second states "Unable to set current time",
>  and the last says "Unable to set timezone".
>  
>  Anyone have any ideas of where to start?
>  
>  Jodie
>  
> > 
> > How are you attempting to change your time zone? You should set it
> > in dom0, which has no network access (and therefore should not be 
> > expected to sync directly with NTP servers). The job of time
> > syncing is handled by qvm-sync-clock, which is run as a cron job
> > every 6 minutes (see /etc/cron.d/qubes-sync-clock.cron).
> > 
> > 
> 
> - -- 
> Andrew David Wong (Axon)
> Community Manager, Qubes OS
> https://www.qubes-os.org
> -BEGIN PGP SIGNATURE-
> 
> iQIcBAEBCgAGBQJYX5oSAAoJENtN07w5UDAw/ioP/iUkv01EcGqHegzxhqYh+RV5
> 9T3HdHV+hk8FamJ1vmagNbhQYq0KyppGxeBtA9vAzO/mr1CUWnLLaihQSzZBtkBt
> BnTGl6jc6H7kwTsCqgEXIS0/UZp1GcLYK28Ri/ZgfC9FoNeW3nTdXnbXhTZGRuEQ
> p4NZ1XuLPVhfbyPvqfr7poTWhN4X13BfWMlY2UA8BkyZT9fSOkeCY/npwdc+y+eB
> B4iYyNsB0LmZV/KGCaYk2o0qBW6NKxSrmm31ZADxucS9LPZEW7p+E03Q9dDaIIHP
> ttVrIwcyBCPFxYThXpCByBvdl7+7TLA555QQFPYkAyOe42nVOYKOhCar/vT1UXes
> xoZfpsn7zTqOOX9o7Lk3QwcuV3X9tv/aNRlgDeUS/sCm+QCDN8i1cFWDmdUeA5Mq
> 0BLUj2rB5bz/Y4lprY1LJ9ayFDeeqrJ6T2dZVzIe6ZDf+YdWJnk0Qun5osRkl1li
> BfUwFRZG/pJx53//GlvrYU0zUAYoRO9xWWEJAb23Krvfgc9blHyGPkEDEGSBMDdd
> 6Ny858cUeTw0ZojZbjLGd3ZggDzUaXaBoOlEqi/8theegk6+mj8HDz8aF42crml6
> xGuhNd8/JBqQY/cyqoCJIuO8vL7PbJ63RxhqVCiabU95+dvnTk7Z2FayO9PF1hoF
> t8wh/TtUqy8h1iKEIyGU
> =v8xf
> -END PGP SIGNATURE-

(Apologies about that. This is the first group I've seen that does these bottom 
posts)

I have already tried that, and it fails with "Failed to set time zone: Unit 
systemd-timedated.service is masked".

-- 
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/7107da61-9527-4561-9e20-ccfc4ad2d786%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Unable to change timezone?

2016-12-25 Thread Andrew David Wong 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2016-12-25 01:56, Jodie wrote:
> That's what I figured the issue was, but I am indeed attempting to
> change dom0's settings from within dom0. I'm attempting to change
> time zone in the date and time settings module in the GUI.
> 
> This is after a fresh update to 3.2 and reboot.
> 

(Please don't top-post.)

You could try it this way:

$ sudo timedatectl set-timezone 

You can view a list of available timezones with:

$ timedatectl list-timezones

You may want to narrow down the list with grep. If you're in Europe,
for example:

$ timedatectl list-timezones | grep Europe
Europe/Amsterdam
Europe/Andorra
Europe/Athens
Europe/Belgrade
Europe/Berlin
Europe/Bratislava
...

> On Saturday, December 24, 2016 at 11:51:57 PM UTC-10, Andrew David
> Wong wrote: On 2016-12-24 23:42, Jodie wrote:
 Hi all,
 
 I seem to be unable to change the time zone. The option to
 set date and time automatically is greyed out. When I select
 the time zone tab of the date and time settings module and
 try to change the time zone to where I currently am right
 now, I get multiple pop up windows, each with an OK button in
 the corner. The first one states "Unable to change NTP
 settings", the second states "Unable to set current time",
 and the last says "Unable to set timezone".
 
 Anyone have any ideas of where to start?
 
 Jodie
 
> 
> How are you attempting to change your time zone? You should set it
> in dom0, which has no network access (and therefore should not be 
> expected to sync directly with NTP servers). The job of time
> syncing is handled by qvm-sync-clock, which is run as a cron job
> every 6 minutes (see /etc/cron.d/qubes-sync-clock.cron).
> 
> 

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

iQIcBAEBCgAGBQJYX5oSAAoJENtN07w5UDAw/ioP/iUkv01EcGqHegzxhqYh+RV5
9T3HdHV+hk8FamJ1vmagNbhQYq0KyppGxeBtA9vAzO/mr1CUWnLLaihQSzZBtkBt
BnTGl6jc6H7kwTsCqgEXIS0/UZp1GcLYK28Ri/ZgfC9FoNeW3nTdXnbXhTZGRuEQ
p4NZ1XuLPVhfbyPvqfr7poTWhN4X13BfWMlY2UA8BkyZT9fSOkeCY/npwdc+y+eB
B4iYyNsB0LmZV/KGCaYk2o0qBW6NKxSrmm31ZADxucS9LPZEW7p+E03Q9dDaIIHP
ttVrIwcyBCPFxYThXpCByBvdl7+7TLA555QQFPYkAyOe42nVOYKOhCar/vT1UXes
xoZfpsn7zTqOOX9o7Lk3QwcuV3X9tv/aNRlgDeUS/sCm+QCDN8i1cFWDmdUeA5Mq
0BLUj2rB5bz/Y4lprY1LJ9ayFDeeqrJ6T2dZVzIe6ZDf+YdWJnk0Qun5osRkl1li
BfUwFRZG/pJx53//GlvrYU0zUAYoRO9xWWEJAb23Krvfgc9blHyGPkEDEGSBMDdd
6Ny858cUeTw0ZojZbjLGd3ZggDzUaXaBoOlEqi/8theegk6+mj8HDz8aF42crml6
xGuhNd8/JBqQY/cyqoCJIuO8vL7PbJ63RxhqVCiabU95+dvnTk7Z2FayO9PF1hoF
t8wh/TtUqy8h1iKEIyGU
=v8xf
-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/04bcd600-7516-77ed-cc5c-f4a14ac6ab2f%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Unable to change timezone?

2016-12-25 Thread Jodie 
That's what I figured the issue was, but I am indeed attempting to change 
dom0's settings from within dom0. I'm attempting to change time zone in the 
date and time settings module in the
GUI.

This is after a fresh update to 3.2 and reboot.

On Saturday, December 24, 2016 at 11:51:57 PM UTC-10, Andrew David Wong wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> On 2016-12-24 23:42, Jodie wrote:
> > Hi all,
> > 
> > I seem to be unable to change the time zone. The option to set
> > date and time automatically is greyed out. When I select the time
> > zone tab of the date and time settings module and try to change the
> > time zone to where I currently am right now, I get multiple pop up
> > windows, each with an OK button in the corner. The first one states
> > "Unable to change NTP settings", the second states "Unable to set
> > current time", and the last says "Unable to set timezone".
> > 
> > Anyone have any ideas of where to start?
> > 
> > Jodie
> > 
> 
> How are you attempting to change your time zone? You should set it in
> dom0, which has no network access (and therefore should not be
> expected to sync directly with NTP servers). The job of time syncing
> is handled by qvm-sync-clock, which is run as a cron job every 6
> minutes (see /etc/cron.d/qubes-sync-clock.cron).
> 
> - -- 
> Andrew David Wong (Axon)
> Community Manager, Qubes OS
> https://www.qubes-os.org
> -BEGIN PGP SIGNATURE-
> 
> iQIcBAEBCgAGBQJYX5atAAoJENtN07w5UDAwGi0P/2KRenl9KmwadUD5MbFk+d8/
> bYzXX4gQkTnJkDBpfwnoGYoZ8CEwv0E2GV67EHEGgMZn4TEuePMBlS1+xarb181F
> 9Tz0DDKjVVjebmgBJT8H9eXnMlikg1+ddPk5EadSz5t7hxdA7MCN14HtkdUfzJCI
> aU1aLwLjY2AVH78/Ye4PZGXPldawWlIqvAK0ETUBJ4PtLz0lVC2UpzBgu6/5+KRM
> 9FtSiqZTs6H6eSxyPY1Wjlzf/jRdu5eFm0aCWa5HFdx6wHflEuiJRIjm5crg1Gw6
> NZqZrSMI6P/LPLhI1eo+2TzM0usKP8CrHsvOg2Y0YQqVcmJwoDXF/kcRFLhGV8z+
> 6Ca1vxBFRZHs+QrmGo7VgL1J/5WT3Fb7EUn0VTPX7FSj60nqnVs0U375xoEoHgIZ
> /UQ0bcV9uJgx4SAlt57MSyKr4IY6PvtU7aV3/9AYCw+5gmPo3NEB7YwEhY5ii/vM
> iblJkffZhPVXKdXUIRpVJD0iGrZfHffjbYOmi40PTktYTPdq6z3w87QUFi4MWP36
> bMC/XYX/63Xbf09badnRF8C7TOEmI4imMc+vG3+dvCBwccS+9twWc7TDNP6ojC2e
> 20zmiXbOcG0oeb4pNn7riOihjlBJtUQUjlHhtFegV9VlUZIoGxYaFXmtBILrN/GQ
> nTgCDMukFhQ/IaJ/jzqm
> =MtO3
> -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/1e495817-314f-4305-8a77-d7cd9bb6c15c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Unable to change timezone?

2016-12-25 Thread Andrew David Wong 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2016-12-24 23:42, Jodie wrote:
> Hi all,
> 
> I seem to be unable to change the time zone. The option to set
> date and time automatically is greyed out. When I select the time
> zone tab of the date and time settings module and try to change the
> time zone to where I currently am right now, I get multiple pop up
> windows, each with an OK button in the corner. The first one states
> "Unable to change NTP settings", the second states "Unable to set
> current time", and the last says "Unable to set timezone".
> 
> Anyone have any ideas of where to start?
> 
> Jodie
> 

How are you attempting to change your time zone? You should set it in
dom0, which has no network access (and therefore should not be
expected to sync directly with NTP servers). The job of time syncing
is handled by qvm-sync-clock, which is run as a cron job every 6
minutes (see /etc/cron.d/qubes-sync-clock.cron).

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

iQIcBAEBCgAGBQJYX5atAAoJENtN07w5UDAwGi0P/2KRenl9KmwadUD5MbFk+d8/
bYzXX4gQkTnJkDBpfwnoGYoZ8CEwv0E2GV67EHEGgMZn4TEuePMBlS1+xarb181F
9Tz0DDKjVVjebmgBJT8H9eXnMlikg1+ddPk5EadSz5t7hxdA7MCN14HtkdUfzJCI
aU1aLwLjY2AVH78/Ye4PZGXPldawWlIqvAK0ETUBJ4PtLz0lVC2UpzBgu6/5+KRM
9FtSiqZTs6H6eSxyPY1Wjlzf/jRdu5eFm0aCWa5HFdx6wHflEuiJRIjm5crg1Gw6
NZqZrSMI6P/LPLhI1eo+2TzM0usKP8CrHsvOg2Y0YQqVcmJwoDXF/kcRFLhGV8z+
6Ca1vxBFRZHs+QrmGo7VgL1J/5WT3Fb7EUn0VTPX7FSj60nqnVs0U375xoEoHgIZ
/UQ0bcV9uJgx4SAlt57MSyKr4IY6PvtU7aV3/9AYCw+5gmPo3NEB7YwEhY5ii/vM
iblJkffZhPVXKdXUIRpVJD0iGrZfHffjbYOmi40PTktYTPdq6z3w87QUFi4MWP36
bMC/XYX/63Xbf09badnRF8C7TOEmI4imMc+vG3+dvCBwccS+9twWc7TDNP6ojC2e
20zmiXbOcG0oeb4pNn7riOihjlBJtUQUjlHhtFegV9VlUZIoGxYaFXmtBILrN/GQ
nTgCDMukFhQ/IaJ/jzqm
=MtO3
-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/b84dc01d-b9ad-ae51-0455-071ec89c42f5%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: most secure way to add repo to template

2016-12-25 Thread Andrew David Wong 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2016-12-24 04:52, Eva Star wrote:
> On 12/24/2016 03:02 PM, Andrew David Wong wrote:
> 
>> 
>> But that repo is already included in the default (main, full)
>> Fedora template. You just have to enable it.
>> 
> 
> I suggest to add paragraph to the docs about "How to add other
> repos not included at the default main template)"
> 

This is actually distro-dependent, so users should consult the
uspstream documentation for the appropriate distro. The procedure
should be the same inside a Qubes TemplateVM of that distro.

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

iQIcBAEBCgAGBQJYX5RdAAoJENtN07w5UDAwuRgP/0punwgzMkzm1lVwo46tgubI
ZQQG0ED9m+lqeCfTk18xQjmphi4oGdy9DvryTe9soXXAleO9A+zK69fzbo2uxubU
JdXR6M5ILd1YV48F5YK5MnwcWSOPJko5Y8abYVumSVsfjmLe0YcJgh8bZjQ6OsZv
7dYjioJpiC6mQsE6MdtgyA8qAfuUsaFFGpniBV0aMzWlJ5l5IljcLVaICfmpnwzC
QVCs0gqoKCchwoVisAT+z/e10wLx1Q2p+dHqcg9azAh6M6F8RxpKlTRla9d7eYQy
jBiMPQoPxIlseIMcoFWdflJ8Fmq0uEl6vueANjZ9zDbtIbMBumJpFAbbK4ES9/J3
FAM8o6VradIrPjHMHi6hctJxf6vPOWb+YE5Ey7uXme5wjZfiTy+uAfDHx+O9AEoF
APrUx7Df+Pney2L+E2i6vpbW48Gu0cI0vLRFtwrB+378H2/uC9oj4o1KwHttxUje
J5b6yX3AmnlxMibDbIHRA0Z4gA53pEenUrsoGCwTqRTYtD9IrFBMRMrdJhs6qUvH
aH30/lqBMdTnS3s2SkwKnM6GLvOewnBiIJtnlyn8UaXyYm9fc3q67JTbOZ6USJA6
j4JoxXxzvnbZP9ss0n3olU4X95cbeRrbwjO/o82S4f3adozU2QJ4IDBTxZ7i138A
UUgmkooBc1W1JVtQPoqN
=OTiL
-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/51ee05bd-9d68-f7cc-f494-166abe59c2e9%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] HCL - Lenovo T400 (Coreboot without ME, with IOMMU*)

2016-12-25 Thread Aphid Farmer 
Says IOMMU is active. However, this Intel generation lacks interrupt 
remapping. There are some attacks[1] and also some Xen-specific 
mitigations[2].



Install notes
-

Coreboot IOMMU changes are not in downstream Libreboot yet.

To compile Coreboot, I followed these[3][4] instructions for ME-less 
Coreboot. Alternatively, you can wait until Libreboot updates their builds.


For step-by-step instructions to flash a Lenovo T400 with an external 
programmer (replacing the factory BIOS), see Libreboot website. The 
Lenovo T400 requires a complete disassembly; the procedure is much 
easier on the Lenovo X200.


After Coreboot + Grub2 payload is flashed, to boot an already-installed 
Qubes:


at grub prompt:
   configfile (ahci0,msdos1)/grub2/grub.cfg
or similar.

If boot hangs on "Loading initial ramdisk":
   'e' to edit the entry "Qubes, with Xen hypervisor"
   append to Xen command line after ${xen_rm_opts}: iommu=no-igfx


Thanks for reading.


[1]http://theinvisiblethings.blogspot.com/2011/05/following-white-rabbit-software-attacks.html
[2]page 24 of same paper
[3]https://www.coreboot.org/Board:lenovo/x200
[4]https://www.coreboot.org/Build_HOWTO


--
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/95ee3853-79f7-6476-2c3b-a02ecad70bd3%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
---
layout:
  'hcl'
type:
  'laptop'
hvm:
  'yes'
iommu:
  'yes'
slat:
  'no'
tpm:
  'unknown'
brand: |
  LENOVO
model: |
  6473PVU
bios: |
  CBET4000 4.5-696-ga4464140f9-dirty
cpu: |
  Intel(R) Core(TM)2 CPU P8700  @ 2.53GHz
cpu-short: |
  FIXME
chipset: |
  Intel Corporation Mobile 4 Series Chipset Memory Controller Hub [8086:2a40] 
(rev 07)
chipset-short: |
  GM45
gpu: |
  Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
  Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a43] (rev 07)
gpu-short: |
  Intel GMA 4500MHD
network: |
  Intel Corporation 82567LF Gigabit Network Connection (rev 03)
  Qualcomm Atheros AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
memory: |
  4058
scsi: |
  Samsung SSD 850  Rev: 2B6Q

versions:

- works:
yes
  qubes: |
R3.2
  xen: |
4.6.3
  kernel: |
4.8.9-12
  remark: |
Coreboot without ME
  credit: |
aphidfarmer but the Coreboot devs did all the real work.
  link: |
FIXLINK

---