On 6/6/23 23:25, ogio.spam wrote:
Hi all,
there is a documented issue for Virtualbox and new kernels (6.3).
All VMs stuck on starting.
It seems to be a problem related with IBT (enable by default on new
Fedora kernels) that causes the VM to refuse to load.
One reference here: https://www.virtualbox.org/ticket/21435
<https://www.virtualbox.org/ticket/21435>
I'll try to disable IBT at boot and try to use VM's but the question is:
There is already a solution (IBT is there why?) or there is only this
workaround?
IBT is a security thing. If Virtualbox is having a problem with that,
it seems likely that they're doing something that they shouldn't be doing.
But also, the usual question when things like this come up. Why aren't
you using qemu/KVM anyway?
_______________________________________________
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
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
