On 6/12/20 8:42 PM, Stephen Morris wrote:
The origonal reason for this thread was the issue with DMESG seeming
to indicate a possible hardware issue on what looked to be core 7, or
whether is was just that the monitoring process couldn't access the
core at the time.
Right. Everything in this branch of the thread is irrelevant to your
question. I just hoped to point out to Patrick that pinning a guest to
a set of CPUs does not reserve those CPUs for the guest's exclusive use
on Linux, as he suggested.
I still think that the log you posted most likely indicates that Windows
simply didn't schedule VirtualBox for too long.
https://www.kernel.org/doc/Documentation/RCU/stallwarn.txt
The stall detector documentation mentions the "starved for" text from
the log you posted in a section describing "Anything that prevents RCU's
grace-period kthreads from running". I'd think that would include the
hypervisor not running the guest.
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
