So I've been having issues with my VirtualBox for about a month now after installing the newest version. I've been trying some things to troubleshoot it, but don't know what I should try.
I would like to use Manjaro plasma, but I've tried a few different distros of linux and I seem to have crashing issues with most of the ones I tried. (ubuntu 20.04 LTS, Linux Mint 20, and Debian 10)
Host:
Windows 10 Home
GA-AX370-Gaming K5 (newest bios driver F50d) I also have SVM turned on for virtualization support.
AMD Ryzen 7 1700X Eight-Core
Corsair Vengeance LPX 16GB RAM
Samsung 960 EVO M.2 SSD
EVGA GeForce RTX 2060 XC
Here's the steps I follow that cause my issue.
1. Clean install of VirtualBox
2. Add new Linux Arch VM
3. Give 4096MB of ram
4. Create Dynamically allocated 32GB VDI drive
5. Set 4 processors
6. Change CD to manjaro-kde-20.1.2-201019-linux58.iso
7. Set VDI to SSD
8. Start VM
9. Select startup disk as the default
10. Select boot Manjaro.x86_64
It will start the boot and after a couple seconds it will crash. I'll post an image tomorrow of the screen I get(forum limit I need to be a member for a day before I can post links), but here is some of what it says at the end.
I had to type this out so hopefully I didn't mess anything up.
-------------------------------------------------------------------------------------------------------------------------------------
Modules linked in: rapl(+) uinput sg crypto_user drm ip_tables x_tables overlay squashfs isofs hid_generic usbhid hid sr_mod cdrom at_generic pata_acpi serio_raw atkbd libps2 ohci_pci crc32c_intel i8042 ehci_pci ehci_hcd intel_agp intel_gtt serio vboxguest e1000 agpgart ohci_hcd ata_piix dm_snapshot dm_bufio dm_mod loop
---[ end trace 8879c8d4e970e46e ]---
RIP: 0010:error_entry+0x1b/0xf0
Code: ba ee 3f 41 0f 22 de e9 3a fd ff ff 0f 1f 00 fc 56 48 8b 74 24 08 48 89 7c 24 08 52 51 50 41 50 41 50 41 51 41 52 41 53 53 55 41 54 <41> 55 41 56 41 57 56 31 d2 31 c9 45 31 c0 45 31 c9 45 31 d2 45 31
RSP: 0018:ffff96dcc0ad0000 EFLAGS: 00010087
RAX: 0000000000017bc0 RBX: 0000000000000000 RCX: ffffffffaac00fc7
RDX: 0000000000000000 RSI: ffffffffaac00ac8 RDI: ffff96dcc0ad00c8
RBP: ffff96dcc0ad00c8 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
FS: 00007f21d4584440(0000) GS:ffff8f011bc80000(0000) knlG:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffff96dcc0acfff8 CR3 000000001145f4000 CR4: 00000000000006e0
Kernel panic - not syncing: Fatal exception in interrupt
Kernel Offset: 0x29000000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)
-------------------------------------------------------------------------------------------------------------------------------------
I've tried everything I can think of. What can I try to do to troubleshoot this? I'm at a loss as to what the issue could be. Thanks for any help.
Kernel panic - not syncing after updating to Virtualbox 6.1.16
Kernel panic - not syncing after updating to Virtualbox 6.1.16
- Attachments
-
- Jaro-2020-11-02-10-05-18.zip
- Log file
- (32.82 KiB) Downloaded 44 times
-
scottgus1
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Windows, Linux
Re: Kernel panic - not syncing after updating to Virtualbox 6.1.16
Images should be cropped and resized to get under the forum's 128kB size limit, then posted using the forum's Upload Attachment tab. This is possible from first day first post. Forum gurus won't go to 3rd-party sites for images or logs that can be zipped and posted using the forum's Upload Attachment tab.jayA wrote:I'll post an image tomorrow of the screen I get(forum limit I need to be a member for a day before I can post links)
Hyper-V is enabled. See HMR3Init: Attempting fall back to NEM (Hyper-V is active)
Also:
More processors can hurt a guest's speed due to extra scheduling oversight on the host. Don't add processors beyond two until you have multi-processor programs installed in the guest OS that can use extra processors.jayA wrote:5. Set 4 2 processors
Re: Kernel panic - not syncing after updating to Virtualbox 6.1.16
Thank you very much for your quick reply.
I have set the processors to 2.
This did not correct my issue however I will look into Hyper-V and see if that will.
I have attached the error image.Images should be cropped and resized to get under the forum's 128kB size limit, then posted using the forum's Upload Attachment tab. This is possible from first day first post. Forum gurus won't go to 3rd-party sites for images or logs that can be zipped and posted using the forum's Upload Attachment tab.
I have set the processors to 2.
This did not correct my issue however I will look into Hyper-V and see if that will.
- Attachments
-
- Error image
- error.png (57.39 KiB) Viewed 13408 times
Re: Kernel panic - not syncing after updating to Virtualbox 6.1.16
I followed the instructions at this link and it corrected my issue. Thanks again.Hyper-V is enabled. See HMR3Init: Attempting fall back to NEM (Hyper-V is active)
-
scottgus1
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Windows, Linux
Re: Kernel panic - not syncing after updating to Virtualbox 6.1.16
Great! Glad you're up and running.