Re: Jessie will need Linux 3.18!
On Feb 5, 2015 3:35 AM, =?UTF-8?B?TWFydGlueCAtIOOCuOOCp+ODvOODoOOCug==?= thiagocmarti...@gmail.com wrote: Okay Thomas, got it! I'll do the required tests under *debian* and fill a bug against Debian Linux Kernel. But, the Kernel code related to this part of it (network and etc), is very different in Linux 3.18, I'm guessing that it will *easier* to just provide Jessie with Linux 3.18, instead of a patch, but, I'm seeing that it might be too late for that... :-( Yes, I tested it with Ubuntu but, I also tested it using Linux from kernel.org, compiled by myself... Only Linux 3.18 solve that issue. Cheers! Bigfixes can be applied to 3.16 if you find a patch. No way to upgrade to 3.18 at this time indeed. Thomas Goirand (zigo)
Re: Jessie will need Linux 3.18!
* Martinx - ジェームズ thiagocmarti...@gmail.com [2015-02-04 20:37]: I was facing a Linux BUG that was fixed only in 3.18. Here it is: https://bugs.launchpad.net/linux/+bug/1362755 So, with Linux 3.16, it will not be possible to use Jessie to create a VLAN tagged Virtual Network within a KVM hypervisor itself. It will not route VLAN tagged packets. I manually backported Linux 3.18 from Ubuntu Vivid, into Trusty: https://launchpad.net/~martinx/+archive/ubuntu/linux Then, the problem solved! I tested the Linux versions from 3.13, to 3.16, all have the same problem... Linux 3.18 is okay. I must say that I did not tested Jessie this days but, I know that Linux 3.16 doesn't work. Basically, Jessie can not be used in a production environment on a Corporate Network, for example... All my firewalls, VPN servers, proxies are KVM Virtual Machines. The VLAN tagged packets does not get routed, it started to work only when with Linux 3.18. Sounds similar to issues reported under #763428 which references https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=927a171886e895b174ed99a06d31fc05bc03750e HTH Martin -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150205105541.gf2...@anguilla.debian.or.at
Re: Jessie will need Linux 3.18!
On 4 February 2015 at 19:08, Ben Hutchings b...@decadent.org.uk wrote: [Redirecting to debian-kernel] Cool! Tks! On Wed, 2015-02-04 at 17:36 -0200, Martinx - ジェームズ wrote: Guys, I was facing a Linux BUG that was fixed only in 3.18. Did you find out what change fixes this? No, I did not bisected the issue... Vlad Yasevich from Redhat (comment #2 at LP #1362755) told me that it is something related to TSO/GSO implementation in the kernel. Does this configuration work in wheezy (with Linux 3.2)? I did not tested it with Linux 3.2 but, I can try it next week. [...] Basically, Jessie can not be used in a production environment on a Corporate Network, for example... [...] Please, don't exaggerate. Debian is already widely used with the Linux 3.16. Apparently certain configurations don't work properly, but we can probably fix that. Okay, sorry... I was just trying to raise up the drama to catch attention... hehe... To make it clear, Jessie KVM guest, acting as a router, can not be used on top of Jessie KVM host, when you have tagged VLANs... I guess that this topology might be pretty common out there... I worked on a lot of companies that are purely based on Debian / Ubuntu (both hypervisors and VMs). Drama off...:-) Jessie is great! Ben. Thiago -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAJSM8J37tuFbkFWHE4_58wS=_-HtMCre=9-mgadrhsoc_cu...@mail.gmail.com
Re: Jessie will need Linux 3.18!
[Redirecting to debian-kernel] On Wed, 2015-02-04 at 17:36 -0200, Martinx - ジェームズ wrote: Guys, I was facing a Linux BUG that was fixed only in 3.18. Did you find out what change fixes this? Does this configuration work in wheezy (with Linux 3.2)? [...] Basically, Jessie can not be used in a production environment on a Corporate Network, for example... [...] Please, don't exaggerate. Debian is already widely used with the Linux 3.16. Apparently certain configurations don't work properly, but we can probably fix that. Ben. -- Ben Hutchings Hoare's Law of Large Problems: Inside every large problem is a small problem struggling to get out. signature.asc Description: This is a digitally signed message part
Re: Jessie will need Linux 3.18!
On 02/04/2015 08:36 PM, Martinx - ジェームズ wrote: Guys, I was facing a Linux BUG that was fixed only in 3.18. Here it is: https://bugs.launchpad.net/linux/+bug/1362755 So, with Linux 3.16, it will not be possible to use Jessie to create a VLAN tagged Virtual Network within a KVM hypervisor itself. It will not route VLAN tagged packets. I manually backported Linux 3.18 from Ubuntu Vivid, into Trusty: https://launchpad.net/~martinx/+archive/ubuntu/linux Then, the problem solved! I tested the Linux versions from 3.13, to 3.16, all have the same problem... Linux 3.18 is okay. I must say that I did not tested Jessie this days but, I know that Linux 3.16 doesn't work. Basically, Jessie can not be used in a production environment on a Corporate Network, for example... All my firewalls, VPN servers, proxies are KVM Virtual Machines. The VLAN tagged packets does not get routed, it started to work only when with Linux 3.18. Please, pay attention into this problem before Debian Jessie release! Best! Thiago Hi Thiago, The best way forward for this kind if issue is to: 1/ Open a bug against the Debian linux kernel. 2/ Provide a patch to fix the issue, attached to the bug. Bug keep this in mind when doing so: You need to test under *debian*, and not just under Ubuntu. From the launchpad bug you've opened, it's looking like you've had the issue in Ubuntu, and there's no way to tell what will happen in Debian. Also, you issue seems related to kvm/qemu, and not only to the kernel. Cheers, Thomas Goirand (zigo) -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54d2cf60.4010...@debian.org
Re: Jessie will need Linux 3.18!
On 5 February 2015 at 00:03, Thomas Goirand z...@debian.org wrote: On 02/04/2015 08:36 PM, Martinx - ジェームズ wrote: Guys, I was facing a Linux BUG that was fixed only in 3.18. Here it is: https://bugs.launchpad.net/linux/+bug/1362755 So, with Linux 3.16, it will not be possible to use Jessie to create a VLAN tagged Virtual Network within a KVM hypervisor itself. It will not route VLAN tagged packets. I manually backported Linux 3.18 from Ubuntu Vivid, into Trusty: https://launchpad.net/~martinx/+archive/ubuntu/linux Then, the problem solved! I tested the Linux versions from 3.13, to 3.16, all have the same problem... Linux 3.18 is okay. I must say that I did not tested Jessie this days but, I know that Linux 3.16 doesn't work. Basically, Jessie can not be used in a production environment on a Corporate Network, for example... All my firewalls, VPN servers, proxies are KVM Virtual Machines. The VLAN tagged packets does not get routed, it started to work only when with Linux 3.18. Please, pay attention into this problem before Debian Jessie release! Best! Thiago Hi Thiago, The best way forward for this kind if issue is to: 1/ Open a bug against the Debian linux kernel. 2/ Provide a patch to fix the issue, attached to the bug. Bug keep this in mind when doing so: You need to test under *debian*, and not just under Ubuntu. From the launchpad bug you've opened, it's looking like you've had the issue in Ubuntu, and there's no way to tell what will happen in Debian. Also, you issue seems related to kvm/qemu, and not only to the kernel. Cheers, Thomas Goirand (zigo) Okay Thomas, got it! I'll do the required tests under *debian* and fill a bug against Debian Linux Kernel. But, the Kernel code related to this part of it (network and etc), is very different in Linux 3.18, I'm guessing that it will *easier* to just provide Jessie with Linux 3.18, instead of a patch, but, I'm seeing that it might be too late for that... :-( Yes, I tested it with Ubuntu but, I also tested it using Linux from kernel.org, compiled by myself... Only Linux 3.18 solve that issue. Cheers! -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/cajsm8j1jkgcyuwpyjg8djf2cssjbjm5tfsrbw1jexzpvah_...@mail.gmail.com
