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
  • 0

    Hi,

    the issue is not specific to your changes, it is known to support and I was requested to roll back to 354 until the new MR-1 is released.

    Basically any configuration change will cause a reboot either the day the change is made or a couple of times over the next couple of days.

    Ian

  • 0 in reply to rfcat_vk

    The MR1 issue was regarding dropping traffic and not passing traffic.

    This sounds like a Kernel panic / Coredumps.

    Can you reproduce this issue in GA? 

     could take a look at this? 

  • 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

Reply
  • 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

Children
No Data