Denied whoinix.NewStatus+status dislayed when starting/creating VM

User Support
1

After recently updating my whonix related templates today I started getting “Denied whoinix.NewStatus+status from (vm name) to Sys-Whonix” error even with vms that aren’t configured to use it.
All tor works and all with its associated qubes.

This is what I have read in relation so far:

However all read is quite a few years ago and on previous versions of Qubes and seem to have been resolved and in my case it isn’t in any relations to shutdowns or nor do I have additional vms setup besides from the default provided by Qubes to connect to Tor.
Ultimately I not made any adjustments unlike some other cases presented and have never had this issue prior updating my templates today.

The fixes in the articles indicate whitelisting individual vms or newly configured network vms for Tor, however I cannot find any in relation to when any vm starts up and starts its first application as then a second denied error would diplay again.

Anyone experiencing the same?

2

What’s your (vm name) template?
Check the features of this qube’s template in dom0:

qvm-features vm-name-template | grep NewStatus
3

Apologies,

By vm name I meant the name of the vm as it will display this with all my vms.
Regarding templates it will do this with vms created from any template(kicksecure-17, debian-12, fedora-40, kali-core), not specific to whonix(but with the whonix template as well i.e the whoinix-workstation-17-dvm)

4

Check the output of this command in dom0 teminal:

qvm-features debian-12 | grep NewStatus

Then create new mytest app qube based on a debian-12 template and start it. Will you see the notification about it?

Denied whonix.NewStatus from mytest to sys-whonix

If it’s a kicksecure template then it’s this issue:

5

Still getting the same issues with the mytest template you requested I make.
Also notice while having the vm up for a while or while watching a video it starts spamming the notification.
Am getting this with all my templates that I mentioned above and regarding Kicksecure, I have been using it for 2 months now and this is the first time this issue has been occurring as mentioned.

So to clarify this is occurring whenever I startup a vm, when I startup the first application within a vm and then starts spamming when the vm is running for a long duration and when playing a video, such as from Youtube, or streaming site.

However it does seem for the most part the article helped by changing the policy for the default to allow.
I do find that this is only occurring now after so long odd tho.

Much appreciated with the , help and hopefully after a full system restart I wont get this issue with my other templates. Time to go and learn the entirety of Salt as it seems to be a Despicable ME run off :joy:

6

Run this command in the qube that is having this issue:

sudo grep -Flr "whonix.NewStatus" /etc /usr /rw

This will show you where these notifications are coming from.
Maybe you have sdwdate installed in all of your templates for some reason.

7

Will do. Shot