Re: [qubes-users] HCL - Dell XPS 15 9560

[Mike Keehan]

On Mon, 20 Feb 2017 09:16:11 +0100
Stefan Schlott  wrote:

> Hi,
> 
> installed Qubes 3.2 on my new laptop. After some initial problems, it
> seems to be working great!
> 
> After installing from the ISO image, the graphics driver was working
> fine (at least I remember it this way), only suspend to RAM crashed
> the machine. I updated all packages (fedora template and dom0), and
> after a reboot, X used the framebuffer driver and did not detect the
> Intel graphics chip :-(
> 
> Both problems were solved by enabling the qubes-dom0-unstable repo and
> updating the dom0 kernel to the version provided there. Intel VGA and
> Suspend to RAM are working fine now.
> 
> 
> The nvidia chip (GTX 1050) is not supported by the nouveau driver,
> and I didn't go through the pain (not to speak of the security
> concerns) of manually installing the latest proprietary driver from
> nVidia on dom0.
> 
> 
> Suspend to RAM seems to have some problem with the WLAN driver,
> though. After some suspend cycles, WLAN won't come up again. I put
> the driver ath10k_pci to the suspend-module-blacklist, I think this
> did the trick.
> 
> 
> Stefan.
> 

Hi Stefan,

I too have a new XPS-15 9560, but I can't install Qubes.  The laptop
boots the installer into terminal mode - the graphics installer does
not come up at all.  

Did you have to do anything special to get the graphical installer
running?

Cheers,

   Mike.

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

Re: [qubes-users] HCL - 20H2S00700

[Mike Keehan]

On Tue, 14 Feb 2017 12:03:45 +0100
Vincent Wiemann  wrote:

> ...

> Installation only possible with VNC as text installation mode doesn't
> prompt for encryption password.
> Sleep mode sometimes freezes the device.
> 
> 

Hi Vincent,

How did you use VNC for the installation?  Web searching has not
helped me find out anything about it.

Regards,

Mike.

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

Re: [qubes-users] HCL - 20H2S00700

[Mike Keehan]

On Thu, 23 Feb 2017 11:35:26 +
Mike Keehan <m...@keehan.net> wrote:

> On Tue, 14 Feb 2017 12:03:45 +0100
> Vincent Wiemann <vincent.wiem...@ironai.com> wrote:
> 
> > ...  
> 
> > Installation only possible with VNC as text installation mode
> > doesn't prompt for encryption password.
> > Sleep mode sometimes freezes the device.
> > 
> >   
> 
> Hi Vincent,
> 
> How did you use VNC for the installation?  Web searching has not
> helped me find out anything about it.
> 
> Regards,
> 
> Mike.
> 

Argh, just found Installing Through VNC for Fedora!
Thanks anyway.

Mike.

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

Re: [qubes-users] Re: HCL - Dell Latitude 7480

[Mike Keehan]

On Sun, 19 Mar 2017 21:39:15 -0700 (PDT)
loke...@gmail.com wrote:

> On Monday, 20 March 2017 12:27:43 UTC+8, lok...@gmail.com  wrote:
> > I have not been able to install Qubes 3.2 on this machine.
> > 
> > The installer cannot start as the graphics card is not supported.
> > The result is that you get dropped into the text-based installer
> > which does not work.
> > 
> > This is kind of disappointing as this is a very light laptop that
> > supports up to 32 GB RAM, which would be very nice to have with
> > Qubes.  
> 
> I forgot to include the actual specs for the machine I used for
> testing:
> 
> Intel(R) Core(TM) i7-7600U CPU @ 2.80GHz
> 16 GB RAM
> Intel Integrated HD Graphics 620
> 
> Specs at: http://www.dell.com/sg/business/p/latitude-14-7480-laptop/pd
> 

Have you booted in UEFI mode?  I had the same problem when using legacy
boot.

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

Re: [qubes-users] Installing Qubes 3.2 on an Alienware

[Mike Keehan]

On Fri, 17 Mar 2017 19:18:03 -0400
Tristan Fleming  wrote:

> Has anyone found a work around for Qubes on an Alienware 17 r4?
> 
> I just bought this laptop thinking that it would work with Qubes. So
> far, I havent had any luck. It was a good excuse to buy a new laptop,
> though! ;)
> 
> I bought the Alienware 17 r4
> Intel(R) Core(TM) i7-7700HQ
> 8gb ram DDR4
> NVIDIA GeForce GTX 1060 with 6GB GDDR5 (problem numero uno)
> 
> So, to the point, I have two problems. One is the GFX card. And the
> other is UEFI.
> 
> Oh, and lest we forget the Qubes bugs.
> 
> I booted in Legacy mode, initial graphics GUI starts, Boot into basic
> graphics mode;
> 
> Basic Graphics Mode FAILS
> 
> Txt based install has common bugs: "LUKS was not provided a pw" Cannot
> partition, cannot install!
> 
> On the Hardware Compatibility List, it says Alienware works but
> without sound. So, how did that person get Alienware to work!?
> 
> Any help is appreciated. My problems are common, but someone figured
> this out, right?
> 
> Thanks, crew!
> 

I found that I had to boot in UEFI mode for the graphical installer
to work with my new laptop - legacy booting the usb stick gave me the 
same text installer problems you are seeing.

Mike.

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

Re: [qubes-users] HCL - Dell XPS 15 9560

[Mike Keehan]

On Fri, 26 May 2017 12:40:03 -0700 (PDT)
Alchemist  wrote:

> I just grabbed a new xps15 and the installer is falling back to text
> mode. I'm not sure why we're getting different results on the same
> computers. Anyone have any ideas? 
> 

Use EFI boot with the usb install stick, not legacy bios.

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

Re: [qubes-users] No bootable device neither in BIOS or UEFI after Qubes R3 fresh install

[Mike Keehan]

On Fri, 5 May 2017 15:16:58 -0700 (PDT)
3...@arctop.co wrote:

> > I am trying to install qubes on my xps 15 9560 but for some reason
> > at the installation destination page the internal ssd is not
> > detected any suggestions?  
> 
> I have the same issue, how did you solve it?
> 

Change the disk setting in the bios from RAID to AHCI.

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

Re: [qubes-users] HCL - 20H2S00700

[Mike Keehan]

On Tue, 2 May 2017 20:39:31 -0700 (PDT)
reubenprev...@gmail.com wrote:

> On Thursday, February 23, 2017 at 5:40:19 AM UTC-6, Mike Keehan wrote:
> > On Thu, 23 Feb 2017 11:35:26 +
> > Mike Keehan <m...@keehan.net> wrote:
> >   
>  [...]  
>  [...]  
>  [...]  
>  [...]  
>  [...]  
> > 
> > Argh, just found Installing Through VNC for Fedora!
> > Thanks anyway.
> > 
> > Mike.  
> 
> Can you explain how you got VNC to work? I can get it started, but
> networking is not working by default so I can't connect to it. Do you
> know how to start networking with ethernet?
> 

Ah, sorry I can't.  I didn't use vnc in the end, as I found that
the Qubes installation gui worked OK if I booted the usb stick
in UEFI mode instead of legacy.

Mike.

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

Re: [qubes-users] Text-based install inevitably failing on my ASUS GL552VW

[Mike Keehan]

On Sun, 21 May 2017 09:36:35 -0700 (PDT)
yessiou...@gmail.com wrote:

> Hello, I tried to install qubes on my ROG laptop a couple months ago
> and didn't get very far. These last couple of days, I've decided to
> re-tackle the issue because I am really interested in using this OS.
> This time, I managed to get a little further on understanding the
> issue I've been having but I do need help to continue.
> 
> So, I'm using a usb flash drive as my installation source. Whenever I
> boot from my usb, I'm greeted with the ususal installation menu with
> all the features it normally should have. Whenever I try to install
> qubes on my system, the graphical menu tries to load and I can see
> the Qubes logo on the light blue background for a split second,
> before it disappears and I continue on the text install menu. No
> matter what I do, I end up with this error :
> 
> "Encryption requested for LUKS device sda2 but no encryption key
> specified for this device."
> 
> Before the installer stops and I have to restart my pc. After reading
> up a little bit on the subject, it seems like the text installer
> simply doesnt allow you to input the encryption key you want to use,
> so it inevitably fails. It seems like this might be due to
> incompatibility with my GTX 960M card, where my system attempts to
> use it but fails because Qubes is incompatible with it. What should I
> do? Something I do know is I could force my system to use intel
> graphics, but my BIOS doesn't let me do that anywhere, and I'm scared
> of flashing another BIOS, screwing things up and bricking my
> expensive device.
> 
> So anyway, thanks in advance to anyone who takes the time to reply,
> and regardless I hope you have a nice day.
> 

I had to use EFI to boot the usb stick on my machine - the legacy
bios boot always ended up in the text installer.  

Mike.

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

Re: [qubes-users] Possible to add second interface to sys-firewall?

[Mike Keehan]

On Fri, 6 Oct 2017 10:20:18 -0400
Ed  wrote:

> What I would like to do is add a second IP to both sys-firewall and 
> sys-net so that I can NAT traffic from one of my VM's in/out through 
> these IP's.  So what I end up with is two IP's on sys-net, one
> handling all the traffic for most of my VM's, the other handling
> traffic for one specific VM.  This way I can do additional firewall
> restrictions on this VM in my networks.
> 
> If I manually add the IP addresses to sys-net and sys-firewall,
> manually add the destination NAT and source NAT rules to both as
> well, then manually add a route in sys-net, and also force another
> rule into the IPTABLES raw table on sys-net (to override a rule added
> by /etc/xen/scripts/vif-routes-qubes which restricts all incoming
> traffic from sys-firewall to the IP assigned by qubes to the default
> interface), then I'm able to make this work.
> 
> However, this is very finicky and totally unscriptable in this 
> configuration, and I'd really like this to be something auto
> configured on boot.
> 
> I've look and looked and don't see where I can add a second interface 
> definition to any config files.  If I manually edit the xen 
> sys-firewall.conf file it just gets overwitten by qubes.  I can do
> all the iptables rules I need in the /rw/config scripts, but what I
> really need is for sys-firewall to add another virtual interface for
> me.
> 
> I tried running: sudo xl network-attach sys-firewall 
> script=/etc/xen/scripts/vif-route-qubes ip=10.150.10.10
> backend=sys-net This will add the interface and setup sys-net with
> the correct routes and rules, HOWEVER, the interface that it adds to
> sys-firewall has the same IP as the existing interface which breaks
> all the traffic going out of sys-firewall
> 
> Has anyone ever had any success doing something like this?
> 
> Any suggestions out there?
> 
> Thanks,
> Ed
> 

Wouldn't it be possible to add a second Firewall VM to be used solely
by your special single vm?

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

Re: [qubes-users] Re: Possible to add second interface to sys-firewall?

[Mike Keehan]

On Fri, 6 Oct 2017 12:17:26 -0400
Ed <e...@edjusted.com> wrote:

> On 10/06/2017 12:10 PM, Mike Keehan wrote:
> 
> > 
> > Wouldn't it be possible to add a second Firewall VM to be used
> > solely by your special single vm?
> >   
> 
> Yes I believe this would def work, and also should be
> automatic/reliable across reboots, but I was really hoping to not
> give up 2-4GB of RAM just for this purpose.
> 

I think you will find that the firewall VM runs OK in just 500Mb, maybe
less.  Search the mail list for "vm memory" - there have been a number
of discussions about how much is actually used by the system VMs.  (I
can't remember the details off hand, or I would give more info!)

It is worth knowing that although a VM is initially set up with a 4Gb
memory allocation, it only uses what it needs.   The rest is still
available to the other qubes etc.


   Mike.

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

Re: [qubes-users] New HCL Entry: Lenovo ThinkPad T470 (20HDCTO1WW)

[Mike Keehan]

On Thu, 30 Nov 2017 02:07:56 -0800
Joe Hemmerlein  wrote:

> Hi,
> 
> so far it was easy to install and run Qubes OS 4.0 RC3 (and RC2) on
> this hardware - as long as I keep boot mode on "Legacy Only".
> 
> However, the TPM chip on this hardware works in UEFI boot mode only;
> and even with secureboot disabled and CSM support enabled, I can't
> get Qubes OS to boot in UEFI mode:
> - The installer doesn't run in UEFI mode (I get text mode grub, but
> whatever i select simply does nothing and returns to grub)
> - If I turn UEFI mode on after installing Qubes OS, I don't even get
> grub.
> - I tried the UEFI troubleshooting guide to no avail, although I was
> unable to run efibootmgr directly while in legacy boot mode ("EFI
> variables are not supported on this system") so in order to run
> efibootmgr, i booted a separate Fedora 26 Live image which does boot
> in UEFI mode. However, even with updated records, the result is the
> same: selecting those options from the UEFI boot menu simply makes
> the screen flicker once and then i'm back in the UEFI boot menu.
> - I tried copying the EFI and CFG file to /EFU/BOOT and renaming them
> to BOOTX64.EFI and .CFG, and also created new entries with efibootmgr
> for this, again without success.
> 
> 
> I also tried installing Qubes OS 3.2 on this system which didn't work
> and initial troubleshooting failed; but I'd like to concentrate my
> efforts on making this work for Qubes 4.0 so i didn't spend too much
> time on getting Qubes OS 3.2 on the T470.
> 
> Any hints about troubleshooting the UEFI boot option are appreciated;
> i can also provide more exact details about what i already tried.
> Given the specs of this machine, I'm really determined to not give up
> easily.
> 
> For now, I'll test other functionality in legacy mode only.
> 
> Cheers,
> -joe
> 

Hi Joe,

This is the content of my EFI/qubes directory after installing
Qubes 4.0-rc3 in EFI mode :-

-rwxr-xr-x 1 root root 22231327 Nov 28 17:29 
initramfs-4.9.56-21.pvops.qubes.x86_64.img
-rwxr-xr-x 1 root root  5316864 Nov 28 17:29 
vmlinuz-4.9.56-21.pvops.qubes.x86_64
-rwxr-xr-x 1 root root  902 Nov 28 17:36 xen.cfg
-rwxr-xr-x 1 root root  2056349 Nov 28 17:29 xen.efi

I then selected which EFI directory to boot from using the bios.

I think the EFI/Boot directory is just a default.

Mike.

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

Re: [qubes-users] Please help list of supported graphics cards

[Mike Keehan]

On Sun, 3 Dec 2017 10:22:54 -0800 (PST)
r...@tuta.io wrote:

> Hey Mike. I did took the drive out and moved to my laptop. I run
> qubes on there with 3.2. I can install 3.2 with no errors on laptop.
> But when i tried to install 4 on the drive with laptop I get the same
> errors. I cant seem to install the version 4 iso on anything. 
> 
> What I was hoping to do was install 4 on laptop and try to get
> working on desktop but that seems to a problem now.
> 
> Im wondering if I should install version 3.2 and attempt to change
> the kernels there and move the drive over?
> 

Yes, 4.0 needs the vtd/iommu stuff to work.  I haven't tried installing
it on a machine without those capabilities.

If you install 3.2 on the drive, and then can use it OK on the other
system, you should be able to upgrade the kernel to 4.11 or more.
However, you still won't be able to install 4.0 on that system until
the graphics issue is fixed or worked around.

Mike.

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

Re: [qubes-users] New HCL Entry: Lenovo ThinkPad T470 (20HDCTO1WW)

[Mike Keehan]

On Thu, 30 Nov 2017 17:10:46 -0800 (PST)
Joe Hemmerlein <voltylici...@gmail.com> wrote:

> On Thursday, November 30, 2017 at 1:37:59 PM UTC-8, Mike Keehan wrote:
> > Hi Joe,
> > 
> > This is the content of my EFI/qubes directory after installing
> > Qubes 4.0-rc3 in EFI mode :-
> > 
> > -rwxr-xr-x 1 root root 22231327 Nov 28 17:29
> > initramfs-4.9.56-21.pvops.qubes.x86_64.img -rwxr-xr-x 1 root root
> > 5316864 Nov 28 17:29 vmlinuz-4.9.56-21.pvops.qubes.x86_64
> > -rwxr-xr-x 1 root root  902 Nov 28 17:36 xen.cfg -rwxr-xr-x 1
> > root root  2056349 Nov 28 17:29 xen.efi
> > 
> > I then selected which EFI directory to boot from using the bios.
> > 
> > I think the EFI/Boot directory is just a default.
> > 
> > Mike.  
> 
> Thanks, Mike. In my case I can't even install Qubes in EFI mode
> because the installer won't run; and installing Qubes in Legacy mode
> will lead to an empty .cfg file. I'll take another stab at it
> tonight. -joe
> 

Hi Joe,

I had trouble installing due to video driver confusion.  As the Qubes
installer is based on Fedora, I tried installing that first to see what 
happens.  Same problem.  It turned out that I needed to add the
option "modprobe.blacklist=nouveau" to the kernel boot line in the
installer to allow Fedora to install OK.

The problem then was how to add that option to the Qubes installer.
Managed in the end by binary editing the iso.

Best of luck with your attempts.

   Mike.

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

Re: [qubes-users] install of 4.0 rc3 failing on XPS 15 (9560)

[Mike Keehan]

On Mon, 11 Dec 2017 02:45:23 -0800 (PST)
Piers Saye  wrote:

> Dell XPS 15 (9560) 1TB 32GB HiRes Touchscreen
> 
> 3.2 running fine with the previously documented fixes.
> 
> 
> When I try and install 4.0 rc3 the installer hangs often prior to
> getting to the GUI installer with a soft lock on CPU #7
> 
> 
> When it does proceed further I am able to get through the various
> screens to the point of actual installation however it gets to action
> (797/1018) qubes-mgmt-salt-base-topd.noarch and then hangs with
> system freeze.
> 
> Any thoughts or anyone that has experienced the same or ideas?
> 

Hi Piers,

I had the same problems with my XPS 9560.

I managed to get Qubes 4.0-rc3 installed by adding the option
"modprobe.blacklist=nouveau" to the installer's boot command line.

It is all running fine now.

Mike.

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

Re: [qubes-users] Rc2 hangs on install -- Dell Inspiron i5759-8835SLV

[Mike Keehan]

On Wed, 1 Nov 2017 16:32:24 -0700 (PDT)
billol...@gmail.com wrote:

> Yeah, I'll do that.  On the other hand, it may be a Fedora thing.
> Just for giggles, I downloaded F26, and it won't install, either --
> it times out, though it gives a different error when it does.
> 
> I use these cheap flash drives I buy in bulk off ebay.  I'll go get a
> pricey one and see if it makes a difference.  But I gotta say, these
> same drives work fine for ubuntu and KDE neon.
> 

I've been having similar 'stuck' problems on my laptop.  And trying to
install Fedora 26 got stuck too.

I found that in my case it is the nouveau driver that gets stuck - the
driver can't handle the newest nvidia chips yet.

I managed to get Fedora to install by adding the option 
'modprobe.blacklist=nouveau' to the kernel boot command line (at the
Fedora install boot use 'e' to edit the command line).

However I haven't yet figured out how to do that for Qubes bootup.

Mike.

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

Re: [qubes-users] Please help list of supported graphics cards

[Mike Keehan]

On Sun, 3 Dec 2017 05:52:14 -0800 (PST)
r...@tuta.io wrote:

> I have a asus strix 270g board with Intel I7 7700k chip. Monitor is
> Ultra Hd.
> 
> My asus rx580 doesnt work and cant seem to set my display to use
> Intel graphics. 
> 
> Keep getting pane dead or lux key errors.
> 

You probably need a more recent kernel - 4.11 or 4.12 handle the
newer Intel graphics devices.  There are more up to date kernel in
the testing repositories.
(there have been a number of posts in the mailing list about
 upgrading to newer kernels and how to do it.)

Mike.
 

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

Re: [qubes-users] New HCL Entry: Lenovo ThinkPad T470 (20HDCTO1WW)

[Mike Keehan]

On Sun, 3 Dec 2017 03:03:59 +0100
Marek Marczykowski-Górecki  wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
> 
> On Sat, Dec 02, 2017 at 01:02:52AM -0800, Joe Hemmerlein wrote:
> > Danke, Stephan, your pointers were very valuable!
> > 
> > At first, I decided to just borrow an external DVD drive and boot
> > off a DVD burned from the ISO, in UEFI mode. The result however was
> > the same as when booting from my previously-created USB stick: grub
> > boots, but no matter what i select, the screen briefly flashes and
> > takes me back to grub. So.. yeah, the ISO image does not appear to
> > be usable out of the box on some UEFI devices, even when burning it
> > to a DVD.
> > 
> > Your description of the livecd-tools helped make good progress, but
> > still without ability to boot the installer completely, but they
> > sent me in the right direction. I then found
> > https://groups.google.com/forum/#!topic/qubes-users/4VsKdxnKHBk,
> > which described a process very similar to yours (it omits the part
> > about using dosfslabel, but has a part about also updating the
> > xen.cfg file).
> > 
> > Altogether, this did the trick!  
> 
> Thanks for posting detailed instruction. And for the pull request for
> qubes-doc!
> 
> > In condensed form, this is what i did to create a USB install stick
> > that works with UEFI on the T470: 1. Use the "livecd-iso-to-disk"
> > utility from fedora livecd-tools to put the ISO image onto an USB
> > stick 2. rename the USB stick's partition label to BOOT 3. edit
> > the /BOOT/EFI/xen.cfg file on the USB stick's partition to make
> > sure all LABEL= instances are replaced with LABEL=BOOT  
> 
> Does anyone have an idea what the difference livecd-iso-to-disk make,
> compared to isohybrid? If possible, we'd like to installation iso work
> out of the box on UEFI systems, including new ones...
> 
> I wonder if Fedora netinst iso (_not_ Live iso) boot on such new
> hardware, after directly dd-ing it to USB stick. Can you check that?
> Just see if installer starts. It's here:
> 
> https://alt.fedoraproject.org/
> 
> If that would work, I can try to find what is different about those
> images and fix Qubes iso.
> 
> - -- 

Hi Marek,

Even using that network iso to boot my Dell XPS 15 (2017), I still need
to add the option "modprobe.blacklist=nouveau" to the boot command line
to allow the installer to work.  Without that option, the installer
gets a 'stuck cpu' error, with the stack trace showing the nouveau
driver as the culprit.

I could not figure out how to edit the xen.cfg file to add the option
there - others seem to have managed to do that though.

Best wishes,

Mike.

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

Re: [qubes-users] Please help list of supported graphics cards

[Mike Keehan]

On Sun, 3 Dec 2017 08:14:47 -0800 (PST)
r...@tuta.io wrote:

> Didnt think about how new it was. I even attempted linux mint
> cinnamon and didnt install. Viewed fine on usb but wouldnt finish
> install. 
> 
> Do you suggest the 4.0-rc3 install or is there a link to upgrading
> kernal manually before install?
> 
> I did google search to upgrade kernal in Qubes but only saw how to
> update while installed. 
> 

Hi,

Ah right, I didn't realise that you couldn't install Qubes.

As for 4.0-rc3, if your chip is i7700 then it should support Qubes
requirements properly.  You may have to make changes in your Bios
to allow virtualisation, iommu and vtd.

Mike.

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

[qubes-users] Nouveau driver does not work during installation of 4.0rc2

[Mike Keehan]

Hi,

Installing 4.0rc2 fails after approx 600-700 packages.  I found
that one of the cpus was getting "stuck after 22secs" - the reason
seems to be that the nouveau driver does not work with the version
of the nvidia chips on my laptop (even the git kernel does not work
with it yet).

The same problem occurs when trying to install Fedora 26.

So I need to add "modprobe.blacklist=nouveau" to the kernel command
line when booting the installer.  This allows Fedora to install.
But I can't figure out a way to do that in the Qubes installer.
Anyone have an idea?

I tried using the grub command line, but the commands available do
not match up with the grub manual online - I'm presuming this is a 
security measure.

Mike.

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

Re: [qubes-users] Re: Nouveau driver does not work during installation of 4.0rc2

[Mike Keehan]

On Sun, 29 Oct 2017 12:11:59 -0700 (PDT)
Foppe de Haan <0spinbo...@gmail.com> wrote:

> On Sunday, October 29, 2017 at 3:44:45 PM UTC+1, Mike Keehan wrote:
> > Hi,
> > 
> > Installing 4.0rc2 fails after approx 600-700 packages.  I found
> > that one of the cpus was getting "stuck after 22secs" - the reason
> > seems to be that the nouveau driver does not work with the version
> > of the nvidia chips on my laptop (even the git kernel does not work
> > with it yet).
> > 
> > The same problem occurs when trying to install Fedora 26.
> > 
> > So I need to add "modprobe.blacklist=nouveau" to the kernel command
> > line when booting the installer.  This allows Fedora to install.
> > But I can't figure out a way to do that in the Qubes installer.
> > Anyone have an idea?
> > 
> > I tried using the grub command line, but the commands available do
> > not match up with the grub manual online - I'm presuming this is a 
> > security measure.
> > 
> > Mike.  
> 
> You should be able to press e and edit the kernel parameters while
> the xen choice menu is up?
> 

Yes, I thought so too:)  But the command is just to run a chainloader,
and adding the option at the end of the line had no effect.

I might try mounting the usb stick in another Linux, copying the file-
system to disk, editing the xen.cfg file (I think that was the name),
and then building a new iso from that.  All a bit of a palaver, but
it ought to work.

Thanks for taking time to help.

Mike.

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

Re: [qubes-users] i7-8750U Coffee Lake Processor Experience.

[Mike Keehan]

On Sat, 19 May 2018 01:57:06 -0700 (PDT)
deusestveritasinsempiter...@gmail.com wrote:

> If you have used the i7-8750U Coffee Lake Processor with Qubes 4.0,
> please drop a short message detailing (Make, Model ect) if it worked
> for you.
> 
> https://groups.google.com/forum/#!topic/qubes-users/hJZLAP0kFG4 This
> is the original message about the problems stemming from the GL63
> 8RD-067 (https://us.msi.com/pdf/nb/GL63%208RD-067.pdf). Figured that
> with all MSI laptops listed on the HCL working with Qubes 4.0 (at
> least fully installing) that the one thing that not one computer had
> on the entire HCL was a i7-8750U Processor-- could be the source of
> the problem.
> 
> Quick recap of the problem: 
> 
> When booting and heading to install everything is Great. Starting
> install everything is Great until [qubes-mgmt-salt-base-topd-]
> [782/1018] (sometimes it's [786/1018] [787/1018] [794/1018]
> [796/1018] but always this file in front
> [qubes-mgmt-salt-base-topd-]) just stops the install, doesn't through
> an error or freeze up, just stops installing. Yes it has been left
> for hours at that stage, you can hear the HHD stop spinning and the
> light that represents it is being written on turns off. One time it
> made it past [796-1018] and threw an error (Tried install via 7
> different USB's and writing dd in Rufus and Fedora) for the first
> time. Never copied the error and it never showed up again. It
> pertained to [salt-master-2017.7.1-1.fc25.noarch.rpm] failing or some
> sort (carelessness to not document is fully noted). 
> 
> Tried to create a Live Bootable using USB as HD with the Laptop in
> question and it failed at the exact same point [782/1018] as it had
> numerous times with the 1TB HDD. Created and a Live Bootable using a
> different computer with the same metrics, and fully booted with not
> even a hiccup. 
> 
> If you can answer any of these questions that would be great: What
> does [qubes-mgmt-salt-base-topd] correlate with? Or even "Salt"? 
> 
> 
> Further reading on this problem: 
> https://groups.google.com/forum/#!topic/qubes-users/hJZLAP0kFG4.
>  
> 
> 
> THANK YOU
> BEST 
> ERIN D.
> 

If it has nVidia graphics, try turning it off/blacklisting it.  Been
discussed many times on this list.

Mike.

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

Re: [qubes-users] i7-8750U Coffee Lake Processor Experience.

[Mike Keehan]

On Sat, 19 May 2018 08:53:31 -0700 (PDT)
deusestveritasinsempiter...@gmail.com wrote:

> > If it has nVidia graphics, try turning it off/blacklisting it.  Been
> > discussed many times on this list.  
> 
> 
> Have tried Nouveau.modeset=0 at the install menu using tab.
> 
> When Qubes 3.2 was installed on the Laptop in question it worked
> completely except for one thing- The display was forced to be 800x600
> and it couldn't be changed with any Xrandr command. 
> 
> Do you know of another way of Disabling/Deleting Nvidia short of
> removing it? Returning it would be near impossible after removing it
> from  motherboard. 
> 
> Have you ever known of anyone using the i7-8750U Processor with Qubes?
> 
> 
> 
> THANK YOU 
> BEST 
> ERIN D.
> 

At the install menu (using tab), enter "modprobe.blacklist=nouveau".
This stops the nouveau driver loading, so the nVidia graphics driver
can't do anything at all.

Mike.

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

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

[Mike Keehan]

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

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

Hi Jarle,

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

Do you know if anyone has achieved this?

Mike.

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

Re: [qubes-users] 4.0-rc4 Install Help

[Mike Keehan]

On Sat, 3 Feb 2018 08:00:33 -0800 (PST)
Shashank  wrote:

> I am using dell XP’s 15 9560, I set the SATA option to ahci
> Instead of RAID and boot into qubes. Qubes 3.2 worked with above
> options perfectly. Is there a way I set legacy mode explicitly? I
> couldn’t find the option 
> 

That's the same laptop as mine.  In the bios, there are a couple of
boot settings.  You need to enable Legacy boot in one of them.
It's not a disk thing.

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

Re: [qubes-users] 4.0-rc4 Install Help

[Mike Keehan]

On Sat, 3 Feb 2018 08:29:08 -0800 (PST)
Shashank  wrote:

> I found it!!
> I have a couple of questions before I change to legacy. Do you use
> legacy and uefi? So the last time I was trying to install(ona diff
> machine) I had switched to legacy and installed qubes rc3. When I
> wanted to boot back into windows I changed to uefi and all he’ll
> broke loose I couldn’t boot back into windows and it was a huge mess. 
> 
> I can’t even remember how I was able to install windows 10 on it back
> again. I always thought that switching back to uefi mode would let me
> boot back into windows. Do you also do the switch? 
> 

In 3.2, Qubes installed OK from an UEFI boot, but it installed itself
as the first and only boot option in the bios.  I was able to add back
the original UEFI boot options in the bios, and then use the F12 to
interrupt before boot, and select Qubes from the one-time menu list.

The best thing to do is to backup your EFI partition first, and make
a note of the bios settings regarding boot up and UEFI.

You should be able to boot in UEFI mode for Windows, but be able to
use Legacy boot for Qubes by interrupting the bios with F12 and then
selecting Qubes there.

But as I say, I haven't managed to get there yet.  I had to fix the EFI
partition this time too - for some reason the installer messes up the
EFI partition type on the disk, and the bios doesn't recognise any boot
partition.  I had to boot from a cdrom and use fdisk to change the EFI
partition type to EFI (which fdisk thought it was anyway!).

I had rc3 running fine, all in UEFI mode, so I think it will all work
eventually.

Good luck.

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

Re: [qubes-users] 4.0-rc4 Install Help

[Mike Keehan]

On Sat, 3 Feb 2018 05:37:05 -0800 (PST)
Shashank  wrote:

> Hi I’ve been trying to install qubes 4.0 rc4 in my dell xps15
> But I am not able to get the installation done. 
> 
> After I boot through the USB:
> 
> *starting graphic installer
> *if installer doesn’t start type inst.txt to start text install
> * not starting VNC because we don’t have network
> * cannot start installation 
> *PRESS ENTER
> 
> At the bottom of the screen I see
> * PANE DEAD
> 
> and the message below goes on repeating
> Watchdog: BUG: soft lockup - cpu stuck for 22s[xorg:1325]
> 
> I tried installing rc3
> Rc3 shows the install menu but again has the same
> Problem like mentioned above
> 
> Could anyone guide me to install it. 
> 

You need to add 'modprobe.blacklist=nouveau' to the kernel options
in the boot line.  Hit the Tab key on the be=oot menu line that you
want to use (I used the Check and Install line), then move the 
cursor to the 'quiet' word and append the above phrase.

Best of luck.

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

Re: [qubes-users] 4.0-rc4 Install Help

[Mike Keehan]

On Sat, 3 Feb 2018 06:45:00 -0800 (PST)
Shashank  wrote:

> Hi 
> 
> The installation does not take me to the options for selecting
> 
> Initially there is a long list of loading that happens 
> 
> And immediately after that it’s the screen that I’ve posted above 
> 
> There is no check and install, install, or rescue qubes screen
> 
> Thanks
> 

You might need to use your Bios boot select options.  

When I first tried the installer, I got the same thing - it tried to
boot up straight into the installer, without giving me options.

I had to interrupt the laptop's boot phase (F12 on my Dell), and then
choose the option to make it boot from the usb in legacy mode I think.
Then the boot menu appeared.

Mike.

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

Re: [qubes-users] 4.0-rc4 Install Help

[Mike Keehan]

On Sat, 3 Feb 2018 07:25:41 -0800 (PST)
Shashank  wrote:

> Yes I am doing the same thing, in fact I had qubes 3.2 earlier 
> Now switching to 4.0. But I am getting this error. 
> 
> I enter the bios boot menu by hitting F12 (one time boot menu)
> And then select the usb to boot into. But for some reason it’s all
> messed up and I really want 4.0. 
> 
> How else would I get to boot options to enter the command 
> Modprob.blacklist=nouveau or
> Inst.text 
> 

Use the Legacy boot, not the UEFI boot option.  Legacy runs grub to
diplay the options menu.  

I ought to warn you that I did not manage to finish the installation
yet.  Everything worked OK up to the boot loader install - that failed
and I don't know why yet.  Also the building of the "init ram disk"
(or whatever it is called - I forget) never finished, so I can't yet
boot into rc4.  Will have another go probably next week.

Mike.

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

Re: [qubes-users] 4.0-rc4 Install Help

[Mike Keehan]

On Sat, 3 Feb 2018 09:22:08 -0800 (PST)
Shashank  wrote:

> I guess I’ll not jump into booting into legacy mode and having to
> mess up all the boot options again. If you do find a way to install
> it in uefi mode like 3.2 please do post the solution. 
> 

HI again.

Well I have managed to get rc4 installed in UEFI mode, but it's not 
a nice process :)

The Qubes iso seems to contain two menus for EFI booting, but the
Dell XPS15 won't display them at all, hence there is no possibility
to edit the boot line and add the modprobe.blacklist option at bootup.

There are two ways I've found to overcome this - in one, I edited the
Qubes iso file before writing it to a usb stick, and the other was by
following the Lenovo troubleshooting link, 
https://www.qubes-os.org/doc/thinkpad-troubleshooting/

1. Binary edit the Qubes iso (I used gvim as plain vim could not
   handle the temp file!?!).
   Search for "i915.preliminary_hw_support=1" and REPLACE it with
   the string "modprobe.blacklist=nouveau   ".  This MUST be exactly
   the same length as the i915 string, so it add three spaces at its
   end.  ANY change in the length of the text line will damage the
   iso and it definitely won't work.

   This probably only needs to be done for the "qubes-verbose" menu
   options, but I didn't check this, I just replaced all the repeats
   of the string in the two menus.  There is a third menu for GRUB
   legacy, but I did not bother replacing them there.

   Then write out the iso to usb, and reboot.  Interrupt the Dell boot
   screen with F2 and select the UEFI usb boot option.  All should work
   OK.  (Qubes-check will fail because the iso has been edited, but
   the check option only appears when legacy booting.)

2. Or, follow the Lenovo troubleshooting guide at the link above, and
   create the usb and change the Label to BOOT and mount it.  I could
   not find the xen.cfg file, but there was a ".cfg" (can't remember
   the name) that contained the bootup command lines.  I replaced the
   option "quiet" with the modprobe.blacklist=nouveau string.  Length
   of the string does not matter in this case. Save the file, unmount
   the usb and try to boot from the it.

   It didn't provide an UEFI boot option on my DELL, but I was able to
   boot the "fallback boot on Anaconda" from my boot manager "refind".
   You may not want to go to the trouble of installing that if you are
   not multi-booting your laptop.  In which case, you only have option
   1.

Some of the problems with the Dell (apart from the nVidia device), are
that it seems to require that any EFI partition must have both the
correct partition type (EFI) and the specific EFI disk identifier,
otherwise its bios does not recognise an EFI boot partition.

Mike.

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

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

[Mike Keehan]

On Fri, 23 Feb 2018 05:50:40 -0800 (PST)
Michael MENG  wrote:

> 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 could try adding "modprobe.blacklist=nouveau" to the boot command
line.

Search the mailing list for similar reports in the past.

Mike.

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

Re: [qubes-users] HCL - Dell XPS 15 9560

[Mike Keehan]

On Wed, 27 Dec 2017 22:18:24 -0800 (PST)
placeholderda...@gmail.com wrote:

> Hey Mike, 
> 
> I am having the same issue as you described. Attempting to install
> 3.2 or 4.0 on a usb and it fails to start X. On 3.2 it just straight
> fails to start, on 4.0 it starts but then goes into a 'soft lockup'
> and then crashes. Anything you specifically did to resolve the issue?
> My bios is the latest available from Dell (1.6.2 I believe).If i
> choose to 'test this install'  I can get to the sceeen where i see
> the qubes logo and the loading bar at the bottom but it just stays
> there forever and never does anything? 
> 

I had to add the option "modprobe.blacklist=nouveau" to the kernel
boot line in xen.cfg.

(I ended up binary editing the iso file before writing it to a usb
stick.  I think there is an easier way, but I couldn't figure it out).

Mike.

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

Re: [qubes-users] High spec laptop for Qubes OS

[Mike Keehan]

On Sun, 25 Feb 2018 01:11:16 +
a...@adammccarthy.co.uk wrote:

> 
> 
> I'm going to buy a new laptop with a higher spec which should
> hopefully handle things well. The following laptops are my final five
> contenders. They all have a discrete GPU, which I'm hoping to
> passthrough to a VM for playing streaming video (h264/h265/vp9
> codecs). 
> 
> I get the impression from the HCL that they should all work fine as
> long as I replace any non-Intel wifi m.2 sticks with an Intel 8265.
> Do you have any thoughts on whether one would be more appropriate
> than another?
> 
> Dell XPS 15 9560 (2017)
> Intel i7-7700HQ Quad Core
> 32GB RAM
> 512GB M.2 NVMe
> Intel + NVIDIA GTX 1050
> 
> Dell XPS 15 2018
> Intel i7-8705G Quad Core
> 32GB RAM
> 512GB M.2 NVMe
> Intel + Radeon RX Vega M GL
> 
> Dell Precision 5520
> Intel Xeon E3-1505M v6 Quad Core
> 32GB RAM
> 512GB M.2 NVMe
> Intel + Nvidia Quadro M1200
> 
> Lenovo P51
> Intel Xeon E3-1505M v6 Quad Core
> 32GB RAM
> 512GB M.2 NVMe
> Intel + NVIDIA Quadro M2200
> 
> Razer Blade
> Intel i7-7700HQ Quad Core
> 16GB RAM
> 512GB M.2 NVMe
> Intel + NVIDIA GTX 1060
>

Hi Adam,

I use the Dell XPS 15 9560 (2017) which works well, but the Nvidia chip
does not work with the nouveau driver at all (yet - might do in future).
I have not tried using Nvidia's own driver.  My screen is 1920x1080,
and handles HD video OK  but with the occasional slight tear.  CPU use
runs to about 30% avg on a HD video.

Best of luck,

  Mike.


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

Re: [qubes-users] Unsupported hardware detected

[Mike Keehan]

-d
On Mon, 10 Sep 2018 13:16:59 +0200
Marc Ballesteros  wrote:

> Hello.
> I am trying to install qubes os 4 on my computer, but I receive the
> "Unsupported hardware detected" message (Missing features:
> HVM/VT-x/AMD.V, IOMMU/VT/)
> I verified the CPU compatibility with lscpu and I see the VT-x
> virtualization system enabled and the ept flag.
> It is possible to install Qubes OS 4 on this system? Thanks
> 
> 
> 
> Arquitectura:x86_64
> modo(s) de operación de las CPUs:32-bit, 64-bit
> Orden de los bytes:  Little Endian
> CPU(s):  8
> Lista de la(s) CPU(s) en línea:  0-7
> Hilo(s) de procesamiento por núcleo: 2
> Núcleo(s) por «socket»:  4
> «Socket(s)»  1
> Modo(s) NUMA:1
> ID de fabricante:GenuineIntel
> Familia de CPU:  6
> Modelo:  60
> Nombre del modelo:   Intel(R) Core(TM) i7-4790 CPU @
> 3.60GHz
> Revisión:3
> CPU MHz: 3396.892
> CPU MHz máx.:4000,
> CPU MHz mín.:800,
> BogoMIPS:7195.68
> Virtualización:  VT-x
> Caché L1d:   32K
> Caché L1i:   32K
> Caché L2:256K
> Caché L3:8192K
> CPU(s) del nodo NUMA 0:  0-7
> Indicadores: fpu vme de pse tsc msr pae mce
> cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr
> sse sse2 ss ht tm pbe
> syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts
> rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq
> dtes64 monitor ds_ cpl vmx
> smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic
> movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm
> cpuid_fault epb inv
> pcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept
> vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid xsaveopt
> dtherm ida arat pln
> pts flush_l1d
> 

Hi Marc,

Qubes 4 requires VT-d in addition to VT-x.  Have a look in the bios
setup to see if you can turn it on there.

Mike.

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

Re: [qubes-users] Re: Security questions (templates and kde)

[Mike Keehan]

On Wed, 7 Mar 2018 12:54:17 -0800 (PST)
Yuraeitha  wrote:

> 
> > I would love to hear how you divide your VMs up. I was looking for
> > examples online, but I couldnt find any; aside from an (ITL?) essay
> > I read last year. But starting easy and growing is good advice.   
> 
> Sure :)
> 
> I put some 6 to 7 launchers next to each others at the upper left
> corner. There are different ways to do this with Qubes in mind, for
> example two clean methods are to either put a single AppVM or similar
> AppVM's in a single launcher and then have multiple of launchers for
> different AppVM's, or instead put all browsers in a single launcher,
> all file-managers in another, all system tools and various VM
> terminals in another, music players and things like these in a mix
> launcher, work tools like libreoffice and similar in yet another one.

Thanks for that Yuraeitha!

I had been looking at editing the Qubes menu to sort it more to my
liking, and wasn't getting anywhere.  But your method of using xfce's
Launchers is just what I needed.  Five minutes work and now I have
a much better "menu" system.  Just what I want.

Thanks again,

   Mike.

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

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

[Mike Keehan]

On Sun, 11 Mar 2018 06:51:35 -0700 (PDT)
Michael MENG  wrote:

> On Tuesday, February 27, 2018 at 10:27:21 PM UTC+8, Yuraeitha wrote:
> > On Tuesday, February 27, 2018 at 3:18:56 PM UTC+1, Michael MENG
> > wrote:  
> > > Yes. I did , but still no luck. Also googled. I did press e when
> > > see grub menu but show mothing.  
> > 
> > btw, you need to use "Tab" key on the installer, not the "E" key.
> > Once Qubes is installed however, it's the regular old "E" Grub
> > again. But during the installer, you need to use "Tab", screen will
> > not change but 3 or so lines appears at the bottom of the screen,
> > where you can add the driver blacklist at the very end (remember to
> > add a proper space before adding it).  
> 
> Thanks for reply, still no luck, is it adding
> "modprobe.blacklist=nouveau" into boot menu? attached photo.
> 

You need a space character at the end of "nouveau"!!

Your screenshot shows "modprobe.blacklist=nouveau_rhgb" - which is
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/20180313130505.1d4f066a.mike%40keehan.net.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: control boot line in installer?

[Mike Keehan]

On Thu, 8 Mar 2018 10:46:31 -0500
Nathan Myers  wrote:

> On 3/8/18 1:19 AM, Nathan Myers wrote:
> > I am trying to install on an ASUS ZenBook UV501 (Skylake, HD530,
> > NV960M, NVME SSD). The installer kernel OOPSes because it loads the
> > nouveau driver module, and gets confused by the bumblebee/optimus
> > hardware arrangement.
> > 
> > I have installed Debian 9.3 on this machine, and it works if I
> > blacklist the nouveau module during boot. (I.e. the i915 module
> > needs to load first.)  But I don't see any way to control the boot
> > line during installation.  ("E" only shows me a chainloader command
> > line.)
> > 
> > Also, when choosing where to install, the installer seems to offer
> > only the whole disk, but I have partitions already in place,
> > currently formatted for swap and ext4, that I would like for the
> > installer to overwrite.  How do I tell the Qubes installer to use
> > those?
> > 
> > Might the 4.0 beta installer deal better with these details?  
> 
> With the 4.0rc5 installer, it never gets to the option to edit the 
> chainloader command line.  It just says X failed, press ENTER, and
> then nothing when i press ENTER.  The log shows it looping trying to
> start things. But the kernel is not obviously OOPSing.
> 
> What to try next?
> 

Try using the instructions at this url -

https://www.qubes-os.org/doc/uefi-troubleshooting/

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

Re: [qubes-users] Qubes 4.0 on Dell XPS 13 9360 no longer boots anything!

[Mike Keehan]

> 
> Hey Mike, 
> 
> If you could find that email that would be fantastic. I have a
> similar problem on my Dell XPS 13 9343 as described later in this
> thread:
> https://groups.google.com/forum/#!topic/qubes-users/G6lMHyD16xc
> 
> Basically, I can only get Qubes 4.0 installed using Legacy boot,
> which is fine with me, but I can't get it to boot. The machine
> reboots itself every time it tries to boot Qubes, no matter if I
> install on an internal or external SSD. I would really love to get it
> working. 
> 
> Tom
> 

Hi Tom,

It sounds like you might have a different problem, but anyway, this is
what I had to do to get my UEFI boot working again.

"I had to fix the EFI - for some reason the installer messes up the
EFI partition type on the disk, and the bios doesn't recognise any boot
partition.  So I booted from a Linux cdrom and used 'fdisk' to change
the EFI partition type to EFI (which fdisk thought it was anyway!)."

I think the installer messed up the disk identifier string, which has
to be something specific for EFI.  'fdisk' fixed it.

If you haven't used fdisk before, be very carefull!  It can easily
ruin your disk partitions irrecoverably.

Best of luck,

   Mike.


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

Re: [qubes-users] Qubes 4.0 on Dell XPS 13 9360 no longer boots anything!

[Mike Keehan]

On Wed, 4 Apr 2018 10:46:04 -0700 (PDT)
Scott B  wrote:

> I decided over the long weekend to install Qubes 4.0 on my laptop
> after realizing that I could set up a dual-boot. I know this isn't
> very security conscious, but I was more concerned whether the
> hardware would be supported. It turns out I can't use my external
> monitor and usb keyboard, but that's not the real problem.
> 
> I noticed after rebooting that I only had the Qubes boot menu option,
> Windows 10 was not available. In an effort to set things back to the
> way they were I removed the Qubes partitions using Ubuntu live from
> usb. (I don't remember at this point, but I think I may have changed
> my settings from UEFI to Legacy before installing and then changed it
> back after removing Qubes.) 
> 
> Now Windows won't boot and the laptop doesn't allow me to add it to
> the UEFI boot menu via the BIOS screen. During POST I get "No
> bootable devices found" even though the SSD shows up in the
> information screen. I have tried installing a dual-boot with Ubuntu
> but continue to get the startup error that there is no bootable
> device. Ubuntu installs, but then won't boot up.
> 
> It seems to me, and I'm just getting up to speed on UEFI, that there
> is something similar to the master boot record missing. I've tried
> the solutions online that require booting from the Windows 10
> installation USB and then attempting to repair my copy of Windows but
> none of them have worked. I'm out of ideas now and just about ready
> to format the drive.
> 
> Has anyone else experienced this and if so, how did you recover?
> 
> Let me know if you need more detailed information and I'll provide it.
> 

Hi Scott,

I had the same problem at one stage on my Dell XPS 15.  The bios did not
list any EFI boot options, not Windows, not Qubes, and gave the "No
bootable device" message.

I had to use 'fdisk' on a recovery CD to rewrite the partition type back
to the boot partition.  I described it earlier on this list to someone 
else.  I'll try to find the email if you still need to fix your box.

Mike.

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

Re: [qubes-users] USB Device Question

[Mike Keehan]

On Sun, 15 Apr 2018 15:34:20 -0400
Stuart Perkins  wrote:

> I have the following setup:
> 
> Qubes 3.2, xfce4 interface
> sys-usb
> 
> I want to be able to connect my Android phone to a vm and rsync its
> contents.  I can connect the phone and "qvm-usb -a" it to the VM, and
> it appears available under the File Manager application as
> "mtp://[usb:002,004]/" but I cannot locate a mount point to use for
> rsync.  It does not appear under /run/user/[uid]/gvfs.  Any idea
> where it mounts so I can use rsync to reference it?
> 
> Thanks in advance...
> 
> Stuart
> 

"mtp://" is the clue :)  mtp is a protocol for communication between a
phone and a computer.  I don't think rsync supports mtp.

(My old phone used to 'mount' OK when I connected it, but my new phone
doesn't - it shows up as an mtp: device.)


Mike.

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

Re: [qubes-users] suspend to ram, r8169, networking in sys-net not working after resume

[Mike Keehan]

On Sat, 21 Apr 2018 14:20:02 +0200 (CEST)
 wrote:

> >> My issue:
> >>
> >> On qubes version r4.0 after resuming from suspend networking isn't
> >> working. On qubes r3.2 this wasn't an issue.
> >>
> >>
> >> After resuming from suspend to ram, networking on sys-net isn't
> >> working: $ ip addr
> >> 6: ens5:  mtu 1500 qdisc
> >> fq_codel state DOWN group default qlen 1000 link/ether
> >> 4c:cc:6a:30:f5:90 brd ff:ff:ff:ff:ff:ff
> >>
...snip...
 
> >> ---
> >> After resuming I've tried:
> >> [user@sys-net ~]$ sudo rmmod r8169
> >> [user@sys-net ~]$ sudo rmmod mii
> >> [user@sys-net ~]$ sudo modprobe mii
> >> [user@sys-net ~]$ sudo modprobe r8169  
> >
> > did you try to `rmmod` *before* suspending ?  
> 

Try adding the module names to the sys-net file 
/etc/qubes-suspend-module-blacklist, and Qubes should handle them
for you.

Mike.


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

Re: [qubes-users] Updates broke an HVM qube

[Mike Keehan]

On Fri, 26 Oct 2018 16:58:09 -0400
Kyaphas Hill  wrote:

> Sheesh, I should've thought of that. No luck though. Same result in
> another terminal window.
> 
> I tried updating by typing "sudo yum update -y && shutdown -h now" in
> the blind. And while that command worked (it ran for a while, then
> shut down), the problem still persists.
> 

Hmm.  Did you try resizing the terminal window by dragging a corner?
I've a vague memory of seeing something like this in the past, but 
not on Qubes.

Mike.


> On Fri, Oct 26, 2018 at 6:39 AM Mike Keehan  wrote:
> 
> > On Thu, 25 Oct 2018 10:47:33 -0700 (PDT)
> > drogo  wrote:
> >  
> > > I recently updated a fedora 28-based qube that I have running in
> > > HVM mode. I also updated dom0 at about the same time. So I'm not
> > > sure which update caused the issue.
> > >
> > > Now when I attempt to start the qube, the terminal for the
> > > template (and its dependent appVM) will only display what looks
> > > like static. Or if you're old enough, what the TV looked like
> > > when you messed with the horizontal hold too far. :)
> > >
> > > The VM seems to be running, as if I type "shutdown -h now" in the
> > > unintelligible terminal, the VM shuts down.
> > >
> > > Any  tips? I'm hoping to avoid having to re-build this qube from
> > > scratch.
> > >
> > > Thanks.
> > >  
> >
> > Try a different terminal emulator - xterm, xfce4-terminal.
> >
> > --
> > You received this message because you are subscribed to a topic in
> > the Google Groups "qubes-users" group.
> > To unsubscribe from this topic, visit
> > https://groups.google.com/d/topic/qubes-users/nP_6mgtX0eY/unsubscribe.
> > To unsubscribe from this group and all its topics, 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/20181026113932.3ba50a6e.mike%40keehan.net
> > .
> > For more options, visit https://groups.google.com/d/optout.
> >  
> 

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

Re: [qubes-users] Updates broke an HVM qube

[Mike Keehan]

On Thu, 25 Oct 2018 10:47:33 -0700 (PDT)
drogo  wrote:

> I recently updated a fedora 28-based qube that I have running in HVM
> mode. I also updated dom0 at about the same time. So I'm not sure
> which update caused the issue.
> 
> Now when I attempt to start the qube, the terminal for the template
> (and its dependent appVM) will only display what looks like static.
> Or if you're old enough, what the TV looked like when you messed with
> the horizontal hold too far. :)
> 
> The VM seems to be running, as if I type "shutdown -h now" in the
> unintelligible terminal, the VM shuts down.
> 
> Any  tips? I'm hoping to avoid having to re-build this qube from
> scratch.
> 
> Thanks. 
> 

Try a different terminal emulator - xterm, xfce4-terminal.

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

Re: [qubes-users] sys-net & sys-firewall fail to start, new install

[Mike Keehan]

On Thu, 17 Jan 2019 16:42:28 -0800 (PST)
scott.lewis.engin...@gmail.com wrote:

> Hello, I apologize in advance if this has already been addressed but
> searching for "sys-net" & "libxl" give many confusing results, I
> don't see any that match both not working, and I'm completely new to
> Qubes. My problem is that after 2 different installs of the same
> version, 4.01, I keep getting the same problems: When I get into
> Qubes I cannot update dom0, and sys-net & sys-firewall both fail to
> start even though my NIC is correctly listed in devices for -net.
> 
> Basic info:
> Dell Optiplex 780, bios= A15 as recommended in HCL.
> Qubes 4.01, sigs checked good.
> Install 1 done by USB, created in windows, had same issues as
> described below. Re-installed by DVD thinking I'd muffed something
> (think I read on reddit that USB installs made from windows had
> issues) and the behavior is exactly the same.
> 
> Behavior observed:
> (anything in [xxx] is me telling you the variation, as I get this for
> 2 VM's, 2 error codes, etc.)
> * Dom0 starts and runs, but -net & -firewall will not.
> * When I attempt to manually start either, I get this error message:
> "ERROR: Start failed: internal error: libxenlight failed to create
> new domain 'sys-net' [or sys-firewall],
> see /var/log/libvirt/libxl/libxl-driver.log for details".
> 
> When I less the log, I get these errors dozens of time with
> timestamps ranging from date of install to today: 1: "[date:time]:
> libxl: libxl_create.c:610:libxl_domain_make:domain creation fail:
> Operation not supported" 2: "[date:time]: libxl:
> libxl_create.c:982:initiate_domain_create:cannot make domain: -3"
> Those errors and nothing else.
> 
> I've tried to update dom0 by command as found in docs, as well as
> through GUI without success. I found a page elsewhere that described
> temporarily putting NIC in firewall or another VM to see if it
> worked, but I must be doing it wrong as I always get loopback errors
> when trying to save. It always tells me failed, regardless. No wonder
> if network isn't working.
> 
> Under sys-net, I see the correct name and model of my NIC, but I
> can't seem to figure out how to see if the NIC is operational since
> sys-net isn't working (new to qubes sorry!), however I verified my
> router is not showing an IP assigned, though link LED is on.
> 
> If anyone can help me try to figure this out, I'd really appreciate
> it. I'm still a bit green on linux but I learn fast, I recently gave
> up on Windows (I hate 10 so much I could scream) so I'm trying to
> dive in with qubes (deep end of the pool I think) as it best suits my
> needs with the VM implementation.
> 
> I'd post the log itself, but I can't seem to figure out how to make
> USB copy work yet since I've been beating my head on the networking
> issue.
> 
> Thanks, and sorry in advance if this duplicated another thread.
> 

Similar issues in the past were raised in this bug report -

https://github.com/QubesOS/qubes-issues/issues/3125

It might give you some pointers.

(I found it by searching for "Qubes libxl_domain_make:domain creation
fail: Operation not supported" in google.)

Mike.

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

Re: [qubes-users] sys-net & sys-firewall fail to start, new install

[Mike Keehan]

Ah, afraid I've run out of ideas now.

I was hoping it was just the iommu not being enabled, but not starting 
any vm at all is not something I've seen before, as long as there is
enough memory.  16Gb is fine.

Sorry, out of inspiration now,

Mike.

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

Re: [qubes-users] sys-net & sys-firewall fail to start, new install

[Mike Keehan]

On Fri, 18 Jan 2019 07:17:00 -0800 (PST)
scott.lewis.engin...@gmail.com wrote:

> On Friday, January 18, 2019 at 9:16:59 AM UTC-5, unman wrote:
> > On Fri, Jan 18, 2019 at 07:40:30AM -0500, Scott wrote:  
> > > Thanks but unfortunately I don't know that issue helps, as those
> > > who were able to resolve it did so by updating which I cannot do
> > > since sys-net fails to start.
> > > 
> > > This issue, https://github.com/QubesOS/qubes-issues/issues/3349 ,
> > > seems to cover that problem but nothing's mentioned about net &
> > > firewall failing to start.
> > > 
> >  > 
> > > On Fri, Jan 18, 2019, 07:22 Mike Keehan  > >   
> > > > On Thu, 17 Jan 2019 16:42:28 -0800 (PST)
> > > > scott wrote:
> > > >  
> > > > > Hello, I apologize in advance if this has already been
> > > > > addressed but searching for "sys-net" & "libxl" give many
> > > > > confusing results, I don't see any that match both not
> > > > > working, and I'm completely new to Qubes. My problem is that
> > > > > after 2 different installs of the same version, 4.01, I keep
> > > > > getting the same problems: When I get into Qubes I cannot
> > > > > update dom0, and sys-net & sys-firewall both fail to start
> > > > > even though my NIC is correctly listed in devices for -net.
> > > > >
> > > > > Basic info:
> > > > > Dell Optiplex 780, bios= A15 as recommended in HCL.
> > > > > Qubes 4.01, sigs checked good.
> > > > > Install 1 done by USB, created in windows, had same issues as
> > > > > described below. Re-installed by DVD thinking I'd muffed
> > > > > something (think I read on reddit that USB installs made from
> > > > > windows had issues) and the behavior is exactly the same.
> > > > >
> > > > > Behavior observed:
> > > > > (anything in [xxx] is me telling you the variation, as I get
> > > > > this for 2 VM's, 2 error codes, etc.)
> > > > > * Dom0 starts and runs, but -net & -firewall will not.
> > > > > * When I attempt to manually start either, I get this error
> > > > > message: "ERROR: Start failed: internal error: libxenlight
> > > > > failed to create new domain 'sys-net' [or sys-firewall],
> > > > > see /var/log/libvirt/libxl/libxl-driver.log for details".
> > > > >
> > > > > When I less the log, I get these errors dozens of time with
> > > > > timestamps ranging from date of install to today: 1:
> > > > > "[date:time]: libxl:
> > > > > libxl_create.c:610:libxl_domain_make:domain creation fail:
> > > > > Operation not supported" 2: "[date:time]: libxl:
> > > > > libxl_create.c:982:initiate_domain_create:cannot make domain:
> > > > > -3" Those errors and nothing else.
> > > > >
> > > > > I've tried to update dom0 by command as found in docs, as
> > > > > well as through GUI without success. I found a page elsewhere
> > > > > that described temporarily putting NIC in firewall or another
> > > > > VM to see if it worked, but I must be doing it wrong as I
> > > > > always get loopback errors when trying to save. It always
> > > > > tells me failed, regardless. No wonder if network isn't
> > > > > working.
> > > > >
> > > > > Under sys-net, I see the correct name and model of my NIC,
> > > > > but I can't seem to figure out how to see if the NIC is
> > > > > operational since sys-net isn't working (new to qubes
> > > > > sorry!), however I verified my router is not showing an IP
> > > > > assigned, though link LED is on.
> > > > >
> > > > > If anyone can help me try to figure this out, I'd really
> > > > > appreciate it. I'm still a bit green on linux but I learn
> > > > > fast, I recently gave up on Windows (I hate 10 so much I
> > > > > could scream) so I'm trying to dive in with qubes (deep end
> > > > > of the pool I think) as it best suits my needs with the VM
> > > > > implementation.
> > > > >
> > > > > I'd post the log itself, but I can't seem to figure out how
> > > > > to make USB copy work yet since I've been beating my head on
> > > > > the networking issue.

Re: [qubes-users] sys-net & sys-firewall fail to start, new install

[Mike Keehan]

On Fri, 18 Jan 2019 08:14:43 -0800 (PST)
Bryce  wrote:

> On Friday, January 18, 2019 at 11:11:00 AM UTC-5, Mike Keehan wrote:
> > Ah, afraid I've run out of ideas now.
> > 
> > I was hoping it was just the iommu not being enabled, but not
> > starting any vm at all is not something I've seen before, as long
> > as there is enough memory.  16Gb is fine.
> > 
> > Sorry, out of inspiration now,
> > 
> > Mike.  
> 
> Thanks anyways Mike. I did manage to attach the pics of memory and
> qubes manager at least, in case they're useful for anyone.
> 

That's odd.  You say you are installing 4.01, yet the qubes manager
shows that fedora is only release 26.  I thought that Qubes 4.01 had
Fedora 29 in it.

Mike.

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

Re: [qubes-users] sys-net & sys-firewall fail to start, new install

[Mike Keehan]

On Fri, 18 Jan 2019 11:55:14 -0800 (PST)
Bryce  wrote:

> On Friday, January 18, 2019 at 11:42:32 AM UTC-5, Bryce wrote:
> > > That's odd.  You say you are installing 4.01, yet the qubes
> > > manager shows that fedora is only release 26.  I thought that
> > > Qubes 4.01 had Fedora 29 in it.
> > > 
> > > Mike.  
> > 
> > Well Mike that could be it; you made me check when you said that,
> > the image I used was "Qubes-R4.0-x86_64.iso" from 11/27/18. I
> > checked the about in qubes itself is 4.0 (R4.0). Looks like I
> > screwed up on which version I created the image from, I wrote down
> > 4.01 but that's not what I used- too much spiked eggnog maybe.
> > Since it doesn't seem to be possible for me to update with the VM's
> > not starting for USB or Net, I will get the latest image and and
> > reinstall to see if there's any issue. Thanks for pointing out my
> > goof, I'll try that today and see if the results are any
> > different!  
> 
> I Reinstalled w/ 4.01 (downloaded today) and sadly I seem to have the
> same issue. Here's what I did:
> * During install I realized what I had forgot before, that previous
> occasions I had to turn off "Intel VT for Direct I/O" in bios in
> order to get the installer to even work. If I don't turn that off,
> the screen goes black and nothing happens no matter which option I
> pick from the setup list- normal install, test & install, and basic
> graphics install all do the same. So I turn it off, and the install
> works fine until the language selections screen then I get an error
> that (I think) IOMMU or it's remapping support are missing, only
> advanced or devs etc should proceed. Thought I grabbed a pic but it
> didn't turn out. I go through the install until it needs to reboot,
> then immediately go back into bios and enable VT-d, and let it boot
> as normal. On the previous installations I don't think I did it
> before completing install, only after. It boots up fine, completes
> install with one error- during the templates setup I get the attached
> error about sys-firewall not starting up again due to libxenlight. I
> login, get to desktop and open qubes manager- all without more
> errors. Only dom0 is running again. Trying to start sys-net or
> sys-firewall gives me the same errors as before about libxenlight
> failing to start the qubes, even though VT-d is turned on. I tried
> unman's earlier suggestion of removing and re-adding the NIC, no luck.
> 
> I hope someone has another idea, is there a way to force vt-d on in
> qubes? Some screenshots attached.
> 

Ah, what a shame.  It does seem as if your iommu is a problem.

Without any other ideas, the only thing I can suggest is that you try
the latest Qubes 3.2 just to allow you to try out Qubes.  It doesn't
require the vt-d stuff, so might work on your box.

The other thing you can do is try googling for iommu and your cpu
together to see if others have had problems (not necessarily in
Qubes, just in general use).
 
  Mike.

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

Re: [qubes-users] Account

[Mike Keehan]

On Mon, 21 Jan 2019 20:44:30 +0100 (CET)
 wrote:

> I signed up for an account with Qubes and got the confirmation, and
> here I am.  But when I go to post a reply, I am not recognized.  Does
> anyone know why that is?
> 
> Thank  you.
> 

Your reply has to go via the gmail server.  I had the same problem
when my replies were being sent via my main email account's server.
I had to select the gmail server for replies to Qubes emails.

Mike

(this may not be your problem, but it was for me.)

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

[qubes-users] Backup stops when the backup file reaches 3Gb

[Mike Keehan]

Hi,

I'm using Qubes Backup to save some of my qubes into another VM.
The backup VM has 18 Gb of storage available, but whenever the
backup file reaches 3Gb, the backup process just hangs.

No CPU usage, no error messages, just stops.  The backup window
shows 40% complete, but never moves any further (different % for
different combinations of qubes in the backup list).

After waiting a considerable time (well, 5-10 minutes), hitting
Cancel in the backup window does cancel it.  The rest of the
system is continuing to work without problem.  Happens every
time I try to use Qubes backup.

The Qubes Disk Space widget shows less than 50% disk used overall,
the backupVM shows only 18% disk used when the 3Gb file has been
saved.

I'm stumped.

Mike.

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

Re: [qubes-users] sys-net & sys-firewall fail to start, new install

[Mike Keehan]

On Tue, 22 Jan 2019 12:26:00 -0800 (PST)
Bryce  wrote:

> On Saturday, January 19, 2019 at 6:37:47 AM UTC-5, Mike Keehan wrote:
> > 
> > Ah, what a shame.  It does seem as if your iommu is a problem.
> > 
> > Without any other ideas, the only thing I can suggest is that you
> > try the latest Qubes 3.2 just to allow you to try out Qubes.  It
> > doesn't require the vt-d stuff, so might work on your box.
> > 
> > The other thing you can do is try googling for iommu and your cpu
> > together to see if others have had problems (not necessarily in
> > Qubes, just in general use).
> >  
> >   Mike.  
> 
> Well, just to put this out there, it seems as if my CPU doesn't
> support SLAT and maybe that's why (I thought from intel's page it
> did). Installing the latest 3 stable and I don't get any errors about
> IOMMU like I did with 4, but just like with 4 I do have to disable
> vt-d in bios in order to boot to the installer.
> 
> Unfortunately as soon as I turn vt-d back on, the system goes thru
> post, I see qubes start to boot and then after a minute (about when I
> think I'd see the disk password prompt) I get a message from my
> monitor that the input timing is wrong, which I've never seen on
> several other operating systems! Wierldy, I was able to reproduce
> this behavior by turning off vt-d, booting up fully and then was able
> to update without issues unlike in 4. Rebooted twice without issues,
> then turned vt-d back on and got the exact same behavior.
> 
> So I guess I just try out using 3.2 without vt-d.
> 
> I'll take a look around the users' group, but I don't see any real
> details on the qubes site for what the key differences are between 3
> & 4 are, can anyone point me to something that will tell me how worth
> it (secure) that it is to use 3.2 instead of replacing hardware to
> run 4?
> 

Hi Bryce,

Glad you got something working for you :)

This is a good description of the changes in Qubes 4.0 :-
   https://www.qubes-os.org/doc/releases/4.0/release-notes/

Mike.

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

Re: [qubes-users] password style

[Mike Keehan]

On Thu, 13 Dec 2018 03:43:33 -0800 (PST)
pulpw...@gmail.com wrote:

> no user login is possible. are there any unallowed chars in it? maybe
> too long?
> 
> the password was:
> +jSyq@12_0rRwY7G&/mBAQ=|?{\#53Ouw8910q@3201i+./\nFVsc
> 

Backslash character might be a problem, especially \n 
Maybe the pipe symbol | and ampersand & too.

Mike.

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

Re: [qubes-users] alternative to bloated templates for faster work and minimal boot time/resources used

[Mike Keehan]

On Thu, 13 Dec 2018 20:31:29 +0100
799  wrote:

> Hello Chris,
> 
> On Wed, 12 Dec 2018 at 22:52, Chris Laprise  wrote:
> 
> > But here's how you could start the loop:
> > qvm-ls --running -O name | (read line; while read line; do qvm-run
> > -p $line 'your vm command goes here'; done)
> > [...]
> >  
> 
> thanks for the hint.
> I tried to run the following command which gives me a list of all
> running VMs (just to get the loop right):
> qvm-ls --running -O name --raw-data | (read line; while read line; do
> echo $line; done)
> In my case:
> my-untrusted
> my-vault
> sys-firewall
> sys-net
> sys-usb
> 
> The command to get the information about the swap usage from a VM
> (here named APPVMNAME can be shown by running the following command
> in dom0:
> 
> echo APPVMNAME = `qvm-run --pass-io APPVMNAME "free" | tail -n +3 |
> gawk '{ print $3 }'`
> 
> But when I bring both peaces together I only get one result back, not
> the result for all AppVMs
> 
> qvm-ls --running -O name --raw-data | (read line; while read line; do
> echo $line `qvm-run --pass-io $line "free" | tail -n +3 | gawk
> '{ print $3 }'` ; done)
> 
> Output in my case:
> my-untrusted 256
> 
> So the output is only showing the output for one VM.
> I don't understand why this is happening.
> 
> - O
> 

Hi,

I can't figure out why the code above only returns the first VM's
result, but the following code works for me :-

for i in `qvm-ls --running -O name --raw-data|grep -v dom0`;
do
   echo $i = `qvm-run --pass-io $i "free"| tail -n +3 | gawk '{print
$3 }'`;
done

Mike.


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

Re: [qubes-users] [R4.0] CPU Freq Scaling, or "Why am I stuck at 2.1 Ghz?"

[Mike Keehan]

On Thu, 6 Dec 2018 15:54:17 -0800 (PST)
Eric Duncan  wrote:

> Finally received my new Thinkpad X1 Yoga 3rd gen.
> 
> i7-8650U up to 4.2 Ghz Turbo
> 
> How can I debug/check that my CPU governor/frequency is scaling
> correcting under Qubes R4?
> 
> So far, the only thing I've found is xentop/xl top that lists the CPU
> - as a never-changing 2.1 Ghz.  Maybe this isn't the best way to
> measure CPU freq under dom0?  All other tools seemed to want to use
> xfce4 tools, which seemed to only be specific to that fedora VM - and
> not the xen host.
> 
> /TL;DR
> 
> 
> I let Windows 10 register itself before wiping the disk and
> installing Qubes R4.  Under Windows, Google Chrome benchmarked around
> 5300 pts with the online tool I was using.  As a test, I also
> installed Arch Linux briefly to test Chrome performance, and it came
> in around 4500 pts.  I chalk that up to not optimizing anything on
> the system - just a raw install and no tweaks.
> 
> Now, under Qubes R4.0, I'm still noticing a lot of
> sluggishness/slowdowns just like my older Thinkpad Helix has always
> had under Qubes R3.2 (and one of the reasons why I waited for this
> quad core CPU to upgrade my Qubes install).  I could never benchmark
> Chrome under that Helix dual-core low-powered device.
> 
> I loaded up Chrome on a new debian-9 VM and... Almost the same
> extremely sluggish performance.  Google Chrome can't even get
> partially through the benchmarks without timing out, much less finish
> them.  
> 
> I've tried assigning 4 and even 8 vcpus to try to max things out.
> 
> I am wondering where to start to debug this.  
> 
> Is it a dom0 cpu scaling thing?  
> 
> Does Qubes impose some artificial throttling?
> 
> Is it a lag in iGPU rendering through the DisplayVM?  (this DisplayVM
> is a new concept to me, still trying to figure it out)
> 
> I've spent about 3 days on this device with various other issues to
> get to this point (no S3 sleep yet, pixel-perfect scaling of the HDR
> 1440p 14" display, etc).  I few duckduckgo searches hasn't turned
> anything up yet; so, i'll continue when I have some time.
> 
> Thanks!
> -E
> 

Hi Eric,

If your Chrome benchmarks involve 3D acceleration using the GPU, then
they won't work under Qubes.

Each Qube VM renders it's windows in software, which is then copied to 
dom0 for display on the Xwindow system.  Only dom0 has access to the
GPU, and you are not supposed to run applications on dom0 for security
reasons.   (And of course, dom0 has no internet connection anyway.)

Mike.

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

Re: [qubes-users] Domain qube1 has failed to start: Not enough memory to start domain 'qube1'

[Mike Keehan]

On Thu, 3 Jan 2019 05:29:15 -0800 (PST)
mike  wrote:

> Hi All,
> 
> Sometimes I cannot start any qube with a popup message as in Subject,
> or when I run qvm-start I get:
> 
> $ qvm-start qube1
> Not enough memory to start domain 'qube1'
> 
> I have 16GB RAM and I am running just a few qubes, so there's
> definitely no real memory issue.
> 
> How can I investigate memory issues in Qubes?
> How can I see how much memory all qubes are using, how much is
> available etc?
> 
> 
> Thanks,
> Mike
> 

You can use xentop to see what's happened to your memory.

Mine shows approx 4Gb in dom0, 2Gb in a couple of web VMs, 1.5Gb in my
mail VM and in sys-firewall, plus much smaller amounts in other sys VMs.
I have approx. 2Gb free in my 16Gb laptop at present.

Mike.

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

Re: [qubes-users] Backup stops when the backup file reaches 3Gb

[Mike Keehan]

On Thu, 24 Jan 2019 11:27:00 -0500
Chris Laprise  wrote:

> On 01/24/2019 06:29 AM, unman wrote:
> > On Thu, Jan 24, 2019 at 01:00:15AM -0500, Chris Laprise wrote:  
> >> On 01/23/2019 08:15 PM, js...@bitmessage.ch wrote:  
> >>> Mike Keehan:  
> >>>> Hi,
> >>>>
> >>>> I'm using Qubes Backup to save some of my qubes into another VM.
> >>>> The backup VM has 18 Gb of storage available, but whenever the
> >>>> backup file reaches 3Gb, the backup process just hangs.
> >>>>
> >>>> No CPU usage, no error messages, just stops.  The backup window
> >>>> shows 40% complete, but never moves any further (different % for
> >>>> different combinations of qubes in the backup list).
> >>>>
> >>>> After waiting a considerable time (well, 5-10 minutes), hitting
> >>>> Cancel in the backup window does cancel it.  The rest of the
> >>>> system is continuing to work without problem.  Happens every
> >>>> time I try to use Qubes backup.
> >>>>
> >>>> The Qubes Disk Space widget shows less than 50% disk used
> >>>> overall, the backupVM shows only 18% disk used when the 3Gb file
> >>>> has been saved.
> >>>>
> >>>> I'm stumped.
> >>>>
> >>>> Mike.  
> >>>
> >>> Hi,
> >>>
> >>> You may have to wait longer than 5-10 minutes. I experience
> >>> something similar when doing a full backup, except it's worse
> >>> because i'm backing up like 2.5TB. It appears to hang for several
> >>> hours at a time (and this happens more than once), but it does
> >>> eventually make visible progress again. The whole process takes
> >>> over 24 hours. This is why i do full backups very infrequently.
> >>>
> >>> For you it shouldn't take nearly as long because it's a lot less
> >>> data, but the progress appearing to hang for a while seems to be
> >>> normal.
> >>>
> >>> I'm using 3.2 tho, and i know they made changes to the backup
> >>> mechanism under the hood in 4.0, so i'm not sure if this issue
> >>> still applies in 4.0.  
> >>
> >> Marek,
> >>
> >> Isn't this the null bytes bug in GNU tar?
> >>
> >> https://groups.google.com/d/msgid/qubes-users/f4d997d5-7191-06d0-e7bb-ef42745a7db5%40posteo.net
> >>
> >> It would be a good idea to update this in dom0. My own backup tool
> >> uses GNU tar as well.
> >>
> >> -- 
> >>
> >> Chris Laprise, tas...@posteo.net
> >> https://github.com/tasket
> >> https://twitter.com/ttaskett
> >> PGP: BEE2 20C5 356E 764A 73EB  4AB3 1DC4 D106 F07F 1886  
> > 
> > It seems a little early to judge.
> > 
> > Mike - it looks from your comment as if you have been trying with
> > subsets of the qubes? Can you confirm if these are running or
> > stopped.
> > 
> > Like jsnow, I'm regularly able to backup far more than 3G without
> > issue, so it looks as if there's something particular about this
> > scenario. It would be helpful if you could confirm the issue when
> > all qubes you are backing up are stopped.
> > Then try bisecting the qubes backup group - keep bisecting if you
> > hit the problem again until you either find the problematic qubes
> > or have backed them all up.
> >   
> 
> Oops, I pasted the wrong link. Here is the correct one:
> 
> https://utcc.utoronto.ca/~cks/space/blog/sysadmin/TarFindingTruncateBug
> 
> The symptoms sound remarkably the same... potentially hours-long
> delays with no adverse effect on data. Trigger condition is not about
> size, but due to corner cases that involve backing up nulls.
> 

I left a backup running before I left home this morning - it was stuck
at 1.8Gb then (confirming that size is not the issue), and it was still
at 1.8Gb when I got home this evening.  That was about 8 hours or so.

I have a recollection from my dim and distant past, that I had a similar
stuck tar issue when it could not handle fifos.  Not Linux in those
days.  There is no mention of fifos (or sockets etc.) in the tar
manpage, so I don't know if gnu tar is supposed to handle them or not.
I had to use cpio to backup systems which contained those things.

Anyway, I'll investigate further tomorrow.  You have given me a number
of things to look into.  Thanks,

Mike.

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

Re: [qubes-users] Backup stops when the backup file reaches 3Gb

[Mike Keehan]

On Fri, 25 Jan 2019 13:52:55 +
Mike Keehan  wrote:

> On Thu, 24 Jan 2019 11:29:50 +
> unman  wrote:
> 
> > On Thu, Jan 24, 2019 at 01:00:15AM -0500, Chris Laprise wrote:  
> > > On 01/23/2019 08:15 PM, js...@bitmessage.ch wrote:
> > > > Mike Keehan:
> > > > > Hi,
> > > > > 
> > > > > I'm using Qubes Backup to save some of my qubes into another
> > > > > VM. The backup VM has 18 Gb of storage available, but
> > > > > whenever the backup file reaches 3Gb, the backup process just
> > > > > hangs.
> > > > > 
> > > > > No CPU usage, no error messages, just stops.  The backup
> > > > > window shows 40% complete, but never moves any further
> > > > > (different % for different combinations of qubes in the
> > > > > backup list).
> > > > > 
> > > > > After waiting a considerable time (well, 5-10 minutes),
> > > > > hitting Cancel in the backup window does cancel it.  The rest
> > > > > of the system is continuing to work without problem.  Happens
> > > > > every time I try to use Qubes backup.
> > > > > 
> > > > > The Qubes Disk Space widget shows less than 50% disk used
> > > > > overall, the backupVM shows only 18% disk used when the 3Gb
> > > > > file has been saved.
> > > > > 
> > > > > I'm stumped.
> > > > > 
> > > > > Mike.
> > > > 
> > > > Hi,
> > > > 
> > > > You may have to wait longer than 5-10 minutes. I experience
> > > > something similar when doing a full backup, except it's worse
> > > > because i'm backing up like 2.5TB. It appears to hang for
> > > > several hours at a time (and this happens more than once), but
> > > > it does eventually make visible progress again. The whole
> > > > process takes over 24 hours. This is why i do full backups very
> > > > infrequently.
> > > > 
> > > > For you it shouldn't take nearly as long because it's a lot less
> > > > data, but the progress appearing to hang for a while seems to be
> > > > normal.
> > > > 
> > > > I'm using 3.2 tho, and i know they made changes to the backup
> > > > mechanism under the hood in 4.0, so i'm not sure if this issue
> > > > still applies in 4.0.
> > > 
> > > Marek,
> > > 
> > > Isn't this the null bytes bug in GNU tar?
> > > 
> > > https://groups.google.com/d/msgid/qubes-users/f4d997d5-7191-06d0-e7bb-ef42745a7db5%40posteo.net
> > > 
> > > It would be a good idea to update this in dom0. My own backup tool
> > > uses GNU tar as well.
> > > 
> > > -- 
> > > 
> > > Chris Laprise, tas...@posteo.net
> > > https://github.com/tasket
> > > https://twitter.com/ttaskett
> > > PGP: BEE2 20C5 356E 764A 73EB  4AB3 1DC4 D106 F07F 1886
> > 
> > It seems a little early to judge.
> > 
> > Mike - it looks from your comment as if you have been trying with
> > subsets of the qubes? Can you confirm if these are running or
> > stopped.
> > 
> > Like jsnow, I'm regularly able to backup far more than 3G without
> > issue, so it looks as if there's something particular about this
> > scenario. It would be helpful if you could confirm the issue when
> > all qubes you are backing up are stopped.
> > Then try bisecting the qubes backup group - keep bisecting if you
> > hit the problem again until you either find the problematic qubes
> > or have backed them all up.
> >   
> 
> OK, progress:)
> 
> I can backup a list of stopped qubes, running out to a 10Gb file
> without any issues.  They all verify OK too.  However, backing up
> running qubes exhibits the problem.  
> 
> Starting up one of these qubes and trying to backup causes the
> progress indicator to stop at some point, BUT, the data is still
> being backed up to disk, and continues flowing for some time.  When
> the data flow stops, then I have to cancel the backup operation.
> However, verifying the backup works OK - file size reported is
> correct, and the verify process finishes successfully.  I haven't
> tried to actually restore one of these yet.
> 
> I tried recording the process status of both dom0 and the backup vm
> during the backups, but could not see any particular process dying
> when the progress updater stopped moving.  The tar processes stopped
> in dom0 but I guess

Re: [qubes-users] X events going to wrong VM?

[Mike Keehan]

On Thu, 28 Mar 2019 13:13:17 -0500
Daniel Allcock  wrote:

> Hello,
> 
> Something peculiar happens occasionally on my qubes 4.0 system.  I run
> claws-mail in one VM, and mousing over the message list shows tooltips
> as intended (not very useful; they just repeat the text that is under
> the mouse). As I mouse up or down, the old tooltip disappears and a
> new one appears, as you would expect.
> 
> But sometimes this happens when another VM's window (say firefox)
> is on top of the claws window, and all the mouse movement takes place
> inside the window on top.  Somehow claws seems
> to be receiving X mouse-motion events meant for the other VM.
> Obviously this looks like a violation of qube isolation.
> 
> The tooltip windows are properly colored.
> So as I move the mouse, yellow-bordered tooltip windows appear and
> disappear on top of a (say) red-bordered window that is on top of 
> a yellow-bordered claws window.  Visually this is very strange.
> 
> I wish I knew how to reproduce this.  It just seems to happen by
> itself every few days.  I have a vague memory of something similar
> happening *once* with some app other than claws.  But I forget the
> details.  Anyone else have this experience? Or thoughts about
> what to try to maybe reproduce it more reliably?
> 
> Thanks,
> Daniel
> 

Hi Daniel,

I have the same problem on my system.  Not only with Claws mailer, but
also with Firefox occasionally, and most often with an xfce panel that
runs in sys-net and shows me the weather and the network load.

The odd part is that the panel widgets display their popups even though
I never hover the mouse over them deliberately.  The popups display
when I use the scrollwheel to switch desktops.

As you say, it is not easily reproducible, so debugging it will be hard
I expect.

Mike.
 

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

Re: [qubes-users] Re: Blank Screen Trying To Install

[Mike Keehan]

On Sun, 24 Mar 2019 02:07:10 -0400
Yushatak  wrote:

> Machine has no legacy mode.
> 
> On Sat, Mar 23, 2019, 11:32 PM Gaijin  wrote:
> 
> > On 2019-03-24 02:41, Yushatak wrote:  
> > > On Thursday, March 21, 2019 at 8:57:09 PM UTC-4, Yushatak wrote:  
> > >> When I boot the Qubes installation media (I dd'd it to a USB
> > >> stick per  
> > the instructions on the site) it initializes Xen, then the kernel
> > starts booting (Linux penguins, etc.), and then it goes to a black
> > screen and there's no activity. F1 does nothing. My hardware is a
> > laptop with an i7 8700K and an Nvidia 1060, so it smelled like
> > nouveau driver problems to me. However, normally one works around
> > that by editing the kernel line in grub with nouveau.modeset=0 and
> > I have no grub! I decided to try editing the grub.conf in the
> > isolinux directory of the ISO by extracting the iso, editing, then
> > regenerating the ISO. Someone on IRC was nice enough to provide me
> > a log from the official build of the ISO so I used the proper
> > switches/etc.. I booted that in a VM to make sure it was OK as a
> > sanity check, then wrote that to the USB stick (which takes like 26
> > minutes, it's USB 2.. not fun) and it stopped booting after
> > attaching the USB stick as a SCSI device, not even quite getting to
> > the black screen. AFAIK my hardware requires a 4.18 kernel and from
> > what they said on IRC there's nothing newer than 4.14 in Qubes
> > anyway, but since it tries to boot I don't know. I throw myself
> > upon your mercy, Qubes community/developers.  
> > >
> > > Nobody has a single thought?  
> >
> > Might the solution be putting your BIOS into Legacy mode?
> > https://groups.google.com/forum/#!topic/qubes-users/Vy5wpWbOYxU
> >
> > In my case switching the HDD from AHCI mode to IDE mode seemed to
> > get past this blank screen and got me to the install screen.
> >  
> 

I had exactly this problem when I installed Qubes.  Searching this mail
list found the answer.  (You have to edit the installation image, or
mount the image, edit it and build a new image for installation.)

Mike.

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

Re: [qubes-users] Re: Blank Screen Trying To Install

[Mike Keehan]

On Sun, 24 Mar 2019 14:39:12 -0700 (PDT)
Yushatak  wrote:

> On Sunday, March 24, 2019 at 3:36:10 PM UTC-4, awokd wrote:
> > Mike Keehan wrote on 3/24/19 3:36 PM:  
> > > On Sun, 24 Mar 2019 02:07:10 -0400
> > > Yushatak  wrote:
> > >   
> > >> Machine has no legacy mode.
> > >>
> > >> On Sat, Mar 23, 2019, 11:32 PM Gaijin  wrote:
> > >>  
> > >>> On 2019-03-24 02:41, Yushatak wrote:  
> > >>>> On Thursday, March 21, 2019 at 8:57:09 PM UTC-4, Yushatak
> > >>>> wrote:  
> > >>>>> When I boot the Qubes installation media (I dd'd it to a USB
> > >>>>> stick per  
> > >>> the instructions on the site) it initializes Xen, then the
> > >>> kernel starts booting (Linux penguins, etc.), and then it goes
> > >>> to a black screen and there's no activity. F1 does nothing. My
> > >>> hardware is a laptop with an i7 8700K and an Nvidia 1060, so it
> > >>> smelled like nouveau driver problems to me. However, normally
> > >>> one works around that by editing the kernel line in grub with
> > >>> nouveau.modeset=0 and I have no grub! I decided to try editing
> > >>> the grub.conf in the isolinux directory of the ISO by
> > >>> extracting the iso, editing, then regenerating the ISO. Someone
> > >>> on IRC was nice enough to provide me a log from the official
> > >>> build of the ISO so I used the proper switches/etc.. I booted
> > >>> that in a VM to make sure it was OK as a sanity check, then
> > >>> wrote that to the USB stick (which takes like 26 minutes, it's
> > >>> USB 2.. not fun) and it stopped booting after attaching the USB
> > >>> stick as a SCSI device, not even quite getting to the black
> > >>> screen. AFAIK my hardware requires a 4.18 kernel and from what
> > >>> they said on IRC there's nothing newer than 4.14 in Qubes
> > >>> anyway, but since it tries to boot I don't know. I throw myself
> > >>> upon your mercy, Qubes community/developers.  
> > >>>>
> > >>>> Nobody has a single thought?  
> > >>>
> > >>> Might the solution be putting your BIOS into Legacy mode?
> > >>> https://groups.google.com/forum/#!topic/qubes-users/Vy5wpWbOYxU
> > >>>
> > >>> In my case switching the HDD from AHCI mode to IDE mode seemed
> > >>> to get past this blank screen and got me to the install screen.
> > >>> 
> > >>  
> > > 
> > > I had exactly this problem when I installed Qubes.  Searching
> > > this mail list found the answer.  (You have to edit the
> > > installation image, or mount the image, edit it and build a new
> > > image for installation.) 
> > I think the issue is he edited grub.cfg but has no legacy mode,
> > which means grub won't be used. Yushatak, try using that same
> > procedure to edit xen.cfg instead. It will be somewhere under
> > boot/efi/EFI/qubes.  
> 
> There is no such path, the closest I'm aware of is EFI/BOOT, which
> contains BOOTX64.cfg, which I already modified with nouveau.modeset=0
> on each option to no avail. To my understanding this is the conf that
> should apply since this is the EFI boot folder, so I don't think that
> setting is the culprit. That said, it's not Xen.cfg, but I did 'ls -R
> | grep Xen.cfg' which resulted in nothing, then did 'ls -R | grep
> xen' which returned packages as well as xen.gz, then 'ls -R | grep
> Xen' which returned nothing, so I'm not sure there is such a config.
> 

Have you looked at this page?
https://www.qubes-os.org/doc/uefi-troubleshooting/

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

Re: [qubes-users] X events going to wrong VM?

[Mike Keehan]

Argh, I meant mouse events, not keyboard.

On Fri, 29 Mar 2019 21:41:33 +
Mike Keehan  wrote:

> On Fri, 29 Mar 2019 11:42:39 -0500
> Daniel Allcock  wrote:
> 
> > Thanks Mike,
> > 
> > Your experience sounds even stranger than my own.  I'm not sure
> > whether it is more worrying---it's not so bad if the panel can read
> > VM's events, since dom0 already reads all of them.  But unexpected
> > events being sent to dom0 sounds like a way to make dom0 do things
> > possibly against user intent.
> > 
> > btw, you wouldn't be the Mike Keehan that I worked for in Summer
> > 1991 at Shell?
> > 
> > Daniel 
> >   
> 
> Hi Daniel,
> 
> I don't think it is events being sent to to dom0, but keyboard events 
> going to the VM.  And then the app in the VM just displays the popup
> as usual.  So I do not think there is any security issue, but just a
> bug somewhere in the event handling code.
> 
> Mike.
>  
> 

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

Re: [qubes-users] X events going to wrong VM?

[Mike Keehan]

On Fri, 29 Mar 2019 11:42:39 -0500
Daniel Allcock  wrote:

> Thanks Mike,
> 
> Your experience sounds even stranger than my own.  I'm not sure
> whether it is more worrying---it's not so bad if the panel can read
> VM's events, since dom0 already reads all of them.  But unexpected
> events being sent to dom0 sounds like a way to make dom0 do things
> possibly against user intent.
> 
> btw, you wouldn't be the Mike Keehan that I worked for in Summer 1991
> at Shell?
> 
> Daniel 
> 

Hi Daniel,

I don't think it is events being sent to to dom0, but keyboard events 
going to the VM.  And then the app in the VM just displays the popup
as usual.  So I do not think there is any security issue, but just a
bug somewhere in the event handling code.

Mike.
 

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

Re: [qubes-users] Hardware support

[Mike Keehan]

On Mon, 4 Mar 2019 12:41:23 +
"'Robin Murison' via qubes-users"  wrote:

> My hardware suppliers are sure my desktop supports IOMMU and yet when
> I try to install Qubes 4 the installation says it does not. My basic
> question is that error reported based on a white list or on the actual
> presence or absence of the feature.
> 
> I have checked with the hardware company that  IOMMU is available and
> does work and I have also checked with the company that built my
> machine that I have all the appropriate settings turned on in the
> BIOS.
> 
> Both say I am doing the right thing and that IOMMU should be working
> and I do not see my processor or mother board specifically on the
> supported hardware list.
> 
> my machine is custom built:
> 
> Processor (CPU)   AMD Athlon 5350 Quad Core APU (2.05GHz/AM1) &
> Radeon™ HD8400
> Motherboard   ASUS® AM1M-A: (M-ATX, DDR3, USB 3.0, 6Gb/s)
> 
> Thanks for any help
> 
> 
> Robin
> 

Hi Robin,

Qubes does a hardware test to determine if the IOMMU works.

According to Wikipedia's "List of IOMMU-supporting hardware" page,
https://en.wikipedia.org/wiki/List_of_IOMMU-supporting_hardware
there are some ASUS motherboards that do not work correctly with
IOMMU support.  You may be unlucky.

Mike.

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

Re: [qubes-users] Qubes - Critique (long)

[Mike Keehan]

On Fri, 15 Mar 2019 21:31:02 -0500
John Goold  wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
> 
> *A Critique of Qubes*
> 
Hi John,

What a nice read, thank you.  I have a very similar background, and age,
so I was very interested to read your story.

I've been using Qubes now for a few years, and love it.  Have had very 
little problem with it; have used and restored using the builtin backup
scheme; and have updated without problem using just the normal,
stable repositories.

The one thing I can suggest that I do differently to you, is that I
power down my laptop, and boot up afresh each day.  Have always done
this during my professional life (wasn't any choice early on as there
was no suspend option), and I can say that I have not experienced any
of the launch issues you described, nor any copy/paste issues between
VMs, not that I do much of that.

As for Flash, it is a pain.  Our BBC still uses it extensively, so I
have to manually download it occasionally and copy the library file
into the appVMs .mozilla directory when necessary.

Anyway, best of luck,

   Mike.

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

Re: [qubes-users] dispvm browser retains information

[Mike Keehan]

On Tue, 12 Mar 2019 08:35:04 +
Jon deps  wrote:

> Hello,  in Thunderbird when I do open-in-vm and check firefox it has 
> retained bookmarks from a previous session,
> 
> I believe this is Not how DVMs are supposed to work ?
> 
> 
> If so how would I troubleshoot and/or  remove  old  DVM data
> sesssions please
> 

Is the qvm-prefs property "template_for_dispvms" True for your
dvm template?

Mike.

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

Re: [qubes-users] not enough memory to start domain "xyz"

[Mike Keehan]

On Sat, 16 Feb 2019 18:56:39 +0100
evo  wrote:

> On 2/16/19 1:10 PM, Johannes Graumann wrote:
> > On Sat, 2019-02-16 at 11:21 +0100, evo wrote:  
> >>
> >> On 2/16/19 11:17 AM, Johannes Graumann wrote:  
> >>> On Sat, 2019-02-16 at 11:08 +0100, evo wrote:  
>  Hey!
> 
>  I got the  message that i don't have enough memory to start a
>  domain.
>  How can i understand, what exactly the problem is?
>  Is it a RAM problem on the dom, or in the domain itself, or on
>  the
>  whole
>  system?  
> >>> Others must answer this.
> >>>  
>  By the way, how can i check up how much RAM i have in the whole
>  laptop?
>  (I forgot it :D )  
> >>> 'free -m' on the CLI does the trick.
> >>>
> >>> Joh
> >>>  
> >>
> >> thanks.
> >> i knew about free -m, but i don't know where should i type it, to
> >> get the whole RAM on the machine. What is CLI? :)
> >>  
> > 
> > 'Command line interface'. Open a Shell on dom0 and type in that
> > command.
> >   
> 
> oh, but this can not be true, it shows me 2562 of total memory :D
> 

Use xentop in dom0 to see where all your memory is being used.

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

Re: [qubes-users] Backup stops when the backup file reaches 3Gb

[Mike Keehan]

On Thu, 24 Jan 2019 11:29:50 +
unman  wrote:

> On Thu, Jan 24, 2019 at 01:00:15AM -0500, Chris Laprise wrote:
> > On 01/23/2019 08:15 PM, js...@bitmessage.ch wrote:  
> > > Mike Keehan:  
> > > > Hi,
> > > > 
> > > > I'm using Qubes Backup to save some of my qubes into another VM.
> > > > The backup VM has 18 Gb of storage available, but whenever the
> > > > backup file reaches 3Gb, the backup process just hangs.
> > > > 
> > > > No CPU usage, no error messages, just stops.  The backup window
> > > > shows 40% complete, but never moves any further (different % for
> > > > different combinations of qubes in the backup list).
> > > > 
> > > > After waiting a considerable time (well, 5-10 minutes), hitting
> > > > Cancel in the backup window does cancel it.  The rest of the
> > > > system is continuing to work without problem.  Happens every
> > > > time I try to use Qubes backup.
> > > > 
> > > > The Qubes Disk Space widget shows less than 50% disk used
> > > > overall, the backupVM shows only 18% disk used when the 3Gb
> > > > file has been saved.
> > > > 
> > > > I'm stumped.
> > > > 
> > > > Mike.  
> > > 
> > > Hi,
> > > 
> > > You may have to wait longer than 5-10 minutes. I experience
> > > something similar when doing a full backup, except it's worse
> > > because i'm backing up like 2.5TB. It appears to hang for several
> > > hours at a time (and this happens more than once), but it does
> > > eventually make visible progress again. The whole process takes
> > > over 24 hours. This is why i do full backups very infrequently.
> > > 
> > > For you it shouldn't take nearly as long because it's a lot less
> > > data, but the progress appearing to hang for a while seems to be
> > > normal.
> > > 
> > > I'm using 3.2 tho, and i know they made changes to the backup
> > > mechanism under the hood in 4.0, so i'm not sure if this issue
> > > still applies in 4.0.  
> > 
> > Marek,
> > 
> > Isn't this the null bytes bug in GNU tar?
> > 
> > https://groups.google.com/d/msgid/qubes-users/f4d997d5-7191-06d0-e7bb-ef42745a7db5%40posteo.net
> > 
> > It would be a good idea to update this in dom0. My own backup tool
> > uses GNU tar as well.
> > 
> > -- 
> > 
> > Chris Laprise, tas...@posteo.net
> > https://github.com/tasket
> > https://twitter.com/ttaskett
> > PGP: BEE2 20C5 356E 764A 73EB  4AB3 1DC4 D106 F07F 1886  
> 
> It seems a little early to judge.
> 
> Mike - it looks from your comment as if you have been trying with
> subsets of the qubes? Can you confirm if these are running or stopped.
> 
> Like jsnow, I'm regularly able to backup far more than 3G without
> issue, so it looks as if there's something particular about this
> scenario. It would be helpful if you could confirm the issue when all
> qubes you are backing up are stopped.
> Then try bisecting the qubes backup group - keep bisecting if you hit
> the problem again until you either find the problematic qubes or have
> backed them all up.
> 

OK, progress:)

I can backup a list of stopped qubes, running out to a 10Gb file without
any issues.  They all verify OK too.  However, backing up running qubes
exhibits the problem.  

Starting up one of these qubes and trying to backup causes the progress
indicator to stop at some point, BUT, the data is still being backed up
to disk, and continues flowing for some time.  When the data flow stops,
then I have to cancel the backup operation.  However, verifying the
backup works OK - file size reported is correct, and the verify process
finishes successfully.  I haven't tried to actually restore one of
these yet.

I tried recording the process status of both dom0 and the backup vm
during the backups, but could not see any particular process dying when
the progress updater stopped moving.  The tar processes stopped in dom0
but I guess that was because they had finished creating the private.img
files.

So it looks like backing up a live VM causes the backup process to fail
at some point, but not before the data is actually backed up.  

It doesn't look like a tar null issue as the data does get to disk OK.
It's just the control of the backup process getting out of step
somewhere.

Mike.

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

Re: [qubes-users] Fedora-26 template unable to update

[Mike Keehan]

On Fri, 25 Jan 2019 02:47:50 -0800
edalva...@riseup.net wrote:

> I've been struggling to update my Fedora-26 template for a while. So
> far none of the various bug-reports I've found on the issue seem to
> help. 
> 
> I've checked that all URL's in /etc/yum.repos.d/qubes-r4.repo use
> https as suggested. 
> 
> CONTENT OF /etc/yum.repos.d/qubes-r4.repo (disabled repos not shown):
> 
> _ name = Qubes OS Repository for VM (updates)_
> _ baseurl = https://yum.qubes-os.org/r4.0/current/vm/fc$releasever_
> _ #baseurl =
> http://yum.sik5nlgfc5qylnnsr57qrbm64zbdx6t4lreyhpon3ychmxmiem7tioad.onion/r4.0/current/vm/fc$releasever_
> _ gpgkey = file:///etc/pki/rpm-gpg/RPM-GPG-KEY-qubes-4-primary_
> _ skip_if_unavailable=False_
> _ gpgcheck = 1_
> _ enabled=1_
> 
> WHEN UPDATING, it doesn't look like DNF gets any fresh data:
> 
> [user@fedora-26 ~]$ sudo dnf -v update
>  Loaded plugins: builddep, config-manager, copr, debug,
> debuginfo-install, download, generate_completion_cache,
> needs-restarting, playground, qubes-hooks, repoclosure, repograph,
> repomanage, reposync
>  DNF version: 2.7.5
>  cachedir: /var/cache/dnf
>  repo: using cache for: updates
>  updates: using metadata from Tue May 29 13:05:48 2018.
>  repo: using cache for: fedora
>  not found deltainfo for: Fedora 26 - x86_64
>  not found updateinfo for: Fedora 26 - x86_64
>  fedora: using metadata from Wed Jul  5 22:31:38 2017.
>  repo: using cache for: qubes-vm-r4.0-current
>  not found deltainfo for: Qubes OS Repository for VM (updates)
>  not found updateinfo for: Qubes OS Repository for VM (updates)
>  qubes-vm-r4.0-current: using metadata from Wed Jan 23 16:47:03 2019.
>  Last metadata expiration check: 0:08:48 ago on Fri Jan 25 11:08:50
> 2019.
>  --> Starting dependency resolution
>  --> Finished dependency resolution  
>  Dependencies resolved.
>  Nothing to do.
>  Complete!
> 
> I've tried cleaning and refreshing:
> 
>  [user@fedora-26 ~]$ sudo dnf clean all
>  53 files removed
>  [user@fedora-26 ~]$ sudo dnf -v update --best --allowerasing
> --refresh --releasever=26
>  Loaded plugins: builddep, config-manager, copr, debug,
> debuginfo-install, download, generate_completion_cache,
> needs-restarting, playground, qubes-hooks, repoclosure, repograph,
> repomanage, reposync
>  DNF version: 2.7.5
>  cachedir: /var/cache/dnf
>  Fedora 26 - x86_64 - Updates703 kB/s |  22 MB
> 00:31
>  updates: using metadata from Tue May 29 13:05:48 2018.
>  Fedora 26 - x86_64  742 kB/s |  53 MB
> 01:13
>  not found deltainfo for: Fedora 26 - x86_64
>  not found updateinfo for: Fedora 26 - x86_64
>  fedora: using metadata from Wed Jul  5 22:31:38 2017.
>  Qubes OS Repository for VM (updates) 53 kB/s | 204 kB
> 00:03
>  not found deltainfo for: Qubes OS Repository for VM (updates)
>  not found updateinfo for: Qubes OS Repository for VM (updates)
>  qubes-vm-r4.0-current: using metadata from Fri Jan 25 00:45:03 2019.
>  Last metadata expiration check: 0:00:00 ago on Fri Jan 25 11:26:26
> 2019.
>  Completion plugin: Generating completion cache...
>  --> Starting dependency resolution
>  --> Finished dependency resolution  
>  Dependencies resolved.
>  Nothing to do.
>  Complete! 
> 
> Any suggestions on this? I really dislike to sit on a outdated
> system :/
> 
> 
> Best regards, 
> Ed Alvarez
> 

Fedora 26 reached end-of-life last year.  You need to install Fedora 28
at least, or Fedora 29.

Mike.

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

Re: [qubes-users] Re: why mail-list?

[Mike Keehan]

On Fri, 01 Feb 2019 16:24:22 -0500
kitchm  wrote:

> I think that it is far more helpful for someone who has
> actually done it to clearly and carefully explain the steps
> involved to use the mail list (or google group postings or
> whatever you call them) in Thunderbird and other e-mail
> clients, as well as Firefox and other web browsers or within
> Tutanota itself.
> 
> I have read everything that has been posted, plus the direct
> administrator's comments about how to do it, without finding
> anything that works so far.
> 
> Personal beliefs mean little when people are crying out for
> help.  If something can be proven to be intuitive, then
> speak up, or else hold your tongue.  The bottom line remains
> that it provably does not work at this point in time.
> 
> Thank you.
> 

What doesn'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/20190201225726.145c80b0.mike%40keehan.net.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Suggestion about an UI detail

[Mike Keehan]

On Tue, 5 Feb 2019 13:58:17 +0100
Nicklas Avén  wrote:

> Hi
> 
> 
> I am a new happy Qubes user. Getting almost everything to work on a
> Dell 7530 with xeon 2186 and Nvidia P3200. Qubes 4.01 made things
> quite easy :-)
> 
> 
> I find Qubes very intuitive to work with, but I have a suggestion
> that I have no idea if it is easy or hard to do.
> 
> It is just a work flow thought without any knowledge about what would
> be affected.
> 
> 
> When I work in one qube it is a common task to open other programs in 
> the same qube. If working in a terminal I want Scite for scratching
> for instance.
> 
> Then it would be awesome if there was a quick way to get the 
> application-list from only that Qube. My suggestion is that I could
> find the application list for that specific Qube by right clicking
> the top of the application. In the menu about maximizing, minimizing
> and so on. With that in place I guess it would be possible to also
> put a key-combination on that feature. Since that would be a 1
> dimensional list it would be easy to navigate just with up and down
> arrows.
> 
> Just a thought since I notice, when I am in the middle of a thought
> in some work, it rips away the focus to think about what Qube I am
> in, searching the start menu for the right qube and then searching
> the application list for the right application.
> 
> I use Qubes primary to separate different customers when I work as a 
> consultant. Never mixing data from different jobs gives confidence.
> 
> BTW, I became a monthly supporter from today, worth every penny.
> Thanks a lot for Qubes OS
> 
> 
> ATB
> 
> 
> Nicklas Avén
> 
> 

Hi Nicklas,

I use a number of xfce Launchers on the taskbar to achieve something
similar.  Each of the launchers is for a separate qube, and has only
as many individual program entries as I want shortcuts for in that
qube.

This was described in this list some time ago, but I can't remember
who it was unfortunately, nor find the original email.  I think it was
in reply to a question about how to organise workflow, or maybe was
it possible to edit the main menu.  Anyway, kudos to the guy who 
described it - it's worked brilliantly for me ever since.

Mike.

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

Re: [qubes-users] Backup stops when the backup file reaches 3Gb

[Mike Keehan]

On Thu, 24 Jan 2019 11:27:00 -0500
Chris Laprise  wrote:

> On 01/24/2019 06:29 AM, unman wrote:
> > On Thu, Jan 24, 2019 at 01:00:15AM -0500, Chris Laprise wrote:  
> >> On 01/23/2019 08:15 PM, js...@bitmessage.ch wrote:  
> >>> Mike Keehan:  
> >>>> Hi,
> >>>>
> >>>> I'm using Qubes Backup to save some of my qubes into another VM.
> >>>> The backup VM has 18 Gb of storage available, but whenever the
> >>>> backup file reaches 3Gb, the backup process just hangs.
> >>>>
> >>>> No CPU usage, no error messages, just stops.  The backup window
> >>>> shows 40% complete, but never moves any further (different % for
> >>>> different combinations of qubes in the backup list).
> >>>>
> >>>> After waiting a considerable time (well, 5-10 minutes), hitting
> >>>> Cancel in the backup window does cancel it.  The rest of the
> >>>> system is continuing to work without problem.  Happens every
> >>>> time I try to use Qubes backup.
> >>>>
> >>>> The Qubes Disk Space widget shows less than 50% disk used
> >>>> overall, the backupVM shows only 18% disk used when the 3Gb file
> >>>> has been saved.
> >>>>
> >>>> I'm stumped.
> >>>>
> >>>> Mike.  
> >>>
> >>> Hi,
> >>>
> >>> You may have to wait longer than 5-10 minutes. I experience
> >>> something similar when doing a full backup, except it's worse
> >>> because i'm backing up like 2.5TB. It appears to hang for several
> >>> hours at a time (and this happens more than once), but it does
> >>> eventually make visible progress again. The whole process takes
> >>> over 24 hours. This is why i do full backups very infrequently.
> >>>
> >>> For you it shouldn't take nearly as long because it's a lot less
> >>> data, but the progress appearing to hang for a while seems to be
> >>> normal.
> >>>
> >>> I'm using 3.2 tho, and i know they made changes to the backup
> >>> mechanism under the hood in 4.0, so i'm not sure if this issue
> >>> still applies in 4.0.  
> >>
> >> Marek,
> >>
> >> Isn't this the null bytes bug in GNU tar?
> >>
> >> https://groups.google.com/d/msgid/qubes-users/f4d997d5-7191-06d0-e7bb-ef42745a7db5%40posteo.net
> >>
> >> It would be a good idea to update this in dom0. My own backup tool
> >> uses GNU tar as well.
> >>
> >> -- 
> >>
> >> Chris Laprise, tas...@posteo.net
> >> https://github.com/tasket
> >> https://twitter.com/ttaskett
> >> PGP: BEE2 20C5 356E 764A 73EB  4AB3 1DC4 D106 F07F 1886  
> > 
> > It seems a little early to judge.
> > 
> > Mike - it looks from your comment as if you have been trying with
> > subsets of the qubes? Can you confirm if these are running or
> > stopped.
> > 
> > Like jsnow, I'm regularly able to backup far more than 3G without
> > issue, so it looks as if there's something particular about this
> > scenario. It would be helpful if you could confirm the issue when
> > all qubes you are backing up are stopped.
> > Then try bisecting the qubes backup group - keep bisecting if you
> > hit the problem again until you either find the problematic qubes
> > or have backed them all up.
> >   
> 
> Oops, I pasted the wrong link. Here is the correct one:
> 
> https://utcc.utoronto.ca/~cks/space/blog/sysadmin/TarFindingTruncateBug
> 
> The symptoms sound remarkably the same... potentially hours-long
> delays with no adverse effect on data. Trigger condition is not about
> size, but due to corner cases that involve backing up nulls.
> 

Thanks to all of you !!

I've been out today, but will have a look at tracking down the culprit
tomorrow:)

Mike.

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

Re: [qubes-users] Qubes backup UI stalls badly

[Mike Keehan]

On Tue, 16 Apr 2019 12:21:54 -0400
Ryan Tate  wrote:

> Today I went to backup my machine using Qubes backup GUI and near the
> end (?) the progress bar was at 100% but the Finish button was not
> clickable. I waited maybe half an hour, an hour, and tried closing
> the window. I got an error message saying the window was not
> responding and asking if I wanted to force close. I said No. Now
> (maybe 15 minutes later) the window is completely blank.
> 
> I have previously been left without a bootable Qubes machine because
> I cancelled a Qubes restore. I am worried I am about to be in the
> same state. Is there anywhere I can check to see if there are big
> stray files left behind in dom0 and not cleaned up? Can I check if
> I’m about to have lvm issues?
> 
> Also, this is not the first time Qubes Backup has behaved oddly. I
> also commonly get it stuck at 99% for hours so I give up and force
> close. Other times, it proceeds pretty quickly to 100% and I get the
> Finish button clickable.
> 
> The backup is only about 90GB (uncompressed, but compressed it is
> somewhere closer to 50GB) and is coming off a speedy internal drive
> to a decent USB3 external disk. No idea why I am having these issues.
> 

It was a combination of issues on my machine that caused the same thing,

1. I do not have the lvm disk setup,
2. Backing up live vms.

As long as I only back up vms that are off, it all works perfectly.
I found this answered by Marek after searching for a while.

I have restored OK too, but have only done this once.  It worked fine.

Mike.
 

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

Re: [qubes-users] Re: desktop suspend breaks sys-usb/ CPU bug present

[Mike Keehan]

On Thu, 13 Jun 2019 19:28:38 +
"'awokd' via qubes-users"  wrote:

> Mike Keehan:
> 
> > There has been a thread on the Linux Kernel mailing list recently,
> > discussing the need to re-enable the SMT chips during resume else
> > something breaks, and then turn them off again.  You may be one
> > of the unlucky ones to heave this affecting your system.  I'm not
> > sure which new kernel the fix is in - may not be until 5.2 comes
> > out.  
> 
> Did they happen to mention if disabling it in UEFI config works
> around the problem?
> 

I think the kernel issue was with hibernation and resume, not with
suspend to memory and resume.  So it is probably a different issue
with the Qubes suspend/resume problems.  

I often have to restart the NetVM after suspend (even with the net
modules on the blacklist), and occasionally the usbVM.

Oddly enough, those two VMs sometimes don't work properly at boot
time, but very rarely.  Could be a race condition or something.

Mike.

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

Re: [qubes-users] has any one get fully worked archlinux template?

[Mike Keehan]

On Sat, 15 Jun 2019 07:31:18 -0700 (PDT)
travorfirefuel...@gmail.com wrote:

> subj
> 

yes

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

Re: [qubes-users] Re: desktop suspend breaks sys-usb/ CPU bug present

[Mike Keehan]

On Thu, 13 Jun 2019 07:14:47 +
"'awokd' via qubes-users"  wrote:

> Jon deps:
> > On 6/12/19 8:14 AM, Jon deps wrote:  
> 
> >> Jun 12 07:52:01 dom0 kernel: MDS CPU bug present and SMT on, data
> >> leak possible. See 
> >> https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html 
> >> for more details.  
> 
> > 
> > .any idea on the  "data leak possible"    journal entry?
> > 
> > sounds a bit scary,  maybe I need to  look around in my UEFI  to
> > disable some cache-ing ?  
> 
> SMT should be off. Do you see that same message if you do a cold
> power on? Also, in "sudo cat /boot/efi/EFI/qubes/xen.cfg", do you see 
> "smt=off" in the Xen options lines?
> 
> I wonder if there is a Xen bug making SMT re-enable after a resume. 
> Please check the above, then look in your UEFI options to disable 
> Hyperthreading/SMT.
> 

There has been a thread on the Linux Kernel mailing list recently,
discussing the need to re-enable the SMT chips during resume else
something breaks, and then turn them off again.  You may be one
of the unlucky ones to heave this affecting your system.  I'm not
sure which new kernel the fix is in - may not be until 5.2 comes
out.

Mike.

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

Re: [qubes-users] Full proper backup of Dom0 possible?

[Mike Keehan]

On Wed, 12 Jun 2019 10:29:54 -0400
Chris Laprise  wrote:

> On 6/11/19 6:50 PM, Chris Laprise wrote:
> > I think the best solution for a safe and comprehensive dom0 backup
> > is to have Qubes simply snapshot the root lv at boot time, before
> > its mounted as read-write. It shouldn't take more than a few script
> > lines in the dom0 startup. Then dom0 can be backed up like any
> > other vm.  
> 
> I created an issue with a 3-line (barely tested) example here:
> 
> https://github.com/QubesOS/qubes-issues/issues/5094
> 

Chris, have you some thoughts on how to restore such a backup?

Mike.

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

Re: [qubes-users] Re: desktop suspend breaks sys-usb/ CPU bug present

[Mike Keehan]

On Thu, 13 Jun 2019 19:28:38 +
"'awokd' via qubes-users"  wrote:

> Mike Keehan:
> 
> > There has been a thread on the Linux Kernel mailing list recently,
> > discussing the need to re-enable the SMT chips during resume else
> > something breaks, and then turn them off again.  You may be one
> > of the unlucky ones to heave this affecting your system.  I'm not
> > sure which new kernel the fix is in - may not be until 5.2 comes
> > out.  
> 
> Did they happen to mention if disabling it in UEFI config works
> around the problem?
> 

Disabling doesn't help.  I'm not sure why it hasn't affected more
systems than it has, it seems odd that it only appeared recently.

Suspend/resume has always been a bit iffy on my laptops, so I don't
use it much.

I think all you can do is try whatever options are available to you
and see if anything helps.

Mike.

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

Re: [qubes-users] Re: CPU overheating issues, pulsating fan, recommendations?

[Mike Keehan]

On Wed, 19 Jun 2019 18:57:52 +
Jon deps  wrote:

> On 6/18/19 11:39 AM, Mike Keehan wrote:
> > On Tue, 18 Jun 2019 04:44:04 +
> > omerta-3q9s2cxqgw4kltdg6p0...@public.gmane.org wrote:
> >   
> >> Hey all,
> >>
> >> Over the last week I've noticed my laptops CPU keeps peaking @
> >> 80-85 every now and then, even when I'm not doing any resource
> >> intensive tasks.
> >>
> >> I run 11-12 VMs @ a time which barely scratches the 34GB RAM on a
> >> P51 Thinkpad with a i7 7820HQ running in a standard temperature
> >> room environment majority of the time.
> >>
> >> Have thought of getting a cooling pad to resolve this, but would
> >> prefer to see if there are any tweaks which can be made within dom0
> >> or the BIOS to put an end to this.
> >>
> >> Also of note, I'm getting similar pulsating fan noise as posted
> >> here https://github.com/QubesOS/qubes-issues/issues/3599.
> >>
> >> Many thanks,
> >> om
> >>  
> > 
> > Run xentop in dom0 to see which of your VMs are using cpu the most.
> > Web browsers can use lots of cpu on some pages!
> > 
> > Mike.
> >   
> 
> fwiw, this morning I woke up and my system was at the qubes 1st login 
> screen , apparently the system has crashed just far enough to close
> all VMs but not reboot?
> 
> I am now looking at the Xentop  CPU numbers and with whonix-ws update 
> and one up to date torbrowser window 1 tab  open  and one page view,
> the CPU is at 150%
> 
> Maxmem was at 2000 , up'd that a bit,  but also changed the VCPU to
> '3' it was set to '2'  and now the CPU with 1 page torbrowser open is
> at 5%
> 
> 
> I guess my question what effect changing the VCPU  of the
> TB-AppVM-Qube is
> 
> or maybe something changed with the whonix-ws recently  to mess up
> the CPU usages???
> 

I don't use whonix, but I've just started it up to see how it behaves.
And yes, it is using 150% cpu in the tor browser (using top in a
terminal window in whonix-user VM), and about 170% cpu in xentop.
(and my fans have come on!).

All I can suggest is to close the tor browser when not in use.

Mike.

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

Re: [qubes-users] Problem with Wireless connection after reinstalling Qubes 4.0.1

[Mike Keehan]

On Sun, 23 Jun 2019 08:31:45 -0700 (PDT)
Anhangá  wrote:

> Hi,
> 
> I'm quite new using Qubes and I've never been so fond with Linux but
> this changed last year so sorry for newbie questions in advance.
> 
> I installed Qubes 4.0.1 using only wifi connection and it was working
> 100% with wifi connections but I had to reinstall after a ssd upgrade
> I did on my laptop and in this second time I used a wired connection
> to do install Qubes 4.0.1.
> 
> In this new installation, wifi connection is not working and I
> counld't figure out why. The connections options only shows My Wired
> Connection but none Wifi connection available as shown in the
> attached Screenshot.
> 
> I've tried the Qubes Wireless troubleshooting (resetting wireless
> cards by reloading drivers) but didn't work.
> 
> I tried some commands on sys-net to see some informations about my
> wireless card and seems that everything is ok.
> 
> 
> 
> lspci -vv:
> 
> 00:07.0 Network controller: Qualcomm Atheros QCA9377 802.11ac
> Wireless Network Adapter (rev 31) Subsystem: Samsung Electronics Co
> Ltd Device 4133 Physical Slot: 7
>   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
> ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF-
> FastB2B- ParErr- DEVSEL=fast >TAbort- SERR-  INTx- Latency: 0 Interrupt: pin A routed to IRQ 72
>   Region 0: Memory at f200 (64-bit, non-prefetchable)
> [size=2M] Capabilities: [40] Power Management version 3
>   Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
> PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst+ PME-Enable-
> DSel=0 DScale=0 PME- Capabilities: [50] MSI: Enable+ Count=1/1
> Maskable- 64bit- Address: fee96000  Data: 4300
>   Capabilities: [70] Express (v2) Endpoint, MSI 00
>   DevCap: MaxPayload 256 bytes, PhantFunc 0,
> Latency L0s unlimited, L1 <64us ExtTag- AttnBtn- AttnInd- PwrInd-
> RBE+ FLReset- SlotPowerLimit 10.000W DevCtl:  CorrErr-
> NonFatalErr- FatalErr- UnsupReq- RlxdOrd+ ExtTag- PhantFunc- AuxPwr-
> NoSnoop+ MaxPayload 128 bytes, MaxReadReq 512 bytes
>   DevSta: CorrErr- NonFatalErr- FatalErr-
> UnsupReq- AuxPwr+ TransPend- LnkCap:  Port #0, Speed 2.5GT/s,
> Width x1, ASPM L0s L1, Exit Latency L0s <4us, L1 <64us ClockPM+
> Surprise- LLActRep- BwNot- ASPMOptComp+ LnkCtl:   ASPM Disabled;
> RCB 64 bytes Disabled- CommClk- ExtSynch- ClockPM- AutWidDis- BWInt-
> AutBWInt- LnkSta: Speed 2.5GT/s (ok), Width x1 (ok)
>   TrErr- Train- SlotClk+ DLActive- BWMgmt-
> ABWMgmt- DevCap2: Completion Timeout: Not Supported, TimeoutDis+,
> LTR+, OBFF Via message AtomicOpsCap: 32bit- 64bit- 128bitCAS-
>   DevCtl2: Completion Timeout: 50us to 50ms,
> TimeoutDis-, LTR-, OBFF Disabled AtomicOpsCtl: ReqEn-
>   LnkSta2: Current De-emphasis Level: -6dB,
> EqualizationComplete-, EqualizationPhase1- EqualizationPhase2-,
> EqualizationPhase3-, LinkEqualizationRequest- Kernel driver in use:
> ath10k_pci Kernel modules: ath10k_pci
> 
> 
> 
> lshw:
> 
> *-network:0
>  description: Ethernet interface
>  product: RTL810xE PCI Express Fast Ethernet controller
>  vendor: Realtek Semiconductor Co., Ltd.
>  physical id: 6
>  bus info: pci@:00:06.0
>  logical name: ens6
>  version: 07
>  serial: 98:83:89:ca:86:9a
>  size: 100Mbit/s
>  capacity: 100Mbit/s
>  width: 64 bits
>  clock: 33MHz
>  capabilities: pm msi pciexpress vpd bus_master cap_list
> ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
> configuration: autonegotiation=on broadcast=yes driver=r8169
> driverversion=2.3LK-NAPI duplex=full firmware=rtl8106e-1_0.0.1
> 06/29/12 ip=192.168.25.11 latency=64 link=yes multicast=yes port=MII
> speed=100Mbit/s resources: irq:71 ioport:c200(size=256)
> memory:f222a000-f222afff memory:f2224000-f2227fff *-network:1
> description: Network controller product: QCA9377 802.11ac Wireless
> Network Adapter vendor: Qualcomm Atheros physical id: 7 bus info:
> pci@:00:07.0 version: 31
>  width: 64 bits
>  clock: 33MHz
>  capabilities: pm msi pciexpress bus_master cap_list
>  configuration: driver=ath10k_pci latency=0
>  resources: irq:72 memory:f200-f21f
>   *-network:0
>description: Ethernet interface
>physical id: 1
>logical name: vif6.0
>serial: fe:ff:ff:ff:ff:ff
>capabilities: ethernet physical
>configuration: broadcast=yes driver=vif ip=10.137.0.5 link=yes
> multicast=yes *-network:1
>description: Ethernet interface
>physical id: 2
>logical name: vif13.0
>serial: fe:ff:ff:ff:ff:ff
>capabilities: ethernet 

Re: [qubes-users] CPU overheating issues, pulsating fan, recommendations?

[Mike Keehan]

On Tue, 18 Jun 2019 04:44:04 +
ome...@firemail.cc wrote:

> Hey all,
> 
> Over the last week I've noticed my laptops CPU keeps peaking @ 80-85 
> every now and then, even when I'm not doing any resource intensive 
> tasks.
> 
> I run 11-12 VMs @ a time which barely scratches the 34GB RAM on a P51 
> Thinkpad with a i7 7820HQ running in a standard temperature room 
> environment majority of the time.
> 
> Have thought of getting a cooling pad to resolve this, but would
> prefer to see if there are any tweaks which can be made within dom0
> or the BIOS to put an end to this.
> 
> Also of note, I'm getting similar pulsating fan noise as posted here 
> https://github.com/QubesOS/qubes-issues/issues/3599.
> 
> Many thanks,
> om
> 

Run xentop in dom0 to see which of your VMs are using cpu the most.
Web browsers can use lots of cpu on some pages!

Mike.

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

Re: [qubes-users] Edit Dom0 conf.

[Mike Keehan]

Files in /etc are owned by the user 'root', so you need to use sudo
to be able to change them.

"sudo vi /etc/. ".

Be carefull, these files are essential for correct operation of
the system.  You would be best advised to make a backup of any
file you want to edit!

Mike.


On Tue, 09 Jul 2019 08:40:09 +
"'Avart Jean-Francois' via qubes-users" 
wrote:

> > Hello,
> >   
> 
> > I love Qubes OS but I'm noobs :)
> >   
> 
> > I try to change de confi file Dom0 for full screen vm streaming.
> >   
> 
> > I try with eidtor "VI" to change de txt, but it's "read only" and
> > not possible to edit the files in the terminal. It's possible to
> > install a GUI editor txt in Dom0 for edit the
> > files /etc/qubes/guid.conf ? 
> 
> > 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/20190709115327.44c25205.mike%40keehan.net.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] bottlenecks during qvm-backup

[Mike Keehan]

On Tue, 23 Apr 2019 21:58:17 +0100
lik...@gmx.de wrote:

> Hi,
> 
> is there a possibility to find the bottlenecks during a qvm-backup? A
> backup of ~100GB with compression takes several hours. During the
> time the (4) cpu cores (xentop) are not used well and the harddisk
> (iotop) is also idling a lot. I'm creating a backup to a usb attached
> ext3 formated harddrive.
> 
> How to find out which components are responsible for the slow process?
> 
> Best, Pete
> 

Just try copying 100Gb to the usb connected drive to see how long that
takes.  USB drive speed can be quite slow.

Mike.

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

Re: [qubes-users] Qubes Installation freeze

[Mike Keehan]

On Sun, 21 Apr 2019 11:52:32 -0700 (PDT)
Blue  wrote:

> I've so far been unable to get qubes 4.0.1 to install on my Dell
> laptop, it keeps freezing of file 909/1042 kernel-qubes-vm.x86_64.
> Its a nvme drive if that makes a difference.
> 
> I've verified the ISO of qubes and that matches, I created the pen
> drive in Ubuntu using the DD command,as  per the site, and I've used
> 2 different 16gb pen drives.
> 
> The pen drive boots in legacy mode and lets me enter all settings and
> starts install. The installation hangs at the file shown above and I
> cannot find any way to exit or restart the machine other than a hard
> reboot.
> 
> I've tried the UEFI troubleshooting on the qubes site as well, anyone
> else got any ideas?
> 

I had the same problem on my Dell laptop.  I had to blacklist the
nouveau module in the xen.cfg file, but if you are using legacy
boot, then the grub.cfg is probably the one to look at.

Mike.
  

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

Re: [qubes-users] request : add to dom0 FFmpeg libraries and codecs h264/h265/libavcodec/libfdk_aac/libmp3lame/libopus/libvpx

[Mike Keehan]

On Sun, 11 Aug 2019 03:47:14 -0700 (PDT)
john due  wrote:

> Hello, Dear Qubes users and devs!
> 
> Can you add please FFmpeg libraries and codecs to dom0 repos?
> Because it impossible to add RPMfusion repo to Dom0 and synchronize
> it with dnf/qubes-dom0-update mechanism.
> it required system-base-release 25 dependencies.
> 
> Best Regards, john due
> 

Why do you need ffmpeg in dom0?  Dom0 is for admin, not for running
applications.  This is to preserve the security of your whole system.

Mike.

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/20190811120316.37bd89f5.mike%40keehan.net.

Re: [qubes-users] Resizing partitions in QVMs

[Mike Keehan]

On Sat, 16 Nov 2019 02:44:24 -
zenandart via qubes-users  wrote:

> Hi,
> 
> I recently ran out space of xvdb on a QVM (while I still had plenty of
> space on xvda), so I gave 10GB or so in Qubes Settings to the VM. But
> all the new space went to xvda, and the space of xvdb didn't change.
> 
> I thought I should resize partitions, then. So I installed GParted.
> But soon I realized that I couldn't resize system partitions in the
> VM, for both of xvda and xvdb are used and therefore cannot be
> unmounted.
> 
> I have some experience resizing partitions in systems that don't have
> VMs, in which case I'll load a system from USB drives to do so, but
> I'm not sure how to do it in Qubes OS.
> 
> I've searched some tutorials about resizing partitions in VirtualBox
> VMs, but I don't think it helps much.
> 
> So, the question is, how can I resize partitions in a QVM?
> 
> Best regards,
> zenandart
> 

In Qube Manager, use "Qube settings" for the VM that is out of space.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/20191116132322.4ba1c72f.mike%40keehan.net.

Re: [qubes-users] Time sync isn't working

[Mike Keehan]

On Mon, 09 Dec 2019 14:46:50 +
"'Oli Sturm' via qubes-users"  wrote:

> On Monday, December 9, 2019 2:40 PM, Mike Keehan 
> wrote:
> 
> > I suspect you need to investigate systemd's timesyncd stuff. Good
> > luck!  
> 
> I believe I would just need to switch that on to activate it. But I
> believe time sync should work in Qubes out of the box - I remember
> reading that somewhere in the docs. Maybe my expectations are wrong
> here?
> 
> Thanks
> Oli
> 

systemd-timesyncd is running on my Qubes sys-net vm.  I'm assuming
that it is part of the standard installation.  You need to investigate
why it is not working on your machine I think.

Mike.

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/20191209150554.4cedb486.mike%40keehan.net.

Re: [qubes-users] Time sync isn't working

[Mike Keehan]

On Mon, 09 Dec 2019 14:04:10 +
"'Oli Sturm' via qubes-users"  wrote:

> Hi,
> 
> I'm running 4.0 with all current updates. I'm trying to figure out
> why I don't get synchronized time anywhere in the system. I have
> found various old issues and discussions about similar problems, but
> unfortunately none of the scenarios described there seem to be
> up-to-date anymore.
> 
> As I understand, my sys-net VM is the "ClockVM". I have confirmed
> that it is configured as such in Qubes settings (using the UI dialog
> in Qube Manager). However, it seems that this VM is not set up to
> sync time with an NTP server. I see that all entries in the "Time"
> block in /etc/systemd/timesyncd.conf are commented. "ntpdate" is not
> installed. Is there some other NTP sync mechanism installed in this
> VM? If so, where is it? In any case it's clearly not working.
> 


Ah the good old days where you just knew where and what to look for.

I suspect you need to investigate systemd's timesyncd stuff.  Good luck!

Mike

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/20191209144000.3435e05b.mike%40keehan.net.

Re: [qubes-users] wipe released diskspace of a disposable VM's

[Mike Keehan]

On Thu, 12 Dec 2019 16:58:41 +0100
"josefh.maier via qubes-users"  wrote:

> Hello list,
> 
> I heard that a Qubes-user was forced to hand over the Qubes-password,
> and that a forensic examiner was able to restore artifacts of a
> deleted disposeable form the harddisk... 
> 
> Is this story possible? And what's the best aprroach to wipe
> diskspace used before by a disposable VM after that VM is closed?
> 
> 
> Thank you!
> 
> Regards,
> 
> Joe
> 

Qubes won't help in this situation - see
https://www.qubes-os.org/doc/disposablevm/#disposablevms-and-local-forensics

They recommend using Tails for this type of situation.

Mike.

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/20191212172347.2d05ca06.mike%40keehan.net.

Re: [qubes-users] Easiest way to redirect USB to a VM?

[Mike Keehan]

On Sun, 6 Oct 2019 22:04:05 -0700 (PDT)
Guerlan  wrote:

> I tried to create sys-usb, and my keyboard stopped working. I then
> rebooted and couldn t use keyboard to put my LUKS password. I had to
> reinstall qubes entirely.
> 
> Is there an easier way to pass USB from dom0 to a VM? I don' t want
> to create a sys-usb and I don' t care too much about security in this
> level. I just need to have my Android phone inside the virtual
> machine.
> 

Have you read the docs?  https://www.qubes-os.org/doc/usb-devices/

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/20191007130640.7ee3aa5f.mike%40keehan.net.

Re: [qubes-users] Easiest way to redirect USB to a VM?

[Mike Keehan]

On Tue, 8 Oct 2019 11:40:23 -0700 (PDT)
Guerlan  wrote:

> Yes, I followed that topic and when I created the sys-usb VM mey
> keyboard and mouse got disabled and I couldn't do anything else.
> 
> That's why I asked if there's an easier (possibly less secure) way to 
> redirect the USB from dom0 directly to another VM. I can't create a
> sys-usb because I will be left without keyboard
> 
> On Monday, October 7, 2019 at 9:06:50 AM UTC-3, Mike Keehan wrote:
> >
> > On Sun, 6 Oct 2019 22:04:05 -0700 (PDT) 
> > Guerlan > wrote: 
> >  
> > > I tried to create sys-usb, and my keyboard stopped working. I
> > > then rebooted and couldn t use keyboard to put my LUKS password.
> > > I had to reinstall qubes entirely. 
> > > 
> > > Is there an easier way to pass USB from dom0 to a VM? I don' t
> > > want to create a sys-usb and I don' t care too much about
> > > security in this level. I just need to have my Android phone
> > > inside the virtual machine. 
> > >   

> >
> > Have you read the docs?  https://www.qubes-os.org/doc/usb-devices/ 
> >  
> 

In the link above, the section titled "With The Command Line Tool" shows
how to use qvm-usb in dom0 to attach usb devices to a VM.

(I think you have been reading the usb-qubes page, and not that in the
link given above!).

Mike.

ps - mailing list etiquette is to post replies below the email, not
above.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/20191008213927.447a674a.mike%40keehan.net.

Re: [qubes-users] Obtaining genuine Qubos installer

[Mike Keehan]

On 3/5/20 2:40 PM, Mark Fernandes wrote:
On Thu, 5 Mar 2020 at 13:30, Mike Keehan <mailto:m...@keehan.net>> wrote:


On 3/5/20 12:31 PM, Mark Fernandes wrote:
 > I want to get a genuine copy of Qubos, from here in the UK
(United Kingdom).
 >
 > The only way described on the Quebos website at present, appears
to be
 > to download the ISO.
 >
 > I have the classic security problem described on the website
 > <https://www.qubes-os.org/doc/install-security/>, where not having a
 > trust-worthy machine, means that I have a never-ending chain of
trust
 > issues for each machine that I use in the obtaining of the software.
 >
 > I suggest that the hyper-linked web-page above, be updated to
provide
 > further guidance as to how to ensure you have a genuine copy of the
 > Qubos software. *_Also, can anyone in this news group provide any
such
 > guidance for myself (and others?)_*
 >
 >
 >
 >     (Solely) some thoughts on how to help ensure possession of a
genuine
 >     copy of Quebos:
 >
 >      1. If Quebos is distributed through PC magazine DVDs, users can
 >         purchase a few copies of a particular magazine having such a
 >         DVD, at random, from different stores, in widely different
 >         locations (different counties, etc.) Users can then
compare the
 >         copies to make sure they are identical.
 >      2. Purchase Quebos from a randomly chosen big PC store, that has
 >         perhaps 100 copies of the software on its shelves, on a day
 >         picked at random, by selecting one of the copies at
random from
 >         the shelves.
 >      3. If a user believes they are being tracked, what they can
do, is
 >         schedule in their mind (or otherwise), to make such a
purchase
 >         over the next few months, and then when they are doing some
 >         activity (for example visiting a friend in the city),
they can
 >         just as an aside go and purchase a copy of the software.
 >      4. Purchase the Quebos software from an online retailer,
that uses
 >         special tamper-evident packaging
<https://www.jwproducts.co.uk>,
 >         and then compare the copy obtained in this way, with software
 >         downloaded from the Quebos website.
 >      5. Obtain software in several ways, then compare copies to make
 >         sure they're identical.
 >
 >
 >
 > Thanks,
 >
 >
 > Mark Fernandes
 >
 >

Have you read the documentation at
https://www.qubes-os.org/doc/installation-guide/ ??


I previously skim read what appeared to be the relevant parts from the 
guide. Just now, I read from the beginning till the following text in 
the guide:


/Once the ISO has been verified as authentic, you should.../


The text after that point appears to be irrelevant.

The only thing relevant to this topic in the guide, appears to be the 
information on verifying signatures (which is of course standard 
practice). In reading information on the Quebos website, there was 
implicit mention that users may be operating under oppressive 
regimes/circumstances. With this in mind, I just feel that more guidance 
is needed on how to obtain authentic copies of the Quebos software. I've 
hinted at some ideas as to how to do this, in my starting post for this 
topic.



Thanks,


Mark Fernandes



And did you thoroughly read the linked "our guide on verifying
signatures" page?

https://www.qubes-os.org/security/verifying-signatures/

It shows you how to verify that the ISO you download was actually
created by the Qubes OS team.  (Quebos is not correct the spelling!).

Mike.

--
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/1bd112e6-608d-dacc-1aff-d82ae4af1a14%40keehan.net.

Re: [qubes-users] No boot after dom0 kernel update

[Mike Keehan]

On 2/24/20 7:17 PM, ncmy...@gmail.com wrote:

Thank you for your kind attention.

I want to make clear that in each case, the new kernel has worked
fine once I persuaded my BIOS to boot it. The problem is always
that, after each kernel upgrade, the BIOS no longer recognizes any
bootable partition, not even listing the drive among its boot options.

Unmounting before fsck is the standard process, but I wonder why
and how the dom0 kernel upgrade script leaves the boot partition
in a state that the BIOS will not boot. I am far from certain that the
fsck.vfat was what restored bootability, but something did.

On Monday, February 24, 2020 at 1:58:48 PM UTC-5, Andrey Arapov wrote:

Is there a way to get reliable booting after a dom0 kernel
update?


I am afraid that there is no such way as the new Linux kernel adds
new features, changes the current ones, which are unlikely were
thoroughly tested (or if tested at all) for the whole range of HW
out there or their combinations.

Whenever you are upgrading the SW, be it a Linux kernel or any other
software, you should always expect things can go wrong.
The good news is that you can always rollback and contribute to the
FOSS by reporting the issue.

Do I need to unmount my /boot partition and fsck.vfat it
before rebooting?


You should always unmount the mount point before fsck'ing any
filesystem.

Kind regards,
Andrey Arapov



If your boot partition needs fsck'ing after something writes to it
(like a Qubes update), then it seems that the partition needs to
be fixed.  Probably best to rebuild it if you know how.

Mike.

--
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/33130140-dc8f-9523-646f-25896193ef36%40keehan.net.

Fwd: Re: [qubes-users] Re: AppVms being killed on resume due to clock skew too large

[Mike Keehan]

Should have replied to the list!


 Forwarded Message 
Subject: Re: [qubes-users] Re: AppVms being killed on resume due to 
clock skew too large

Date: Sat, 1 Feb 2020 11:49:29 +
From: Mike Keehan 
To: mmo...@disroot.org

On 2/1/20 10:27 AM, mmo...@disroot.org wrote:

Same problem again, this time not related to any socket closure.
Apparently related to systemd:


[41911.199732] audit: type=1104 audit(1580516883.707:119): pid=4917 
uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred 
grantors=pam_rootok acct="root" exe="/usr/lib/qubes/qrexec-agent" 
hostname=? addr=? terminal=? res=success'
[41920.252871] clocksource: timekeeping watchdog on CPU0: Marking 
clocksource 'tsc' as unstable because the skew is too large:
[41920.252927] clocksource: 'xen' wd_now: 2a1620baf67a wd_last: 
2a140e3c5f9f mask: 
[41920.252972] clocksource: 'tsc' cs_now: ff88779d4270 cs_last: 
5083a288ea9a mask: 

[41920.253013] tsc: Marking TSC unstable due to clocksource watchdog
[41921.161370] audit: type=1100 audit(1580516893.670:120): pid=4955 
uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:authentication 
grantors=pam_rootok acct="root" exe="/usr/lib/qubes/qrexec-agent" 
hostname=? addr=? terminal=? res=success'
[41921.163039] audit: type=1103 audit(1580516893.672:121): pid=4955 
uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred 
grantors=pam_rootok acct="root" exe="/usr/lib/qubes/qrexec-agent" 
hostname=? addr=? terminal=? res=success'
[41921.176874] audit: type=1105 audit(1580516893.686:122): pid=4955 
uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:session_open 
grantors=pam_keyinit,pam_limits,pam_systemd,pam_unix,pam_umask,pam_lastlog 
acct="root" exe="/usr/lib/qubes/qrexec-agent" hostname=? addr=? 
terminal=? res=success'
[41922.205481] audit: type=1106 audit(1580552389.038:123): pid=4955 
uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:session_close 
grantors=pam_keyinit,pam_limits,pam_systemd,pam_unix,pam_umask,pam_lastlog 
acct="root" exe="/usr/lib/qubes/qrexec-agent" hostname=? addr=? 
terminal=? res=success'
[41922.205554] audit: type=1104 audit(1580552389.038:124): pid=4955 
uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred 
grantors=pam_rootok acct="root" exe="/usr/lib/qubes/qrexec-agent" 
hostname=? addr=? terminal=? res=success'
*[41932.321374] systemd[4919]: segfault at 640550f11920 ip 
640550345cbd sp 7ffd40e80440 error 6 in systemd[6405502f6000+b7000]
[41932.321420] Code: 24 28 02 00 00 48 85 c9 74 0f 48 89 81 28 02 00 00 
49 8b 84 24 28 02 00 00 48 85 c0 0f 84 a0 07 00 00 49 8b 94 24 20 02 00 
00 <48> 89 90 20 02 00 00 49 c7 84 24 28 02 00 00 00 00 00 00 49 c7 84*
[41932.321515] audit: type=1701 audit(1580552399.156:125): auid=0 uid=0 
gid=0 ses=4 pid=4919 comm="systemd" exe="/usr/lib/systemd/systemd" 
sig=11 res=1
[41932.336794] audit: type=1130 audit(1580552399.171:126): pid=1 uid=0 
auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@0-4990-0 
comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? 
terminal=? res=success'
[41932.627105] audit: type=1131 audit(1580552399.456:127): pid=1 uid=0 
auid=4294967295 ses=4294967295 msg='unit=user@0 comm="systemd" 
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[41932.636551] audit: type=1131 audit(1580552399.471:128): pid=1 uid=0 
auid=4294967295 ses=4294967295 msg='unit=user-runtime-dir@0 
comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? 
terminal=? res=success'
[41932.661359] audit: type=1131 audit(1580552399.495:129): pid=1 uid=0 
auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@0-4990-0 
comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? 
terminal=? res=success'
[41934.482123] BUG: unable to handle kernel NULL pointer dereference at 
0080

[41934.482143] PGD 0 P4D 0
[41934.482150] Oops:  [#1] SMP PTI
[41934.482159] CPU: 0 PID: 5002 Comm: Compositor Tainted: G O 
4.19.94-1.pvops.qubes.x86_64 #1

[41934.482178] RIP: 0010:mem_cgroup_page_lruvec+0x28/0x50
[41934.482189] Code: 00 00 0f 1f 44 00 00 0f 1f 44 00 00 48 8b 47 38 48 
8b 17 48 85 c0 48 0f 44 05 dc d1 0c 01 48 c1 ea 36 48 8b 84 d0 48 0a 00 
00 <48> 3b b0 80 00 00 00 75 12 f3 c3 48 8d 86 a0 a1 02 00 48 3b b0 80

[41934.48] RSP: 0018:c900011d3aa8 EFLAGS: 00010046
[41934.482232] RAX:  RBX: 82369cc0 RCX: 
c900011d3ae8
[41934.482246] RDX:  RSI: 8880f9fd5000 RDI: 
ea0002adec00
[41934.482265] RBP: 88802f7e6fb8 R08: c900011d3ae8 R09: 
0001eb39
[41934.482279] R10: 000fa000 R11:  R12: 
8880f9fd5000
[41934.482294] R13: ea0002adec00 R14: 0014 R15: 
88802f7e7000
[41934.482308] FS: 00

Re: [qubes-users] Re: AppVms being killed on resume due to clock skew too large

[Mike Keehan]

On 1/31/20 1:11 PM, mmo...@disroot.org wrote:

Hi everyone!

Is anyone experiencing this issue on resume (VMs being killed randomly 
apparently due to clock skew that generates kernel panic) ??

This is happening very often and it makes suspend useless.

I'm using a Lenovo T480s.

Any ideas are really appreciated!

Thanks!

December 22, 2019 8:13 PM, mmo...@disroot.org 
 wrote:


Hello,

I've been struggle with this for months now.
Whenever there's a resume from suspend some random AppVms are
killed. Although this doesn't happen all the time it happens often
enough on resume sufficiently to indicate an issue.
It seems that the clock skew is too large resulting in a kernel
panic that kills the AppVM as the error below shows.

Is anyone experiencing the same issue? Is there any solution to this?

Thank you in advance.

/*[38009.358471] clocksource: timekeeping watchdog on CPU0: Marking
clocksource 'tsc' as unstable because the skew is too large:
[38009.358521] clocksource: 'xen' wd_now: 2697b2c28a19 wd_last:
2696858155d9 mask: 
[38009.358558] clocksource: 'tsc' cs_now: ff40e6dd060e cs_last:
4900d58115e2 mask: *
[38009.358594] tsc: Marking TSC unstable On 1/31/20 1:11 PM, 
mmo...@disroot.org wrote:> Hi everyone!

Is anyone experiencing this issue on resume (VMs being killed randomly 
apparently due to clock skew that generates kernel panic) ??

This is happening very often and it makes suspend useless.

I'm using a Lenovo T480s.

Any ideas are really appreciated!

Thanks!

December 22, 2019 8:13 PM, mmo...@disroot.org 
 wrote:


Hello,

I've been struggle with this for months now.
Whenever there's a resume from suspend some random AppVms are
killed. Although this doesn't happen all the time it happens often
enough on resume sufficiently to indicate an issue.
It seems that the clock skew is too large resulting in a kernel
panic that kills the AppVM as the error below shows.

Is anyone experiencing the same issue? Is there any solution to this?

Thank you in advance.

/*[38009.358471] clocksource: timekeeping watchdog on CPU0: Marking
clocksource 'tsc' as unstable because the skew is too large:
[38009.358521] clocksource: 'xen' wd_now: 2697b2c28a19 wd_last:
2696858155d9 mask: 
[38009.358558] clocksource: 'tsc' cs_now: ff40e6dd060e cs_last:
4900d58115e2 mask: *
[38009.358594] tsc: Marking TSC unstable due to clocksource watchdog
[79151.795501] borgmatic[2418]: segfault at 6060cafd8549 ip
6060ca2ae054 sp 7ffe9d9bbad8 error 4 in
python3.5[6060ca158000+3f]
[79151.795535] Code: 08 4c 8b 5e 08 4c 89 5b f0 4c 89 4e 08 4d 89 0b
48 89 73 e8 4c 89 43 f8 eb 92 66 90 66 2e 0f 1f 84 00 00 00 00 00 48
8b 47 08  80 a9 00 00 00 40 75 03 31 c0 c3 53 48 8b 80 48 01 00
00 48 89
[79152.712396] general protection fault:  [#1] SMP PTI
[79152.712416] CPU: 1 PID: 2425 Comm: systemctl Tainted: G O
4.19.84-1.pvops.qubes.x86_64 #1
[79152.712444] RIP: 0010:__pv_queued_spin_lock_slowpath+0x199/0x270
[79152.712462] Code: eb bd 83 e0 03 c1 ea 12 4c 8d 6d 44 48 c1 e0 04
41 be 01 00 00 00 4c 8d a0 80 10 02 00 8d 42 ff 48 98 4c 03 24 c5 20
77 17 82 <49> 89 2c 24 b8 00 80 00 00 eb 15 84 c0 75 0a 41 0f b6 54
24 44 84
[79152.712509] RSP: 0018:c96c7b60 EFLAGS: 00010002
[79152.712524] RAX: 3ffe RBX: 8880f47b0764 RCX:
0001
[79152.712544] RDX: 3fff RSI:  RDI:
8880f47b0764
[79152.712565] RBP: 8880f5b21080 R08:  R09:
c9637e90
[79152.712585] R10: c96c7e20 R11: 0001 R12:
64616f6c00708019
[79152.712605] R13: 8880f5b210c4 R14: 0001 R15:
0008
[79152.712626] FS: () GS:8880f5b0()
knlGS:
[79152.712647] CS: 0010 DS:  ES:  CR0: 80050033
[79152.712664] CR2: 7f088e3efab4 CR3: 0220a004 CR4:
003606e0
[79152.712687] DR0:  DR1:  DR2:

[79152.712707] DR3:  DR6: fffe0ff0 DR7:
0400
[79152.712727] Call Trace:
[79152.712739] _raw_spin_lock_irqsave+0x32/0x40
[79152.712755] try_to_wake_up+0x3d/0x490
[79152.712767] __wake_up_common+0x96/0x180
[79152.712780] ep_poll_callback+0x1ac/0x2f0
[79152.712791] __wake_up_common+0x96/0x180
[79152.712803] __wake_up_common_lock+0x7c/0xc0
[79152.712819] sock_def_wakeup+0x32/0x40
[79152.712831] unix_release_sock+0x288/0x2d0
[79152.712844] unix_release+0x19/0x30
[79152.712855] __sock_release+0x3d/0xc0
[79152.712866] sock_close+0x11/0x20
[79152.712878] __fput+0xe2/0x210

Re: [qubes-users] New user - network qubes vms

[Mike Keehan]

On 2/4/20 11:26 AM, Douglas Giovani Oechsler wrote:

Hello All!
How are you?

I am starting use Qubes. At my scenario we have PFsense with no DHCP 
network. Inside qubes how can switch qubes vm internal IP? I am reading 
official documentation but, still lost about thiis.


Please, how can I fix or what is my wrong?

Thank you!

Douglas




It's not a Qubes specific issue.  The sys-net VM uses NetworkManager and
dhclient to setup the network.  You need to search for information on
how to set up a static ip address with these standard Linux programs.
(If I knew, I would tell you, but it's a long time since I used them
myself).

Mike.

--
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/44e777fa-9292-f586-dfea-7913b9da6834%40keehan.net.

Re: [qubes-users] Wifi connected but does not work

[Mike Keehan]

On 2/20/20 9:20 AM, hazon.sass...@gmail.com wrote:

Hi
I have a fresh qubes install on my laptop. The wifi is connected and works on 
other devices but can't ping google and can't open a web page on firefox.
What information do you need me to share to you to be able to help me ?
Thanks



What does "works on other devices" mean?

--
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/a96a02df-d754-91d6-f16b-214fb932edda%40keehan.net.

Re: [qubes-users] How to set the screensaver to either show keyboard language or not to lock screen ?

[Mike Keehan]

On 2/13/20 8:10 PM, A E wrote:
tor. 13. feb. 2020 kl. 18.48 skrev Mike Keehan <mailto:m...@keehan.net>>:




On 2/13/20 5:27 PM, A E wrote:
 > tor. 13. feb. 2020 kl. 11.11 skrev A mailto:anneeyr...@gmail.com>
 > <mailto:anneeyr...@gmail.com <mailto:anneeyr...@gmail.com>>>:
 >
 >     How to set the screensaver to either show keyboard language
or not
 >     to lock screen as default ?
 >
 >     I have tried to set it to not lock the screen by uncheck it
in the
 >     Screensaver settings. But it still continues to lock the screen.
 >
 >     --
 >     You received this message because you are subscribed to a
topic in
 >     the Google Groups "qubes-users" group.
 >     To unsubscribe from this topic, visit
 >
https://groups.google.com/d/topic/qubes-users/uMl6_djER5E/unsubscribe.
 >     To unsubscribe from this group and all its topics, send an
email to
 > qubes-users+unsubscr...@googlegroups.com
<mailto:qubes-users%2bunsubscr...@googlegroups.com>
 >     <mailto:qubes-users%2bunsubscr...@googlegroups.com
<mailto:qubes-users%252bunsubscr...@googlegroups.com>>.
 >     To view this discussion on the web visit
 >

https://groups.google.com/d/msgid/qubes-users/4ba32760-f4ea-4f1f-b92f-588306d2fa5d%40googlegroups.com.
 >
 >
 > Every time the screensaver lock the screen, I need to
reset/restart the
 > pc as I can’t know which keyboard layout is used and that is just a
 > little bit annoying ! 
 >
 > So I hope someone can explain to me how I can get it to show the
 > keyboard layout or not locking the screen.
 >
 > If that isn’t possible, can I then somehow disable or uninstall the
 > screensaver ?
 >

In screensaver preferences, set "Lock screen after" to 0 minutes.


You’re right, I forgot once again that Linux/Qubes OS consist of small 
programs that is made by different other creators.


Setting “lock screen after” 0 minutes just makes the screensaver to lock 
immediately when the screensaver gets activated.


I have wrote to the creator of the screensaver, and he says X11 sucks 
and makes it impossible to get the keyboard layout showed.


So I have to disable the lock.

One option is to set the lockTimeout to a large number so that it won’t 
lock. lockTimeout control have long after a blank screen the lock will 
be activated.


Another solution is to disable or uninstall the program.



Ah, you are right about the "lock after" option.

I've just checked my system, and in the screensaver preferences window,
the Mode can be set to Disable Screen Saver.  I think that is what you
need to do.

Mike.

--
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/e9a70b4f-1322-5202-919b-d05f799b0a6d%40keehan.net.

Re: [qubes-users] Grayscale display settings

[Mike Keehan]

On Sun, 19 Jan 2020 19:46:58 +0100
max.nichtsodringl...@posteo.de wrote:

> Hey there,
> 
> what is the best way to switch my whole display to black and white / 
> grayscale?
> 
> I found this thread: 
> https://askubuntu.com/questions/443335/how-can-ubuntu-be-made-grayscale/443346#443346
> 
> But I'm unsure where to implement this in dom0.
> 
> Thanks!
> 
> Max
> 

Those settings would go in /etc/X11/xorg.conf normally, I seem to remember.
Qubes doesn't have this file in a default setup, but you could try adding one.  

You need to search for X11 configuration settings.

Mike.

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/20200120125841.564e7b35%40keehan.net.

Re: [qubes-users] Fedora kernel for VM

[Mike Keehan]

On Tue, 14 Jan 2020 03:09:48 -0800 (PST)
Asad Manzur  wrote:

> Hi
> I've been searching around but I can't find any documentation on how to
> install fedora vanilla kernel for a VM. Can anyone guide me in the correct
> direction please. I am wanting to use vanilla Fedora kernel so that I can
> run my Intel AX200 WiFi card on my Clevo laptop. Thanks for your help
> 

In Qube Settings, make the default kernel "none".  It will then use the 
kernel in the VM image.

Also, you will need to pass through the network card to the VM.

Best of luck,

   Mike.

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/20200114130255.6dd3fbd8%40keehan.net.

Re: [qubes-users] Fedora kernel for VM

[Mike Keehan]

On Tue, 14 Jan 2020 03:09:48 -0800 (PST)
Asad Manzur  wrote:

> Hi
> I've been searching around but I can't find any documentation on how to
> install fedora vanilla kernel for a VM. Can anyone guide me in the correct
> direction please. I am wanting to use vanilla Fedora kernel so that I can
> run my Intel AX200 WiFi card on my Clevo laptop. Thanks for your help
> 

You also need to set the VM to be HVM for the pci pass-through to 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/20200114130727.2081273b%40keehan.net.