Dear Maintainer,

while using the a virtual machine it shutdown.

[ 3496.073809] kauditd_printk_skb: 4 callbacks suppressed
[ 3496.073812] audit: type=1400 audit(1746563968.184:209): apparmor="DENIED"
operation="mknod" class="file" profile="libvirt-c4ceefe8-352a-47cc-
aef0-502667220ffe" name="/core.70856" pid=70856 comm=535049434520576F726B6572
requested_mask="c" denied_mask="c" fsuid=64055 ouid=64055
[ 3496.075034] virbr0: port 1(vnet2) entered disabled state
[ 3496.075315] vnet2 (unregistering): left allmulticast mode
[ 3496.075321] vnet2 (unregistering): left promiscuous mode
[ 3496.075324] virbr0: port 1(vnet2) entered disabled state
[ 3497.050449] audit: type=1400 audit(1746563969.160:210): apparmor="STATUS"
operation="profile_remove" profile="unconfined"
name="libvirt-c4ceefe8-352a-47cc-aef0-502667220ffe" pid=102174
comm="apparmor_parser"

reassign 1104817 qemu-system
thanks

Hello,

AFAIKS, this has nothing todo with the audit package

Looks like qemu is crashing(?) and libvirt apparmor profile is not
allowing to write the core file.

I'm reassigning to qemu package

Kind regards,

Laurent Bigonville

Le 6/05/25 à 22:51, Nicola a écrit :

Control: severity -1 normal
Control: tag -1 + moreinfo
So. This is something crashing (maybe qemu? I dunno, there's no
indication of what is crashing), and an apparmor profile denying
to write a core file.

Please find out what is crashing and how to reproduce the crash.

Thanks,

/mjt

There's no information in this bug report besides the fact that
something tried to write a core file.  Not even an indication this
was qemu which crashed, no version, no nothing, and apparently the
OP does not respond to inquires.

Closing this bug report.  Please feel free to reopen it if you think
it is incorrect.

Thanks,

/mjt