Hello Klaus, While this wasn't exactly what I had in mind when I came up with this <https://github.com/tgerczei/smartos-guesthandler>, it may come in handy right now as it will override what SmartOS intends to do concerning booting the guests.
Yours, Tamás On 2018-06-26 08:28, Klaus Dörrscheidt wrote: > Hello SmartOS community, > > I'm running a SmartOS host in my home lab with a couple of zones and > KVM VMs. Yesterday, I rebooted the host in order to update > to smartos-20180621T003454Z. When the machine came back, I was able to > login via SSH to the global zone, but then the machine became > unresponsive. Going back to the older release leads to the same > result. When booting the kernel with "standalone=true,noimport=true" I > can login and import the zpools. > > So, I assume that the issue stems from autobooting KVM VMs that > request more memory than the system has. Since the last reboot I had > created a couple of KVM VMs, but only a few were actually running at > any given time. I thought that I had disabled autobooting for those, > but I might be wrong. I'm quite new to SmartOS - so, is there a way > that I could boot the system half-way (say, via "noimport=true"), > disable autoboot for KVM VMs, and continue system initialization > afterwards? > > Best regards, > Klaus > *smartos-discuss* | Archives > <https://www.listbox.com/member/archive/184463/=now> | Modify > <https://www.listbox.com/member/?> Your Subscription > [Powered by Listbox] <http://www.listbox.com> > ------------------------------------------- smartos-discuss Archives: https://www.listbox.com/member/archive/184463/=now Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125 Powered by Listbox: http://www.listbox.com
