-
Notifications
You must be signed in to change notification settings - Fork 70
Kernel 4.9 crashes inside the VM when used with Semaphore CI #91
Comments
Kernel is being update to 4.9.24 |
@gorozco1 I will give it a try with the new version, but I doubt it will work. I think something related to the kernel config is making this crash happening. |
Which ubuntu version is running as a host? |
Could you paste the crash details into this issue? |
I suspect it's Trusty (14.04.1) running 3.13.0-32-generic (https://semaphoreci.com/jamesodhunt/procenv/branches/master/builds/22) |
@sboeuf - can you confirm? |
with cc and recent changes in cc-kernel to support iptables networking stuff we will have a co-dependency with the host kernel, it should be minimum 4.x in the host (I guess), could you confirm @mcastelino @amshinde |
@jodh-intel @gorozco1 Yes this is Ubuntu 14.04 with kernel 3.13 on the host. |
@gorozco1 @amshinde Do we support Ubuntu 14.04? In any case you should get an error on iptables-restore and not a crash if the host has a iptables module enabled which we do not enable in our CC kernel. From initial testing it was ok to have iptables module enabled in CC but not enabled on the host kernel. So there should not be a dependency across the kernels per-se if we have all modules enabled that are enabled across distros. Unless the 3.x kernel has a module that is no longer supported in 4.x. The logs will help. |
The recent kernel changes may cause a failure in iptables-restore command in the worst case, but should not cause a crash. |
Assigned to @sboeuf for now to ensure we don't forget to add the logs. |
Run 1:
Run 2:
Run 3:
Run 4:
|
For some unknown reasons, we cannot use the latest kernels for Clear Containers guest kernel when using Semaphore CI. Indeed, using some 4.9 kernels (maybe something changed in the config and it is not related to the kernel version), makes the kernel crashing inside the VM, while it works perfectly with kernel 4.5-50. This was the kernel released just before we switch to 4.9.4-53.
The text was updated successfully, but these errors were encountered: