Custom Query (16363 matches)
Results (304 - 306 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #4704 | wontfix | Should suggest unloading KVM module instead of recompiling kernel | ||
| Description |
When kernel module kvm-intel or kvm-amd is loaded and VirtualBox errors out with VERR_VMX_IN_VMX_ROOT_MODE, it shows help text "Please disable the KVM kernel extension, recompile your kernel and reboot". It should check if kvm-intel/kvm-amd are loaded and instruct to remove that module instead. It is a lot easier than a kernel recompilation. At least Mandriva Linux has been shipping kvm as modules in the default kernels for quite some time now. |
|||
| #20624 | fixed | VirtualBox v6.1.28 shows "Failed to open a session for the virtual machine ... Call to NEMR0InitVMPart2 failed: VERR_NEM_INIT_FAILED (VERR_NEM_VM_CREATE_FAILED). Result Code: E_FAIL (0x80004005) Component: ConsoleWrap Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}" in 64-bit W10... | ||
| Description |
Others and I are seeing this in my detailed https://forums.virtualbox.org/viewtopic.php?f=6&t=104175 forum thread with logs and comments. We had no problems in v6.1.26. VB kept showing this after starting a guest VM: "Failed to open a session for the virtual machine ... Call to NEMR0InitVMPart2 failed: VERR_NEM_INIT_FAILED (VERR_NEM_VM_CREATE_FAILED). Result Code: E_FAIL (0x80004005) Component: ConsoleWrap Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}". They last worked on a couple days ago too in v6.1.26 before upgrading to v6.1.28. I already tried rebooting, repairing, etc. I was forced to downgrade back to v6.1.26. Attached and http://zimage.com/~ant/temp/AntsVirtualBox6.1.zip for my VB settings and logs. Thank you for reading and hopefully answering soon. :) |
|||
| #7996 | obsolete | vbox 3.2.12 causes kernel panic on Hardened Gentoo host | ||
| Description |
Using the latest stable hardened kernel from Gentoo (hardened-sources-2.6.36-r6) starting a virtual machine causes a kernel panic on amd64. The kernel is configured with UDEREF off (as discussed in Ticket #2652), but with KERNEX on. The problem occurs because the vbox code tries to modify read-only kernel pages which it should not do. For the panic, see: http://bugs.gentoo.org/show_bug.cgi?id=350503 |
|||

