#14893 closed defect (invalid)
Fails during boot
| Reported by: | MikhailRokhin | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 5.0.10 |
| Keywords: | Cc: | ||
| Guest type: | BSD | Host type: | Windows |
Description
Attachments (3)
Change History (10)
by , 9 years ago
by , 9 years ago
by , 9 years ago
| Attachment: | VBoxHardening.log added |
|---|
comment:1 by , 9 years ago
comment:3 by , 9 years ago
Replying to frank:
Actually did you check if the guest boots on real hardware?
VirtualBox fails during it's boot. It's FBSD-11-current-i386. Have a debugging try, please. It's abnormal that VirtualBox itself fails.
To repeat, compile kernel with: options KSTACK_PAGES=64 options KVA_PAGES=1024
It would be normal, if kernel failed within the VB, keeping VB alive, but it crashes VB. Hopefully VB will be isolated from running guests totally.)
Thank you for developing VB.
follow-up: 5 comment:4 by , 9 years ago
You didn't answer my question.
The guest triple faults. That means, the guest does the same what the software would do on real hardware to reset the system if there are no other options. VirtualBox is just so convenient to display a message box and allow to attach a debugger.
follow-up: 6 comment:5 by , 9 years ago
Replying to frank:
You didn't answer my question.
The guest triple faults. That means, the guest does the same what the software would do on real hardware to reset the system if there are no other options. VirtualBox is just so convenient to display a message box and allow to attach a debugger.
For e.g., VMWare behaves normally - mentioned kernel fails within the VMWare machine and the message about it appears, but the VMWare machine doesn't fail itself nor crash. That's the only thing I meant - VirtualBox machine should stand still like hardware whatever software ran within it fails or not.
Thank you.
follow-up: 7 comment:6 by , 9 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
Replying to MikhailRokhin:
Replying to frank:
You didn't answer my question.
The guest triple faults. That means, the guest does the same what the software would do on real hardware to reset the system if there are no other options. VirtualBox is just so convenient to display a message box and allow to attach a debugger.
For e.g., VMWare behaves normally - mentioned kernel fails within the VMWare machine and the message about it appears, but the VMWare machine doesn't fail itself nor crash. That's the only thing I meant - VirtualBox machine should stand still like hardware whatever software ran within it fails or not.
I don't understand. If the guest kernel fails and prints a panic, what else should the VMM do than showing a message that the guest triple-faulted? Again, a real PC would reboot immediately preventing any diagnostic.
comment:7 by , 7 years ago
Replying to frank:
Replying to MikhailRokhin:
Replying to frank:
You didn't answer my question.
The guest triple faults. That means, the guest does the same what the software would do on real hardware to reset the system if there are no other options. VirtualBox is just so convenient to display a message box and allow to attach a debugger.
For e.g., VMWare behaves normally - mentioned kernel fails within the VMWare machine and the message about it appears, but the VMWare machine doesn't fail itself nor crash. That's the only thing I meant - VirtualBox machine should stand still like hardware whatever software ran within it fails or not.
I don't understand. If the guest kernel fails and prints a panic, what else should the VMM do than showing a message that the guest triple-faulted? Again, a real PC would reboot immediately preventing any diagnostic.
Disagree with you - real PC would hang. Again, whatever guest failure is, it can't crash VMM itself, when VMM is isolated totally from running guest - VMM may show anything of results of guest failure: either reboot, or hang/halt.
In 5.1.26 version of VB this issue has gone. Thank you for developing VB.
Is this a FreeBSD guest? Which version? Or can you even point to an .iso file?