[qubes-users] Fedora 28 has no audio on Qubes!

Hi Everyone, I've just updated my template to Fedora 28 and although everything is working fine. It seems that sound is not working by any means (each VM based on Fedora 28 is not even listed in the volume control). In all the previous versions of Fedora this was working fine. Having a appvm

[qubes-users] Wireguard not working on fedora-29

Hi, I'm trying to use wireguard but it fails due to the lack of the kernel-devel source files in the qubes-kernel-vm. So I've tried to use the default kernel that is shipped with fedora-29 but it fails to boot with HVM support. I've managed to install it successfully however on debian-9, it

Re: [qubes-users] Wireguard not working on fedora-29

I saw this issue. But unfortunately the latest-kernel-vm (5.1.2-1) doesn't contain the modules for wireguard. So the problem still remains. When I use the debian-9 template on the sys-vpn the other appvms are not able to resolve any records, only the sys-vpn. Any ideas? June 8, 2019 5:48

[qubes-users] Wireguard randomly hangs when the request is originated from a different AppVM

Hi, I'm having random issues while on wireguard where request to some sites simply stalls until it times out. If I reload the pages often enough I will finally able to get the response, although this happens randomly, currently I'm able to reproduce this issue in ever few requests. When the

Re: [qubes-users] Wireguard not working on fedora-29

Thanks Chris. I've solved this differently. I'm using the PostUp/PostDown script to set the DNAT rules through a script that I've made, which also sets the resolv.conf properly since the resolvconf daemon is not working as it should. Thank you! June 8, 2019 9:24 PM, "Chris Laprise"

[qubes-users] Re: Wireguard randomly hangs when the request is originated from a different AppVM

Well after some more troubleshooting I found the root cause. It seems to be related with the MTU. Wireguard by default sets its vif with a MTU of 1420 while the other AppVms are using a default MTU of 1500 which causes the hanging and stall in the connection request. When I set the interfaces

[qubes-users] How can I restore a template from a backup?

Hello, I've done a fresh install of Qubes and I'm trying to restore the debian-9 & fedora-29 templates from a backup, but I'm not able to do it since the templates were installed by the package manager. Is is possible to restore the templates from a backup or this is only applicable to the

[qubes-users] Does anyone managed to have wireguard working on Fedora 29?

Hello, I'm able to get wireguard working over debian when using a HVM AppVM. However I'd like to do use wireguard on the fedora template in a PVH template. This issue (https://github.com/QubesOS/qubes-issues/issues/3591) that was closed marmarek states that the kernel-latest-(qubes-vm) contains

Re: [qubes-users] Does anyone managed to have wireguard working on Fedora 29?

Thanks the package is now successfully installed! Now I changed the kernel of my sys-firewall to point to the new kernel - 5.2.3-1 and tried to start the AppVM. However the sys-firewall is started fine but qrexec fails and throws an error that it cannot communicate with the sys-firewall so I'm

Re: [qubes-users] Does anyone managed to have wireguard working on Fedora 29?

Thanks. However the latest kernel package is not being installed: [xx@dom0 ~]$ sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing kernel-latest-qubes-vm Using sys-firewall as UpdateVM to download updates for Dom0; this may take some time... Last metadata expiration check: 0:03:24

Re: [qubes-users] Does anyone managed to have wireguard working on Fedora 29?

The 5.1.15-1 was deleted with the --action=upgrade Is there a way to reinstall the package again? July 28, 2019 2:49 PM, dhorf-hfref.4a288...@hashmail.org wrote: > On Sun, Jul 28, 2019 at 12:34:25PM +, mmo...@disroot.org wrote: > >> Thanks the package is now successfully installed! > >

Re: [qubes-users] Does anyone managed to have wireguard working on Fedora 29?

It worked with the 5.1.15-1 ! Many thanks! July 28, 2019 3:19 PM, mmo...@disroot.org wrote: > The 5.1.15-1 was deleted with the --action=upgrade > Is there a way to reinstall the package again? > > July 28, 2019 2:49 PM, dhorf-hfref.4a288...@hashmail.org wrote: > >> On Sun, Jul 28, 2019 at

Re: [qubes-users] Does anyone managed to have wireguard working on Fedora 29?

>1) don't "top post" > >2) in dom0 do uname -a does it say kernel 4.19 , if so you don't > need "the wg package" > >3) do a little search for "tasket vpn qubes github" and try his > script per instructions > > then report back I'm using kernel 4.19.43-1 so where can I find the wg

[qubes-users] Lenovo T480/T480s anyone got power management working properly?

Hello, I'm struggling to get my T480s working on resume as it displays a blank screen that doesn't allow me to do anything. All problematic modules are already part of the suspend blacklist: ehci_pci xhci_pci iwldvm iwlmvm Nonetheless the resume only works when I shutdown the sys-usb before

[qubes-users] Re: Resume issues with Qubes

Thanks for the reply. I do have a few devices attached to the sys-usb, and this worked well in the past. Only recently I started to see some AppVMS being randomly halted and due to the lack of logs I cannot isolate the issue. I'm experience this quite often, almost on every resume now. Given

[qubes-users] Resume issues with Qubes

Hi, Recently, around a month ago, I start to experience some issues with Qubes on my T480(s) possibly due to some sort of update, since I haven't got these issues before. All issues are related witrh the resume on suspend. The resume never worked with the sys-usb since day one, so I had to

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

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

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

Problem still occurs even after memory balancing has been disabled. On random resumes: [37968.267047] audit: type=1104 audit(1581552250.086:231): pid=13012 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_rootok acct="root" exe="/usr/lib/qubes/qrexec-agent" hostname=?

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

Are you suggesting to disable the memory balancing? I can do that and see if it solves anything.. -- 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

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

It was a typo sorry about that. I'm now replying to the list. I'm using fedora 30 and debian 9, both templates and AppVMS uses pvh virtualization. I have nothing fancy on my setup, this is what it comes out of the box. Do you have any idea Mike about what might be originating this? Thanks!

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

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

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

Many thanks for the suggestion! I'm not using any proprietary modules of any sort, below are the only modules that I are loaded in the AppVM that was killed (as you can see nothing really special): Module Size Used by fuse 126976 3 ip6table_filter 16384 1 ip6_tables 32768 1 ip6table_filter

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

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"

[qubes-users] Re: Fedora 32: dnf update fails

Just checked it dnf update succeeds in an AppVM (using the same templatevm ) without using the tinyproxy. So guess this is probably due to tinyproxy?? March 22, 2021 2:00 PM, mmo...@disroot.org (mailto:mmo...@disroot.org) wrote: Forgot to add the repository config: [updates] name=Fedora

[qubes-users] Fedora 32: dnf update fails

Hello, The update on my fedora 32 template VM fails with a 404 on any source in the update repo. Currently I'm not able to install any package on my template. Can someone advice? Thanks. Below is the output: [root@fedora-32 yum.repos.d]# dnf update --refresh Fedora 32 openh264 (From Cisco) -

[qubes-users] Re: Fedora 32: dnf update fails

Well, run dnf again and without doing anything this time it worked. Have no idea what went wrong but the issue was solved. Thanks everyone! March 22, 2021 2:11 PM, mmo...@disroot.org (mailto:mmo...@disroot.org) wrote: Just checked it dnf update succeeds in an AppVM (using the same templatevm )