| 1 | <?xml version='1.0' encoding='UTF-8'?>
|
|---|
| 2 | <!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
|
|---|
| 3 | <topic xml:lang="en-us" id="solariscodedumper">
|
|---|
| 4 | <title>Configuring the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> CoreDumper on Oracle Solaris Hosts</title>
|
|---|
| 5 |
|
|---|
| 6 | <body>
|
|---|
| 7 | <p>
|
|---|
| 8 | <ph conkeyref="vbox-conkeyref-phrases/product-name"/> is capable of producing its own core files for
|
|---|
| 9 | extensive debugging when things go wrong. Currently this is only
|
|---|
| 10 | available on Oracle Solaris hosts.
|
|---|
| 11 | </p>
|
|---|
| 12 | <p>
|
|---|
| 13 | The <ph conkeyref="vbox-conkeyref-phrases/product-name"/> CoreDumper can be enabled using the following
|
|---|
| 14 | command:
|
|---|
| 15 | </p>
|
|---|
| 16 | <pre xml:space="preserve">$ VBoxManage setextradata <varname>VM-name</varname> VBoxInternal2/CoreDumpEnabled 1</pre>
|
|---|
| 17 | <p>
|
|---|
| 18 | You can specify which directory to use for core dumps with this
|
|---|
| 19 | command, as follows:
|
|---|
| 20 | </p>
|
|---|
| 21 | <pre xml:space="preserve">$ VBoxManage setextradata <varname>VM-name</varname> VBoxInternal2/CoreDumpDir <varname>path-to-directory</varname>
|
|---|
| 22 | </pre>
|
|---|
| 23 | <p>
|
|---|
| 24 | Make sure the directory you specify is on a volume with sufficient
|
|---|
| 25 | free space and that the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> process has sufficient
|
|---|
| 26 | permissions to write files to this directory. If you skip this
|
|---|
| 27 | command and do not specify any core dump directory, the current
|
|---|
| 28 | directory of the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> executable will be used. This
|
|---|
| 29 | would most likely fail when writing cores as they are protected
|
|---|
| 30 | with root permissions. It is recommended you explicitly set a core
|
|---|
| 31 | dump directory.
|
|---|
| 32 | </p>
|
|---|
| 33 | <p>
|
|---|
| 34 | You must specify when the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> CoreDumper should be
|
|---|
| 35 | triggered. This is done using the following commands:
|
|---|
| 36 | </p>
|
|---|
| 37 | <pre xml:space="preserve">$ VBoxManage setextradata <varname>VM-name</varname> VBoxInternal2/CoreDumpReplaceSystemDump 1
|
|---|
| 38 | $ VBoxManage setextradata <varname>VM-name</varname> VBoxInternal2/CoreDumpLive 1</pre>
|
|---|
| 39 | <p>
|
|---|
| 40 | At least one of the above two commands will have to be provided if
|
|---|
| 41 | you have enabled the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> CoreDumper.
|
|---|
| 42 | </p>
|
|---|
| 43 | <p>
|
|---|
| 44 | Setting <codeph>CoreDumpReplaceSystemDump</codeph> sets up the
|
|---|
| 45 | VM to override the host's core dumping mechanism and in the event
|
|---|
| 46 | of any crash only the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> CoreDumper would produce the
|
|---|
| 47 | core file.
|
|---|
| 48 | </p>
|
|---|
| 49 | <p>
|
|---|
| 50 | Setting <codeph>CoreDumpLive</codeph> sets up the VM to produce
|
|---|
| 51 | cores whenever the VM process receives a
|
|---|
| 52 | <codeph>SIGUSR2</codeph> signal. After producing the core file,
|
|---|
| 53 | the VM will not be terminated and will continue to run. You can
|
|---|
| 54 | thus take cores of the VM process using the following command:
|
|---|
| 55 | </p>
|
|---|
| 56 | <pre xml:space="preserve">$ kill -s SIGUSR2 <varname>VM-process-id</varname>
|
|---|
| 57 | </pre>
|
|---|
| 58 | <p>
|
|---|
| 59 | The <ph conkeyref="vbox-conkeyref-phrases/product-name"/> CoreDumper creates core files of the form
|
|---|
| 60 | <filepath>core.vb.<varname>process-name</varname>.<varname>process-ID</varname>
|
|---|
| 61 | </filepath>
|
|---|
| 62 | such as <filepath>core.vb.VBoxHeadless.11321</filepath>.
|
|---|
| 63 | </p>
|
|---|
| 64 | </body>
|
|---|
| 65 |
|
|---|
| 66 | </topic>
|
|---|
