Guest User!

You are not Sophos Staff.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 6 replies
  • Subscribers 31 subscribers
  • Views 1825 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Kernel panic and reboot when configuring Jumbo Frame in vSphere

FoW
  • Hypervisor: VMware ESXi, 7.0.0, 15843807
  • Adapter: VMXNET3
  • SCSI: LSI Logic Parallel 
  • Guest OS Version: Othe Linux 4.x or later Linux (64-bit)
  • XG Firewall Version: SFVH (SFOS 18.0.1 MR-1.HF050520.2)

After adjusting the MTU to 9000, whenever the interface is refreshed, it is rebooted with the kernel panic. If it is not unlinked, the reboot is repeated.

It occurs regardless of whether or not the upper physical switch supports Jumbo Frame.

I have allowed support access for my appliance. If you are interested, take a look.

  • a3645e1c-4877-3381-8949-cb66c4565dc1@eu2.apu.sophos.com

 If the staff wants my VM image, I can provide it.

 
 


This thread was automatically locked due to age.
Parents Reply Children
  • 0 in reply to LuCar Toni

    Hi LuCar Toni,

    the hot fix that was applied to MR-1 was supposed to fix that issue. The issue then became spontaneous reboots sometime after a configuration change which could have been a simple as adding an exception.

    I raised this with the Devs and was requested to roll back to 354 until the updated MR-1 ws released.

    ian

  • 0 in reply to LuCar Toni

    Hi  :

    I would suggest to confirm the issue status in v18 GA. If it is observing with GA version then we may need to check and collect the required logs.

    OR 

    You may wait for re-release of v18 MR1 and you may confirm the issue status further with that version.

  • 0 in reply to Vishal_R

    My appliance was compromised so I don't want to go back to GA.

    I can try changing my network environment and cloning the VM, but the environment can be different. I will check back later when MR1 is re-released and give feedback to this thread again.

    Thanks.

  • 0 in reply to FoW

    My gut feeling is that it's nothing to do with your change but something in MR1 - I'm still running 18.0.1 MR1 as never had any problem with packet loss, and I had made some configuration changes that I didn't want yo have to re-do in the GA.

    Every 3 days it will randomly reboot, nothing in the logs and the usage graphs are blank for that period.

    I've looked at the advanced shell logs and it just stops logging at the time of the reboot, and then logs again as it's rebooting.

    The interesting thing is that I had about 21 days of uptime before this started, and it's all happened about the time the hot fix was applied