HP Integrity rx2800 Kernel Debugging Guide - Page 32

The new entry is copied to the bottom of the list and becomes the last entry. Because

Page 32 highlights

1. At the command-line prompt, enter the following command: C:\>bootcfg The current boot configuration appears, as shown in the following example: Boot Options -----------Timeout: 20 Default: \Device\HarddiskDmVolumes\PhysicalDmVolumes\BlockVolume1\WINDOWS CurrentBootEntryID: 1 Boot Entries -----------Boot entry ID: 1 OS Friendly Name: Windows Server 2003, Enterprise OsLoadOptions: /redirect BootFilePath: \Device\HarddiskVolume1\EFI\Microsoft\WINNT50\ia64ldr.efi OsFilePath: \Device\HarddiskDmVolumes\PhysicalDmVolumes\BlockVolume1\WINDOWS Boot entry ID: 2 OS Friendly Name: Internal Bootable DVD Boot entry ID: 3 OS Friendly Name: EFI Shell [Built-in] In this example, you can see that "Boot entry ID 1" is the default Windows boot option. It has only the out-of-band management (EMS or SAC prompt) configured as an option (the "redirect" option). On some systems, the NOVESA option is listed here, too. You must add a couple of options to enable live debugging. Make a copy of the boot entry and then add the options. 2. Make a copy of the default boot entry by issuing the following command: C:\>bootcfg /copy /d "Windows Server 2003, Enterprise with Debugging Enabled" /id 1 The system indicates that it successfully copied boot entry "1." The new entry is copied to the bottom of the list and becomes the last entry. Because the previous example contains only three boot entries, the new boot entry is assigned "ID 4" (remember, this is only an example; if your system has more boot options, your ID number will be higher). 3. Issue the bootcfg command again to see the new boot entry ID 4: C:\>bootcfg The new boot configuration appears: Boot Options -----------Timeout: 20 Default: \Device\HarddiskDmVolumes\PhysicalDmVolumes\BlockVolume1\WINDOWS CurrentBootEntryID: 1 Boot Entries -----------Boot entry ID: 1 32 Debugging the kernel remotely

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37

1.
At the command-line prompt, enter the following command:
C:\>bootcfg
The current boot configuration appears, as shown in the following example:
Boot Options
------------
Timeout: 20
Default:
\Device\HarddiskDmVolumes\PhysicalDmVolumes\BlockVolume1\WINDOWS
CurrentBootEntryID: 1
Boot Entries
------------
Boot entry ID: 1
OS Friendly Name: Windows Server 2003, Enterprise
OsLoadOptions: /redirect
BootFilePath:
\Device\HarddiskVolume1\EFI\Microsoft\WINNT50\ia64ldr.efi
OsFilePath:
\Device\HarddiskDmVolumes\PhysicalDmVolumes\BlockVolume1\WINDOWS
Boot entry ID: 2
OS Friendly Name: Internal Bootable DVD
Boot entry ID: 3
OS Friendly Name: EFI Shell [Built-in]
In this example, you can see that “Boot entry ID 1” is the default Windows boot option. It
has only the out-of-band management (EMS or SAC prompt) configured as an option (the
“redirect” option). On some systems, the
NOVESA
option is listed here, too.
You must add a couple of options to enable live debugging. Make a copy of the boot entry
and then add the options.
2.
Make a copy of the default boot entry by issuing the following command:
C:\>bootcfg /copy /d
Windows Server 2003, Enterprise with Debugging
Enabled
/id 1
The system indicates that it successfully copied boot entry “1.”
The new entry is copied to the bottom of the list and becomes the last entry. Because the
previous example contains only three boot entries, the new boot entry is assigned “ID 4”
(remember, this is only an example; if your system has more boot options, your ID number
will be higher).
3.
Issue the
bootcfg
command again to see the new boot entry ID 4:
C:\>bootcfg
The new boot configuration appears:
Boot Options
------------
Timeout: 20
Default:
\Device\HarddiskDmVolumes\PhysicalDmVolumes\BlockVolume1\WINDOWS
CurrentBootEntryID: 1
Boot Entries
------------
Boot entry ID: 1
32
Debugging the kernel remotely