Re: [zones-discuss] preferred way to image-update zones
Jordan Vaughan skrev: On 12/ 4/09 02:28 PM, Anil wrote: Once a the global zone is upgraded (and rebooted with the new BE), what is the best way to update the zones? It seems like all I would need to do is: pkg -R zone path/root image-update reboot zone This seems like a hack, how would post package processing happen if this is not done from the zone itself? Should I instead *from the zone* take a clone, update parentbe zfs option, set it to active. Then, imate-update the snapshot/clone? This seems like a hack too! Try detaching and attaching the zones that need to be upgraded: # zoneadm -z zone detach [image-update the global zone] [reboot the machine to the new BE] # zoneadm -z zone attach -U You might be able to perform the detach/attach operations while in the updated global zone BE. Please see the Zones FAQ (http://hub.opensolaris.org/bin/view/Community+Group+zones/faq) for details. Hope that helps, Jordan What is the reason for the detach/attach? I have just switched to OS, and when I upgraded from 127 to 128a, with one zone (named swan), I ran (in the global zone): --- pkg image-update --be-name os-snv_128a beadm mount os-snv_128a /a pkg -R /a/zones/swan/root image-update beadm umount os-snv_128a beadm activate os-snv_128a init 6 --- This allows me to update everything without having to stop anything, A speed optimization might be: --- beadm create os-snv_128a beadm mount os-snv_128a /a pkg -R /a image-update pkg -R /a/zones/swan/root image-update beadm umount os-snv_128a beadm activate os-snv_128a init 6 --- Here the image-updates:s can be run in parallel. As I'm a newcomer to opensolaris updates I might be way off. Thomas ___ zones-discuss mailing list zones-discuss@opensolaris.org
[zones-discuss] capped-memory on a zone
I am working on zones for my honours project at uni. I created a zone with capped-memory and now I want to remove the caps. I deleted the capped-memory entries from the zone configuration using zonecfg. I then rebooted the zone as it didn't seem to take effect, but upon rebooting vmstat is still showing less than 100MB free. How can I remove the memory limit from the zone? I'm running OpenSolaris build 126 64-bit. Thanks Andrew. -- This message posted from opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] capped-memory on a zone
I am working on zones for my honours project at uni. I created a zone with capped-memory and now I want to remove the caps. I deleted the capped-memory entries from the zone configuration using zonecfg. I then rebooted the zone as it didn't seem to take effect, but upon rebooting vmstat is still showing less than 100MB free. How can I remove the memory limit from the zone? I'm running OpenSolaris build 126 64-bit. Thanks Andrew. OK, cancel that - it seems a reboot is not enough to remove the memory cap - I actually need to shut the VM down, the start it back up again. Cheers Andrew. -- This message posted from opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
[zones-discuss] problem with zone networking
I'm not sure what the problem is here. I have created a vnic over an existing physical nic as follows: dladm create-vnic -l e1000g0 e1000g1 I then use e1000g1 (the VNIC) as the interface for an exclusive-IP zone. Problem 1: upon rebooting the host e1000g1 is only half there in that it doesn't show up in dladm show-vnic output but if I try dladm create-vnic -l e1000g0 e1000g1 it complains that there is already an e1000g1. Deleting and re-adding the VNIC and everything works fine. Problem 2 (the real problem): after creating the VNIC I can no longer reach my default router. I'm guessing this is due to a routing mis-configuration, but it could just as easily be something else given the strangeness above. Does anyone have any ideas? I'm running OpenSolaris build 126 x64. Thanks Andrew. -- This message posted from opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] problem with zone networking
I'm not sure what the problem is here. I have created a vnic over an existing physical nic as follows: dladm create-vnic -l e1000g0 e1000g1 I then use e1000g1 (the VNIC) as the interface for an exclusive-IP zone. Problem 1: upon rebooting the host e1000g1 is only half there in that it doesn't show up in dladm show-vnic output but if I try dladm create-vnic -l e1000g0 e1000g1 it complains that there is already an e1000g1. Deleting and re-adding the VNIC and everything works fine. Problem 2 (the real problem): after creating the VNIC I can no longer reach my default router. I'm guessing this is due to a routing mis-configuration, but it could just as easily be something else given the strangeness above. Does anyone have any ideas? I'm running OpenSolaris build 126 x64. Thanks Andrew. OK, problem 1 was fixed by upgrading to build 128a. Problem 2 still exists, although wierdly the zone's networking is fine. The global zone is also fine until I reboot - after that I cannot contact the default router (an ADSL router) or any other machine. The non-global zone can successfully communicate with the ADSL router and the internet. Cheers Andrew. -- This message posted from opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] problem with zone networking
I'm not sure what the problem is here. I have created a vnic over an existing physical nic as follows: dladm create-vnic -l e1000g0 e1000g1 I then use e1000g1 (the VNIC) as the interface for an exclusive-IP zone. Problem 1: upon rebooting the host e1000g1 is only half there in that it doesn't show up in dladm show-vnic output but if I try dladm create-vnic -l e1000g0 e1000g1 it complains that there is already an e1000g1. Deleting and re-adding the VNIC and everything works fine. Problem 2 (the real problem): after creating the VNIC I can no longer reach my default router. I'm guessing this is due to a routing mis-configuration, but it could just as easily be something else given the strangeness above. Does anyone have any ideas? I'm running OpenSolaris build 126 x64. Thanks Andrew. OK, problem 1 was fixed by upgrading to build 128a. Problem 2 still exists, although wierdly the zone's networking is fine. The global zone is also fine until I reboot - after that I cannot contact the default router (an ADSL router) or any other machine. The non-global zone can successfully communicate with the ADSL router and the internet. Cheers Andrew. I should add - the global zone can ping the non-global zone. It is everything else that doesn't work. This suggests to me that it might be some sort of routing problem, but I don't know where to go from here. Thanks Andrew. -- This message posted from opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] preferred way to image-update zones
It seems to be -U, looking at the source at least: http://cvs.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/cmd/zoneadm/zoneadm.c#attach_func -- This message posted from opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
