[Kernel-packages] [Bug 2002889] Re: 5.15.0-58.64 breaks xen bridge networking (pvh domU)
Bionic: The problem does **not** occur on Ubuntu 18.04 with HWE-kernel 5.4.0-137 (really) The problem does **not** occur on Ubuntu 18.04 with HWE-kernel 5.4.0-139 > fixed! The problem **does** occur on Ubuntu 18.04 with kernel 4.15.0-204 The problem does **not** occur on Ubuntu 18.04 with kernel 4.15.0-206.217 > fixed! Thank you very much! ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2002889 Title: 5.15.0-58.64 breaks xen bridge networking (pvh domU) Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Bug description: [Impact] Xen guests will not have network access. This fixes a regression due to the fix for CVE-2022-3643. [Testing] This has only been build-tested. [Potential regression] Xen guests might not have network access. -- With 5.15.0-58.64-generic, bridge networking on xen is broken : no packet (check with tcpdump) flowing between dom0 and any domUs attached to a network bridge. downgrading to 5.15.0-57-generic fix the issue. Thus the patch to the netback driver seems the cause. relevant network config : brtctl show : br0 8000.XXXno eno1 vif1.0 relevant domU config : kernel = '/usr/lib/grub-xen/grub-i386-xen_pvh.bin' type = 'pvh' vif = [ 'ip=192.168.10.10 ,bridge=br0' ] No message in dmesg, journal, xen logs.. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2002889/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002889] Re: 5.15.0-58.64 breaks xen bridge networking (pvh domU)
** Tags removed: verification-needed-focal verification-needed-jammy ** Tags added: verification-done-focal verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2002889 Title: 5.15.0-58.64 breaks xen bridge networking (pvh domU) Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Bug description: [Impact] Xen guests will not have network access. This fixes a regression due to the fix for CVE-2022-3643. [Testing] This has only been build-tested. [Potential regression] Xen guests might not have network access. -- With 5.15.0-58.64-generic, bridge networking on xen is broken : no packet (check with tcpdump) flowing between dom0 and any domUs attached to a network bridge. downgrading to 5.15.0-57-generic fix the issue. Thus the patch to the netback driver seems the cause. relevant network config : brtctl show : br0 8000.XXXno eno1 vif1.0 relevant domU config : kernel = '/usr/lib/grub-xen/grub-i386-xen_pvh.bin' type = 'pvh' vif = [ 'ip=192.168.10.10 ,bridge=br0' ] No message in dmesg, journal, xen logs.. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2002889/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002889] Re: 5.15.0-58.64 breaks xen bridge networking (pvh domU)
On Ubuntu 20.04 the Kernel 5.4.0-144 solves the problem. Thank you very much. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2002889 Title: 5.15.0-58.64 breaks xen bridge networking (pvh domU) Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Bug description: [Impact] Xen guests will not have network access. This fixes a regression due to the fix for CVE-2022-3643. [Testing] This has only been build-tested. [Potential regression] Xen guests might not have network access. -- With 5.15.0-58.64-generic, bridge networking on xen is broken : no packet (check with tcpdump) flowing between dom0 and any domUs attached to a network bridge. downgrading to 5.15.0-57-generic fix the issue. Thus the patch to the netback driver seems the cause. relevant network config : brtctl show : br0 8000.XXXno eno1 vif1.0 relevant domU config : kernel = '/usr/lib/grub-xen/grub-i386-xen_pvh.bin' type = 'pvh' vif = [ 'ip=192.168.10.10 ,bridge=br0' ] No message in dmesg, journal, xen logs.. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2002889/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002889] Re: 5.15.0-58.64 breaks xen bridge networking (pvh domU)
Ob Ubuntu 20.04 with linux-generic-hwe-20.04 (5.15.0.66.73~20.04.27) from focal proposed solves the problem. Thank you very much. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2002889 Title: 5.15.0-58.64 breaks xen bridge networking (pvh domU) Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Bug description: [Impact] Xen guests will not have network access. This fixes a regression due to the fix for CVE-2022-3643. [Testing] This has only been build-tested. [Potential regression] Xen guests might not have network access. -- With 5.15.0-58.64-generic, bridge networking on xen is broken : no packet (check with tcpdump) flowing between dom0 and any domUs attached to a network bridge. downgrading to 5.15.0-57-generic fix the issue. Thus the patch to the netback driver seems the cause. relevant network config : brtctl show : br0 8000.XXXno eno1 vif1.0 relevant domU config : kernel = '/usr/lib/grub-xen/grub-i386-xen_pvh.bin' type = 'pvh' vif = [ 'ip=192.168.10.10 ,bridge=br0' ] No message in dmesg, journal, xen logs.. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2002889/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002889] Re: 5.15.0-58.64 breaks xen bridge networking (pvh domU)
On Ubuntu 22.04 5.15.0-66 from focal proposed solves this problem. Thank you very much. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2002889 Title: 5.15.0-58.64 breaks xen bridge networking (pvh domU) Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Bug description: [Impact] Xen guests will not have network access. This fixes a regression due to the fix for CVE-2022-3643. [Testing] This has only been build-tested. [Potential regression] Xen guests might not have network access. -- With 5.15.0-58.64-generic, bridge networking on xen is broken : no packet (check with tcpdump) flowing between dom0 and any domUs attached to a network bridge. downgrading to 5.15.0-57-generic fix the issue. Thus the patch to the netback driver seems the cause. relevant network config : brtctl show : br0 8000.XXXno eno1 vif1.0 relevant domU config : kernel = '/usr/lib/grub-xen/grub-i386-xen_pvh.bin' type = 'pvh' vif = [ 'ip=192.168.10.10 ,bridge=br0' ] No message in dmesg, journal, xen logs.. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2002889/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002889] Re: 5.15.0-58.64 breaks xen bridge networking (pvh domU)
We are affected on live machines too. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2002889 Title: 5.15.0-58.64 breaks xen bridge networking (pvh domU) Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Bug description: [Impact] Xen guests will not have network access. This fixes a regression due to the fix for CVE-2022-3643. [Testing] This has only been build-tested. [Potential regression] Xen guests might not have network access. -- With 5.15.0-58.64-generic, bridge networking on xen is broken : no packet (check with tcpdump) flowing between dom0 and any domUs attached to a network bridge. downgrading to 5.15.0-57-generic fix the issue. Thus the patch to the netback driver seems the cause. relevant network config : brtctl show : br0 8000.XXXno eno1 vif1.0 relevant domU config : kernel = '/usr/lib/grub-xen/grub-i386-xen_pvh.bin' type = 'pvh' vif = [ 'ip=192.168.10.10 ,bridge=br0' ] No message in dmesg, journal, xen logs.. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2002889/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1920660] Re: Missing Commit for 5.4-Kernel breaks xen Dom0
Kernel 5.4.0-71 works for us with xen. Thank you very much! ** Changed in: linux (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1920660 Title: Missing Commit for 5.4-Kernel breaks xen Dom0 Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Bug description: You commited "xen: Fix event channel callback via INTX/GSI" for kernel 5.4.0-67 for HWE 18.04 and 20.04. This commit is incomplete and breaks Ubuntu as Dom0 for xen. You need also Commit "xen: Fix XenStore initialisation for XS_LOCAL" See https://lkml.org/lkml/2021/1/28/1235 See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915195 Upstream: Commit: 3499ba8198cad47b731792e5e56b9ec2a78a83a2 Fixing Commit: 5f46400f7a6a4fad635d5a79e2aa5a04a30ffea1 5.10: Commit: fa5f2e04daa44961a1026e93f0cc88caa3c27d3d (5.10.11) Fixing Commit: 5f3d54c00f1f2682cee9c590c22655b0330ffd18 (5.10.13) 5.4: Commit: a09d4e7acdbf276b2096661ee82454ae3dd24d2b (5.4.93) Fixing commit 2c7b4b25293aebd2563188f7196f6e0ff0cb0f9f (5.4.95) Without this patch you cannot start guests (DomU) on this machine! Error message while creating DomU: libxl: error: libxl_device.c:1105:device_backend_callback: Domain X:unable to add device with path / libxl: error: libxl_create.c:1452:domcreate_launch_dm: Domain X:unable to add disk devices See: - https://lkml.org/lkml/2021/1/28/1231 and https://lkml.org/lkml/2021/1/29/14 - https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.4.107=2c7b4b25293aebd2563188f7196f6e0ff0cb0f9f - https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.4.95 - http://changelogs.ubuntu.com/changelogs/pool/main/l/linux-hwe-5.4/linux-hwe-5.4_5.4.0-67.75~18.04.1/changelog - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915195 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1920660/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921902] Re: Security-Fix Xen XSA 371 for Kernel 5.4.0-71
Due to kind of report are no logs available. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1921902 Title: Security-Fix Xen XSA 371 for Kernel 5.4.0-71 Status in linux package in Ubuntu: Confirmed Bug description: Today [XSA 371](http://xenbits.xen.org/xsa/advisory-371.html) was published which contain a security patch for a commit which is included in proposed 5.4.0-71. The [Patch](http://xenbits.xen.org/xsa/xsa371-linux.patch) is only 1 line maybe you can add this security fix to 5.4.0-71 release. Thank you in advance. Original Commit: XSA-365: xen-blkback: fix error handling in xen_blkbk_map() New commit with security fix: XSA-371: xen-blkback: don't leak persistent grants from xen_blkbk_map() See - http://xenbits.xen.org/xsa/advisory-371.html - http://xenbits.xen.org/xsa/xsa371-linux.patch - http://xenbits.xen.org/xsa/advisory-365.html - http://xenbits.xen.org/xsa/xsa365-linux.patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921902/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921902] [NEW] Security-Fix Xen XSA 371 for Kernel 5.4.0-71
Public bug reported: Today [XSA 371](http://xenbits.xen.org/xsa/advisory-371.html) was published which contain a security patch for a commit which is included in proposed 5.4.0-71. The [Patch](http://xenbits.xen.org/xsa/xsa371-linux.patch) is only 1 line maybe you can add this security fix to 5.4.0-71 release. Thank you in advance. Original Commit: XSA-365: xen-blkback: fix error handling in xen_blkbk_map() New commit with security fix: XSA-371: xen-blkback: don't leak persistent grants from xen_blkbk_map() See - http://xenbits.xen.org/xsa/advisory-371.html - http://xenbits.xen.org/xsa/xsa371-linux.patch - http://xenbits.xen.org/xsa/advisory-365.html - http://xenbits.xen.org/xsa/xsa365-linux.patch ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Securit-Fix Xen XSA 371 for Kernel 5.4.0-71 + Security-Fix Xen XSA 371 for Kernel 5.4.0-71 ** Description changed: Today [XSA 371](http://xenbits.xen.org/xsa/advisory-371.html) was published which contain a security patch for a commit which is included in proposed 5.4.0-71. The [Patch](http://xenbits.xen.org/xsa/xsa371-linux.patch) is only 1 line maybe you can add this security fix to 5.4.0-71 release. Thank you in advance. + + Original Commit: + XSA-365: xen-blkback: fix error handling in xen_blkbk_map() + + New commit with security fix: + XSA-371: xen-blkback: don't leak persistent grants from xen_blkbk_map() + + See + - http://xenbits.xen.org/xsa/advisory-371.html + - http://xenbits.xen.org/xsa/xsa371-linux.patch + - http://xenbits.xen.org/xsa/advisory-365.html + - http://xenbits.xen.org/xsa/xsa365-linux.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1921902 Title: Security-Fix Xen XSA 371 for Kernel 5.4.0-71 Status in linux package in Ubuntu: New Bug description: Today [XSA 371](http://xenbits.xen.org/xsa/advisory-371.html) was published which contain a security patch for a commit which is included in proposed 5.4.0-71. The [Patch](http://xenbits.xen.org/xsa/xsa371-linux.patch) is only 1 line maybe you can add this security fix to 5.4.0-71 release. Thank you in advance. Original Commit: XSA-365: xen-blkback: fix error handling in xen_blkbk_map() New commit with security fix: XSA-371: xen-blkback: don't leak persistent grants from xen_blkbk_map() See - http://xenbits.xen.org/xsa/advisory-371.html - http://xenbits.xen.org/xsa/xsa371-linux.patch - http://xenbits.xen.org/xsa/advisory-365.html - http://xenbits.xen.org/xsa/xsa365-linux.patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921902/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1920660] Re: Missing Commit for 5.4-Kernel breaks xen Dom0
Kernel 5.4.0-71 is on proposed-channel and solves this problem! Big thanks to you all! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1920660 Title: Missing Commit for 5.4-Kernel breaks xen Dom0 Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.4 package in Ubuntu: Confirmed Bug description: You commited "xen: Fix event channel callback via INTX/GSI" for kernel 5.4.0-67 for HWE 18.04 and 20.04. This commit is incomplete and breaks Ubuntu as Dom0 for xen. You need also Commit "xen: Fix XenStore initialisation for XS_LOCAL" See https://lkml.org/lkml/2021/1/28/1235 See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915195 Upstream: Commit: 3499ba8198cad47b731792e5e56b9ec2a78a83a2 Fixing Commit: 5f46400f7a6a4fad635d5a79e2aa5a04a30ffea1 5.10: Commit: fa5f2e04daa44961a1026e93f0cc88caa3c27d3d (5.10.11) Fixing Commit: 5f3d54c00f1f2682cee9c590c22655b0330ffd18 (5.10.13) 5.4: Commit: a09d4e7acdbf276b2096661ee82454ae3dd24d2b (5.4.93) Fixing commit 2c7b4b25293aebd2563188f7196f6e0ff0cb0f9f (5.4.95) Without this patch you cannot start guests (DomU) on this machine! Error message while creating DomU: libxl: error: libxl_device.c:1105:device_backend_callback: Domain X:unable to add device with path / libxl: error: libxl_create.c:1452:domcreate_launch_dm: Domain X:unable to add disk devices See: - https://lkml.org/lkml/2021/1/28/1231 and https://lkml.org/lkml/2021/1/29/14 - https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.4.107=2c7b4b25293aebd2563188f7196f6e0ff0cb0f9f - https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.4.95 - http://changelogs.ubuntu.com/changelogs/pool/main/l/linux-hwe-5.4/linux-hwe-5.4_5.4.0-67.75~18.04.1/changelog - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915195 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1920660/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1920660] Re: Missing Commit for 5.4-Kernel breaks xen Dom0
This patch seems to be part of 5.4.0-71 https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/commit/?h=Ubuntu-5.4.0-71.79=b6c0a7f33687639b59ce52882cf35e95e5f5454a I will test if available in proposed-repo. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1920660 Title: Missing Commit for 5.4-Kernel breaks xen Dom0 Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.4 package in Ubuntu: Confirmed Bug description: You commited "xen: Fix event channel callback via INTX/GSI" for kernel 5.4.0-67 for HWE 18.04 and 20.04. This commit is incomplete and breaks Ubuntu as Dom0 for xen. You need also Commit "xen: Fix XenStore initialisation for XS_LOCAL" See https://lkml.org/lkml/2021/1/28/1235 See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915195 Upstream: Commit: 3499ba8198cad47b731792e5e56b9ec2a78a83a2 Fixing Commit: 5f46400f7a6a4fad635d5a79e2aa5a04a30ffea1 5.10: Commit: fa5f2e04daa44961a1026e93f0cc88caa3c27d3d (5.10.11) Fixing Commit: 5f3d54c00f1f2682cee9c590c22655b0330ffd18 (5.10.13) 5.4: Commit: a09d4e7acdbf276b2096661ee82454ae3dd24d2b (5.4.93) Fixing commit 2c7b4b25293aebd2563188f7196f6e0ff0cb0f9f (5.4.95) Without this patch you cannot start guests (DomU) on this machine! Error message while creating DomU: libxl: error: libxl_device.c:1105:device_backend_callback: Domain X:unable to add device with path / libxl: error: libxl_create.c:1452:domcreate_launch_dm: Domain X:unable to add disk devices See: - https://lkml.org/lkml/2021/1/28/1231 and https://lkml.org/lkml/2021/1/29/14 - https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.4.107=2c7b4b25293aebd2563188f7196f6e0ff0cb0f9f - https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.4.95 - http://changelogs.ubuntu.com/changelogs/pool/main/l/linux-hwe-5.4/linux-hwe-5.4_5.4.0-67.75~18.04.1/changelog - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915195 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1920660/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1920660] Re: Missing Commit for 5.4-Kernel breaks xen Dom0
No, this bug is not fixed in 5.4.0-70. xen guests do not start with this kernel version. It seems this version has only the patches from 5.4.0-69 and 5.4.0-70 and NOT 5.4.0-68, see https://launchpad.net/ubuntu/+source/linux/5.4.0-70.78 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1920660 Title: Missing Commit for 5.4-Kernel breaks xen Dom0 Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.4 package in Ubuntu: Confirmed Bug description: You commited "xen: Fix event channel callback via INTX/GSI" for kernel 5.4.0-67 for HWE 18.04 and 20.04. This commit is incomplete and breaks Ubuntu as Dom0 for xen. You need also Commit "xen: Fix XenStore initialisation for XS_LOCAL" See https://lkml.org/lkml/2021/1/28/1235 See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915195 Upstream: Commit: 3499ba8198cad47b731792e5e56b9ec2a78a83a2 Fixing Commit: 5f46400f7a6a4fad635d5a79e2aa5a04a30ffea1 5.10: Commit: fa5f2e04daa44961a1026e93f0cc88caa3c27d3d (5.10.11) Fixing Commit: 5f3d54c00f1f2682cee9c590c22655b0330ffd18 (5.10.13) 5.4: Commit: a09d4e7acdbf276b2096661ee82454ae3dd24d2b (5.4.93) Fixing commit 2c7b4b25293aebd2563188f7196f6e0ff0cb0f9f (5.4.95) Without this patch you cannot start guests (DomU) on this machine! Error message while creating DomU: libxl: error: libxl_device.c:1105:device_backend_callback: Domain X:unable to add device with path / libxl: error: libxl_create.c:1452:domcreate_launch_dm: Domain X:unable to add disk devices See: - https://lkml.org/lkml/2021/1/28/1231 and https://lkml.org/lkml/2021/1/29/14 - https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.4.107=2c7b4b25293aebd2563188f7196f6e0ff0cb0f9f - https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.4.95 - http://changelogs.ubuntu.com/changelogs/pool/main/l/linux-hwe-5.4/linux-hwe-5.4_5.4.0-67.75~18.04.1/changelog - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915195 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1920660/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1920660] Re: Missing Commit for 5.4-Kernel breaks xen Dom0
** Also affects: linux-hwe-5.4 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1920660 Title: Missing Commit for 5.4-Kernel breaks xen Dom0 Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.4 package in Ubuntu: New Bug description: You commited "xen: Fix event channel callback via INTX/GSI" for kernel 5.4.0-67 for HWE 18.04 and 20.04. This commit is incomplete and breaks Ubuntu as Dom0 for xen. You need also Commit "xen: Fix XenStore initialisation for XS_LOCAL" See https://lkml.org/lkml/2021/1/28/1235 See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915195 Upstream: Commit: 3499ba8198cad47b731792e5e56b9ec2a78a83a2 Fixing Commit: 5f46400f7a6a4fad635d5a79e2aa5a04a30ffea1 5.10: Commit: fa5f2e04daa44961a1026e93f0cc88caa3c27d3d (5.10.11) Fixing Commit: 5f3d54c00f1f2682cee9c590c22655b0330ffd18 (5.10.13) 5.4: Commit: a09d4e7acdbf276b2096661ee82454ae3dd24d2b (5.4.93) Fixing commit 2c7b4b25293aebd2563188f7196f6e0ff0cb0f9f (5.4.95) Without this patch you cannot start guests (DomU) on this machine! Error message while creating DomU: libxl: error: libxl_device.c:1105:device_backend_callback: Domain X:unable to add device with path / libxl: error: libxl_create.c:1452:domcreate_launch_dm: Domain X:unable to add disk devices See: - https://lkml.org/lkml/2021/1/28/1231 and https://lkml.org/lkml/2021/1/29/14 - https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.4.107=2c7b4b25293aebd2563188f7196f6e0ff0cb0f9f - https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.4.95 - http://changelogs.ubuntu.com/changelogs/pool/main/l/linux-hwe-5.4/linux-hwe-5.4_5.4.0-67.75~18.04.1/changelog - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915195 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1920660/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1920660] Re: Missing Commit for 5.4-Kernel breaks xen Dom0
The commit is missing so you do not need not our server data. => Confirmed ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1920660 Title: Missing Commit for 5.4-Kernel breaks xen Dom0 Status in linux package in Ubuntu: Confirmed Bug description: You commited "xen: Fix event channel callback via INTX/GSI" for kernel 5.4.0-67 for HWE 18.04 and 20.04. This commit is incomplete and breaks Ubuntu as Dom0 for xen. You need also Commit "xen: Fix XenStore initialisation for XS_LOCAL" See https://lkml.org/lkml/2021/1/28/1235 See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915195 Upstream: Commit: 3499ba8198cad47b731792e5e56b9ec2a78a83a2 Fixing Commit: 5f46400f7a6a4fad635d5a79e2aa5a04a30ffea1 5.10: Commit: fa5f2e04daa44961a1026e93f0cc88caa3c27d3d (5.10.11) Fixing Commit: 5f3d54c00f1f2682cee9c590c22655b0330ffd18 (5.10.13) 5.4: Commit: a09d4e7acdbf276b2096661ee82454ae3dd24d2b (5.4.93) Fixing commit 2c7b4b25293aebd2563188f7196f6e0ff0cb0f9f (5.4.95) Without this patch you cannot start guests (DomU) on this machine! Error message while creating DomU: libxl: error: libxl_device.c:1105:device_backend_callback: Domain X:unable to add device with path / libxl: error: libxl_create.c:1452:domcreate_launch_dm: Domain X:unable to add disk devices See: - https://lkml.org/lkml/2021/1/28/1231 and https://lkml.org/lkml/2021/1/29/14 - https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.4.107=2c7b4b25293aebd2563188f7196f6e0ff0cb0f9f - https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.4.95 - http://changelogs.ubuntu.com/changelogs/pool/main/l/linux-hwe-5.4/linux-hwe-5.4_5.4.0-67.75~18.04.1/changelog - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915195 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1920660/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1920660] [NEW] Missing Commit for 5.4-Kernel breaks xen Dom0
Public bug reported: You commited "xen: Fix event channel callback via INTX/GSI" for kernel 5.4.0-67 for HWE 18.04 and 20.04. This commit is incomplete and breaks Ubuntu as Dom0 for xen. You need also Commit "xen: Fix XenStore initialisation for XS_LOCAL" See https://lkml.org/lkml/2021/1/28/1235 See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915195 Upstream: Commit: 3499ba8198cad47b731792e5e56b9ec2a78a83a2 Fixing Commit: 5f46400f7a6a4fad635d5a79e2aa5a04a30ffea1 5.10: Commit: fa5f2e04daa44961a1026e93f0cc88caa3c27d3d (5.10.11) Fixing Commit: 5f3d54c00f1f2682cee9c590c22655b0330ffd18 (5.10.13) 5.4: Commit: a09d4e7acdbf276b2096661ee82454ae3dd24d2b (5.4.93) Fixing commit 2c7b4b25293aebd2563188f7196f6e0ff0cb0f9f (5.4.95) Without this patch you cannot start guests (DomU) on this machine! Error message while creating DomU: libxl: error: libxl_device.c:1105:device_backend_callback: Domain X:unable to add device with path / libxl: error: libxl_create.c:1452:domcreate_launch_dm: Domain X:unable to add disk devices See: - https://lkml.org/lkml/2021/1/28/1231 and https://lkml.org/lkml/2021/1/29/14 - https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.4.107=2c7b4b25293aebd2563188f7196f6e0ff0cb0f9f - https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.4.95 - http://changelogs.ubuntu.com/changelogs/pool/main/l/linux-hwe-5.4/linux-hwe-5.4_5.4.0-67.75~18.04.1/changelog - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915195 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Missing Commit for 5.4-Kernel breaks dom0 + Missing Commit for 5.4-Kernel breaks xen Dom0 ** Description changed: - Your commited "xen: Fix event channel callback via INTX/GSI" for kernel 5.4.0-67 for HWE 18.04 and 20.04. + You commited "xen: Fix event channel callback via INTX/GSI" for kernel 5.4.0-67 for HWE 18.04 and 20.04. This commit is incomplete and breaks Ubuntu as Dom0 for xen. You need also Commit "xen: Fix XenStore initialisation for XS_LOCAL" + See https://lkml.org/lkml/2021/1/28/1235 See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915195 Upstream: Commit: 3499ba8198cad47b731792e5e56b9ec2a78a83a2 - Fixing Commit: 5f46400f7a6a4fad635d5a79e2aa5a04a30ffea1 + Fixing Commit: 5f46400f7a6a4fad635d5a79e2aa5a04a30ffea1 5.10: Commit: fa5f2e04daa44961a1026e93f0cc88caa3c27d3d (5.10.11) Fixing Commit: 5f3d54c00f1f2682cee9c590c22655b0330ffd18 (5.10.13) 5.4: Commit: a09d4e7acdbf276b2096661ee82454ae3dd24d2b (5.4.93) Fixing commit 2c7b4b25293aebd2563188f7196f6e0ff0cb0f9f (5.4.95) - Without this patch you cannot start guests (DomU) on this machine! Error message while creating DomU: libxl: error: libxl_device.c:1105:device_backend_callback: Domain X:unable to add device with path / libxl: error: libxl_create.c:1452:domcreate_launch_dm: Domain X:unable to add disk devices - See: - https://lkml.org/lkml/2021/1/28/1231 and https://lkml.org/lkml/2021/1/29/14 - https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.4.107=2c7b4b25293aebd2563188f7196f6e0ff0cb0f9f - https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.4.95 - http://changelogs.ubuntu.com/changelogs/pool/main/l/linux-hwe-5.4/linux-hwe-5.4_5.4.0-67.75~18.04.1/changelog - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915195 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1920660 Title: Missing Commit for 5.4-Kernel breaks xen Dom0 Status in linux package in Ubuntu: New Bug description: You commited "xen: Fix event channel callback via INTX/GSI" for kernel 5.4.0-67 for HWE 18.04 and 20.04. This commit is incomplete and breaks Ubuntu as Dom0 for xen. You need also Commit "xen: Fix XenStore initialisation for XS_LOCAL" See https://lkml.org/lkml/2021/1/28/1235 See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915195 Upstream: Commit: 3499ba8198cad47b731792e5e56b9ec2a78a83a2 Fixing Commit: 5f46400f7a6a4fad635d5a79e2aa5a04a30ffea1 5.10: Commit: fa5f2e04daa44961a1026e93f0cc88caa3c27d3d (5.10.11) Fixing Commit: 5f3d54c00f1f2682cee9c590c22655b0330ffd18 (5.10.13) 5.4: Commit: a09d4e7acdbf276b2096661ee82454ae3dd24d2b (5.4.93) Fixing commit 2c7b4b25293aebd2563188f7196f6e0ff0cb0f9f (5.4.95) Without this patch you cannot start guests (DomU) on this machine! Error message while creating DomU: libxl: error: libxl_device.c:1105:device_backend_callback: Domain X:unable to add device with path / libxl: error: libxl_create.c:1452:domcreate_launch_dm: Domain X:unable to add disk devices See: - https://lkml.org/lkml/2021/1/28/1231 and https://lkml.org/lkml/2021/1/29/14 - https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.4.107=2c7b4b25293aebd2563188f7196f6e0ff0cb0f9f -
[Kernel-packages] [Bug 1829378] Re: Kernel 4.15.0-50 or newer wont boot as Xen-DomU with PVH
Tested the proposed Kernel 4.15.0-56 and could boot as PVH-Guest.
Changed Tag to verification-done-xenial.
** Tags removed: verification-done-bionic verification-needed-xenial
** Tags added: verification-done-xenial
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1829378
Title:
Kernel 4.15.0-50 or newer wont boot as Xen-DomU with PVH
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Bionic:
Fix Committed
Bug description:
=== SRU Justification ===
[Impact]
NULL pointer dereference in acpi_quirk_matches_bios_ids() renders kernel
unbootable.
[Fix]
It's a regression caused by commit abd273f52766 ("UBUNTU: SAUCE: ACPI /
bus: Add some Lenovo laptops in list of acpi table term list").
When both bios_vendor and bios_ver are NULL then a NULL string is passed
to strncmp() and the issue occurs.
VMs may not provides string bios_vendor or bios_ver, so bail out early
when either bios_vendor or bios_ver is NULL.
[Test]
User reported the test kernel with proposed fix solves the issue.
[Regression Potenial]
Low. It's quite trivial so I don't think it'll regress anything.
=== Original Bug Report ===
After upgrading HWE-16.04-kernel from 4.15.0-48 to 4.15.0-50 the kernel
crashes while booting as PVH-Guest with Xen 4.12 (booting as PV works).
Kernel 4.15.0-48 and prior did boot without any problems as PVH.
We have the same problem for Ubuntu 18.04 with Kernel 4.15.0-50.
Ubunutu 18.04 with HWE-Kernel 4.18.0-20 boots without problems as PVH-
DomU.
See also https://lists.xenproject.org/archives/html/xen-
users/2019-05/msg00010.html
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829378/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829378] Re: Kernel 4.15.0-50 or newer wont boot as Xen-DomU with PVH
Tested the proposed Kernel 4.15.0-56 and could boot as PVH-Guest.
Changed Tag to verification-done-bionic.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1829378
Title:
Kernel 4.15.0-50 or newer wont boot as Xen-DomU with PVH
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Bionic:
Fix Committed
Bug description:
=== SRU Justification ===
[Impact]
NULL pointer dereference in acpi_quirk_matches_bios_ids() renders kernel
unbootable.
[Fix]
It's a regression caused by commit abd273f52766 ("UBUNTU: SAUCE: ACPI /
bus: Add some Lenovo laptops in list of acpi table term list").
When both bios_vendor and bios_ver are NULL then a NULL string is passed
to strncmp() and the issue occurs.
VMs may not provides string bios_vendor or bios_ver, so bail out early
when either bios_vendor or bios_ver is NULL.
[Test]
User reported the test kernel with proposed fix solves the issue.
[Regression Potenial]
Low. It's quite trivial so I don't think it'll regress anything.
=== Original Bug Report ===
After upgrading HWE-16.04-kernel from 4.15.0-48 to 4.15.0-50 the kernel
crashes while booting as PVH-Guest with Xen 4.12 (booting as PV works).
Kernel 4.15.0-48 and prior did boot without any problems as PVH.
We have the same problem for Ubuntu 18.04 with Kernel 4.15.0-50.
Ubunutu 18.04 with HWE-Kernel 4.18.0-20 boots without problems as PVH-
DomU.
See also https://lists.xenproject.org/archives/html/xen-
users/2019-05/msg00010.html
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829378/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829378] Re: Kernel 4.15.0-50 or newer wont boot as Xen-DomU with PVH
@kaihengfeng thank you very much! We can boot Ubuntu 16.04 with this kernel as PVH-xen-guest. > Booting paravirtualized kernel on Xen PVH tu ky. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829378 Title: Kernel 4.15.0-50 or newer wont boot as Xen-DomU with PVH Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: New Bug description: After upgrading HWE-16.04-kernel from 4.15.0-48 to 4.15.0-50 the kernel crashes while booting as PVH-Guest with Xen 4.12 (booting as PV works). Kernel 4.15.0-48 and prior did boot without any problems as PVH. We have the same problem for Ubuntu 18.04 with Kernel 4.15.0-50. Ubunutu 18.04 with HWE-Kernel 4.18.0-20 boots without problems as PVH- DomU. See also https://lists.xenproject.org/archives/html/xen- users/2019-05/msg00010.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829378/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829378] Re: Kernel 4.15.0-50 or newer wont boot as Xen-DomU with PVH
** Summary changed: - Kernel 4.15.0-50 wont boot as Xen-DomU with PVH + Kernel 4.15.0-50 or newer wont boot as Xen-DomU with PVH -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829378 Title: Kernel 4.15.0-50 or newer wont boot as Xen-DomU with PVH Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: New Bug description: After upgrading HWE-16.04-kernel from 4.15.0-48 to 4.15.0-50 the kernel crashes while booting as PVH-Guest with Xen 4.12 (booting as PV works). Kernel 4.15.0-48 and prior did boot without any problems as PVH. We have the same problem for Ubuntu 18.04 with Kernel 4.15.0-50. Ubunutu 18.04 with HWE-Kernel 4.18.0-20 boots without problems as PVH- DomU. See also https://lists.xenproject.org/archives/html/xen- users/2019-05/msg00010.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829378/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829378] Re: Kernel 4.15.0-50 wont boot as Xen-DomU with PVH
Sonmething new? Do you need further information? We tried kernel linux-image-4.15.0-54 and were not able to boot as pvh (xen buld from source 4.12-staging from today). linux-image-4.15.0-48 we are able to boot as pvh. Some patches between 4.15.0-48 and 4.15.0-50 destroyed the ability to boot as pvh. ky. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829378 Title: Kernel 4.15.0-50 wont boot as Xen-DomU with PVH Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: New Bug description: After upgrading HWE-16.04-kernel from 4.15.0-48 to 4.15.0-50 the kernel crashes while booting as PVH-Guest with Xen 4.12 (booting as PV works). Kernel 4.15.0-48 and prior did boot without any problems as PVH. We have the same problem for Ubuntu 18.04 with Kernel 4.15.0-50. Ubunutu 18.04 with HWE-Kernel 4.18.0-20 boots without problems as PVH- DomU. See also https://lists.xenproject.org/archives/html/xen- users/2019-05/msg00010.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829378/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1304001] Re: xen:balloon errors in 14.04 beta
Problem also without hvm: Kernels: Linux version 3.13.0-27-generic (buildd@akateko) (gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #50-Ubuntu SMP Thu May 15 18:06:16 UTC 2014 (Ubuntu 3.13.0-27.50-generic 3.13.11) Linux version 3.13.0-35-generic (buildd@panlong) (gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #62-Ubuntu SMP Fri Aug 15 01:58:42 UTC 2014 (Ubuntu 3.13.0-35.62-generic 3.13.11.6) CPU: 2x AMD Opteron(tm) Processor 4226 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1304001 Title: xen:balloon errors in 14.04 beta Status in “linux” package in Ubuntu: Confirmed Bug description: Xen balloon errors on HVM instances on EC2 (Xen 4.2.amazon): ubuntu@ip-10-63-20-99:~$ uname -a Linux ip-10-63-20-99 3.13.0-23-generic #45-Ubuntu SMP Fri Apr 4 06:58:38 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux ubuntu@ip-10-63-20-99:~$ dmesg |grep xen [0.00] xen:events: Xen HVM callback vector for event delivery is enabled [0.494613] xen:balloon: Initialising balloon driver [0.496046] xen_balloon: Initialising balloon driver [0.500077] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [0.541047] Switched to clocksource xen [0.562579] xen: -- pirq=16 - irq=8 (gsi=8) [0.562622] xen: -- pirq=17 - irq=12 (gsi=12) [0.562649] xen: -- pirq=18 - irq=1 (gsi=1) [0.562673] xen: -- pirq=19 - irq=6 (gsi=6) [0.562705] xen: -- pirq=20 - irq=4 (gsi=4) [0.920527] xen: -- pirq=21 - irq=47 (gsi=47) [0.920596] xen:grant_table: Grant tables using version 1 layout [1.029661] xen_netfront: Initialising Xen virtual ethernet driver [1.236083] xenbus_probe_frontend: Device with no driver: device/vfb/0 [2.516067] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [6.533941] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 14.560075] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 30.592064] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 62.688153] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 94.752164] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 126.816161] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 158.880084] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 190.944069] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 223.008141] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 255.072112] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 287.136190] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 319.200053] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 351.264164] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 383.328080] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 415.392077] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 447.456112] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 479.520128] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 511.584110] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 543.648181] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 575.712070] xen:balloon: reserve_additional_memory: add_memory() failed: -17 [ 607.776178] xen:balloon: reserve_additional_memory: add_memory() failed: -17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1304001/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1018561] Re: e1000e needs updating due to 82574L keeps dropping RX packets
I expected a patch in update or backport, not an expire. ** Changed in: linux (Ubuntu) Status: Expired = Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1018561 Title: e1000e needs updating due to 82574L keeps dropping RX packets Status in “linux” package in Ubuntu: Incomplete Bug description: Description:Ubuntu 12.04 LTS Release:12.04 Networking driver e1000e needs updating due to 82574L (and others?) keeps dropping RX packets. Information about how to fix it can be found here (http://www.doxer.org/learn-linux/resolved-intel-e1000e-driver-bug-on-82574l-ethernet-controller-causing-network-blipping/) but including it in the default kernel or official package would be preferable. This controller is popular in Supermicro servers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1018561/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
