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=?
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
Perhaps due to memory balancing being temporarily unable to service all AppVMs
upon dom0 wake?
--
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
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!
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
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"
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
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
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
