<I apologize for the delay in sending this message, apparently my email client ate it>
Please ignore this message if you are not currently running snv_123 and don't plan to upgrade to snv_123. Those who skip nsv_123 and go directly to snv_124 may also ignore. With the integration of PSARC 2009/104 Hot-Plug Support for ACPI-based Systems 6846955 Device tree creation and acpi virtual nexus driver for acpi based x86 systems 6849408 Device matching rule in ppm.conf is not flexible enough into snv_123 on Aug 27, 2009, a workaround may be needed in order to successfully boot a debug kernel on an xvm domain. This workaround is described in the work around field of CR 6879838, which I will copy at the end of this email. With the putback of CR 6879838, a similar workaround may need to be applied to systems which are currently running snv_123. The workaround in this case is to 1) remove all "cpudrv" entries from /etc/path_to_inst 2) run "bootadm update-archive" 3) reboot It is recommended that all users upgrading from snv_123 do this even if they don't plan on running xvm so that things will be cleaned up if they do so in the future. --Mike The workaround for snv_123 is: 1) remove all "cpudrv" entries from /etc/path_to_inst 2) run "bootadm update-archive" 3) reboot going through BIOS with "reboot -p" or a power cycle 4) at the grub menu select the "bare metal" kernel option to edit (hit 'e') 5) add to the end of the "kernel" line "-B acpidev-autoconfig=no" 6) boot the system (hit 'b' at the grub menu) 7) run "bootadm update-archive" 8) reboot the system to the "bare metal" 9) run "bootadm update-archive"
