date:20180223

On Fri, February 23, 2018 7:35 pm, Daniil .Travnikov wrote:
> пятница, 23 февраля 2018 г., 14:07:38 UTC+3 пользователь awokd написал:
>> On Fri, February 23, 2018 10:46 am, Daniil .Travnikov wrote:
>>
>>
>> EFI is a bit different, not sure you get a Troubleshooting menu there.
>> If
>> not, see
>> https://www.qubes-os.org/doc/uefi-troubleshooting/#change-installer-ker
>> nel-parameters-in-uefi for how to edit the configuration directly on the
>> installer.
>
> Many hours spent on this situation. I already changed my BOOTX64.cfg like
> in guide:
>
> ---
> Edit /mnt/sysimage/boot/efi/EFI/qubes/xen.cfg and add to every kernel
> section:
>
>
> mapbs=1 noexitboot=1 ---
>
>
> And still nothing.
>
>
> What else could it be? It is very strange, because Qubes 3.2 working fine
> with one of the kernels, but newer version in some reason won't work.

The newer R3.2 kernel still didn't work with iommu=no-igfx? That's too
bad, thought it might help there.

It might help if you were able to get the R4.0 installer boot logs to see
what is causing the crash. The problem is you might be literally the only
person in the world running Qubes 4.0 on that hardware, so there is no
magic answer guaranteed to fix it. It uses parts of the Fedora 25
installer, so the process of getting boot logs might be the same (but I
don't know for sure).

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

[qubes-users] Re: QUBES 4 r4 - dom0 UTC time is incorrect - manual change each reboot.

2018-02-23 Thread Alex Dubois

On Monday, 19 February 2018 16:19:07 UTC, QUBE-A-LICIOUS  wrote:
> On Monday, February 19, 2018 at 4:08:36 AM UTC-6, schnuren...@gmail.com wrote:
> > On Sunday, February 18, 2018 at 5:52:34 PM UTC+1, QUBE-A-LICIOUS wrote:
> > > On Thursday, February 15, 2018 at 5:42:44 PM UTC-5, schnuren...@gmail.com 
> > > wrote:
> > > > On Tuesday, February 13, 2018 at 10:51:12 PM UTC+1, QUBE-A-LICIOUS 
> > > > wrote:
> > > > > Hi there,
> > > > > 
> > > > > I have a fresh install of Qubes 4r4.  However, when I reboot and or 
> > > > > login I have to manually change dom0 time to UTC.
> > > > > 
> > > > > Impact: Whonix/Tor does not work because of the incorrect time.
> > > > > 
> > > > > Manual workaround:
> > > > > 1.  Get the correct UTC from a browser.
> > > > > 2.  Open Dom0 Terminal and update to UTC such as the following:
> > > > > 
> > > > >   sudo date --set "2018-02-13 21:30"
> > > > > 
> > > > > 3. Shutdown Service:sys-whonix
> > > > > 4.  Restart a whonix domain such as Domain:anon-whonix(this restarts 
> > > > > the sys-whonix service that was just shutdown.
> > > > > 5.  Then run WhonixCheck to make sure it works.  It usually does and 
> > > > > Whonix/Tor is functional.
> > > > > 
> > > > > =
> > > > > Qubes cannot be this bad, really.
> > > > > 
> > > > > How can I have this Date and time correctly updated on boot up?  Like 
> > > > > it should.
> > > > > 
> > > > > Thanks for all your help.
> > > > > NSJ
> > > > 
> > > > Most times it is easy to point on another guilty one instead looking 
> > > > what may happen with the own stuff. So far you are the only one with 
> > > > this misbehavior.
> > > > Qubes works as expected - at least in this point.
> > > > But most user already experienced this behavior; qubes-os or any other 
> > > > distribution.
> > > > The keyword is hwclock. You always update the software-based time, but 
> > > > if you restart, all temporary data is gone. (should)
> > > > So your OS fetches at boot the time from the bios.
> > > > If you update your time within the qubes-os, you should update your 
> > > > hardware clock (hc) as well: sudo hwclock --systohc
> > > > If your time resets when you unplug your device from power supply, your 
> > > > device's battery is flat.
> > > 
> > > --
> > > I did some analysis this morning.  So at the same point in time the 
> > > following settings on my Qubes laptop showed the following values.  
> > > (Bottom line is that whonix/tor does not work)
> > > 
> > > 1.  The hardware BIOS clock is:  1030  (BIOS battery good, removed laptop 
> > > battery for few hours and date/time stayed same)
> > > 
> > > 2.  Dom0 time is: 0530 ( via date command)
> > > 
> > > 3.  service:sys-whonix is:  1030 (via date command)
> > > 
> > > 4.  Clock on upper right of screen is:  0430
> > > 
> > > Tor Boostrap info is:
> > > 
> > > Whonixcheck gave up waiting
> > > clock skew -21635 in directory from DIRSERV
> > > 
> > > sudo date --set “2018 -02-18 17:30:00”
> > > 
> > > -
> > > I think that on a normal bootup the clocks should be in sync and 
> > > Whonix/Tor should work.
> > 
> > bios time differs a lot from dom0 and dom0 time seems in the UTC 
> > (timezone), while the clock on your desktop should be therefore in the -1 
> > hour timezone. 
> > There is already something wrong, isn't it?
> > Could you please set the correct time in dom0 and do a 'sudo hwclock 
> > --systohw' to get dom0's sys date and bios time in sync.
> > And reboot pls. After reboot check the time in bios, dom0 and your clockVM 
> > (probably sys-net) before connecting to any network.
> > In System Tools -> Qubes Global Settings in dom0 you can check the name of 
> > the clock VM.
> > The time of your whonix should, as far as I know, differs in timezone as 
> > qubes built-in rule randomly each bootup of the VM. (Do not know for sure)
> > 
> > I either do not know whether sys-whonix only changes the timezone and if it 
> > is an attack surface if someone from the outside could simulate/fake 
> > specific minutes and seconds your network-time-daemon adapt and your whonix 
> > could be associated to your isp.
> > 
> > Even there seems to be some misconfiguration I never got, the behavior 
> > remembers me to an empty hardware battery.
> 
> ==
> 1.  I changed to the correct Time Zone from the command line.  Fixed the -1 
> hour offset.
> 2.  I updated the dom0 time
> 3.  I ran the sudo hwclock -w to set the hardware clock from the current 
> system time.
> 4.  I rebooted the laptop.
> 
> The current results are:
> 
> 1.  BIOS clock is:  1530  (via BIOS menu on startup)
> 
> 2.  Dom0 time is: 0930 with correct time zone.  (Correct!)
> 
> 3.  service:sys-whonix is:  1530 UTC
> 
> 4.  Clock on upper right of screen is:  0930 (Correct!)
> 
> 5.  sys-net is 0930.  (Correct!)
> 
> 6.  Tor Boostrap info is:  (from sys-whonix occurs right after startup)
> 
> ERROR systemd clock check result:
> Unexpected

Re: [qubes-users] How to delete or upgrade app VMs?

On Friday, February 23, 2018 at 8:03:55 PM UTC+1, Unman wrote:
> On Fri, Feb 23, 2018 at 10:44:04AM -0800, Yuraeitha wrote:
> > On Friday, February 23, 2018 at 3:00:51 AM UTC+1, Kyle Breneman wrote:
> > > >Does this help?
> > > 
> > > >https://www.qubes-os.org/doc/templates/fedora/#after-installing
> > > 
> > > 
> > > Yes, somewhat, but I found #7 on this page more helpful.  I've almost 
> > > gotten everything configured the way I want, but one thing still puzzles 
> > > me.  I used "sudo dnf remove qubes-template-fedora-23" from the terminal 
> > > (mistakenly did this before deleting/switching all app VMs that depended 
> > > on it), but apparently that didn't completely remove fedora-23 template 
> > > VM because even after several restarts the fedora-23 template VM is still 
> > > showing up in the Qubes VM Manager.  How can I get rid of it for good?
> > > 
> > > 
> > > Regards,
> > > 
> > > Kyle
> > > 
> > > 
> > > 
> > > On Wed, Feb 21, 2018 at 1:25 AM, Andrew David Wong  
> > > wrote:
> > > -BEGIN PGP SIGNED MESSAGE-
> > > 
> > > Hash: SHA512
> > > 
> > > 
> > > 
> > > 
> > > 
> > > On 2018-02-20 22:48, Kyle Breneman wrote:
> > > 
> > > > I'm running Qubes 3.2.  I have the default Fedora 23 template VM, and 
> > > > the
> > > 
> > > > default app VMs built from it, but I also installed a Fedora 26 template
> > > 
> > > > VM.  Now I want to delete or upgrade my Fedora 23 app VMs, but I cannot
> > > 
> > > > figure out how to do this.  The "Delete VM" menu option in the Qubes VM
> > > 
> > > > Manager always seems to be grayed-out.  How can I either delete these 
> > > > app
> > > 
> > > > VMs based on Fedora 23, or switch them over to my Fedora 26 template?
> > > 
> > > >
> > > 
> > > > Regards,
> > > 
> > > > Kyle
> > > 
> > > >
> > > 
> > > 
> > > 
> > > Does this help?
> > > 
> > > 
> > > 
> > > https://www.qubes-os.org/doc/templates/fedora/#after-installing
> > > 
> > > 
> > > 
> > > - --
> > > 
> > > Andrew David Wong (Axon)
> > > 
> > > Community Manager, Qubes OS
> > > 
> > > https://www.qubes-os.org
> > > 
> > > 
> > > 
> > > -BEGIN PGP SIGNATURE-
> > > 
> > > 
> > > 
> > > iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlqNELUACgkQ203TvDlQ
> > > 
> > > MDDjCBAAuCHhRevjEfHIRhSkpTs6QIh8c8BBy+dWceVM14Qu24187j6hZ5OedsJZ
> > > 
> > > QVoP00tdW+xRZfnroW15f9Rzb5MPWQp/RW84rESGVBt1f7mCwzwR1aLRa7ivBPWf
> > > 
> > > +idL5WdJIMAYrCTAaI7zksPFfYrgK9tSgmULVqrkOkpYI3K24/N8JZyRmRJc6GEU
> > > 
> > > O6+8pprFykzoRE2pvSL0J1Vg24a4paYyuaKTT1wHBqkHg87Sm42amueTQUkXP8p7
> > > 
> > > d1hQ0JHyfMma53Qv2taA0l1K9WR9ifB+HH5dc0w5d7KUvc5Bs0fr5ed/5vim75fX
> > > 
> > > HyJn5P/wugaaw0+vBwU381WkCYuq/tB/HLPDirsDjK0iX9hkh6/McDZ7uD0mWmCH
> > > 
> > > NZnHKjifEkF57P5wNLVFaz90q6YfrGnyS8jJKNEopcurZOtpd0wHKnW7eh/0iO6H
> > > 
> > > EEeYkJ5M309AvFFWLE1UDHfCuPgTll/l3WB+SzUTGeF9wq7JP6RlsT02at7kXCHt
> > > 
> > > mAxfycSJ6b3B35XxBdqVmUKo9jB/XwjgGOT/RJGU/w9PxXcgmI7yR8oOXPtopH7v
> > > 
> > > HKR/dwSHlMfox+tAzAf2SFE7KIwr3JtEjcrLDP0+fDrW3QnK0zhdC5R7jXI//cwM
> > > 
> > > bFQ7jKlS8wI1ZEOYZw2oBWm72nkFO0uIt8A+60mxdq4/zY++FPg=
> > > 
> > > =Xrgv
> > > 
> > > -END PGP SIGNATURE-
> > 
> > It's an issue someone else encountered in the past, somewhere on these mail 
> > threads, at least a good couple months back if memory serves. I thought it 
> > had since then been made impossible by now to remove the template 
> > prematurely? But it seems not. In this case, you can now only remove it 
> > manually once the damage has been done. At least to my knowledge about it. 
> > The link Andrew linked should do the trick.
> > 
> > Currently there is not enough redundancy to prevent mistakes such as 
> > premature removal, or mixing up qvm-remove and "dnf remove", which both can 
> > cause mayharm. 
> > 
> > Is this something that's been put on github tracking issues/features? 
> > anyone knows?
> > 
> 
> I dont think it is possible to mix up qvm-remove and dnf remove. You
> cannot use qvm-remove on a template installed using dnf, and dnf remove
> wont do anything on a cloned template.
> Also, isnt there still a warning if trying to remove a template which
> has qubes using it? If not, that's a bad regression. I'm sure there was.
> 
> Does the template still appear if you run 'dnf list *template*'?
> If a template remains, I would first try dnf-remove again and note the
> response.
> Then manually remove it , if that hasnt worked and errors cant be fixed,
> but that sounds like a dnf issue.

Now that I read your post, I'm actually unsure which one of two scenarios it 
was that happened for this user posting some months back, it was either 
(qvm-remove on a rpm installed template that went through without being 
stopped), or it was ('dnf remove' which removed the template despite there 
still being AppVM's and system processes tied to it). Frustratingly I don't 
remember which one it was, it's been too long now.

I remember the user who had issues with this (one of the two scenarios above), 
was an issue that wasn't

Re: [qubes-users] Re: Can't install Qubes, Rebooting after loading initrd.img

On Friday, February 23, 2018 at 8:35:00 PM UTC+1, Daniil .Travnikov wrote:
> пятница, 23 февраля 2018 г., 14:07:38 UTC+3 пользователь awokd написал:
> > On Fri, February 23, 2018 10:46 am, Daniil .Travnikov wrote:
> > 
> > EFI is a bit different, not sure you get a Troubleshooting menu there. If
> > not, see
> > https://www.qubes-os.org/doc/uefi-troubleshooting/#change-installer-kernel-parameters-in-uefi
> > for how to edit the configuration directly on the installer.
> 
> Many hours spent on this situation. I already changed my BOOTX64.cfg like in 
> guide:
> 
> ---
> Edit /mnt/sysimage/boot/efi/EFI/qubes/xen.cfg and add to every kernel section:
> 
> mapbs=1
> noexitboot=1
> ---
> 
> And still nothing.
> 
> What else could it be? It is very strange, because Qubes 3.2 working fine 
> with one of the kernels, but newer version in some reason won't work.

There is another way you can try fix this, that "might" work. I'll elaborate. 

Considering it's server hardware, I wonder if it's a similar problem for some 
server categories in general? I have at one point tried to install Qubes on a 
ProLiant Microserver Gen10, which resulted in a very similar experience to 
yours. 

>From memory, I recall HVM working, while I/O MMU did not, pretty similar to 
>yours. I may have an untested solution, but I never got around to testing it 
>out. 

Using it, I believe you can make it work if you change all your VM's to 
visualization mode "PV" instead of HVM or PVH.

I never got as far as to test that though, but think about it for a moment. HVM 
had PCI issues in early Qubes 4, it does PCI pass-through differently from PV 
mode and as far as I understand it, it relies on I/O MMU to work. PVH currently 
can't use PCI pass-through. Which leaves PV mode, which is also what Qubes 3.2. 
uses.

Since you have trouble getting the installer to work and install Qubes, you may 
not be able to do this fix on your local hardware. You may have to pull out the 
drive, put it in another computer and install Qubes there. Update everything, 
and then make sure you put sys-net and sys-usb in PV mode with the "qvm-prefs 
virt_mode" command in dom0.

Now because sys-net and sys-usb are in PV mode, it may be able to bypass the 
missing I/O MMU issue, which as far as I understand it is related to PCI 
pass-through. That's why you want sys-net, sys-usb and any other hardware that 
is pass-through to be using PV mode.

This isn't a beautiful fix, but it may just work. It's not the first time I've 
fixed a Qubes 4 install with this approach, however, I have not yet tried it on 
this server hardware, which like yours is missing I/O MMU. I believe it might 
work, but it might also not work. While installing on another machine has in 
the past worked, I never tried to use it to change sys-net and sys-usb to PV 
mode before putting it back.

This might also be what makes the difference between Qubes 3.2. and Qubes 4.0 
for you, considering Qubes 3.2. uses PV mode, and Qubes 4.0 uses HVM for 
pass-through and otherwise PVH for everything else. Considering you have no I/O 
MMU, it might not be surprising? that Qubes 4.0 doesn't work for you when not 
in PV mode.

If you use this approach, then be careful you don't wipe out any other drives 
or EFI settings on the other machine during install, take precautions against 
it. Also it's far easier to use LegacyBIOS/Grub, so you don't have to mess with 
EFI paths when bring the drive back.

-- 
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/2d647d70-ec41-4149-ab8f-3048fd8e0506%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] fix resume in Qubes (Was X230 Corebooted -> resume broken

2018-02-23 Thread '[799]' via qubes-users

Hello,

a topic I had in the Coreboot Mailing list about fixibg resume in Qubes ...
belongs mostly to this list.

Original-Nachricht
An 24. Feb. 2018, 02:13, [799] schrieb:

// Please excuse my recent mail as it was sent while I was writing, the scriot
wasn't yet complete - here the complete version //

Original-Nachricht
An 23. Feb. 2018, 14:32, [...] schrieb:

Me >> If I close the lid, the laptop shuts off.

> I do have the very same problem,if you find a
> solution, id be glad if you give me a hint .

I think I came up with an idea how to work arround this problem:

I found out that I can put the laptop to sleep when choosing "shutdown" from
the top right Qubes button with your username on it (where you normally
shutdown Qubes).

The laptop will switch to resume to RAM and you can then close the laptop lid.
if you open the laptop again you need to login but run into a problem with all
AppVMs that had PCI Controllers attached, which will also affect your
networking.

What you need to do is to kill those AppVMs (mainly sys-net and sys-usb) and
restart them again.
After the restart if sys-net your AppVMs can't through the sys-net VM.

A workarround is to reconnect your firewall-VMs to sys-net by setting the netvm
to none (= "" in Qubes 4) and then setting it back to the sys-net VM.
This will bring back networking. As such my workarround is:

1) use "Suspend" from the upper right Qubes menu

2) close Laptop lid after resume

3) open lid and login

4) run the following script in dom0 to kill sys-net/sys-usb and reconnect the
proxy VMs:

#!/bin/bash
# qvm-resume
# kills and reconnect sys-net/sys-usb
# to fix networking after resume
qvm-kill --force sys-net sys-usb
qvm-start sys-net sys-usb
# for Qubes 4rc4, Qubes 3.2 uses another
# Syntax with qvm-prefs to disable the NetVm
qvm-prefs --set sys-firewall netvm ""
qvm-prefs --set sys-firewall netvm sys-net

Can you try if this will also work in your case?

If this is working the only thing we need to do, is to setup resume when
closing the lid and then the run the "qvm-resume" script after wake up or login
back.

what do you think?

[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/DPRp9G4MaM6lAsDB_S4H1YV8wkTakNJzcLC4M8O0OmPf9lDIIqrCOyXl3D5a9DhnJjaD1Ezh-Corpjv-PfGz7z99ttcYy7Q32tdivswpyh0%3D%40protonmail.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Will there be a gentoo template in the plans?

2018-02-23 Thread abnormal

Subj.

-- 
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/fbd0d374-6651-4721-a0b9-9c937300fafd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] How to delete or upgrade app VMs?

2018-02-23 Thread Andrew David Wong

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2018-02-22 20:02, Kyle Breneman wrote:
>> Yes, somewhat, but I found #7 on this page
>>  more
>> helpful.  I've almost gotten everything configured the way I want, but one
>> thing still puzzles me.  I used "sudo dnf remove qubes-template-fedora-23"
>> from the terminal (mistakenly did this before deleting/switching all app
>> VMs that depended on it), but apparently that didn't completely remove
>> fedora-23 template VM because even after several restarts the fedora-23
>> template VM is still showing up in the Qubes VM Manager.  How can I get rid
>> of it for good?
>>
> 
> See link in first line.  I forgot link the first time I sent this.
> 

Try this:

https://www.qubes-os.org/doc/remove-vm-manually/#how-to-remove-a-templatevm-manually

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

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlqPz0EACgkQ203TvDlQ
MDDNHg/+N7nL72Oq9NhkPu7Or5uqgSEFF7mlFU5jCqmV6M/+t29sBAXK5f8sRrZ0
7MWuTq1y+foJTD2ENnD2N0s++LtnH87xC3tubcnCsTipNve92JGINbTDz4AtRRvK
qNw7Z5DGCjW74CE1qxoOitHpPoNozyjlQ1WsxXjubIzryWGXgcpVMFA4RK1JILN/
1/v1emEGD7+RgpUmTy8uN3OXxxSzV6ZY3T5o2EsG2gWIZdb9EchPS+h9thK4mJsq
9CBmdAzmoMsS6wqeGu3rTAdhKTrJpDhUk1iicSGdQELB/qCLNBQaunqpzdHgVwad
XPf/ksGz5xknc3WYmgEvshhXcDUlgBMISRb3mL6lTIzcGZ7wIVls9M11nVLfq+Dv
lkHt6smQNZrZThZPSTN+fWKty1PJJvYsxwhmys4PX1/tr3/oUp4NfAcePrV3xnzZ
JKABfs29MSO6ctn3Tr1eagBhjsbfS+liQGF4+V6n0gCPikYcZ6Ux0/3hCpZWBmxF
3DHOFmggfRJMjclMLvvOPnaUw5A/VyPT+ZdpAH6NHFwya7TiqQMd5AAvBOkckus8
PfYPMb5ivOlZQKgf53QU+09ca9upXbDlz0dwX6TrrKtnU7Zt/P+/eBXz2LlkexNt
91nN17KVU5ezZuCMS+dtqxv8o2SUeiaXjxg0tuiJmSw+ERUxrY4=
=mCfK
-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/bbc339a5-580e-2301-1494-eb02b7a26a4f%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] USB VM based on fedora-26 doesn't pass block devices

2018-02-23 Thread Kelly Dean


awokd writes:
> I wonder if this might be related to a recent patch in testing. Are both
> your dom0 and templates on the same repository (current vs. testing) and
> updated? A recent patch also required a reboot once both were updated.

Both on current, and both updated, and rebooted since last update.

Anyway, problem solved. I plugged the USB device into a different port, and it 
worked (I got xvdi in the appVM). Then I detached and moved it back to the port 
where I was having the problem, and this time it worked there too. Aargh, 
heisenbug.

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

Re: [qubes-users] How to delete or upgrade app VMs?

On Friday, February 23, 2018 at 3:00:51 AM UTC+1, Kyle Breneman wrote:
> >Does this help?
> 
> >https://www.qubes-os.org/doc/templates/fedora/#after-installing
> 
> 
> Yes, somewhat, but I found #7 on this page more helpful.  I've almost gotten 
> everything configured the way I want, but one thing still puzzles me.  I used 
> "sudo dnf remove qubes-template-fedora-23" from the terminal (mistakenly did 
> this before deleting/switching all app VMs that depended on it), but 
> apparently that didn't completely remove fedora-23 template VM because even 
> after several restarts the fedora-23 template VM is still showing up in the 
> Qubes VM Manager.  How can I get rid of it for good?
> 
> 
> Regards,
> 
> Kyle
> 
> 
> 
> On Wed, Feb 21, 2018 at 1:25 AM, Andrew David Wong  wrote:
> -BEGIN PGP SIGNED MESSAGE-
> 
> Hash: SHA512
> 
> 
> 
> 
> 
> On 2018-02-20 22:48, Kyle Breneman wrote:
> 
> > I'm running Qubes 3.2.  I have the default Fedora 23 template VM, and the
> 
> > default app VMs built from it, but I also installed a Fedora 26 template
> 
> > VM.  Now I want to delete or upgrade my Fedora 23 app VMs, but I cannot
> 
> > figure out how to do this.  The "Delete VM" menu option in the Qubes VM
> 
> > Manager always seems to be grayed-out.  How can I either delete these app
> 
> > VMs based on Fedora 23, or switch them over to my Fedora 26 template?
> 
> >
> 
> > Regards,
> 
> > Kyle
> 
> >
> 
> 
> 
> Does this help?
> 
> 
> 
> https://www.qubes-os.org/doc/templates/fedora/#after-installing
> 
> 
> 
> - --
> 
> Andrew David Wong (Axon)
> 
> Community Manager, Qubes OS
> 
> https://www.qubes-os.org
> 
> 
> 
> -BEGIN PGP SIGNATURE-
> 
> 
> 
> iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlqNELUACgkQ203TvDlQ
> 
> MDDjCBAAuCHhRevjEfHIRhSkpTs6QIh8c8BBy+dWceVM14Qu24187j6hZ5OedsJZ
> 
> QVoP00tdW+xRZfnroW15f9Rzb5MPWQp/RW84rESGVBt1f7mCwzwR1aLRa7ivBPWf
> 
> +idL5WdJIMAYrCTAaI7zksPFfYrgK9tSgmULVqrkOkpYI3K24/N8JZyRmRJc6GEU
> 
> O6+8pprFykzoRE2pvSL0J1Vg24a4paYyuaKTT1wHBqkHg87Sm42amueTQUkXP8p7
> 
> d1hQ0JHyfMma53Qv2taA0l1K9WR9ifB+HH5dc0w5d7KUvc5Bs0fr5ed/5vim75fX
> 
> HyJn5P/wugaaw0+vBwU381WkCYuq/tB/HLPDirsDjK0iX9hkh6/McDZ7uD0mWmCH
> 
> NZnHKjifEkF57P5wNLVFaz90q6YfrGnyS8jJKNEopcurZOtpd0wHKnW7eh/0iO6H
> 
> EEeYkJ5M309AvFFWLE1UDHfCuPgTll/l3WB+SzUTGeF9wq7JP6RlsT02at7kXCHt
> 
> mAxfycSJ6b3B35XxBdqVmUKo9jB/XwjgGOT/RJGU/w9PxXcgmI7yR8oOXPtopH7v
> 
> HKR/dwSHlMfox+tAzAf2SFE7KIwr3JtEjcrLDP0+fDrW3QnK0zhdC5R7jXI//cwM
> 
> bFQ7jKlS8wI1ZEOYZw2oBWm72nkFO0uIt8A+60mxdq4/zY++FPg=
> 
> =Xrgv
> 
> -END PGP SIGNATURE-

It's an issue someone else encountered in the past, somewhere on these mail 
threads, at least a good couple months back if memory serves. I thought it had 
since then been made impossible by now to remove the template prematurely? But 
it seems not. In this case, you can now only remove it manually once the damage 
has been done. At least to my knowledge about it. The link Andrew linked should 
do the trick.

Currently there is not enough redundancy to prevent mistakes such as premature 
removal, or mixing up qvm-remove and "dnf remove", which both can cause 
mayharm. 

Is this something that's been put on github tracking issues/features? anyone 
knows?

-- 
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/9d802448-2086-47f4-99b9-6f2b9df4fc59%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] How to delete or upgrade app VMs?

2018-02-23 Thread Unman

On Fri, Feb 23, 2018 at 10:44:04AM -0800, Yuraeitha wrote:
> On Friday, February 23, 2018 at 3:00:51 AM UTC+1, Kyle Breneman wrote:
> > >Does this help?
> > 
> > >https://www.qubes-os.org/doc/templates/fedora/#after-installing
> > 
> > 
> > Yes, somewhat, but I found #7 on this page more helpful.  I've almost 
> > gotten everything configured the way I want, but one thing still puzzles 
> > me.  I used "sudo dnf remove qubes-template-fedora-23" from the terminal 
> > (mistakenly did this before deleting/switching all app VMs that depended on 
> > it), but apparently that didn't completely remove fedora-23 template VM 
> > because even after several restarts the fedora-23 template VM is still 
> > showing up in the Qubes VM Manager.  How can I get rid of it for good?
> > 
> > 
> > Regards,
> > 
> > Kyle
> > 
> > 
> > 
> > On Wed, Feb 21, 2018 at 1:25 AM, Andrew David Wong  
> > wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > 
> > Hash: SHA512
> > 
> > 
> > 
> > 
> > 
> > On 2018-02-20 22:48, Kyle Breneman wrote:
> > 
> > > I'm running Qubes 3.2.  I have the default Fedora 23 template VM, and the
> > 
> > > default app VMs built from it, but I also installed a Fedora 26 template
> > 
> > > VM.  Now I want to delete or upgrade my Fedora 23 app VMs, but I cannot
> > 
> > > figure out how to do this.  The "Delete VM" menu option in the Qubes VM
> > 
> > > Manager always seems to be grayed-out.  How can I either delete these app
> > 
> > > VMs based on Fedora 23, or switch them over to my Fedora 26 template?
> > 
> > >
> > 
> > > Regards,
> > 
> > > Kyle
> > 
> > >
> > 
> > 
> > 
> > Does this help?
> > 
> > 
> > 
> > https://www.qubes-os.org/doc/templates/fedora/#after-installing
> > 
> > 
> > 
> > - --
> > 
> > Andrew David Wong (Axon)
> > 
> > Community Manager, Qubes OS
> > 
> > https://www.qubes-os.org
> > 
> > 
> > 
> > -BEGIN PGP SIGNATURE-
> > 
> > 
> > 
> > iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlqNELUACgkQ203TvDlQ
> > 
> > MDDjCBAAuCHhRevjEfHIRhSkpTs6QIh8c8BBy+dWceVM14Qu24187j6hZ5OedsJZ
> > 
> > QVoP00tdW+xRZfnroW15f9Rzb5MPWQp/RW84rESGVBt1f7mCwzwR1aLRa7ivBPWf
> > 
> > +idL5WdJIMAYrCTAaI7zksPFfYrgK9tSgmULVqrkOkpYI3K24/N8JZyRmRJc6GEU
> > 
> > O6+8pprFykzoRE2pvSL0J1Vg24a4paYyuaKTT1wHBqkHg87Sm42amueTQUkXP8p7
> > 
> > d1hQ0JHyfMma53Qv2taA0l1K9WR9ifB+HH5dc0w5d7KUvc5Bs0fr5ed/5vim75fX
> > 
> > HyJn5P/wugaaw0+vBwU381WkCYuq/tB/HLPDirsDjK0iX9hkh6/McDZ7uD0mWmCH
> > 
> > NZnHKjifEkF57P5wNLVFaz90q6YfrGnyS8jJKNEopcurZOtpd0wHKnW7eh/0iO6H
> > 
> > EEeYkJ5M309AvFFWLE1UDHfCuPgTll/l3WB+SzUTGeF9wq7JP6RlsT02at7kXCHt
> > 
> > mAxfycSJ6b3B35XxBdqVmUKo9jB/XwjgGOT/RJGU/w9PxXcgmI7yR8oOXPtopH7v
> > 
> > HKR/dwSHlMfox+tAzAf2SFE7KIwr3JtEjcrLDP0+fDrW3QnK0zhdC5R7jXI//cwM
> > 
> > bFQ7jKlS8wI1ZEOYZw2oBWm72nkFO0uIt8A+60mxdq4/zY++FPg=
> > 
> > =Xrgv
> > 
> > -END PGP SIGNATURE-
> 
> It's an issue someone else encountered in the past, somewhere on these mail 
> threads, at least a good couple months back if memory serves. I thought it 
> had since then been made impossible by now to remove the template 
> prematurely? But it seems not. In this case, you can now only remove it 
> manually once the damage has been done. At least to my knowledge about it. 
> The link Andrew linked should do the trick.
> 
> Currently there is not enough redundancy to prevent mistakes such as 
> premature removal, or mixing up qvm-remove and "dnf remove", which both can 
> cause mayharm. 
> 
> Is this something that's been put on github tracking issues/features? anyone 
> knows?
> 

I dont think it is possible to mix up qvm-remove and dnf remove. You
cannot use qvm-remove on a template installed using dnf, and dnf remove
wont do anything on a cloned template.
Also, isnt there still a warning if trying to remove a template which
has qubes using it? If not, that's a bad regression. I'm sure there was.

Does the template still appear if you run 'dnf list *template*'?
If a template remains, I would first try dnf-remove again and note the
response.
Then manually remove it , if that hasnt worked and errors cant be fixed,
but that sounds like a dnf issue.

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

[qubes-users] Intel Core i7-920 - Qubes 4.0-rc4 problem ("no IOMMU?" in libxl-driver.log)

2018-02-23 Thread Thorsten Schierer

I'm currently running Qubes 3.2 on a Intel Core i7-920 processor just fine.
Now I wanted to test the new Qubes 4.0-rc4 and ran into some issue. The
installer tells me, there is no vt-d/.../... support available, although it
should be fine. VT-d is enabled in bios and hyper-v or vmware are fully
functional on that machine under Windows.
So I thought it was a false warning and decided to continue the
installation leading to another error message when the configuration tries
to run sys-net.
After Qubes OS was booted, the sys-net etc. were not started automatically,
so I tried to run then manually which ended in the same error message.
libxl-driver.log displays "PCI device cannot be assigned - no IOMMU?"

Since my search for a solution to this problem led nowhere (entries on
mailing lists and google) I wanted to ask here in this mailing list.

I checked the minimum requirements on Qubes 4.0 to make sure the hardware
meets them:

64-bit Intel or AMD processor (x86_64 aka x64 aka AMD64) ---> YES
(Intel Core i7-920)
Intel VT-x with EPT or AMD-V with RVI --->YES (ark.intel.com
lists "VT-x
with EPT")
Intel VT-d or AMD-Vi --->YES (VT-d is enabled in BIOS)
4 GB RAM --->YES (16 GB RAM available)
32 GB disk space --->YES (256GB USB 3.0 Stick for testing)

Also something weird to mention: After some reboots (while trying to fix
the issue) the sys-net and sys-firewall were automatically started
(displaying 2 console windows, showing the boot of these VMs, which is not
the case in Qubes 3.2).
This happened only once and I could not reproduce this anymore. So now I'm
stuck with the "no IOMMU?" error in libxl-driver.log.

Any idea what the problem is and how it can be solved?

--
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/CAMtrDxRhEnJnO6jk7yBmp1ffROmR1TuJdrQ3D%3Dh%3DsUhfj0BJ1Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Can't install Qubes, Rebooting after loading initrd.img

пятница, 23 февраля 2018 г., 14:07:38 UTC+3 пользователь awokd написал:
> On Fri, February 23, 2018 10:46 am, Daniil .Travnikov wrote:
> 
> EFI is a bit different, not sure you get a Troubleshooting menu there. If
> not, see
> https://www.qubes-os.org/doc/uefi-troubleshooting/#change-installer-kernel-parameters-in-uefi
> for how to edit the configuration directly on the installer.

Many hours spent on this situation. I already changed my BOOTX64.cfg like in 
guide:

---
Edit /mnt/sysimage/boot/efi/EFI/qubes/xen.cfg and add to every kernel section:

mapbs=1
noexitboot=1
---

And still nothing.

What else could it be? It is very strange, because Qubes 3.2 working fine with 
one of the kernels, but newer version in some reason won't work.

-- 
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/d841a582-80e4-4a52-a291-407ac960024d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: How to add "nouveau.modeset=0" to boot settings in Qubes 4.x? (ASUS ROG GL552VW-DM141 laptop)

On Friday, February 23, 2018 at 12:10:03 AM UTC+1, @LeeteqXV wrote:
> Hi all. I initially thought to save some time and cleared a reply
>   to an existing thread to do a new post, but that did not work.
>   Sorry about the wrong post. Reposting it here now. Thanks for the
>   reply and pointing it out, Yuraeitha.
> 
> See my reply + follow-up question at the bottom, below the quoted
>   posts:
> 
> 
> 
> ##
> 
> My original post, incl. a reply by "Yuraeitha" below..:
> 
> 
> 
> 
> 
> "I am considering Qubes 4.x for an ASUS ROG GL552VW-DM141 laptop
>   with NVIDIA graphics and built-in/onboard "fallback" Intel
>   graphics.
>   
> 
>   
> 
>   In order to get for example Ubuntu Mate installed onto it, to get
>   past the installer incompatibilities with NVidia, it is necessary
>   to edit the boot menu and add "nouveau.modeset=0" to the startup
>   command. Then Ubuntu boots fine.
>   
> 
>   
> 
>   Can this be done with Qubes 4.x?
>   
> 
>   How/where to affect such boot commands; can that be done from the
>   boot media/USB stick directly, as we do with other Linux live USB
>   sticks?
>   
> 
>   
> 
>   Thanks,
>   "
> 
> 
> -- 
> https://mastodon.technology/@LeeteqXV/
> 
> ###
> 
> Reply from "Yuraeitha" on Feb. 19th..:
> 
> 
>   
> 
> 
> 
>   
> 
> 
> 
>   
> - show
> quoted text -
> 
> 
> "@LeeteqXV
> 
>   It's probably best you start a new thread, this thread is
>   about a whole different issue altogether.
> 
> But since this is an old thread, I'll briefly answer
>   you. 
> 
>   This what you seek, directing a GPU directly into an
>   AppVM, or any other work arounds, can currently be done in
>   Qubes 3.2. nor Qubes 4.0.
> 
> However, it is planned for Qubes 4.1, which may reach
>   release. Just don't get hyped yet, things can change, 4.0.
>   is barely finished and 4.1. is currently only on the
>   drawing board. Look here for quick information about 4.1. 
> https://github.com/rootkovska/qubes-roadmap you
>   can see the GTX passthrough ability on the map.
> 
> Also, you don't really need Ubuntu for these kind of
>   things, it can easily be fixed up in both Debian and
>   Fedora. You can use Intel graphics just fine for 4k
>   videos, you don't need nvidia for stuff like that on
>   modern motherboard/CPU systems. You may need powerful
>   graphic cards for gaming and high end graphics, but this
>   too isn't possible, at least before Qubes 4.1. anyway. If
>   you didn't need these in Qubes 4, then it will likely make
>   no difference to you to use Intel graphics. Also Qubes
>   dom0 frequently has nvidia graphic issues and may require
>   a full properitary driver download/install, with a manual
>   install.
> 
> To get a bit back on-topic, it saves you whole lot of
>   hassle if you get adjusted to not be depending too much on
>   Ubuntu and others that give everything on a silverplate.
>   Although DVM protected content is never stable regardless
>   of the Linux distribution, unless you download the Google
>   Chrome browser from Google (Not Chromium), which usually
>   always have working DVM videos in any Linux. Issue being,
>   that Firefox and others, often loose the ability to play
>   the video, especially Microsoft silverlight videos, which
>   the work-arounds frequently break.
> 
> Essentially you can play the codecs fine, HTML5 is for
>   example extremely easy to install in Fedora through
>   enabling the RPMFusion repositories, which can easily be
>   done in Qubes fedora template (best make a copy first).
>   But it does not include HTML5-DVM.
> 
> Essentially, DVM is so messed up, you ma/y just want to
>   download the Google Browser specifically for these videos,
>   and just be done with the crapware copyright protectors
>   throw at us. It's not like they care about Linux anyway,
>   so why would changing to Ubuntu make any difference?
>   Ubuntu is just as unstable in this regard of protected
>   content due to lack of developer support of protected
>   contents.
> 
> However, Fedora+Firefox+RPMFusionRepositories+ffmpeg+Firefox's
>   own DVM = Netflix and all HTML5 videos on youtube, and
>

Re: [qubes-users] Re: Can't install Qubes, Rebooting after loading initrd.img

On Fri, February 23, 2018 10:46 am, Daniil .Travnikov wrote:

> I thought that this issues in url which you provided in existing systems
> which already installed. How can I change for example "startup parameters
> for Xen"?

If you are using legacy boot for the installer, go to the Troubleshooting
menu. You might want to first try "Install Qubes R4.0-rc4 in basic
graphics mode" if you haven't already.
You can also press TAB on it to edit the startup options directly.

> How could this changes has any affects on USB Boot Installer from this
> guide? Or maybe I must change some options in this installer, then how
> could I do that? Through terminal in existing system?

EFI is a bit different, not sure you get a Troubleshooting menu there. If
not, see
https://www.qubes-os.org/doc/uefi-troubleshooting/#change-installer-kernel-parameters-in-uefi
for how to edit the configuration directly on the installer.

> I am asking becuase in some reason I can't open terminal in boot process
> from 'installer flash disk' with Qubes Release 4.0-rc4 (when I must click
> 'e' button in process of installation which I showed on sreenshots
> before). But for installed system 3.2 which already on my main ssd disk I
> can do that, but it does not make any sense to change anything in already
> installed system or am I wrong?

You're right, no point in changing the options of your currently installed
R3.2!

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

Re: [qubes-users] Re: Can't install Qubes, Rebooting after loading initrd.img

пятница, 23 февраля 2018 г., 14:07:38 UTC+3 пользователь awokd написал:
> On Fri, February 23, 2018 10:46 am, Daniil .Travnikov wrote:
>

First of all, thank you very much for your time I am very appreciate that you 
trying to help me.

> If you are using legacy boot for the installer, go to the Troubleshooting
> menu. You might want to first try "Install Qubes R4.0-rc4 in basic
> graphics mode" if you haven't already.
> You can also press TAB on it to edit the startup options directly.

Yes, I tried this basic graphics mode, but nothing new changes. What options I 
have on this Tab command line?

Screenshot: https://prnt.sc/iiounx

> EFI is a bit different, not sure you get a Troubleshooting menu there. If
> not, see
> https://www.qubes-os.org/doc/uefi-troubleshooting/#change-installer-kernel-parameters-in-uefi
> for how to edit the configuration directly on the installer.

Like I understand, all this process must be on the system. But I am stuck on 
this process, when I must to mount my usb disk.

Usually when I attach my usb I see him on desktop or in some system folder.
In this guide I see that I must "mount the EFI partition", could you please 
tell me how can I do that in Qubes 3.2?

P.S. When I put 'qvm-block' in terminal I see my usb disk of course, but what 
next?

-- 
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/fb75ef87-a98b-4741-b7d9-a8081c39b554%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Install to Dell T3610, no Intel graphics, VNC install, NVS 310

2018-02-23 Thread CMaurice

Aye, there's no onboard graphics, there's compatibility with VGA or some sort 
of pass through for boot and BIOS, not sure.

But anyway, tried 3.2 and that worked fine! So at least I can learn a bit about 
Qubes before having to re-install for 4 final.

All the best

On Friday, 23 February 2018 02:24:44 UTC, awokd  wrote:
> On Thu, February 22, 2018 1:39 pm, CMaurice wrote:
> > So, having exhausted other options as far as I could tell, followed the
> > instructions for installing over VNC, which went ok.
> >
> > Legacy boot elected in BIOS for hd and for USB media at install.
> >
> >
> > But on boot without nomodeset and no i915 entry went quickly to a reboot
> >
> >
> > Log nomodeset.out attached.
> >
> >
> > Booting without nomodeset and with modprobe.blacklist=nouveau in place of
> > the i915 entry failed at '[OK] Started Accounts Service' (logs dmesg.txt,
> > Xorg.9.log attached).
> >
> >
> >
> > I'd be grateful for ideas on how to proceed, even perhaps alternate
> > graphics card suggestions.
> 
> Saw in your other email this is Qubes 4.0rc4. Looks like you've tried all
> the basic steps and then some. Does this laptop have a way to use Intel
> integrated graphics? If so, check
> https://www.qubes-os.org/doc/intel-igfx-troubleshooting/ for the command
> line option to enable that driver.
> Nvidia and Linux generally don't work well together, and I don't have any
> of their hardware so don't have much insight there. AMD RX580s and earlier
> (maybe newer too but not a lot of data) work pretty well with Qubes, as
> does Intel video (usually).

-- 
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/64870589-0d16-4e6b-9256-d12114612a84%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Can't install Qubes, Rebooting after loading initrd.img

пятница, 23 февраля 2018 г., 5:13:32 UTC+3 пользователь awokd написал:
> On Thu, February 22, 2018 9:51 pm, Daniil .Travnikov wrote:
> > When I updated last time my BIOS Firmware, it was been from here:
> > https://downloadcenter.intel.com/download/23908/Intel-Server-Board-S5520HC
> > -S5500HCV-S5520HCT-and-Intel-Workstation-Board-S5520SC-Firmware-Update-Pa
> > ckage-for-EFI?product=36599
> >
> > "S5520HC S5500HCV S5520HCT S5520SC BIOS Recovery Package for EFI"
> >
> >
> >
> > Maybe this is the problem, that my bios in some reason could working
> > always with EFI mode even if I change it on 'Disable' in bios menu?
> 
> I don't think that's the problem, since in your other email you said it
> was booting from GRUB, correct? Assuming that board uses Intel video, have
> you seen https://www.qubes-os.org/doc/intel-igfx-troubleshooting/ ?

Thank you very much vor your reply.

I thought that this issues in url which you provided in existing systems which 
already installed. How can I change for example "startup parameters for Xen"?

How could this changes has any affects on USB Boot Installer from this guide? 
Or maybe I must change some options in this installer, then how could I do 
that? Through terminal in existing system?

I am asking becuase in some reason I can't open terminal in boot process from 
'installer flash disk' with Qubes Release 4.0-rc4 (when I must click 'e' button 
in process of installation which I showed on sreenshots before). But for 
installed system 3.2 which already on my main ssd disk I can do that, but it 
does not make any sense to change anything in already installed system or am I 
wrong?

-- 
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/13ac5a6f-539d-4fcc-a3e4-b1dc40a029be%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Install to Dell T3610, no Intel graphics, VNC install, NVS 310

On Fri, February 23, 2018 10:28 am, CMaurice wrote:
> Aye, there's no onboard graphics, there's compatibility with VGA or some
> sort of pass through for boot and BIOS, not sure.
>
> But anyway, tried 3.2 and that worked fine! So at least I can learn a bit
> about Qubes before having to re-install for 4 final.

Glad you got it running at least. I realized after I sent my last email
your Dell probably isn't a laptop or you wouldn't be asking about video
cards!

If you are going shopping for one, check out the following in case you
ever want to try pass-through some day.

https://en.wikipedia.org/wiki/List_of_IOMMU-supporting_hardware#AMD
http://www.overclock.net/t/1307834/xen-vga-passthrough-compatible-graphics-adapters
https://wiki.xenproject.org/wiki/Xen_VGA_Passthrough_Tested_Adapters#ATI.2FAMD_display_adapters


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

[qubes-users] Re: Proxy/firewall VM with template fedora-26-minimal non-functional

2018-02-23 Thread velcro

 Try downloading a fresh fedora 26 template:

https://www.qubes-os.org/news/2018/01/06/fedora-26-upgrade/


-- 
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/ce65d625-a1a7-4eba-a3cb-8d35472f247f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] New laptop install R4rc5 fresh install, X startup failed.

2018-02-23 Thread Michael MENG

I bought new Dell i5577 with GTX1050 for R4, however, it shown X startup failed 
when install, I got the same screen below. how can I install R4?

https://13366229192823780453.googlegroups.com/attach/3b6e252a5cb32/q1.jpg?part=0.1=1=ANaJVrH2rTi3F5s4yeRUs1mcblkJI2qGPjCrM_W2U4MWFWPP9pIA0wu4kT_vrTwSpskN2u7UGY-V0XheioXXWTGHhL5nsgmVzPD4ms2CTbWWHL_4m1A22us
 

-- 
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/f6ce7bca-f504-4749-9c17-456b02ecda22%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Can't install Qubes, Rebooting after loading initrd.img

пятница, 23 февраля 2018 г., 16:20:13 UTC+3 пользователь awokd написал:
> On Fri, February 23, 2018 1:10 pm, Daniil .Travnikov wrote:
> 
> > I/O MMU:Not active
> 
> This might be the problem. Look through your BIOS settings and make sure
> it's turned on.
> 
> P.S. You might also want to check out
> https://www.qubes-os.org/doc/intel-igfx-troubleshooting/#workaround-for-existing-systems-with-vt-d-enabled-grub--legacy-mode
> for your R3.2 configuration- it might be why you can't use the newer
> kernel on it.

I enabled this feature and tried again replace "quiet" with "iommu=no-igfx" and 
changed in Qubes 3.2 the startup parameters for Xen:

---
Open a terminal in dom0
Edit /etc/default/grub (e.g. sudo nano /etc/default/grub)
Add to the line GRUB_CMDLINE_XEN_DEFAULT the setting iommu=no-igfx, save and 
quit
Commit the change withsudo grub2-mkconfig --output /boot/grub2/grub.cfg
---


But still nothing. This is screenshot in BIOS with new enable function: 
https://prnt.sc/iiqpdo

-- 
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/e1d9c9e4-bdfe-46d9-94c4-94bb39736b50%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Can't install Qubes, Rebooting after loading initrd.img

пятница, 23 февраля 2018 г., 7:29:00 UTC-5 пользователь awokd написал:
> On Fri, February 23, 2018 11:41 am, Daniil .Travnikov wrote:

> Try replacing "quiet" with "iommu=no-igfx".

Replaced, and have seen some new lines in black screen until again he's got 
rebooted.


> However, I checked out that link for your board and it's pretty old, Q1
> '09. In Qubes R3.2, can you run "qubes-hcl-report"?

This is result:

[user@dom0 ~]$ qubes-hcl-report
Qubes release 3.2 (R3.2)

Brand:  Intel Corporation
Model:  S5520HC
BIOS:   S5500.86B.01.00.0064.050520141428

Xen:4.6.6
Kernel: 4.4.14-11

RAM:16314 Mb

CPU:
  Intel(R) Xeon(R) CPU   E5606  @ 2.13GHz
Chipset:
  Intel Corporation 5520 I/O Hub to ESI Port [8086:3406] (rev 22)
VGA:
  Matrox Electronics Systems Ltd. MGA G200e [Pilot] ServerEngines (SEP1) 
[102b:0522] (rev 02) (prog-if 00 [VGA controller])

Net:
  Intel Corporation 82575EB Gigabit Network Connection (rev 02)
  Intel Corporation 82575EB Gigabit Network Connection (rev 02)

SCSI:
  OCZ-AGILITY3 Rev: 2.15
  OCZ-AGILITY3 Rev: 2.15
  ST1000DM003-9YN1 Rev: CC4C
  Transcend 8GBRev: 1100

HVM:Active
I/O MMU:Not active
HAP/SLAT:   Yes
TPM:Device not found
Remapping:  no

Qubes HCL Files are copied to: 'dom0'
    Qubes-HCL-Intel_Corporation-S5520HC-20180223-080907.yml - HCL 
Info


-- 
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/dbca8a5e-0dec-49b3-bd79-11a92ecb0945%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Can't install Qubes, Rebooting after loading initrd.img

пятница, 23 февраля 2018 г., 15:30:16 UTC+3 пользователь Unman написал:

Thanks for your help!

> Use qvm-block -a to attach the usb disk to a qube.
> Open a terminal in that qube.
> The disk should have appeared as /dev/xvdi, with partitions as xvdi1
> xvdi2 etc. If your EFI partition is the first on the disk:
> Just use 'sudo mount /dev/xvdi1 /mnt' to mount the EFI partition. 
> Then you can edit the files under /mnt

Is it possible to edit this files only in another qubes? Can I do this 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/055e25da-196e-402e-b57a-713e19e673d8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Can't install Qubes, Rebooting after loading initrd.img

2018-02-23 Thread Unman

On Fri, Feb 23, 2018 at 05:19:53AM -0800, Daniil .Travnikov wrote:
> пятница, 23 февраля 2018 г., 15:30:16 UTC+3 пользователь Unman написал:
> 
> Thanks for your help!
> 
> > Use qvm-block -a to attach the usb disk to a qube.
> > Open a terminal in that qube.
> > The disk should have appeared as /dev/xvdi, with partitions as xvdi1
> > xvdi2 etc. If your EFI partition is the first on the disk:
> > Just use 'sudo mount /dev/xvdi1 /mnt' to mount the EFI partition. 
> > Then you can edit the files under /mnt
> 
> Is it possible to edit this files only in another qubes? Can I do this in 
> Dom0?
> 
Of course, if your disk is attached to dom0 rather than to a sys-usb
then you can edit directly in dom0. (I just assumed it wouldnt be.)

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

Re: [qubes-users] Re: Can't install Qubes, Rebooting after loading initrd.img