Niels, If you platform image is between 20150528T153328Z and (older than) 20150723T072528Z, it's probably that OS-4461 is to blame. A reboot of the node will "unstick" the zone. Upgrading to 20150723T072528Z or newer should prevent that issue from reoccurring.
On 19 October 2015 at 12:29, Niels Goossens <[email protected]> wrote: > Hello all, > > One of my LX zones is in state "down". It's not possible to get the zone > back up, with error message Cannot to start vm from state "down", must be > "stopped". > > I recently rebooted that zone, but did not check if it came back up (it > does usually.. I know what they say about assumptions). > > Now I found something like this issue on this list from 2014, but that > seemed to be related to a degraded pool (mine is not). > > I prefer not to reboot the global zone, as you can imagine. What options > do I have left? > > Kind regards, > > Niels > *smartos-discuss* | Archives > <https://www.listbox.com/member/archive/184463/=now> > <https://www.listbox.com/member/archive/rss/184463/26937779-40cf8a10> | > Modify > <https://www.listbox.com/member/?&;> > Your Subscription <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
