Hi Andy,

OK, I booted a t2.micro instance from my AMI (Original OmniOS CE r151022
HVM).  Updated pkg and then updated to r151022as.

Then shut the instance down, changed the type to m4.large, then started
the instance.  A panic/reboot loop ensued.  Stopped the instance.

Changed the instance back to t2.micro and booted.  Applied the hotfix
and rebooted.  Rebooted fine.

Stopped the instance, changed instance type to m4.large, and started the
instance.  The instance started and I could log in just fine.

To be sure, I stopped and restarted the instance a few times. It always
came back up ok.

So, the patch looks good to me.  If you can think of any more tests you
would like me to run, I'll give them a go for you.

Thank you for the speedy fix.



On 09/04/18 18:05, Al Slater wrote:
> Hi Andy,
> Wow, that was fast.  I will test this when I have fed the family.
> I have my own AMI, so I can spin a server as a T2 instance, apply the
> fix and then restart after changing to an M4.
> regards
> Al
> On 09/04/18 16:04, Andy Fiddaman wrote:
>> Al,
>> I've prepared a hot-fix containing this driver update if you'd like to
>> test. I tried to test it myself on AWS but can't provision any type of
>> machine from that unofficial CE r151022 AMI in London. Just snapshot the
>> EBS volume first in case of problems.
>> To install:
>>   pkg apply-hot-fix https://downloads.omniosce.org/pkg/r151022/7186-xnf.p5p
>> which will create a new boot-environment, and reboot.
>> Assuming it looks ok, this update will be part of next Monday's release.
>> Regards,
>> Andy
>> On Mon, 9 Apr 2018, Al Slater wrote:
>> ; Hi,
>> ;
>> ; Has the fix for 7186 (xnf: panic on Xen 4.x) been integrated into
>> ; r151022 since the initial CE release?
>> ;
>> ; I have an instance in AWS that they required me to stop and start again
>> ; due to host patching.  When I started it again the instance went into a
>> ; panic/reboot loop.  The stack dump looked similar to the one in the
>> ; error report.
>> ;
>> ; I managed to get the instance started by changing the instance type from
>> ; m4.large to t2.large.  Presumably AWS are migrating towards Xen versions
>> ; > 4 in london region.  I don't know how long until the t2 hosts are 
>> updated.
>> ;
>> ; regards
>> ;
>> ;
> _______________________________________________
> OmniOS-discuss mailing list
> OmniOS-discuss@lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss
OmniOS-discuss mailing list

Reply via email to