[OmniOS-discuss] xnf panic

2018-04-09 Thread Al Slater
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 sim

Re: [OmniOS-discuss] xnf panic

2018-04-09 Thread Al Slater
On 09/04/2018 08:49, Al Slater wrote: > 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 >

Re: [OmniOS-discuss] xnf panic

2018-04-09 Thread Andy Fiddaman
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? Hi Al, No, that one was not selected for back-porting. I'll get it added to the list for the next weekly release. Regards, Andy -- Citrus

Re: [OmniOS-discuss] xnf panic

2018-04-09 Thread Andy Fiddaman
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:

Re: [OmniOS-discuss] xnf panic

2018-04-09 Thread Al Slater
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 thi

Re: [OmniOS-discuss] xnf panic

2018-04-09 Thread Al Slater
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