Wow. It worked. I am in awe. As you said, trial and error.
BUT, if we want more people to at least experiment with it, we need to make it easy for them. This has *got* to be documented on the wiki - "how to multiboot into smartos from grub2" I probably even could do this straight from a loopback ISO. Thanks Nahum! תודה רבה לך! Avi On Wed, Dec 2, 2015 at 9:01 PM, Nahum Shalman <[email protected]> wrote: > It's possible that the boot archive needs a describing path as well. And > you could give it the extra flags too. > This is all a trial and error problem that I can't experiment with since I > don't have a system with grub2 at hand to do the testing. > > insmod multiboot > set root='hd0,gpt14' > multiboot /platform/i86pc/kernel/amd64/unix > /platform/i86pc/kernel/amd64/unix -B smartos=true > module /platform/i86pc/amd64/boot_archive > /platform/i86pc/amd64/boot_archive type=rootfs name=ramdisk > > > On 12/02/2015 01:10 PM, Avi Deitcher wrote: > > I get basically the same error, but with '-B' inserted: > > krtld: failed to open '-B' > krtld: bind_primary(): no relocation information found for module -B > krtld: error during initial load/link phase > krtld could neither locate nor resolve symbols for: > > -B > > in the boot archive. Please verify that this file matches what is found in > the boot archive. > ... > Press any key to reboot. > > > On Wed, Dec 2, 2015 at 6:52 PM, Nahum Shalman <[email protected]> > wrote: > >> Right, that just looks like you're not passing in all the necessary >> arguments. >> Inspired by the link I sent you, I think you need to give it more >> information: >> >> insmod multiboot >> set root='hd0,gpt14' >> multiboot /platform/i86pc/kernel/amd64/unix >> /platform/i86pc/kernel/amd64/unix -B smartos=true >> module /platform/i86pc/amd64/boot_archive >> >> should be one step closer. >> >> -Nahum >> >> On 12/02/2015 11:38 AM, Avi Deitcher wrote: >> >> OK, so to be more precise: >> >> >> > 3- I tried direct loopback then multiboot/module commands, no valid disk >> >> >> insmod multiboot >> set root='hd0,gpt14' >> multiboot /platform/i86pc/kernel/amd64/unix >> module /platform/i86pc/amd64/boot_archive >> >> I get the error: >> >> null path >> krtld: failed to open '' >> krtld: bind_primary(): no relocation information found for module >> krtld: error during initial load/link phase >> krtld could neither locate nor resolve symbols for: >> >> in the boot archive >> ... >> Press any key to reboot. >> >> Same if I try it with -B smartos=true >> >> Etc. >> >> >> You wrote: >> >> > You never showed how you attempted to boot using multiboot. >> >> > Take inspiration from >> >> > https://docs.oracle.com/cd/E26502_01/html/E28983/gkvif.html >> >> Did I mention that this listbox is driving me nuts? I want to sign up for >> the list, get a daily digest... but get updates to any email threads in >> which I participate. Google Groups has that option, as does nearly every >> other. Every subscription based thing does (github?). listbox apparently >> does not. Argh. >> >> On Wed, Dec 2, 2015 at 11:22 AM, Avi Deitcher <[email protected]> wrote: >> >>> I have an existing server using grub2 to boot into multiple operating >>> systems (currently 3 CentOS installations and one vmware). I want to boot >>> SmartOS as well. Unfortunately, the usual "use a burnt CD/DVD" or "stick in >>> a USB drive" don't really work, as I rarely have physical access. >>> >>> I set aside 2 partitions on the physical disk - gpt14 1GB and gpt12 >>> 100GB. >>> >>> I downloaded the smartos-latest.iso, but how can I get grub2 to boot? >>> >>> 1- I cannot burn and install a physical CD/DVD or USB drive >>> 2- grub2 can loopback mount an ISO, but it needs a direct kernel to boot >>> from there, cannot do chainloader. I tried: >>> >>> insmod chain >>> loopback (loop0) (hd0,14)/smartos-latest.iso >>> set root='loop0' >>> chainloader +1 >>> >>> no luck. >>> >>> 2- I tried memdisk, same issue, it sees memdisk, but then immediately >>> reboots the physical machine >>> 3- I tried direct loopback then multiboot/module commands, no valid disk >>> 4- I tried emptying the contents of the iso into the gpt14 partition, >>> then just tried to 'chainloader +1' it, no valid boot disk found >>> >>> And so on. >>> >>> How can I just get the thing to boot without physical access? Yes, I do >>> have console access of course. >>> >>> Thanks. >>> >>> >>> -- >>> Avi Deitcher >>> Follow me http://twitter.com/avideitcher >>> Read me http://blog.atomicinc.com >>> >> >> >> >> -- >> Avi Deitcher >> [email protected] >> Follow me http://twitter.com/avideitcher >> Read me http://blog.atomicinc.com >> >> >> > > > -- > Avi Deitcher > [email protected] > Follow me http://twitter.com/avideitcher > Read me http://blog.atomicinc.com > > > -- Avi Deitcher [email protected] Follow me http://twitter.com/avideitcher Read me http://blog.atomicinc.com ------------------------------------------- smartos-discuss Archives: https://www.listbox.com/member/archive/184463/=now RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00 Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb Powered by Listbox: http://www.listbox.com
