| 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><ph conkeyref="vbox-conkeyref-phrases/product-name"/> is capable of producing its own core files for extensive
|
|---|
| 8 | debugging when things go wrong. Currently this is only available on Oracle Solaris hosts. </p>
|
|---|
| 9 | <p>The <ph conkeyref="vbox-conkeyref-phrases/product-name"/> CoreDumper can be enabled using the following command: </p>
|
|---|
| 10 | <pre xml:space="preserve">$ VBoxManage setextradata <varname>VM-name</varname> VBoxInternal2/CoreDumpEnabled 1</pre>
|
|---|
| 11 | <p>You can specify which directory to use for core dumps with this command, as follows: </p>
|
|---|
| 12 | <pre xml:space="preserve">$ VBoxManage setextradata <varname>VM-name</varname> VBoxInternal2/CoreDumpDir <varname>path-to-directory</varname>
|
|---|
| 13 | </pre>
|
|---|
| 14 | <p> Ensure the directory you specify is on a volume with sufficient free space and that the <ph
|
|---|
| 15 | conkeyref="vbox-conkeyref-phrases/product-name"/> process has sufficient permissions to write files to this
|
|---|
| 16 | directory. If you skip this command and do not specify any core dump directory, the current directory of the <ph
|
|---|
| 17 | conkeyref="vbox-conkeyref-phrases/product-name"/> executable will be used. This would most likely fail when
|
|---|
| 18 | writing cores as they are protected with root permissions. It is recommended you explicitly set a core dump
|
|---|
| 19 | directory. </p>
|
|---|
| 20 | <p>You must specify when the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> CoreDumper should be triggered.
|
|---|
| 21 | This is done using the following commands: </p>
|
|---|
| 22 | <pre xml:space="preserve">$ VBoxManage setextradata <varname>VM-name</varname> VBoxInternal2/CoreDumpReplaceSystemDump 1
|
|---|
| 23 | $ VBoxManage setextradata <varname>VM-name</varname> VBoxInternal2/CoreDumpLive 1</pre>
|
|---|
| 24 | <p>At least one of the above two commands will have to be provided if you have enabled the <ph
|
|---|
| 25 | conkeyref="vbox-conkeyref-phrases/product-name"/> CoreDumper. </p>
|
|---|
| 26 | <p>Setting <codeph>CoreDumpReplaceSystemDump</codeph> sets up the VM to override the host's core dumping mechanism
|
|---|
| 27 | and in the event of any crash only the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> CoreDumper would
|
|---|
| 28 | produce the core file. </p>
|
|---|
| 29 | <p>Setting <codeph>CoreDumpLive</codeph> sets up the VM to produce cores whenever the VM process receives a
|
|---|
| 30 | <codeph>SIGUSR2</codeph> signal. After producing the core file, the VM will not be terminated and will continue
|
|---|
| 31 | to run. You can thus take cores of the VM process using the following command: </p>
|
|---|
| 32 | <pre xml:space="preserve">$ kill -s SIGUSR2 <varname>VM-process-id</varname>
|
|---|
| 33 | </pre>
|
|---|
| 34 | <p>The <ph conkeyref="vbox-conkeyref-phrases/product-name"/> CoreDumper creates core files of the form
|
|---|
| 35 | <filepath>core.vb.<varname>process-name</varname>.<varname>process-ID</varname>
|
|---|
| 36 | </filepath> such as <filepath>core.vb.VBoxHeadless.11321</filepath>. </p>
|
|---|
| 37 | </body>
|
|---|
| 38 |
|
|---|
| 39 | </topic>
|
|---|
