Opened 22 months ago
Last modified 21 months ago
#21338 new defect
Kernel Panic Boot2Docker Distro
| Reported by: | goldfita | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox-7.0.4 |
| Keywords: | Cc: | ||
| Guest type: | Linux | Host type: | Windows |
Description
Please see this Vagrant bug report. The comment by phinze suggests this is a VirtualBox issue.
Attachments (1)
Change History (5)
comment:1 by , 22 months ago
by , 21 months ago
| Attachment: | docker-host_default_1669677871377_9677-2022-12-15-18-20-23.log added |
|---|
comment:2 by , 21 months ago
How can I run dmesg? It's crashing at boot. Note that I have been using VirtualBox and Vagrant for a long time without issue. It's just when I try to use docker, I can't get anything to work.
comment:3 by , 21 months ago
Hi goldfita,
Sorry, misread description. So far, nothing catches my eye in the log. You can get guest dmesg by adding "console=ttyS0" to the kernel commandline and then read it on the host side (see https://www.virtualbox.org/wiki/Serial_redirect).
comment:4 by , 21 months ago
While I was trying to figure out the magic keys to get into the boot loader, I found a workaround for my problem: 2 cpus. If you still want to see the dmesg output, I'll need some help with the boot loader. Otherwise, we can close this ticket.


Hi goldfita,
Please attach VBox.log and host
dmesgbefore host kernel panic. Could you please also provide crash dump or kernel backtrace?