[Bug 1541678] Re: if-post-down.d/vlan and if-pre-up.d/vlan should support predictable NIC names
I ran into this as well. VLAN configuration is broken on Xenial unless you disable predictable network interface names, or you set up systemd .link files to rename your NICs (but, importantly, not vlan or bridge interfaces) to have a name starting with "eth". Since the upstream bug hasn't seen any activity for seven weeks, can we have an Ubuntu-specific fix? Seems like kind of an important piece of functionality that's broken out-of-the-box in an LTS release. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1541678 Title: if-post-down.d/vlan and if-pre-up.d/vlan should support predictable NIC names To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vlan/+bug/1541678/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 788637] Re: ipv6 conntrack fails to match certain packets with fragmentation header
** Patch added: defrag-fix.diff https://bugs.launchpad.net/bugs/788637/+attachment/2143633/+files/defrag-fix.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/788637 Title: ipv6 conntrack fails to match certain packets with fragmentation header -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 788637] [NEW] ipv6 conntrack fails to match certain packets with fragmentation header
Public bug reported: Binary package hint: linux-image-2.6.32-31-server Linux kernels prior to 2.6.34 have a bug which causes IPv6 packets containing a fragmentation header with offset=0 and the MF bit clear to not be properly matched by IPv6 conntrack. These kinds of packets are becoming much more common on the Internet because RFC6145-compliant NAT64 implementations specify that this header should be added to any translated IPv4 packet with the DF bit clear. I have attached the upstream patch that fixed the problem in 2.6.34. I have confirmed that it applies to Lucid's 2.6.32-31 and fixes the problem. To demonstrate the problem more clearly, here is what happens when stock Ubuntu 2.6.32-31 from Lucid tries to match a NAT64-translated HTTP session to Google: Chain FORWARD (policy ACCEPT 0 packets, 0 bytes) pkts bytes target prot opt in out source destination 40 30503 ACCEPT all * * ::/0 ::/0 state ESTABLISHED 0 0 ACCEPT all * * ::/0 ::/0 state RELATED 5 686 ACCEPT all * * ::/0 ::/0 state NEW 24 1735 ACCEPT all * * ::/0 ::/0 state INVALID Note all the INVALID packets, and there should only be a single NEW packet. With the patch applied, here is the result: Chain FORWARD (policy ACCEPT 0 packets, 0 bytes) pkts bytes target prot opt in out source destination 66 32707 ACCEPT all * * ::/0 ::/0 state ESTABLISHED 0 0 ACCEPT all * * ::/0 ::/0 state RELATED 180 ACCEPT all * * ::/0 ::/0 state NEW 0 0 ACCEPT all * * ::/0 ::/0 state INVALID This is the correct and expected result. Please apply the attached patch to the Lucid kernel so that Lucid can be used as an IPv6 stateful firewall. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/788637 Title: ipv6 conntrack fails to match certain packets with fragmentation header -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 270479] Re: Debian/Ubuntu netpbm is many years out-of-date with upstream
The obscenely old netpbm tools are a showstopper for me to migrate my fax/document management system to Ubuntu. Please bring this package up- to-date with other Linux distributions! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/270479 Title: Debian/Ubuntu netpbm is many years out-of-date with upstream -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 591869] Re: CONFIG_IPV6_SIT_6RD is disabled in kernel config
** Tags removed: needs-kernel-logs needs-upstream-testing -- CONFIG_IPV6_SIT_6RD is disabled in kernel config https://bugs.launchpad.net/bugs/591869 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 591869] Re: CONFIG_IPV6_SIT_6RD is disabled in kernel config
I removed the needs-kernel-logs and needs-upstream-testing tags because I don't think there's anything that needs to debugged or checked upstream. I'm not reporting a software failure; I'm just asking for a config option to be turned on. (If there's a more appropriate place to make this kind of request, please let me know.) Just to confirm, I tested to make sure that the latest Maverick kernel (2.6.35-2.2 now) does not have 6rd support: r...@maverick:~# uname -a Linux maverick 2.6.35-2-generic #2-Ubuntu SMP Tue Jun 8 19:15:10 UTC 2010 i686 GNU/Linux r...@maverick:~# grep 6RD /boot/config-$(uname -r) # CONFIG_IPV6_SIT_6RD is not set r...@maverick:~# ip tunnel add sit1 mode sit local 10.100.100.1 ttl 64 r...@maverick:~# ip tunnel 6rd dev sit1 6rd-prefix 2001:0db8::/32 6rd-relay_prefix 10.0.0.0/8 ioctl: Invalid argument r...@maverick:~# If I grab the 2.6.35-2 source package, I can add CONFIG_IPV6_SIT_6RD=y to debian.master/config/config.common.ubuntu and rebuild new kernel packages with 6rd support. Using my custom-built kernel package with CONFIG_IPV6_SIT_6RD, I get the following result from the above test: r...@maverick:~# uname -a Linux maverick 2.6.35-2-generic #2 SMP Wed Jun 9 23:52:10 EDT 2010 i686 GNU/Linux r...@maverick:~# grep 6RD /boot/config-$(uname -r) CONFIG_IPV6_SIT_6RD=y r...@maverick:~# ip tunnel add sit1 mode sit local 10.100.100.1 ttl 64 r...@maverick:~# ip tunnel 6rd dev sit1 6rd-prefix 2001:0db8::/32 6rd-relay_prefix 10.0.0.0/8 r...@maverick:~# ip tunnel show sit1 sit1: ipv6/ip remote any local 10.100.100.1 ttl 64 6rd-prefix 2001:db8::/32 6rd-relay_prefix 10.0.0.0/8 r...@maverick:~# Let me know if you need further justification for this request, or if I should raise the discussion in a different venue. Thanks. -- CONFIG_IPV6_SIT_6RD is disabled in kernel config https://bugs.launchpad.net/bugs/591869 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 591869] [NEW] CONFIG_IPV6_SIT_6RD is disabled in kernel config
Public bug reported: Binary package hint: linux-image-2.6.35-1-generic-pae The 2.6.35-1 packages in maverick do not have the CONFIG_IPV6_SIT_6RD option enabled. This option controls the availability of the IPv6 Rapid Deployment (6rd) implementation in the IPv6 SIT module. 6rd is an automatic tunneling mechanism that allows ISPs to provide IPv6 access to their customers using an existing IPv4 infrastructure. Free.fr has been using 6rd since 2007, and Comcast is rolling out 6rd- based IPv6 trials this month. Several other ISPs are planning to deploy 6rd as well. With the CONFIG_IPV6_SIT_6RD kernel config option enabled, the behavior of the kernel will not change unless the user specifically configures a 6rd interface using ip tunnel. (On the userland side, 6rd is supported in iproute-20100519-2 which is already in maverick.) Please enable the CONFIG_IPV6_SIT_6RD option in the maverick kernel config so that Ubuntu users can receive IPv6 connectivity with 6rd. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- CONFIG_IPV6_SIT_6RD is disabled in kernel config https://bugs.launchpad.net/bugs/591869 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 589163] Re: Cannot start kvm guest
I'll echo James Hogarth's concerns here that whatever QA happened with this update, if any, obviously didn't include any QEMU/KVM testing. After updating to 2.6.32-22.35, I was unable to get qemu-kvm to run at all, regardless of which options I used. Didn't anybody try running KVM on the new kernel after applying a KVM-related patch? My VM host was down for an hour this afternoon as a result of applying what was supposed to be a long-term stable update. I was bit last year by a KVM update with an obvious data loss bug (see bug #404394), so after today's bug, I'm regretting my choice of Ubuntu for my VM hosts. -- Cannot start kvm guest https://bugs.launchpad.net/bugs/589163 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 486943] Re: scroll wheel broken with QEMU's emulated USB tablet
** Attachment added: abs-dev-wheel-fix.patch http://launchpadlibrarian.net/35960946/abs-dev-wheel-fix.patch -- scroll wheel broken with QEMU's emulated USB tablet https://bugs.launchpad.net/bugs/486943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 486943] [NEW] scroll wheel broken with QEMU's emulated USB tablet
Public bug reported: Binary package hint: xserver-xorg-input-evdev When running Karmic as a guest under KVM/QEMU and using the -usbdevice tablet option to KVM/QEMU, the pointer positioning works correctly but the scroll wheel is ignored. The problem is a bug in the version of the xinput evdev driver in Karmic (2.2.5), which causes wheel events to be ignored from pointing devices with absolute axes. This is fixed in the latest version of the evdev driver: http://cgit.freedesktop.org/xorg/driver/xf86-input- evdev/commit/?h=evdev-2.3-branchid=d764dded18c47cec009babc075f2324cba1781ce I have attached a backport of that commit, which I have confirmed fixes the problem. ** Affects: xserver-xorg-input-evdev (Ubuntu) Importance: Undecided Status: New -- scroll wheel broken with QEMU's emulated USB tablet https://bugs.launchpad.net/bugs/486943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 404394] Re: qcow2 corruption regression
I ran into this bug as well, fortunately on a VM with no important data on it. KVM 84+dfsg-0ubuntu11 is rock-solid for me in production, but 0ubuntu12.3 causes data corruption nearly immediately on VMs that use virtio and qcow2. Here is a from-scratch reproduction procedure, which I have confirmed works: (1) Install Ubuntu 9.04 Server on a 64-bit system with VMX or SVM support. I'm using a run-of-the-mill Intel 64-bit desktop PC. Accept the defaults for everything in the installer. (2) Run aptitude update; aptitude full-upgrade; aptitude install kvm; reboot (3) Get a copy of ubuntu-9.04-server-amd64.iso. (4) Run kvm-img create -f qcow2 test.img 2G ; kvm -m 512 -net none -curses -drive file=test.img,if=virtio,boot=on -cdrom ubuntu-9.04 -server-amd64.iso -boot d (5) The installer uses framebuffer which doesn't work in Curses console mode. You'll end up at a screen that says 640 x 480 Graphic mode. Working blind: press enter, then escape. Wait five seconds for the Curses input layer to deliver the escape, then press enter again. The screen might flash briefly. Now type install fb=false and press enter. This should start booting the installer kernel in non-framebuffer mode. (6) Go through the installer, selecting all the defaults again. Do keyboard layout selection manually because the auto-detection doesn't work in Curses mode. (7) After formatting the filesystem, the installer will report, The attempt to mount a file system with type ext3 in LVM VG ubuntu, LV root at / failed. In dmesg you will find a ton of end_request: I/O error, dev vda, sector 3670331 messages. For fun, also try installing Ubuntu 8.04.3 Server as the guest. The same problem occurs. Using a raw disk image instead of qcow2 doesn't trigger this problem. Using an emulated IDE controller instead of virtio doesn't trigger this problem. KVM 84+dfsg-0ubuntu11 doesn't trigger this problem. -- qcow2 corruption regression https://bugs.launchpad.net/bugs/404394 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to kvm in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 404394] Re: qcow2 corruption regression
I ran into this bug as well, fortunately on a VM with no important data on it. KVM 84+dfsg-0ubuntu11 is rock-solid for me in production, but 0ubuntu12.3 causes data corruption nearly immediately on VMs that use virtio and qcow2. Here is a from-scratch reproduction procedure, which I have confirmed works: (1) Install Ubuntu 9.04 Server on a 64-bit system with VMX or SVM support. I'm using a run-of-the-mill Intel 64-bit desktop PC. Accept the defaults for everything in the installer. (2) Run aptitude update; aptitude full-upgrade; aptitude install kvm; reboot (3) Get a copy of ubuntu-9.04-server-amd64.iso. (4) Run kvm-img create -f qcow2 test.img 2G ; kvm -m 512 -net none -curses -drive file=test.img,if=virtio,boot=on -cdrom ubuntu-9.04 -server-amd64.iso -boot d (5) The installer uses framebuffer which doesn't work in Curses console mode. You'll end up at a screen that says 640 x 480 Graphic mode. Working blind: press enter, then escape. Wait five seconds for the Curses input layer to deliver the escape, then press enter again. The screen might flash briefly. Now type install fb=false and press enter. This should start booting the installer kernel in non-framebuffer mode. (6) Go through the installer, selecting all the defaults again. Do keyboard layout selection manually because the auto-detection doesn't work in Curses mode. (7) After formatting the filesystem, the installer will report, The attempt to mount a file system with type ext3 in LVM VG ubuntu, LV root at / failed. In dmesg you will find a ton of end_request: I/O error, dev vda, sector 3670331 messages. For fun, also try installing Ubuntu 8.04.3 Server as the guest. The same problem occurs. Using a raw disk image instead of qcow2 doesn't trigger this problem. Using an emulated IDE controller instead of virtio doesn't trigger this problem. KVM 84+dfsg-0ubuntu11 doesn't trigger this problem. -- qcow2 corruption regression https://bugs.launchpad.net/bugs/404394 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
