After starting Bochs either from the command prompt or the OS shell, the following steps are done before the simulation is running.
parse command line (except bochsrc options)
parse remaining command line options (bochsrc syntax)
initialize configuration interface
enter start menu / dialog (unless quick start mode is enabled)
initialize all parts of the simulator
enter debugger prompt / dialog (if present)
enter the simulation loop
During simulation, Bochs usually generates more or less log output. By default it is sent to the console, otherwise to the specified log file. The amount of output can be controlled with the log options in bochsrc, the start menu and the runtime configuration.
Under certain conditions Bochs can cause a panic and usually asks the user what to do. If such a panic happens during startup, it is mostly a configuration or permission problem and we recommend to quit Bochs and to review the bochsrc options used.
To quit the simulation, the "power" button in the Bochs headerbar should be used, unless the guest OS has the capability to turn off the computer (APM or ACPI).
If a Bochs runtime issue cannot be fixed by configuration changes and it has not yet been reported in the bochs-developers mailing list or the SF trackers for Bochs, it should be reported in the mailing list or the SF bug tracker for the Bochs project.
The following table shows the arguments that can be used on the command line. For other arguments, see section bochsrc.
Table 5-1. command line arguments
|-q||quick start (skip configuration interface)|
|-f filename||specify configuration file|
|-log filename||specify Bochs log file|
|-dbglog filename||specify Bochs internal debugger log file|
|-n||don't try to load a configuration file|
|-r path||specify path for restoring state|
|-noconsole||disable console window (Windows only)|
|--help||display help message and exit|
|--help features||display available features / devices and exit|
|--help cpu||display supported CPU models and exit (CPU level > 4 only)|
These arguments are handled directly after starting Bochs. The next step is to load a default or specified configuration file (unless disabled with -n). Then the rest of the command line (bochsrc options) is parsed. This is done after reading the configuration file so that the command line arguments can override the settings from the file.