Bug#1093849: Probably QEMU crashed

2025-04-27 Thread Roland Clobus

Hello Chris,

On 27/04/2025 13:27, Chris Hofstaedtler wrote:

* Chris Hofstaedtler  [250418 15:18]:

* Roland Clobus  [250418 09:03]:

in the log with QEMU-issues, I saw this line:
`dmesg: read kernel buffer failed: Operation not permitted`

[..]
I've changed the sysctl now, and hope this is enough to make it work. 
We'll see in the next few days.


Unfortunately dmesg access appears to be restricted by docker too.

I still get this in the log:

| dmesg: read kernel buffer failed: Operation not permitted

Not sure how to work around that. Any ideas?


I've logged a similar bug report upstream about the OOM detection:
https://github.com/os-autoinst/os-autoinst/issues/2672

If you change the script 'check_qemu_oom' to use journalctl instead of 
dmesg (and add the worker to the group, as mentioned in the bug report),

would you then be able to get a better output?

With kind regards,
Roland Clobus


OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1093849: Probably QEMU crashed

2025-04-27 Thread Chris Hofstaedtler

* Chris Hofstaedtler  [250418 15:18]:

* Roland Clobus  [250418 09:03]:

in the log with QEMU-issues, I saw this line:
`dmesg: read kernel buffer failed: Operation not permitted`

[..]
I've changed the sysctl now, and hope this is enough to make it work. 
We'll see in the next few days.


Unfortunately dmesg access appears to be restricted by docker too.

I still get this in the log:

| dmesg: read kernel buffer failed: Operation not permitted

Not sure how to work around that. Any ideas?

Chris



Bug#1093849: Probably QEMU crashed

2025-04-18 Thread Chris Hofstaedtler

Hello Roland,

* Roland Clobus  [250418 09:03]:

in the log with QEMU-issues, I saw this line:
`dmesg: read kernel buffer failed: Operation not permitted`

That is caused by the script 'check_qemu_oom', which calls 'dmesg'.
On a regular system, 'dmesg' is not accessible for normal users,
which I reported upstream [1].

Could you try to allow the isotovideo user to access dmesg, and see 
whether you get an out-of-memory message for QEMU?


I've changed the sysctl now, and hope this is enough to make it 
work. We'll see in the next few days.


Thanks,
Chris



Bug#1093849: Probably QEMU crashed

2025-04-18 Thread Roland Clobus

Hello Chris,

in the log with QEMU-issues, I saw this line:
`dmesg: read kernel buffer failed: Operation not permitted`

That is caused by the script 'check_qemu_oom', which calls 'dmesg'.
On a regular system, 'dmesg' is not accessible for normal users,
which I reported upstream [1].

Could you try to allow the isotovideo user to access dmesg, and see 
whether you get an out-of-memory message for QEMU?


With kind regards,
Roland Clobus

[1] https://github.com/os-autoinst/os-autoinst/issues/2672


OpenPGP_signature.asc
Description: OpenPGP digital signature