I think this is an artifact of a manual setup. Ordinarily, if
booting from a zfs root pool, grub wouldn't even be able
to read the menu.lst if it couldn't interpret the pool format.
I'm not sure what the entire sequence of events is here,
so I'm not sure if there's a bug. Perhaps you could
Upon further thought, it was probably just defaulting to the first
thing grub could boot -- my laptop is partitioned (in order) xp,
recovery partition, solaris. The grub menu though lists the options
in order of solaris b62 (zfs /), solaris b74 (also zfs /), recovery
partition, windows. So my
Apparently with zfs boot, if the zpool is a version grub doesn't
recognize, it merely ignores any zfs entries in menu.lst, and
apparently instead boots the first entry it thinks it can boot. I ran
into this myself due to some boneheaded mistakes while doing a very
manual zfs / install at the