Hi,
interesting report.
The virtualization component here is just participating to then push numad over
the cliff into the crash.
The issue is in numad.
Can you isolate what happens to the config and interactions with numad
to crash it without something complex as avocado to run against the
system?
If not, can you provide the core dump of numad so that one might see
where the crash happened?
** Also affects: numad (Ubuntu)
Importance: Undecided
Status: New
** Changed in: qemu (Ubuntu)
Status: New => Invalid
** Changed in: numad (Ubuntu)
Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage
(ubuntu-power-triage)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2139262
Title:
[Ubuntu26.04] [FW1110] : vm fails to start with memory hot plug ,error
:operation failed: Failed to query numad for the advisory nodeset
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/numad/+bug/2139262/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
