* Karen Tung (Karen.Tung at Sun.COM) wrote: > Hi Glenn, > > Thanks for the write up, I have a question/comment about "Stage 5" > in the text write up.
Thanks for the input :-) > > Stage 5: (GUEST) > > > > DC (running inside the Guest) configures a root pool using the Guest's > > virtual disk (which it will need to figure out what the disk is > called). It > > then proceeds to populate and configure that root pool based on the > installation > > manifest which was included during construction of the PVMC ISO. The > process in > > some ways will be similar to how the slim_cd is constructed (minus the > iso and > > usb creation steps). Packages will be downloaded from a repository > (specified > > in the manifest) to the root pool. Additional configuration to make > the root > > pool bootable as well as turning it into a proper installation will > also be > > performed. > > You mentioned that the process in similar to the slim_cd construction > steps minus the iso and usb creation steps. I think that it would be best > to just use the current im-pop step to install the packages, and then, > reboot > the Guest to let the rest of the configuration happen naturally. What *exactly* happens during the installation is TBD. We'll certainly need some sort of mechanism for discovering the disk in the virtual machine, creating a root pool on it, etc for instance. I spoke with Sarah earlier today and she thought that I might be able to leverage the AI frontend 'installer' to do the actual installation. I need to evaluate that. As for what process DC will use to 'lay down the bits', I believe it will look similar to the slim_cd process but I'm sure we'll need to make some changes there. im-pop does seem a likely stopping point, as long as the rest of the configuration can happen upon reboot without user intervention (which I'll need to check). Thanks! -- Glenn
