Hi, afaik the Joyent images have still the custom kernel but will most likely switch to stock kernels. More information on the „Joyent optimized kernels“ is here: http://linux.joyent.com/
About „the one big partition“ thing: It is the system partition. You should add a second data disk for all your stuff (that will automatically get formatted and mounted at /data). I guess none will be happy if you set a fixed disk size for the image … because honestly everyone wants to have it a different size. If you really want to rely on only one disk and need that to be larger than the 10G you have to repartition and then yes - it might be easier to just install from an iso. You will miss the metadata tools if you convert that VM into an image and provision later (giving pubkeys via metadata for example). If you’re interested in the tooling around the image creation for CentOS you might find information here: https://github.com/joyent/mi-centos — Daniel Am 31.03.2014 um 07:18 schrieb Tom Robinson <[email protected]>: > Hi, > > I've asked briefly on the #smartos IRC but thought I might get a broader > response to my questions here. > > Does anyone have thoughts to share on running imgadm available images for > CentOS vs custom installed > instances of CentOS? Is there something in the SmartOS image kernels that is > relevant or are these > just stock CentOS kernels? Also, generally, what is the strategy for KVM > 'updates'? E.g., When > CentOS release updated kernels, is it OK to just update the KVMs in place > (yum update)? > > One thing that I don't like on the joyant KVM images is the 'one big > partition' partitioning > strategy for what will be a 'production' server. I've gone to the trouble of > re-partitioning > centos-6 2.6.0 (df81f45e-8f9f-11e3-a819-93fab527c81e). Then I made my own > image (clone) so I can > redeploy it without the re-partitioning headache. Am I going down a dead-end > path with this strategy? > > Clearly, it was lot easier installing a custom CentOS KVM (booted from an > ISO) than re-partitioning > the stock SmartOS image. I installed acpid on the custom guest so that a call > to 'vmadm stop UUID' > from the GZ shutdown the guest instance without trouble and otherwise it > seemed to run OK (test was > only to boot it and configure the network, and try startup/shutdown control). > I am concerned, > however, that there's some link to the hypervisor I'm missing with a custom > image. > > All comments are welcome. > > Kind regards, > Tom > > -- > > Tom Robinson > IT Manager/System Administrator > > MoTeC Pty Ltd > > 121 Merrindale Drive > Croydon South > 3136 Victoria > Australia > > T: +61 3 9761 5050 > F: +61 3 9761 5051 > E: [email protected] > > > > > > ------------------------------------------- > smartos-discuss > Archives: https://www.listbox.com/member/archive/184463/=now > RSS Feed: https://www.listbox.com/member/archive/rss/184463/21955186-c7d24c67 > Modify Your Subscription: https://www.listbox.com/member/?&; > Powered by Listbox: http://www.listbox.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
