Hi all - i was just thinking, scary, is there a clean easy way to rewrap a domu and boot it as the dom0??? thought I would ping the universe it see if I was just being stupidly hopeful, before i went off and invested a bunch of time and effort for a zero gain.. thanx, rich
Rich Reynolds wrote:> Hi all - > i was just thinking, scary, is there a clean easy way to rewrap a domu > and boot it as the dom0??? thought I would ping the universe it see if > I was just being stupidly hopeful, before i went off and invested a > bunch of time and effort for a zero gain..It can be done... But I wouldn''t call it clean. I''ll ignore the zfs root case since I haven''t tried to move one of those in the past. The easiest way would be to have a domU use an entire disk so you don''t have to dd the disk around. You need to fix up the disk dev links, which can be tricky. i.e. the links in /dev/dsk and /dev/rdsk need to point to the new device path. If you change your disk (e.g. from c0t0d0s0 to c3t0d0s0), you will also have to modify /etc/vfstab for at least root and swap. You also need to modify bootpath in /boot/solaris/bootenv.rc e.g. setprop bootpath /pci@0,0/pci1022,7458@11/pci1000,3060@4/sd@3,0:a If you get that right, you will be able to boot up in metal or dom0 (assuming you have grub installed and a proper menu.lst). It''s not that hard, but can be pretty error prone. I''ve done it many times in the past setting up a disk to boot in a new system, or when you switch from ide to a sata driver, etc. One trick is to boot into the failsafe, and use the /dev/dsk and /dev/rdsk links on the disk your trying to boot. Saves on the typos :-). i.e. when booted from the failsafe which is a ramdisk mount the disk @ /a and do something like the following. # rm /a/dev/dsk /a/dev/rdsk # cd / # tar cpf - dev/dsk | (cd /a;tar xpf - ) # tar cpf - dev/rdsk | (cd /a;tar xpf - ) then you just need to fix your NIC and you should be all set. MRJ
mark - thanx for the quick reply... see inline... Mark Johnson wrote:> > > Rich Reynolds wrote: >> Hi all - >> i was just thinking, scary, is there a clean easy way to rewrap a domu >> and boot it as the dom0??? thought I would ping the universe it see >> if I was just being stupidly hopeful, before i went off and invested a >> bunch of time and effort for a zero gain.. > > It can be done... But I wouldn''t call it clean. > > I''ll ignore the zfs root case since I haven''t tried > to move one of those in the past. The easiest way would > be to have a domU use an entire disk so you don''t have > to dd the disk around.Why would I need to dd disk images about...seem to me that once built and properly targeted(granted not simple)I should be able to launch any instance that is "active" (in the BIOS sense). While certainly separate disks alleviates many headaches, and potential failure points, just having an active partition should be sufficient, or am I being wooden-headed.> > You need to fix up the disk dev links, which can be > tricky. i.e. the links in /dev/dsk and /dev/rdsk > need to point to the new device path. If you change > your disk (e.g. from c0t0d0s0 to c3t0d0s0), you will > also have to modify /etc/vfstab for at least root and > swap. > > You also need to modify bootpath in /boot/solaris/bootenv.rc > e.g. > > setprop bootpath /pci@0,0/pci1022,7458@11/pci1000,3060@4/sd@3,0:a >one step that im sure I would have missed...> If you get that right, you will be able to boot up > in metal or dom0 (assuming you have grub installed > and a proper menu.lst). It''s not that hard, but can be > pretty error prone. I''ve done it many times in the past > setting up a disk to boot in a new system, or when > you switch from ide to a sata driver, etc.menu.lst''s are foe vienies, to paraphrase Arnold. in the past I have typed all the grub stuff by hand till I was ready to "productize", but then again i did that sort of nonsense for SunOS3.5 too...> > One trick is to boot into the failsafe, and use > the /dev/dsk and /dev/rdsk links on the disk your > trying to boot. Saves on the typos :-). >thats a huge good point!!!> i.e. when booted from the failsafe which is a ramdisk > mount the disk @ /a and do something like the following. > # rm /a/dev/dsk /a/dev/rdsk > # cd / > # tar cpf - dev/dsk | (cd /a;tar xpf - ) > # tar cpf - dev/rdsk | (cd /a;tar xpf - ) > > then you just need to fix your NIC and you should be > all set. >cool, so I will give it a go in the next week or so as a way to upgrade my base system from b102 to b106...sort of like liveupgrade the hard way. ill let you know how it goes, and then try the ZFS swing to be ready for 2009.6...> > > MRJ >thanx, rich
Rich Reynolds wrote:> mark - > > thanx for the quick reply... see inline... > > Mark Johnson wrote: >> >> >> Rich Reynolds wrote: >>> Hi all - >>> i was just thinking, scary, is there a clean easy way to rewrap a >>> domu and boot it as the dom0??? thought I would ping the universe >>> it see if I was just being stupidly hopeful, before i went off and >>> invested a bunch of time and effort for a zero gain.. >> >> It can be done... But I wouldn''t call it clean. >> >> I''ll ignore the zfs root case since I haven''t tried >> to move one of those in the past. The easiest way would >> be to have a domU use an entire disk so you don''t have >> to dd the disk around. > Why would I need to dd disk images about...seem to me that once built > and properly targeted(granted not simple)I should be able to launch any > instance that is "active" (in the BIOS sense). While certainly separate > disks alleviates many headaches, and potential failure points, just > having an active partition should be sufficient, or am I being > wooden-headed.If your using the entire disk (i.e. c0t0d0p0) then you wouldn''t. If your using a slice, or a file based disk, then you would.>> >> You need to fix up the disk dev links, which can be >> tricky. i.e. the links in /dev/dsk and /dev/rdsk >> need to point to the new device path. If you change >> your disk (e.g. from c0t0d0s0 to c3t0d0s0), you will >> also have to modify /etc/vfstab for at least root and >> swap. >> >> You also need to modify bootpath in /boot/solaris/bootenv.rc >> e.g. >> >> setprop bootpath /pci@0,0/pci1022,7458@11/pci1000,3060@4/sd@3,0:a >> > one step that im sure I would have missed... >> If you get that right, you will be able to boot up >> in metal or dom0 (assuming you have grub installed >> and a proper menu.lst). It''s not that hard, but can be >> pretty error prone. I''ve done it many times in the past >> setting up a disk to boot in a new system, or when >> you switch from ide to a sata driver, etc. > menu.lst''s are foe vienies, to paraphrase Arnold. in the past I have > typed all the grub stuff by hand till I was ready to "productize", but > then again i did that sort of nonsense for SunOS3.5 too...ha!>> >> One trick is to boot into the failsafe, and use >> the /dev/dsk and /dev/rdsk links on the disk your >> trying to boot. Saves on the typos :-). >> > thats a huge good point!!! > >> i.e. when booted from the failsafe which is a ramdisk >> mount the disk @ /a and do something like the following. >> # rm /a/dev/dsk /a/dev/rdsk >> # cd / >> # tar cpf - dev/dsk | (cd /a;tar xpf - ) >> # tar cpf - dev/rdsk | (cd /a;tar xpf - ) >> >> then you just need to fix your NIC and you should be >> all set. >> > cool, so I will give it a go in the next week or so as a way to upgrade > my base system from b102 to b106...sort of like liveupgrade the hard > way. ill let you know how it goes, and then try the ZFS swing to be > ready for 2009.6...Good luck! MRJ