I recently came across a Solaris 10 guest domain in a hung state.
I accessed its console from the primary domain but I was not able to see a login prompt or anything for that matter.
I was able to ping the server but unable to login to it via ssh.
Hence we decided to reboot the guest domain but we wanted to make sure that a crash dump was generated which could be shared with Oracle support for further analysis.
We decided to induce a kernel panic in the guest domain to ensure the generation of a crash dump on system restart.
The command used to accomplish this is ldm panic-domain.
[sahil@primary-domain-p:~] $ sudo ldm panic-domain test-domain-g
[sahil@primary-domain-p:~] $ sudo ldm list test-domain-g
NAME STATE FLAGS CONS VCPU MEMORY UTIL NORM UPTIME
test-domain-g active -t---- 5002 64 158G 100% 100% 157d 1h
[sahil@primary-domain-p:~] $ sudo console test-domain-g
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
Connecting to console "test-domain-g" in group "test-domain-g" ....
Press ~? for control options ..
6:21 100% done
100% done: 1523171 pages dumped, dump succeeded
rebooting...
Resetting...
NOTICE: Entering OpenBoot.
NOTICE: Fetching Guest MD from HV.
NOTICE: Starting additional cpus.
NOTICE: Initializing LDC services.
NOTICE: Probing PCI devices.
NOTICE: Finished PCI probing.
I accessed its console from the primary domain but I was not able to see a login prompt or anything for that matter.
I was able to ping the server but unable to login to it via ssh.
Hence we decided to reboot the guest domain but we wanted to make sure that a crash dump was generated which could be shared with Oracle support for further analysis.
We decided to induce a kernel panic in the guest domain to ensure the generation of a crash dump on system restart.
The command used to accomplish this is ldm panic-domain.
[sahil@primary-domain-p:~] $ sudo ldm panic-domain test-domain-g
[sahil@primary-domain-p:~] $ sudo ldm list test-domain-g
NAME STATE FLAGS CONS VCPU MEMORY UTIL NORM UPTIME
test-domain-g active -t---- 5002 64 158G 100% 100% 157d 1h
[sahil@primary-domain-p:~] $ sudo console test-domain-g
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
Connecting to console "test-domain-g" in group "test-domain-g" ....
Press ~? for control options ..
6:21 100% done
100% done: 1523171 pages dumped, dump succeeded
rebooting...
Resetting...
NOTICE: Entering OpenBoot.
NOTICE: Fetching Guest MD from HV.
NOTICE: Starting additional cpus.
NOTICE: Initializing LDC services.
NOTICE: Probing PCI devices.
NOTICE: Finished PCI probing.
The ldm panic-domain command ensured that a crash dump was generated when the guest domain underwent a reboot.
I hope this quick tip was helpful.
Hi Shail,
ReplyDeleteThanks for highlighting this and indicating about How to panic a guest domain in Solaris where more study and thought is necessary.
I hear browser security should be taken seriously, which top extensions/add-on's do you guys use/recommend to make Firefox really safe when I am browsing, I am using Linux mint on my acer laptop to browse and email.
All UNIX files have its description stored in a structure called ‘inode’. The inode contains info about the file-size, its location, time of last access, time of last modification, permission and so on. Directories are also represented as files and have an associated inode.
Great effort, I wish I saw it earlier. Would have saved my day :)
Thanks and Regards,
Kevin