[Bug 1955655] Re: kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted Virtualization( SEV) is enabled without setting swiotlb boot param
** Also affects: grub2 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: Confirmed ** Also affects: grub2 (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Impish) Status: New => Invalid ** Changed in: linux (Ubuntu Jammy) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955655 Title: kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted Virtualization( SEV) is enabled without setting swiotlb boot param To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1955655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955655] Re: kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted Virtualization( SEV) is enabled without setting swiotlb boot param
So testing with Fedora's boot/efi/EFI/fedora/grubx64.efi in place of the Ubuntu version solves the problem. So it is indeed the situation that you describe in comment #15 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955655 Title: kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted Virtualization( SEV) is enabled without setting swiotlb boot param To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1955655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955655] Re: kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted Virtualization( SEV) is enabled without setting swiotlb boot param
Hi xnox, Thanks for the reply. I'll test both options and report to you here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955655 Title: kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted Virtualization( SEV) is enabled without setting swiotlb boot param To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1955655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955395] Re: Jammy kernel does not boot when Secure Encrypted Virtualization( SEV) is enabled
Recent tests with the most recent 5.15 kernel (5.15.0-25-generic) do display the same problem, though the symptom is different. Booting w/o the swiotlb=262144 leads to the boot sequence stopping after these messages : [1.376749] i2c i2c-0: Memory type 0x07 not supported yet, not instantiating SPD [1.379840] cryptd: max_cpu_qlen set to 1000 [1.381359] scsi host1: ahci [1.384854] AVX2 version of gcm_enc/dec engaged. [1.385579] AES CTR mode by8 optimization enabled [1.386280] scsi host2: ahci [1.387162] scsi host3: ahci [1.387659] scsi host4: ahci [1.388141] scsi host5: ahci [1.388675] scsi host6: ahci [1.389091] ata1: SATA max UDMA/133 abar m4096@0x9100 port 0x91000100 irq 36 [1.389937] ata2: SATA max UDMA/133 abar m4096@0x9100 port 0x91000180 irq 36 [1.390787] ata3: SATA max UDMA/133 abar m4096@0x9100 port 0x91000200 irq 36 [1.391599] ata4: SATA max UDMA/133 abar m4096@0x9100 port 0x91000280 irq 36 [1.392417] ata5: SATA max UDMA/133 abar m4096@0x9100 port 0x91000300 irq 36 [1.393251] ata6: SATA max UDMA/133 abar m4096@0x9100 port 0x91000380 irq 36 [1.707933] ata3: SATA link down (SStatus 0 SControl 300) [1.709684] ata4: SATA link down (SStatus 0 SControl 300) [1.711379] ata5: SATA link down (SStatus 0 SControl 300) [1.712945] ata2: SATA link down (SStatus 0 SControl 300) [1.714405] ata1: SATA link down (SStatus 0 SControl 300) [1.715926] ata6: SATA link down (SStatus 0 SControl 300) [3.352937] pcieport :00:1e.0: pciehp: Slot(0): No device found [3.356935] pcieport :00:1e.2: pciehp: Slot(2): No device found [3.368942] pcieport :00:1e.1: pciehp: Slot(1): No device found [3.368958] pcieport :00:1e.3: pciehp: Slot(3): No device found [3.384970] pcieport :00:1e.4: pciehp: Slot(4): No device found [3.384991] pcieport :00:1e.6: pciehp: Slot(6): No device found [3.396926] pcieport :00:1e.5: pciehp: Slot(5): No device found [3.396957] pcieport :00:1e.7: pciehp: Slot(7): No device found And after a period of time we start seeing : [ 242.880954] INFO: task kworker/u16:0:8 blocked for more than 120 seconds. [ 242.882063] Not tainted 5.15.0-25-generic #25-Ubuntu [ 242.882895] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 242.884165] task:kworker/u16:0 state:D stack:0 pid:8 ppid: 2 flags:0x4000 [ 242.885520] Workqueue: events_unbound async_run_entry_fn [ 242.886383] Call Trace: [ 242.886783] [ 242.887133] __schedule+0x23d/0x590 [ 242.887716] schedule+0x4e/0xb0 [ 242.888221] async_synchronize_cookie_domain+0xcc/0x110 [ 242.889077] ? wait_woken+0x70/0x70
[Bug 1956575] Re: [Regression] Focal kernel 5.4.0-92.103 fails to boot when Secure Encrypted Virtualization(SEV) is enabled
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956575 Title: [Regression] Focal kernel 5.4.0-92.103 fails to boot when Secure Encrypted Virtualization(SEV) is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956575] Re: [Regression] Focal kernel 5.4.0-92.103 fails to boot when Secure Encrypted Virtualization(SEV) is enabled
Here is the result of a similar bisect on the bionic kernel : https://kernel.ubuntu.com/git/ubuntu/ubuntu- bionic.git/commit/?id=091554e4a5b2a7647830a1c7beea781148b51509 091554e4a5b2a7647830a1c7beea781148b51509 is the first bad commit commit 091554e4a5b2a7647830a1c7beea781148b51509 Author: Lenny Szubowicz Date: Tue Nov 30 12:04:00 2021 +0100 efi: Support for MOK variable config table BugLink: https://bugs.launchpad.net/bugs/1928679 Because of system-specific EFI firmware limitations, EFI volatile variables may not be capable of holding the required contents of the Machine Owner Key (MOK) certificate store when the certificate list grows above some size. Therefore, an EFI boot loader may pass the MOK certs via a EFI configuration table created specifically for this purpose to avoid this firmware limitation. An EFI configuration table is a much more primitive mechanism compared to EFI variables and is well suited for one-way passage of static information from a pre-OS environment to the kernel. This patch adds initial kernel support to recognize, parse, and validate the EFI MOK configuration table, where named entries contain the same data that would otherwise be provided in similarly named EFI variables. Additionally, this patch creates a sysfs binary file for each EFI MOK configuration table entry found. These files are read-only to root and are provided for use by user space utilities such as mokutil. A subsequent patch will load MOK certs into the trusted platform key ring using this infrastructure. Signed-off-by: Lenny Szubowicz Link: https://lore.kernel.org/r/20200905013107.10457-2-lszub...@redhat.com Signed-off-by: Ard Biesheuvel (cherry picked from commit 58c909022a5a56cd1d9e89c8c5461fd1f6a27bb5) Signed-off-by: Dimitri John Ledkov Acked-by: Thadeu Lima de Souza Cascardo Acked-by: Tim Gardner Signed-off-by: Kleber Sacilotto de Souza arch/x86/kernel/setup.c | 1 + drivers/firmware/efi/Makefile | 1 + drivers/firmware/efi/arm-init.c | 1 + drivers/firmware/efi/efi.c | 9 + drivers/firmware/efi/mokvar-table.c | 360 include/linux/efi.h | 34 6 files changed, 406 insertions(+) create mode 100644 drivers/firmware/efi/mokvar-table.c -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956575 Title:
[Bug 1956575] Re: [Regression] Focal kernel 5.4.0-92.103 fails to boot when Secure Encrypted Virtualization(SEV) is enabled
Hello @kmously, yes I am able to reproduce the same panic on 4.15.0-166. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956575 Title: [Regression] Focal kernel 5.4.0-92.103 fails to boot when Secure Encrypted Virtualization(SEV) is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956575] Re: [Regression] Focal kernel 5.4.0-92.103 fails to boot when Secure Encrypted Virtualization(SEV) is enabled
According to the following advisory[1] from HP, this is a known issue which is fixed upstream : "Advisory: Red Hat Enterprise Linux 8.3 - Guest Stops Responding at efi_mokvar_sysfs_init+0xa9/0x19d with AMD Secure Encrypted Virtualization (SEV) Enabled" The upstream fix cited in the article is the following : https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8d651ee9c71bb12fc0c8eb2786b66cbe5aa3e43b x86/ioremap: Map EFI-reserved memory as encrypted for SEV Adding this commit on top of kernel 5.4.0-92.103 does fix the booting issue. [1] https://support.hpe.com/hpesc/public/docDisplay?docId=a00119071en_us=en_US ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) 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/1956575 Title: [Regression] Focal kernel 5.4.0-92.103 fails to boot when Secure Encrypted Virtualization(SEV) is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956575] Re: [Regression] Focal kernel 5.4.0-92.103 fails to boot when Secure Encrypted Virtualization(SEV) is enabled
** Description changed: The latest Focal kernel (linux-image-5.4.0-92-generic) fails to boot when SEV is enabled. The kernel panics with the following backtrace : [1.531125] ledtrig-cpu: registered to indicate activity on CPUs [1.531760] EFI Variables Facility v0.08 2004-May-17 [1.532575] general protection fault: [#1] SMP NOPTI [1.533116] CPU: 11 PID: 1 Comm: swapper/0 Not tainted 5.4.157-debug6 #15 [1.533788] Hardware name: Scaleway SCW-ENT1-L, BIOS 0.0.0 02/06/2015 [1.534429] RIP: 0010:efi_mokvar_sysfs_init+0x9d/0x184 [1.534949] Code: 00 48 85 c0 0f 85 b3 00 00 00 48 c7 c7 b0 db e2 a1 41 bd f4 ff ff ff e8 98 90 16 ff e9 e6 00 00 00 48 85 d2 0f 85 a5 00 00 00 <80> 3b 00 0f 84 b5 00 00 00 48 85 db 0f 84 ac 00 00 00 48 8b 3d 85 [1.535120] RSP: 0018:b96e4001bdf8 EFLAGS: 00010202 [1.535120] RAX: b6262a23e510e179 RBX: b625e392251db281 RCX: [1.535120] RDX: b96e400cd000 RSI: 978437e5dc38 RDI: a2121860 [1.535120] RBP: b96e4001be10 R08: R09: 0228 [1.538947] R10: 0001 R11: R12: 978437e555a0 [1.538947] R13: R14: R15: [1.538947] FS: () GS:97843f6c() knlGS: [1.538947] CS: 0010 DS: ES: CR0: 80050033 [1.538947] CR2: CR3: 00080011a060a001 CR4: 00360ee0 [1.538947] Call Trace: [1.538947] ? efi_rci2_sysfs_init+0x29a/0x29a [1.538947] do_one_initcall+0x4a/0x200 [1.538947] kernel_init_freeable+0x1c0/0x263 [1.538947] ? rest_init+0xb0/0xb0 [1.538947] kernel_init+0xe/0x110 [1.538947] ret_from_fork+0x22/0x40 [1.538947] Modules linked in: [1.545871] ---[ end trace 815dc8177e65da02 ]--- [1.546328] RIP: 0010:efi_mokvar_sysfs_init+0x9d/0x184 [1.546872] Code: 00 48 85 c0 0f 85 b3 00 00 00 48 c7 c7 b0 db e2 a1 41 bd f4 ff ff ff e8 98 90 16 ff e9 e6 00 00 00 48 85 d2 0f 85 a5 00 00 00 <80> 3b 00 0f 84 b5 00 00 00 48 85 db 0f 84 ac 00 00 00 48 8b 3d 85 [1.548703] RSP: 0018:b96e4001bdf8 EFLAGS: 00010202 [1.549218] RAX: b6262a23e510e179 RBX: b625e392251db281 RCX: [1.549916] RDX: b96e400cd000 RSI: 978437e5dc38 RDI: a2121860 [1.550617] RBP: b96e4001be10 R08: R09: 0228 [1.551337] R10: 0001 R11: R12: 978437e555a0 [1.552036] R13: R14: R15: [1.552737] FS: () GS:97843f6c() knlGS: [1.553529] CS: 0010 DS: ES: CR0: 80050033 [1.554093] CR2: CR3: 00080011a060a001 CR4: 00360ee0 [1.554818] Kernel panic - not syncing: Attempted to kill init! exitcode=0x000b [1.555335] Kernel Offset: 0x1fa0 from 0x8100 (relocation range: 0x8000-0xbfff) [1.555335] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x000b ]--- - - - The previous kernel (linux-image-5.4.0-91-generic) boots correctly with SEV. + The previous kernel (linux-image-5.4.0-91-generic) boots correctly with + SEV. Bisection of the kernels b/w 5.4.0-91 and 5.4.0-92 identified the following commit as the source of regresssion : # git bisect good - Bisecting: 0 revisions left to test after this (roughly 1 step) - [5f79bc17fd8d078378a9f3c8773ebcb506cb6f40] Revert "UBUNTU: SAUCE: (lockdown) Make get_cert_list() not complain about cert lists that aren't present." + 7ca05228f713c24eb55574b36e32d9b54c5a1b76 is the first bad commit + commit 7ca05228f713c24eb55574b36e32d9b54c5a1b76 + Author: Lenny Szubowicz + Date: Fri Sep 4 21:31:05 2020 -0400 + + efi: Support for MOK variable config table + + BugLink: https://bugs.launchpad.net/bugs/1928679 + + ... Since the panic happens in very early stages of boot, no trace of the panic is present in the log files and apparently it is not possible to collect a kernel crash dump, the crashkernel has not been enabled yet. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956575 Title: [Regression] Focal kernel 5.4.0-92.103 fails to boot when Secure Encrypted Virtualization(SEV) is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956575] Re: [Regression] Focal kernel 5.4.0-92.103 fails to boot when Secure Encrypted Virtualization(SEV) is enabled
Details of the bisected commit : https://kernel.ubuntu.com/git/ubuntu/ubuntu- focal.git/commit/?id=5f79bc17fd8d078378a9f3c8773ebcb506cb6f40 Revert "UBUNTU: SAUCE: (lockdown) Make get_cert_list() not complain about cert lists that aren't present." BugLink: https://bugs.launchpad.net/bugs/1932029 This partially reverts commit f32d73b5b9b4d8cb8e64bf51091c971d05116d48. The reverted commit fixed stray warnings, and changed get_cert_list() function prototype (return rc, pass cert-list by reference). The stray warnings fix was incomplete, and was done again in mainline with a different change of get_cert_list() function prototype (return cert-list pointer, pass EFI error status by reference), which got also cherrypicked into Ubuntu kernel ending up with passing both cert-list & efi error status by reference. Cherrypicking both get_cert_list() function prototype changes is redundant, and prevents clean cherrypicks from mainline. Revert the get_cert_list() function prototype to the one in mainline. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956575 Title: [Regression] Focal kernel 5.4.0-92.103 fails to boot when Secure Encrypted Virtualization(SEV) is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956575] [NEW] [Regression] Focal kernel 5.4.0-92.103 fails to boot when Secure Encrypted Virtualization(SEV) is enabled
Public bug reported: The latest Focal kernel (linux-image-5.4.0-92-generic) fails to boot when SEV is enabled. The kernel panics with the following backtrace : [1.531125] ledtrig-cpu: registered to indicate activity on CPUs [1.531760] EFI Variables Facility v0.08 2004-May-17 [1.532575] general protection fault: [#1] SMP NOPTI [1.533116] CPU: 11 PID: 1 Comm: swapper/0 Not tainted 5.4.157-debug6 #15 [1.533788] Hardware name: Scaleway SCW-ENT1-L, BIOS 0.0.0 02/06/2015 [1.534429] RIP: 0010:efi_mokvar_sysfs_init+0x9d/0x184 [1.534949] Code: 00 48 85 c0 0f 85 b3 00 00 00 48 c7 c7 b0 db e2 a1 41 bd f4 ff ff ff e8 98 90 16 ff e9 e6 00 00 00 48 85 d2 0f 85 a5 00 00 00 <80> 3b 00 0f 84 b5 00 00 00 48 85 db 0f 84 ac 00 00 00 48 8b 3d 85 [1.535120] RSP: 0018:b96e4001bdf8 EFLAGS: 00010202 [1.535120] RAX: b6262a23e510e179 RBX: b625e392251db281 RCX: [1.535120] RDX: b96e400cd000 RSI: 978437e5dc38 RDI: a2121860 [1.535120] RBP: b96e4001be10 R08: R09: 0228 [1.538947] R10: 0001 R11: R12: 978437e555a0 [1.538947] R13: R14: R15: [1.538947] FS: () GS:97843f6c() knlGS: [1.538947] CS: 0010 DS: ES: CR0: 80050033 [1.538947] CR2: CR3: 00080011a060a001 CR4: 00360ee0 [1.538947] Call Trace: [1.538947] ? efi_rci2_sysfs_init+0x29a/0x29a [1.538947] do_one_initcall+0x4a/0x200 [1.538947] kernel_init_freeable+0x1c0/0x263 [1.538947] ? rest_init+0xb0/0xb0 [1.538947] kernel_init+0xe/0x110 [1.538947] ret_from_fork+0x22/0x40 [1.538947] Modules linked in: [1.545871] ---[ end trace 815dc8177e65da02 ]--- [1.546328] RIP: 0010:efi_mokvar_sysfs_init+0x9d/0x184 [1.546872] Code: 00 48 85 c0 0f 85 b3 00 00 00 48 c7 c7 b0 db e2 a1 41 bd f4 ff ff ff e8 98 90 16 ff e9 e6 00 00 00 48 85 d2 0f 85 a5 00 00 00 <80> 3b 00 0f 84 b5 00 00 00 48 85 db 0f 84 ac 00 00 00 48 8b 3d 85 [1.548703] RSP: 0018:b96e4001bdf8 EFLAGS: 00010202 [1.549218] RAX: b6262a23e510e179 RBX: b625e392251db281 RCX: [1.549916] RDX: b96e400cd000 RSI: 978437e5dc38 RDI: a2121860 [1.550617] RBP: b96e4001be10 R08: R09: 0228 [1.551337] R10: 0001 R11: R12: 978437e555a0 [1.552036] R13: R14: R15: [1.552737] FS: () GS:97843f6c() knlGS: [1.553529] CS: 0010 DS: ES: CR0: 80050033 [1.554093] CR2: CR3: 00080011a060a001 CR4: 00360ee0 [1.554818] Kernel panic - not syncing: Attempted to kill init! exitcode=0x000b [1.555335] Kernel Offset: 0x1fa0 from 0x8100 (relocation range: 0x8000-0xbfff) [1.555335] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x000b ]--- - The previous kernel (linux-image-5.4.0-91-generic) boots correctly with SEV. Bisection of the kernels b/w 5.4.0-91 and 5.4.0-92 identified the following commit as the source of regresssion : # git bisect good Bisecting: 0 revisions left to test after this (roughly 1 step) [5f79bc17fd8d078378a9f3c8773ebcb506cb6f40] Revert "UBUNTU: SAUCE: (lockdown) Make get_cert_list() not complain about cert lists that aren't present." Since the panic happens in very early stages of boot, no trace of the panic is present in the log files and apparently it is not possible to collect a kernel crash dump, the crashkernel has not been enabled yet. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: Confirmed ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Summary changed: - [Regression] Focal kernel 5.4.0-92.103 fails to boot when Secure Encrypted Virtualization(SEV) is enagbled + [Regression] Focal kernel 5.4.0-92.103 fails to boot when Secure Encrypted Virtualization(SEV) is enabled -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956575 Title: [Regression] Focal kernel 5.4.0-92.103 fails to boot when Secure Encrypted Virtualization(SEV) is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955655] Re: kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted Virtualization( SEV) is enabled without setting swiotlb boot param
Hello, The kernel panic occurs very early in the boot sequence, even before the root fs is mounted to capture the log. Here is the kenrel backtrace : [1.251773] Kernel panic - not syncing: Can not allocate SWIOTLB buffer earlier and can't now provide you with the DMA bounce buffer [1.253440] CPU: 2 PID: 212 Comm: systemd-udevd Not tainted 5.13.0-23-generic #23-Ubuntu [1.255022] Hardware name: Scaleway SCW-ENT1-S, BIOS 0.0.0 02/06/2015 [1.256228] Call Trace: [1.256697] show_stack+0x52/0x58 [1.257355] dump_stack+0x7d/0x9c [1.257989] panic+0x101/0x2e3 [1.258821] swiotlb_tbl_map_single.cold+0x57/0x7c [1.259750] swiotlb_map+0x61/0x240 [1.260428] dma_direct_map_page+0x115/0x1a0 [1.261255] dma_map_page_attrs+0x35/0x50 [1.262016] vring_map_one_sg+0x4c/0x50 [1.262787] virtqueue_add_split+0x23c/0x4a0 [1.263427] virtqueue_add_inbuf+0x48/0x50 [1.263909] virtscsi_kick_event.isra.0+0x8b/0xd0 [virtio_scsi] [1.264616] virtscsi_probe+0x31e/0x33b [virtio_scsi] [1.265216] virtio_dev_probe+0x163/0x220 [1.265683] really_probe+0x24b/0x4c0 [1.266134] driver_probe_device+0xf0/0x160 [1.266647] device_driver_attach+0xab/0xb0 [1.267188] __driver_attach+0xb2/0x140 [1.267648] ? device_driver_attach+0xb0/0xb0 [1.268163] bus_for_each_dev+0x7e/0xc0 [1.268620] driver_attach+0x1e/0x20 [1.269061] bus_add_driver+0x135/0x1f0 [1.269516] driver_register+0x95/0xf0 [1.269957] ? 0xc038e000 [1.270344] register_virtio_driver+0x20/0x30 [1.270885] init+0x8d/0x1000 [virtio_scsi] [1.271380] ? 0xc038e000 [1.271762] do_one_initcall+0x48/0x1d0 [1.272213] ? kmem_cache_alloc_trace+0xfb/0x240 [1.272759] do_init_module+0x62/0x290 [1.273199] load_module+0xa8f/0xb10 [1.273620] __do_sys_finit_module+0xc2/0x120 [1.274155] __x64_sys_finit_module+0x18/0x20 [1.274680] do_syscall_64+0x61/0xb0 [1.275118] ? syscall_exit_to_user_mode+0x27/0x50 [1.275667] ? __x64_sys_newfstatat+0x1c/0x20 [1.276177] ? do_syscall_64+0x6e/0xb0 [1.276614] ? ksys_read+0x67/0xe0 [1.277049] ? exit_to_user_mode_prepare+0x37/0xb0 [1.277614] ? syscall_exit_to_user_mode+0x27/0x50 [1.278180] ? __x64_sys_read+0x19/0x20 [1.278653] ? do_syscall_64+0x6e/0xb0 [1.279116] entry_SYSCALL_64_after_hwframe+0x44/0xae [1.279709] RIP: 0033:0x7fe040ccd94d [1.280140] Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d b3 64 0f 00 f7 d8 64 89 01 48 [1.282337] RSP: 002b:7ffe2399a6d8 EFLAGS: 0246 ORIG_RAX: 0139 [1.283252] RAX: ffda RBX: 562e8ab7a030 RCX: 7fe040ccd94d [1.284077] RDX: RSI: 7fe040e61441 RDI: 0005 [1.284910] RBP: 0002 R08: R09: 7ffe2399a810 [1.285754] R10: 0005 R11: 0246 R12: 7fe040e61441 [1.286594] R13: 562e8ab79ef0 R14: 562e8abd1c50 R15: 562e8abd4400 [1.288517] Kernel Offset: 0x25a0 from 0x8100 (relocation range: 0x8000-0xbfff) [1.289795] ---[ end Kernel panic - not syncing: Can not allocate SWIOTLB buffer earlier and can't now provide you with the DMA bounce buffer ]--- - -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955655 Title: kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted Virtualization( SEV) is enabled without setting swiotlb boot param To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955655] Re: kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted Virtualization( SEV) is enabled without setting swiotlb boot param
As a complement of information, here are the messages pertaining to the TLB during the log : $ grep -i tlb swiotlb_crash.out [0.003802] software IO TLB: SWIOTLB bounce buffer size adjusted to 1024MB [0.037784] kvm-guest: KVM setup pv remote TLB flush [0.040674] software IO TLB: Cannot allocate buffer [0.229918] Last level iTLB entries: 4KB 512, 2MB 255, 4MB 127 [0.230877] Last level dTLB entries: 4KB 512, 2MB 255, 4MB 127, 1GB 0 [0.322941] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages [0.324641] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages [0.799064] PCI-DMA: Using software bounce buffering for IO (SWIOTLB) [0.800761] software IO TLB: No low mem [1.251773] Kernel panic - not syncing: Can not allocate SWIOTLB buffer earlier and can't now provide you with the DMA bounce buffer [1.258821] swiotlb_tbl_map_single.cold+0x57/0x7c [1.259750] swiotlb_map+0x61/0x240 [1.289795] ---[ end Kernel panic - not syncing: Can not allocate SWIOTLB buffer earlier and can't now provide you with the DMA bounce buffer ]--- -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955655 Title: kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted Virtualization( SEV) is enabled without setting swiotlb boot param To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955655] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1955655/+attachment/5549376/+files/acpidump.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955655 Title: kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted Virtualization( SEV) is enabled without setting swiotlb boot param To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955655] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1955655/+attachment/5549375/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955655 Title: kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted Virtualization( SEV) is enabled without setting swiotlb boot param To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955655] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1955655/+attachment/5549374/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955655 Title: kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted Virtualization( SEV) is enabled without setting swiotlb boot param To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955655] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1955655/+attachment/5549373/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955655 Title: kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted Virtualization( SEV) is enabled without setting swiotlb boot param To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955655] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1955655/+attachment/5549372/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955655 Title: kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted Virtualization( SEV) is enabled without setting swiotlb boot param To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955655] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1955655/+attachment/5549371/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955655 Title: kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted Virtualization( SEV) is enabled without setting swiotlb boot param To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955655] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1955655/+attachment/5549370/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955655 Title: kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted Virtualization( SEV) is enabled without setting swiotlb boot param To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955655] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1955655/+attachment/5549369/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955655 Title: kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted Virtualization( SEV) is enabled without setting swiotlb boot param To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955655] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1955655/+attachment/5549368/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955655 Title: kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted Virtualization( SEV) is enabled without setting swiotlb boot param To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955655] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1955655/+attachment/5549367/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955655 Title: kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted Virtualization( SEV) is enabled without setting swiotlb boot param To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955655] [NEW] kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted Virtualization( SEV) is enabled without setting swiotlb boot param
Public bug reported: While investigating LP: #1955395 by using the -generic kernel image, it appeared that it is impossible to boot the kernel unless the boot parameter swiotlb is set to 512M (swiotlb=262144). Wnen not set, the kernel tries to adjust the bounce buffer to 1024Mb it fails and later trigger a kernel panic with the following trace : $ grep TLB /tmp/console.log [0.003665] software IO TLB: SWIOTLB bounce buffer size adjusted to 1024MB [0.034219] kvm-guest: KVM setup pv remote TLB flush [0.037063] software IO TLB: Cannot allocate buffer [0.223009] Last level iTLB entries: 4KB 512, 2MB 255, 4MB 127 [0.223634] Last level dTLB entries: 4KB 512, 2MB 255, 4MB 127, 1GB 0 [0.297424] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages [0.297424] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages [1.018860] PCI-DMA: Using software bounce buffering for IO (SWIOTLB) [1.019552] software IO TLB: No low mem [1.451497] Kernel panic - not syncing: Can not allocate SWIOTLB buffer earlier and can't now provide you with the DMA bounce buffer [1.491589] ---[ end Kernel panic - not syncing: Can not allocate SWIOTLB buffer earlier and can't now provide you with the DMA bounce buffer ]--- The SWIOTLB adjustment comes from the following kernel commit : https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e998879d4fb7991856916972168cf27c0d86ed12 For some reason, the LowMem allocation fails (as seen by the "software IO TLB: No low mem" msg),hence the SWIOTLB adjustment cannot be completed. When booting with the swiotlb=262144 value, we get the following output : $ grep TLB /tmp/console.log [0.050908] kvm-guest: KVM setup pv remote TLB flush [0.308896] Last level iTLB entries: 4KB 512, 2MB 255, 4MB 127 [0.309494] Last level dTLB entries: 4KB 512, 2MB 255, 4MB 127, 1GB 0 [0.373162] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages [0.373162] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages [1.071136] PCI-DMA: Using software bounce buffering for IO (SWIOTLB) [1.071837] software IO TLB: mapped [mem 0x5bebe000-0x7bebe000] (512MB) [1.529804] software IO TLB: Memory encryption is active and system is using DMA bounce buffers For comparaison, the Fedora 34 kernel (5.15.4-101.fc34.x86_64) with the same adjustment mechanism does correctly adjust the SWIOTLB bounce buffer, without the need to set the swiotlb= value at boot time. The SWIOTLB buffer adjustment has been introduced in kernel 5.11. We can make SEV enabled resources available for testing if needed. ...Louis --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 23 13:32 seq crw-rw 1 root audio 116, 33 Dec 23 13:32 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Scaleway SCW-ENT1-S Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic root=UUID=1f577236-6bf2-48ef-998a-ba45f71aca7f ro console=tty1 console=ttyS0 swiotlb=262144 ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-23-generic N/A linux-backports-modules-5.13.0-23-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 5.13.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 02/06/2015 dmi.bios.release: 0.0 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-3.0 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnScaleway:pnSCW-ENT1-S:pvrpc-q35-3.0:cvnQEMU:ct1:cvrpc-q35-3.0:sku: dmi.product.name: SCW-ENT1-S dmi.product.version: pc-q35-3.0 dmi.sys.vendor: Scaleway ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: apport-collected jammy uec-images ** Tags added: apport-collected jammy uec-images ** Description changed: While investigating LP: #1955395 by using the -generic kernel image, it appeared that it is impossible to boot the kernel unless the boot parameter swiotlb is set to 512M (swiotlb=262144).
[Bug 1955395] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1955395/+attachment/5548709/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955395 Title: KVM flavor of Jammy kernel 5.13 does not boot when Secure Encrypted Virtualization( SEV) is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955395] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1955395/+attachment/5548710/+files/acpidump.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955395 Title: KVM flavor of Jammy kernel 5.13 does not boot when Secure Encrypted Virtualization( SEV) is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955395] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1955395/+attachment/5548708/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955395 Title: KVM flavor of Jammy kernel 5.13 does not boot when Secure Encrypted Virtualization( SEV) is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955395] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1955395/+attachment/5548707/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955395 Title: KVM flavor of Jammy kernel 5.13 does not boot when Secure Encrypted Virtualization( SEV) is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955395] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1955395/+attachment/5548706/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955395 Title: KVM flavor of Jammy kernel 5.13 does not boot when Secure Encrypted Virtualization( SEV) is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955395] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1955395/+attachment/5548705/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955395 Title: KVM flavor of Jammy kernel 5.13 does not boot when Secure Encrypted Virtualization( SEV) is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955395] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1955395/+attachment/5548704/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955395 Title: KVM flavor of Jammy kernel 5.13 does not boot when Secure Encrypted Virtualization( SEV) is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955395] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1955395/+attachment/5548703/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955395 Title: KVM flavor of Jammy kernel 5.13 does not boot when Secure Encrypted Virtualization( SEV) is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955395] Re: KVM flavor of Jammy kernel 5.13 does not boot when Secure Encrypted Virtualization( SEV) is enabled
apport information ** Changed in: linux (Ubuntu Jammy) Status: Incomplete => Confirmed ** Tags added: apport-collected uec-images ** Description changed: Booting the latest Jammy Ubuntu Cloud Image which embark the -kvm flavor of the kernel does not boot on a QEMU server with Secure Encrypted Virtualization( SEV) enabled. Using the same kernel without the -kvm optimisation does boot correctly + --- + ProblemType: Bug + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 Dec 20 10:41 seq + crw-rw 1 root audio 116, 33 Dec 20 10:41 timer + AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' + ApportVersion: 2.20.11-0ubuntu74 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + CRDA: N/A + CasperMD5CheckResult: unknown + DistroRelease: Ubuntu 22.04 + IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' + Lsusb: Error: command ['lsusb'] failed with exit code 1: + Lsusb-t: + + Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: + MachineType: Scaleway SCW-ENT1-XL + Package: linux (not installed) + PciMultimedia: + + ProcEnviron: + TERM=screen + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=C.UTF-8 + SHELL=/bin/bash + ProcFB: + + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic root=UUID=1f577236-6bf2-48ef-998a-ba45f71aca7f ro console=tty1 console=ttyS0 swiotlb=262144 + ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19 + RelatedPackageVersions: + linux-restricted-modules-5.13.0-23-generic N/A + linux-backports-modules-5.13.0-23-generic N/A + linux-firmware N/A + RfKill: Error: [Errno 2] No such file or directory: 'rfkill' + Tags: jammy uec-images + Uname: Linux 5.13.0-23-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: N/A + _MarkForUpload: True + dmi.bios.date: 02/06/2015 + dmi.bios.release: 0.0 + dmi.bios.vendor: EFI Development Kit II / OVMF + dmi.bios.version: 0.0.0 + dmi.chassis.type: 1 + dmi.chassis.vendor: QEMU + dmi.chassis.version: pc-q35-3.0 + dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnScaleway:pnSCW-ENT1-XL:pvrpc-q35-3.0:cvnQEMU:ct1:cvrpc-q35-3.0:sku: + dmi.product.name: SCW-ENT1-XL + dmi.product.version: pc-q35-3.0 + dmi.sys.vendor: Scaleway ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1955395/+attachment/5548701/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955395 Title: KVM flavor of Jammy kernel 5.13 does not boot when Secure Encrypted Virtualization( SEV) is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955395] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1955395/+attachment/5548702/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955395 Title: KVM flavor of Jammy kernel 5.13 does not boot when Secure Encrypted Virtualization( SEV) is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955395] Re: KVM flavor of Jammy kernel 5.13 does not boot when Secure Encrypted Virtualization( SEV) is enabled
** Attachment added: "version.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955395/+attachment/5548694/+files/version.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955395 Title: KVM flavor of Jammy kernel 5.13 does not boot when Secure Encrypted Virtualization( SEV) is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955395] Re: KVM flavor of Jammy kernel 5.13 does not boot when Secure Encrypted Virtualization( SEV) is enabled
** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955395/+attachment/5548693/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955395 Title: KVM flavor of Jammy kernel 5.13 does not boot when Secure Encrypted Virtualization( SEV) is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955395] [NEW] KVM flavor of Jammy kernel 5.13 does not boot when Secure Encrypted Virtualization( SEV) is enabled
Public bug reported: Booting the latest Jammy Ubuntu Cloud Image which embark the -kvm flavor of the kernel does not boot on a QEMU server with Secure Encrypted Virtualization( SEV) enabled. Using the same kernel without the -kvm optimisation does boot correctly ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: Incomplete ** Tags: jammy ** Also affects: linux (Ubuntu Jammy) 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/1955395 Title: KVM flavor of Jammy kernel 5.13 does not boot when Secure Encrypted Virtualization( SEV) is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929255] Re: update-initrd-links creates incorrect symlinks
** Also affects: linux-base (Ubuntu Bionic) 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/1929255 Title: update-initrd-links creates incorrect symlinks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1929255/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915509] Re: QEMU 1:4.2-3ubuntu6.12 : Unable to start SEV enabled VM using virtio driver
Hello, After much digging and searching the internet, I have found what needs to be used to get IOMMU enabled and, hence start a SEV vm using VIRTIO : -device virtio-blk-pci,drive=drive0,id=virblk0,num-queues=4,disable-modern=off,disable-legacy=on,iommu_platform=on \ -drive file=/var/lib/libvirt/images/real-qemu.qcow2,if=none,id=drive0 \ The addition of disable-modern=off,disable-legacy=on does the trick ! Thanks for your suggestions. ...Louis ** Changed in: qemu (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915509 Title: QEMU 1:4.2-3ubuntu6.12 : Unable to start SEV enabled VM using virtio driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1915509/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915509] [NEW] QEMU 1:4.2-3ubuntu6.12 : Unable to start SEV enabled VM using virtio driver
Public bug reported: When using the VIRTIO driver, starting a VM with SEV enabled on sev enabled hardware fails. The situation may be tested with the following commands : $ dd if=/dev/urandom of=/tmp/sev_key.aes bs=8 count=4 $ cp /usr/share/OVMF/OVMF_CODE.fd /tmp $ cp /usr/share/OVMF/OVMF_VARS.fd /tmp $ qemu-system-x86_64 -name real-qemu \ -machine pc-q35-3.0,accel=kvm,usb=off,vmport=off,dump-guest-core=off,memory-encryption=sev0 \ -display none \ -monitor none \ -nographic \ -nodefaults \ -m 16384.0M \ -serial mon:stdio \ -smp 2 \ -cpu host \ -device sga \ -device pcie-root-port,port=0x10,chassis=1,id=pci.1,bus=pcie.0,multifunction=on,addr=0x2 \ -netdev user,id=net0,net=192.168.100.0/24,dhcpstart=192.168.100.1 \ -device virtio-net-pci,netdev=net0,id=net0,mac=52:54:00:cc:56:90,bus=pci.1,addr=0x0,romfile=,iommu_platform=on \ -drive if=pflash,format=raw,readonly,file=/tmp/OVMF_CODE.fd \ -drive if=pflash,format=raw,file=/tmp/OVMF_VARS.fd \ -drive file=/var/lib/libvirt/images/real-qemu.qcow2,if=virtio,id=disk0 \ -object sev-guest,id=sev0,cbitpos=47,reduced-phys-bits=1,policy=0x3 \ -object secret,id=masterKey0,format=raw,file=/tmp/sev_key.aes The output when starting the VM shows : qemu-system-x86_64: Guest says index 53230 is available When running the same script using the 'ide' driver instead of the 'virtio' driver, the VM starts correctly : root@ubuntu:~# dmesg | grep -i sev [0.243361] AMD Secure Encrypted Virtualization (SEV) active There is a mention in the libvirt knowledge base documentation about the requirement to use IOMMU to make the virtio work (https://libvirt.org/kbase/launch_security_sev.html#virtio) so another test was to enable IOMMU : $ qemu-system-x86_64 -name real-qemu \ -machine pc-q35-3.0,accel=kvm,usb=off,vmport=off,dump-guest-core=off,memory-encryption=sev0 \ -display none \ -monitor none \ -nographic \ -nodefaults \ -m 16384.0M \ -serial mon:stdio \ -smp 2 \ -cpu host \ -device sga \ -device pcie-root-port,port=0x10,chassis=1,id=pci.1,bus=pcie.0,multifunction=on,addr=0x2 \ -netdev user,id=net0,net=192.168.100.0/24,dhcpstart=192.168.100.1 \ -device virtio-net-pci,netdev=net0,id=net0,mac=52:54:00:cc:56:90,bus=pci.1,addr=0x0,romfile=,iommu_platform=on \ -drive if=pflash,format=raw,readonly,file=/tmp/OVMF_CODE.fd \ -drive if=pflash,format=raw,file=/tmp/OVMF_VARS.fd \ -device virtio-blk-pci,drive=drive0,id=virblk0,num-queues=4,iommu_platform=on \ -drive file=/var/lib/libvirt/images/real-qemu.qcow2,if=none,id=drive0 \ -object sev-guest,id=sev0,cbitpos=47,reduced-phys-bits=1,policy=0x3 \ -object secret,id=masterKey0,format=raw,file=/tmp/sev_key.aes This also fails and issues the following error message : qemu-system-x86_64: -device virtio-blk-pci,drive=drive0,id=virblk0,num-queues=4,iommu_platform=on: VIRTIO_F_IOMMU_PLATFORM was supported by neither legacy nor transitional device Is it possible to use SEV in conjunction with the VIRTIO driver ? ** Affects: qemu (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/1915509 Title: QEMU 1:4.2-3ubuntu6.12 : Unable to start SEV enabled VM using virtio driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1915509/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880522] Re: CONFIG_NF_TABLES is not enabled in linux-image-5.4.0-1009-kvm
Hello, Sorry to switch this bug back to Confirmed, but the fix that you mention is clearly not present in the latest kernel available in Focal : root@launchpad-kernel:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04 LTS Release:20.04 Codename: focal root@launchpad-kernel:~# uname -a Linux launchpad-kernel 5.4.0-1030-kvm #31-Ubuntu SMP Wed Dec 9 17:27:05 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux root@launchpad-kernel:~# grep IP_VS /boot/config-5.4.0-1030-kvm # CONFIG_IP_VS is not set root@launchpad-kernel:~# modprobe ip_vs modprobe: FATAL: Module ip_vs not found in directory /lib/modules/5.4.0-1030-kvm -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880522 Title: CONFIG_NF_TABLES is not enabled in linux-image-5.4.0-1009-kvm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1880522/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880522] Re: CONFIG_NF_TABLES is not enabled in linux-image-5.4.0-1009-kvm
Hello again, Sorry for the noise, I blindly reported what one of our user told me without checking. Its problem is IP_VS which has nothing to do with this bug. Thanks for your help in fixing this and, once again sorry. ...Louis -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880522 Title: CONFIG_NF_TABLES is not enabled in linux-image-5.4.0-1009-kvm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1880522/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880522] Re: CONFIG_NF_TABLES is not enabled in linux-image-5.4.0-1009-kvm
Hello Stefan, Any hint on who could check on that ? What needs to be clarified is if this is a requirement and there to stay or not. Kind regards, ...Louis -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880522 Title: CONFIG_NF_TABLES is not enabled in linux-image-5.4.0-1009-kvm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1880522/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880522] [NEW] CONFIG_NF_TABLES is not enabled in linux-image-5.4.0-1009-kvm
Public bug reported: The NF_TABLES options are not included in the -kvm flavor of the 5.4 kernel. This package is used in the Ubuntu Cloud Image. The linux-image-5.4.0-31-generic package has the options present in the config file. ** 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/1880522 Title: CONFIG_NF_TABLES is not enabled in linux-image-5.4.0-1009-kvm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880522/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873809] Re: Make linux-kvm bootable in LXD VMs
Hello, Just tested the latest image in ./current and it boots fine : root@focal-ok:~# uname -a Linux focal-ok 5.4.0-1009-kvm #9-Ubuntu SMP Mon Apr 20 20:23:56 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux root@focal-ok:~# cat /etc/cloud/build.info build_name: server serial: 20200421 root@focal-ok:~# uname -r 5.4.0-1009-kvm root@focal-ok:~# grep -i ^CONFIG_EFI /boot/config-5.4.0-1009-kvm CONFIG_EFI=y CONFIG_EFI_STUB=y CONFIG_EFI_MIXED=y CONFIG_EFI_VARS=y CONFIG_EFI_ESRT=y CONFIG_EFI_RUNTIME_WRAPPERS=y CONFIG_EFI_EARLYCON=y CONFIG_EFI_PARTITION=y CONFIG_EFIVAR_FS=m Thanks for the quick turnaround ! ...Louis -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873809 Title: Make linux-kvm bootable in LXD VMs To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1873809/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873809] Re: Make linux-kvm bootable in LXD VMs
Hello, thanks for the quick turnaround. For the record, some EFI configs did exist in prior 5.3 images : root@focal:/boot# cat /etc/cloud/build.info build_name: server serial: 20200223 root@focal:/boot# uname -r 5.3.0-1009-kvm root@focal:/boot# grep -i ^CONFIG_EFI config-5.3.0-1009-kvm CONFIG_EFI=y CONFIG_EFI_VARS=y CONFIG_EFI_ESRT=y CONFIG_EFI_RUNTIME_WRAPPERS=y CONFIG_EFI_EARLYCON=y CONFIG_EFI_PARTITION=y CONFIG_EFIVAR_FS=m I'll be using the other image for testing in the meantime ...Louis -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873809 Title: Make linux-kvm bootable in LXD VMs To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-bl-tutorials/+bug/1873809/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863866] [NEW] tinc missing net-tools dependency for Bionic onward
Public bug reported: net-tools is not installed by default on Bionic and after. tinc expects ifconfig to be available so it should depends on net-tools ** Affects: tinc (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/1863866 Title: tinc missing net-tools dependency for Bionic onward To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tinc/+bug/1863866/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1635463] Re: pip freeze includes "pkg-resources==0.0.0"
Hello, for what it's worth, the problem comes from the debianized version of virtualenv which uses a debundled version of pkg_resource which gets added into the virtualenv at creation time : $ virtualenv . Running virtualenv with interpreter /usr/bin/python2 New python executable in /home/caribou/git/quividi/test/bin/python2 Also creating executable in /home/caribou/git/quividi/test/bin/python Installing setuptools, pkg_resources, pip, wheel...done. $ pip freeze pkg-resources==0.0.0 Using the pip installed version of virtualenv can be a workable workaround : $ sudo apt -y purge python3-virtualenv virtualenv tox $ pip install virtualenv $ virtualenv . pip install virtualenv Collecting virtualenv Downloading https://files.pythonhosted.org/packages/c5/97/00dd42a0fc41e9016b23f07ec7f657f636cb672fad9cf72b80f8f65c6a46/virtualenv-16.7.7-py2.py3-none-any.whl (3.4MB) 100% || 3.4MB 351kB/s Installing collected packages: virtualenv Successfully installed virtualenv-16.7.7 $ virtualenv . New python executable in /home/caribou/git/quividi/test/bin/python Installing setuptools, pip, wheel... done. $ source bin/activate $ pip freeze $ hth, ...Louis -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1635463 Title: pip freeze includes "pkg-resources==0.0.0" To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1635463/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847361] Re: Upgrade of qemu binaries causes running instances not able to dynamically load modules
Hello, Nice to see so many known and friendly faces around this bug. Let me outline a *real life* issue that we're facing following this issue. We've put block storage in private beta a while ago (https://www.scaleway.com/fr/betas/#block-storage) based on RBD storage. The same platform experienced another QEMU issue (LPl #1837869) kindly fixed and SRU by @paelzer) that we deployed on the same platform this week. So all the instances currently running that have NOT used RBD based storage during the BETA but will still be running when we go live and want to use RBD storage when it goes GA will experience this bug unless they reboot their instance. We're looking into a workaround solution to alleviate this situation but I thought I'd share the context to give a some kind of "real life" experience :-) Kind regards, Louis (aka caribou) ;-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847361 Title: Upgrade of qemu binaries causes running instances not able to dynamically load modules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1847361/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852766] [NEW] Attaching RBD device after qemu upgrade fails with "Unknown protocol 'rbd'"
Public bug reported: After upgrading the following QEMU packages to latest Bionic version (1:2.11+dfsg-1ubuntu7.20) : - qemu-system-x86 - qemu-system-common - qemu-utils - qemu-block-extra:amd64 Attaching an RBD device to a VM that was running prior to the upgrade fails with "Unknown protocol 'rbd' This only happens if this is the first RBD device to be attached after the upgrade. Attaching a device, then upgrading to 1:2.11+dfsg- 1ubuntu7.20 will not generate the error message and the device will attach correctly. Attaching a device to a new VM created _AFTER_ the upgrade does not trigger the problem either. Downgrading qemu-block-extra:amd64 after the upgrade and prior to first attaching an RBD device will also not trigger the error. Here are two examples : Using : ii qemu-block-extra:amd641:2.11+dfsg-1ubuntu7 ii qemu-system-common1:2.11+dfsg-1ubuntu7 ii qemu-system-x86 1:2.11+dfsg-1ubuntu7 ii qemu-utils1:2.11+dfsg-1ubuntu7 ./qmp-shell -H /opt/vms/1/qmp.sock (QEMU) drive_add auto format=raw,cache=writeback,file=rbd:rbd/disk-086264fd-9ca4-42a9-9deb-4a8be80f2bab:rbd_cache=true:id=compute-hv:conf=/etc/ceph/ceph.conf:keyring=/etc/ceph/ceph.client.compute-hv.keyring,id=volume-8b84f816-6e11-4a17-a2ce-0cdb6f486bfe,throttling.iops-total=1,if=none OK With : ii qemu-block-extra:amd641:2.11+dfsg-1ubuntu7 ii qemu-system-common1:2.11+dfsg-1ubuntu7 ii qemu-system-x86 1:2.11+dfsg-1ubuntu7 ii qemu-utils1:2.11+dfsg-1ubuntu7 and an existing QEMU process running $ apt udpate && apt -y install qemu-utils qemu-system-x86 qemu-system-common qemu-block-extra:amd64 Using : ii qemu-block-extra:amd641:2.11+dfsg-1ubuntu7.20 ii qemu-system-common1:2.11+dfsg-1ubuntu7.20 ii qemu-system-x86 1:2.11+dfsg-1ubuntu7.20 ii qemu-utils1:2.11+dfsg-1ubuntu7.20 ./qmp-shell -H /opt/vms/1/qmp.sock (QEMU) drive_add auto format=raw,cache=writeback,file=rbd:rbd/disk-086264fd-9ca4-42a9-9deb-4a8be80f2bab:rbd_cache=true:id=compute-hv:conf=/etc/ceph/ceph.conf:keyring=/etc/ceph/ceph.client.compute-hv.keyring,id=volume-8b84f816-6e11-4a17-a2ce-0cdb6f486bfe,throttling.iops-total=1,if=none Unknown protocol 'rbd' (QEMU) Restarting the QEMU process fixes the issue. ** Affects: qemu (Ubuntu) Importance: Undecided Status: New ** Affects: qemu (Ubuntu Bionic) Importance: Medium Status: Confirmed ** Also affects: qemu (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: qemu (Ubuntu Bionic) Status: New => Confirmed ** Changed in: qemu (Ubuntu Bionic) Importance: Undecided => Medium ** Description changed: After upgrading the following QEMU packages to latest Bionic version (1:2.11+dfsg-1ubuntu7.20) : - qemu-system-x86 - qemu-system-common - qemu-utils - qemu-block-extra:amd64 Attaching an RBD device to a VM that was running prior to the upgrade fails with "Unknown protocol 'rbd' This only happens if this is the first RBD device to be attached after the upgrade. Attaching a device, then upgrading to 1:2.11+dfsg- 1ubuntu7.20 will not generate the error message and the device will attach correctly. Attaching a device to a new VM created _AFTER_ the upgrade does not trigger the problem either. Downgrading qemu-block-extra:amd64 after the upgrade and prior to first attaching an RBD device will also not trigger the error. Here are two examples : Using : ii qemu-block-extra:amd641:2.11+dfsg-1ubuntu7 ii qemu-system-common1:2.11+dfsg-1ubuntu7 ii qemu-system-x86 1:2.11+dfsg-1ubuntu7 ii qemu-utils1:2.11+dfsg-1ubuntu7 ./qmp-shell -H /opt/vms/1/qmp.sock (QEMU) drive_add auto format=raw,cache=writeback,file=rbd:rbd/disk-086264fd-9ca4-42a9-9deb-4a8be80f2bab:rbd_cache=true:id=compute-hv:conf=/etc/ceph/ceph.conf:keyring=/etc/ceph/ceph.client.compute-hv.keyring,id=volume-8b84f816-6e11-4a17-a2ce-0cdb6f486bfe,throttling.iops-total=1,if=none OK - With : ii qemu-block-extra:amd641:2.11+dfsg-1ubuntu7 ii qemu-system-common1:2.11+dfsg-1ubuntu7 ii qemu-system-x86 1:2.11+dfsg-1ubuntu7 ii qemu-utils1:2.11+dfsg-1ubuntu7 and an existing QEMU process running $ apt udpate && apt -y install qemu-utils qemu-system-x86 qemu-system-common qemu-block-extra:amd64 Using : ii qemu-block-extra:amd641:2.11+dfsg-1ubuntu7.20 ii qemu-system-common1:2.11+dfsg-1ubuntu7.20 ii qemu-system-x86 1:2.11+dfsg-1ubuntu7.20 ii qemu-utils1:2.11+dfsg-1ubuntu7.20 ./qmp-shell -H
[Bug 1805183] Re: systemd-resolved constantly restarts on Bionic upgraded from Xenial
Ok, I'll have a look at it; I only backported the Eoan fix to Bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1805183 Title: systemd-resolved constantly restarts on Bionic upgraded from Xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1805183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845619] [NEW] Please backport bugfix for Debian Bug 838503 : mdadm should not start syncing RAID1 arrays at full speed during installation
Public bug reported: Debian bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838503 fixes slow installation caused by RAID synchronization. This is fixed in DISCO and EOAN already. ** Affects: partman-md (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: partman-md (Ubuntu Bionic) Importance: Medium Assignee: Louis Bouchard (louis) Status: Confirmed ** Affects: partman-md (Ubuntu Disco) Importance: Undecided Status: Fix Released ** Affects: partman-md (Ubuntu Eoan) Importance: Undecided Status: Fix Released ** Also affects: partman-md (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: partman-md (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: partman-md (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: partman-md (Ubuntu Disco) Status: New => Fix Released ** Changed in: partman-md (Ubuntu Eoan) Status: New => Fix Released ** Changed in: partman-md (Ubuntu Bionic) Status: New => Confirmed ** Changed in: partman-md (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: partman-md (Ubuntu Bionic) Assignee: (unassigned) => Louis Bouchard (louis) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845619 Title: Please backport bugfix for Debian Bug 838503 : mdadm should not start syncing RAID1 arrays at full speed during installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/partman-md/+bug/1845619/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837869] Re: Cannot complete snapshot if read-only backing store is opened by another VM
As discussed offline, a new round of test confirms that the fix in your PPA fixes the File Lock issue. ** Changed in: qemu (Ubuntu Bionic) Status: Incomplete => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1837869 Title: Cannot complete snapshot if read-only backing store is opened by another VM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1837869/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1837869] Re: Cannot complete snapshot if read-only backing store is opened by another VM
Hi, Sorry, I'm off on vacation until August 12th. Will look at this once I'm back ...Louis Le mer. 31 juil. 2019 à 09:05, Christian Ehrhardt < 1837...@bugs.launchpad.net> a écrit : > Hrm, that didn't help. > Now I can't even start the guests anymore: > root@b:~# qemu-system-x86_64: -drive > file=./top-vm02.img,if=virtio,id=disk0: Failed to get "write" lock > > It seems I too blindly picked out of context for this :-/. > But I also don't have a lot of time for this right now. > Maybe I should just start bisecting it in the background ... > > Let me know if you have identified anything quicker than me. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1837869 > > Title: > Cannot complete snapshot if read-only backing store is opened by > another VM > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1837869/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1837869 Title: Cannot complete snapshot if read-only backing store is opened by another VM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1837869/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837869] [NEW] Cannot complete snapshot if read-only backing store is opened by another VM
Public bug reported:
On Bionic, Qemu complains that it cannot acquire write lock when
commiting a snapshot if a read-only backing-store is opened by another
qemu process. This behavior does not happen with version 2.12 in Cosmic.
Reproducer
==
Create two QCOW2 containers sharing the same base file as a backing store :
base.qcow2
|
+-+-+
| |
middle-vm02.img middle-vm02.img
| |
top-vm01.img top-vm02.img
# cat mkimage
#!/bin/bash
qemu-img create -f qcow2 base.qcow2 10G
qemu-img create -f qcow2 -b base.qcow2 middle-vm01.img 10G
qemu-img create -f qcow2 -b base.qcow2 middle-vm02.img 10G
qemu-img create -f qcow2 -b middle-vm01.img top-vm01.img 10G
qemu-img create -f qcow2 -b middle-vm01.img top-vm02.img 10G
Start two VM each using its own top-vm{id}.img
# cat runvm
#!/bin/bash
qemu-system-x86_64 -nographic -qmp unix:./qmp-1.sock,server,nowait -enable-kvm
-device virtio-scsi-pci,id=scsi -device sga -nodefaults -monitor none -m
256M -drive file=./top-vm01.img,if=virtio,id=disk0 -smp 1 -smbios
type=1,manufacturer=test&
qemu-system-x86_64 -nographic -qmp unix:./qmp-2.sock,server,nowait -enable-kvm
-device virtio-scsi-pci,id=scsi -device sga -nodefaults -monitor none -m
256M -drive file=./top-vm02.img,if=virtio,id=disk0 -smp 1 -smbios
type=1,manufacturer=test&
Create a snapshot
./scripts/qmp/qmp-shell ./qmp-1.sock
Welcome to the QMP low-level shell!
Connected to QEMU 2.11.1
(QEMU) blockdev-snapshot-sync device=disk0 snapshot-file=tmp.qcow2 format=qcow2
Formatting 'tmp.qcow2', fmt=qcow2 size=10737418240 backing_file=./top-vm01.img
backing_fmt=qcow2 cluster_size=65536 lazy_refcounts=off refcount_bits=16
{"return": {}}
Commit the snapshot
(QEMU) block-commit device=disk0 base=top-vm01.img
{"error": {"class": "GenericError", "desc": "Failed to get \"write\" lock"}}
Expected Behavior
=
The commit should complete succesfully as the base.img backing store is opened
read-only so no write lock is required
Current Behavior
The commit fails with "Failed to get "write" lock
** Affects: qemu (Ubuntu)
Importance: Undecided
Status: New
** Affects: qemu (Ubuntu Bionic)
Importance: Undecided
Status: Confirmed
** Affects: qemu (Ubuntu Disco)
Importance: Undecided
Status: Fix Released
** Also affects: qemu (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: qemu (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: qemu (Ubuntu Bionic)
Status: New => Confirmed
** Changed in: qemu (Ubuntu Disco)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1837869
Title:
Cannot complete snapshot if read-only backing store is opened by
another VM
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1837869/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1805183] Re: systemd-resolved constantly restarts on Bionic upgraded from Xenial
For Info, I'm repearing an SRU upload for Bionic hopefully available by End Of Day ** Description changed: [Impact] Log noise due to needless restart of resolved on lease expiry, maybe loss of cached state? + Application that require Name Resolution may fail while the service is being unnecessarily restarted [Test case] (1) Append make_resolv_conf to the end of the file, so it gets executed (2) Execute the file with bash -x and different settings and ensure there are no restarts if the settings are the same, and that there are if settings change; for example: sudo new_domain_name_servers=8.8.4.4 interface="wlp61s0" reason=REBIND bash -x debian/extra/dhclient-enter-resolved-hook sudo new_domain_name_servers=8.8.4.4 interface="wlp61s0" reason=REBIND bash -x debian/extra/dhclient-enter-resolved-hook => no restart sudo new_domain_name_servers=8.8.8.8 interface="wlp61s0" reason=REBIND bash -x debian/extra/dhclient-enter-resolved-hook => should restart sudo new_domain_name_servers=8.8.8.8 interface="wlp61s0" reason=REBIND bash -x debian/extra/dhclient-enter-resolved-hook => no restart sudo new_domain_name_servers=8.8.4.4 interface="wlp61s0" reason=REBIND bash -x debian/extra/dhclient-enter-resolved-hook => should restart [Regression potential] The change only restarts resolved when the settings change. If there's a bug in the logic, resolved might not be restarted when it should be. Also, since there will be less restarts of resolved, it will run longer, so if there are memory leaks they will become more apparent. [Original bug report] If a cloud server is upgraded from Xenial to Bionic, the dhclient system remains in place and any DHCP lease refreshes cause a needless restart of the system-resolved daemon Nov 26 16:59:41 srv-qvjhx dhclient[825]: DHCPREQUEST of 10.226.209.106 on ens3 to 10.226.209.105 port 67 (xid=0x2bd41d7d) Nov 26 16:59:41 srv-qvjhx dhclient[825]: DHCPACK of 10.226.209.106 from 10.226.209.105 Nov 26 16:59:41 srv-qvjhx systemd[1]: Stopping Network Name Resolution... Nov 26 16:59:41 srv-qvjhx systemd[1]: Stopped Network Name Resolution. Nov 26 16:59:41 srv-qvjhx systemd[1]: Starting Network Name Resolution... Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: Positive Trust Anchors: Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: . IN DS 19036 8 2 49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5 Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: Negative trust anchors: 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 1 Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: Using system hostname 'srv-qvjhx'. Nov 26 16:59:41 srv-qvjhx systemd[1]: Started Network Name Resolution. Nov 26 16:59:41 srv-qvjhx systemd[1]: Starting resolvconf-pull-resolved.service... Nov 26 16:59:41 srv-qvjhx dhclient[825]: bound to 10.226.209.106 -- renewal in 1466 seconds. Nov 26 16:59:41 srv-qvjhx systemd[1]: Started resolvconf-pull-resolved.service. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:16.04.25 ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160 Uname: Linux 4.4.0-139-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CrashDB: ubuntu Date: Mon Nov 26 16:17:52 2018 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1805183 Title: systemd-resolved constantly restarts on Bionic upgraded from Xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1805183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1805183] Re: systemd-resolved constantly restarts on Bionic upgraded from Xenial
** Changed in: systemd (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu Bionic) Assignee: (unassigned) => Louis Bouchard (louis) ** Changed in: systemd (Ubuntu Bionic) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1805183 Title: systemd-resolved constantly restarts on Bionic upgraded from Xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1805183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834505] Re: Random kernel panics in QEMU instances when running on EPYC architecture
** Changed in: linux (Ubuntu) Status: Incomplete => Opinion ** Changed in: linux (Ubuntu) Status: Opinion => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834505 Title: Random kernel panics in QEMU instances when running on EPYC architecture To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834505/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834505] [NEW] Random kernel panics in QEMU instances when running on EPYC architecture
Public bug reported: We have been seeing many kernel panic in QEMU instances on newly deployed servers all running on the EPYC architecture. Many of the KP occur early after the start of the QEMU process or within a few hours. All the servers are running an up to date Bionic. After the first few panics on 4.15 kernels, we upgraded to 4.18 and still had panics. The only thing running on the underlying server is QEMU processes. Here is a typical backtrace of a kernel panic : [58034.598930] BUG: unable to handle kernel paging request at 943276c49f64 [58034.612039] PGD 8363067 P4D 8363067 PUD 8367067 PMD 759ac063 PTE 800076c49163 [58034.612992] Oops: [#1] SMP NOPTI [58034.613462] CPU: 0 PID: 0 Comm: swapper/0 Kdump: loaded Not tainted 4.18.0-20-generic #21~18.04.1-Ubuntu [58034.614685] Hardware name: Scaleway Standard PC (i440FX + PIIX, 1996), BIOS 0.0.0 02/06/2015 [58034.615803] RIP: 0010:sched_ttwu_pending+0x6b/0xe0 [58034.616385] Code: 4b a1 93 00 41 83 a4 24 98 09 00 00 03 4c 89 e7 48 89 45 d8 c7 45 e0 00 00 00 00 e8 ef ca ff ff 48 8d 73 d0 48 83 fe d0 74 2c <0f> b6 96 64 08 00 00 48 8b 46 30 48 8d 4d d8 4c 89 e7 48 8d 5> [58034.618537] RSP: 0018:94327f803f90 EFLAGS: 00010087 [58034.619134] RAX: 34c83ba48a83 RBX: 943276c49730 RCX: [58034.619992] RDX: 2a12 RSI: 943276c49700 RDI: 94327fe3e000 [58034.620913] RBP: 94327f803fb8 R08: 3753c7b87c93 R09: [58034.621835] R10: R11: R12: 94327f822c00 [58034.622723] R13: R14: R15: [58034.623539] FS: () GS:94327f80() knlGS: [58034.624513] CS: 0010 DS: ES: CR0: 80050033 [58034.625214] CR2: 943276c49f64 CR3: 76544000 CR4: 003406f0 [58034.626268] Call Trace: [58034.626605] [58034.626924] scheduler_ipi+0xa9/0x130 [58034.627400] smp_reschedule_interrupt+0x39/0xe0 [58034.627925] reschedule_interrupt+0xf/0x20 [58034.628398] [58034.628659] RIP: 0010:rcu_idle_exit+0x40/0x70 [58034.629181] Code: fa 66 0f 1f 44 00 00 48 c7 c3 80 a6 01 00 65 48 03 1d ec 4b 50 4e 48 8b 03 48 85 c0 74 16 48 83 c0 01 48 89 03 4c 89 e7 57 9d <0f> 1f 44 00 00 5b 41 5c 5d c3 e8 a1 c6 ff ff 48 b8 00 00 00 0> [58034.631577] RSP: 0018:b2e03e48 EFLAGS: 0202 ORIG_RAX: ff02 [58034.632566] RAX: 4000 RBX: 94327f81a680 RCX: 94327f81a680 [58034.633557] RDX: RSI: 94327f81a680 RDI: 0202 [58034.634416] RBP: b2e03e58 R08: 0001cc00 R09: 0001 [58034.635292] R10: b2e03d98 R11: R12: 0202 [58034.636107] R13: R14: R15: 7e369c93 [58034.637052] do_idle+0x13f/0x280 [58034.637453] cpu_startup_entry+0x73/0x80 [58034.638067] rest_init+0xae/0xb0 [58034.638506] start_kernel+0x539/0x55a [58034.638938] x86_64_start_reservations+0x24/0x26 [58034.639470] x86_64_start_kernel+0x74/0x77 [58034.639958] secondary_startup_64+0xa5/0xb0 [58034.640441] Modules linked in: cfg80211 veth xt_nat xt_tcpudp ipt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_fi> None of the server has experienced any kernel panic itself. After analysing many of the crashes and seeing many of them handling interrupts, we decided to reboot the instances with the noapic parameter. No kernel panic has been seen since but this is just a workaround until a solution is found. AMD has been informed of the issue. TIA, ...Louis (aka Caribou) ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834505 Title: Random kernel panics in QEMU instances when running on EPYC architecture To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834505/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834505] Re: Random kernel panics in QEMU instances when running on EPYC architecture
** Description changed: We have been seeing many kernel panic in QEMU instances on newly deployed servers all running on the EPYC architecture. Many of the KP occur early after the start of the QEMU process or within a few hours. + + All the servers are running an up to date Bionic. After the first few + panics on 4.15 kernels, we upgraded to 4.18 and still had panics. The only thing running on the underlying server is QEMU processes. Here is a typical backtrace of a kernel panic : [58034.598930] BUG: unable to handle kernel paging request at 943276c49f64 [58034.612039] PGD 8363067 P4D 8363067 PUD 8367067 PMD 759ac063 PTE 800076c49163 [58034.612992] Oops: [#1] SMP NOPTI [58034.613462] CPU: 0 PID: 0 Comm: swapper/0 Kdump: loaded Not tainted 4.18.0-20-generic #21~18.04.1-Ubuntu [58034.614685] Hardware name: Scaleway Standard PC (i440FX + PIIX, 1996), BIOS 0.0.0 02/06/2015 [58034.615803] RIP: 0010:sched_ttwu_pending+0x6b/0xe0 [58034.616385] Code: 4b a1 93 00 41 83 a4 24 98 09 00 00 03 4c 89 e7 48 89 45 d8 c7 45 e0 00 00 00 00 e8 ef ca ff ff 48 8d 73 d0 48 83 fe d0 74 2c <0f> b6 96 64 08 00 00 48 8b 46 30 48 8d 4d d8 4c 89 e7 48 8d 5> [58034.618537] RSP: 0018:94327f803f90 EFLAGS: 00010087 [58034.619134] RAX: 34c83ba48a83 RBX: 943276c49730 RCX: [58034.619992] RDX: 2a12 RSI: 943276c49700 RDI: 94327fe3e000 [58034.620913] RBP: 94327f803fb8 R08: 3753c7b87c93 R09: [58034.621835] R10: R11: R12: 94327f822c00 [58034.622723] R13: R14: R15: [58034.623539] FS: () GS:94327f80() knlGS: [58034.624513] CS: 0010 DS: ES: CR0: 80050033 [58034.625214] CR2: 943276c49f64 CR3: 76544000 CR4: 003406f0 [58034.626268] Call Trace: [58034.626605] [58034.626924] scheduler_ipi+0xa9/0x130 [58034.627400] smp_reschedule_interrupt+0x39/0xe0 [58034.627925] reschedule_interrupt+0xf/0x20 [58034.628398] [58034.628659] RIP: 0010:rcu_idle_exit+0x40/0x70 [58034.629181] Code: fa 66 0f 1f 44 00 00 48 c7 c3 80 a6 01 00 65 48 03 1d ec 4b 50 4e 48 8b 03 48 85 c0 74 16 48 83 c0 01 48 89 03 4c 89 e7 57 9d <0f> 1f 44 00 00 5b 41 5c 5d c3 e8 a1 c6 ff ff 48 b8 00 00 00 0> [58034.631577] RSP: 0018:b2e03e48 EFLAGS: 0202 ORIG_RAX: ff02 [58034.632566] RAX: 4000 RBX: 94327f81a680 RCX: 94327f81a680 [58034.633557] RDX: RSI: 94327f81a680 RDI: 0202 [58034.634416] RBP: b2e03e58 R08: 0001cc00 R09: 0001 [58034.635292] R10: b2e03d98 R11: R12: 0202 [58034.636107] R13: R14: R15: 7e369c93 [58034.637052] do_idle+0x13f/0x280 [58034.637453] cpu_startup_entry+0x73/0x80 [58034.638067] rest_init+0xae/0xb0 [58034.638506] start_kernel+0x539/0x55a [58034.638938] x86_64_start_reservations+0x24/0x26 [58034.639470] x86_64_start_kernel+0x74/0x77 [58034.639958] secondary_startup_64+0xa5/0xb0 [58034.640441] Modules linked in: cfg80211 veth xt_nat xt_tcpudp ipt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_fi> None of the server has experienced any kernel panic itself. After analysing many of the crashes and seeing many of them handling interrupts, we decided to reboot the instances with the noapic parameter. No kernel panic has been seen since but this is just a workaround until a solution is found. AMD has been informed of the issue. TIA, ...Louis (aka Caribou) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834505 Title: Random kernel panics in QEMU instances when running on EPYC architecture To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834505/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820755] Re: Netboot install fails due to linux-image-4.4.0-143-generic.postinst linux-update-symlinks not found
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-base (Ubuntu Xenial) 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/1820755 Title: Netboot install fails due to linux-image-4.4.0-143-generic.postinst linux-update-symlinks not found To manage notifications about this bug go to: https://bugs.launchpad.net/bluelinux/+bug/1820755/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1506550] Re: quassel can't play audio notifications in wily
** Changed in: quassel (Ubuntu) Assignee: Louis Bouchard (louis) => (unassigned) ** Changed in: quassel (Ubuntu Wily) Assignee: Louis Bouchard (louis) => (unassigned) ** Changed in: quassel (Ubuntu Xenial) Assignee: Louis Bouchard (louis) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1506550 Title: quassel can't play audio notifications in wily To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/quassel/+bug/1506550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1447695] Re: sosreport 3.2 does not collect systemd information
** Changed in: sosreport (Ubuntu Trusty) Assignee: Louis Bouchard (louis) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1447695 Title: sosreport 3.2 does not collect systemd information To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1447695/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1434991] Re: python attributeError 'SSLTimeoutError' after upgrade
** Changed in: pywbem (Ubuntu) Assignee: Louis Bouchard (louis) => (unassigned) ** Changed in: pywbem (Ubuntu Trusty) Assignee: Louis Bouchard (louis) => (unassigned) ** Changed in: pywbem (Ubuntu Utopic) Assignee: Louis Bouchard (louis) => (unassigned) ** Changed in: pywbem (Ubuntu Vivid) Assignee: Louis Bouchard (louis) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1434991 Title: python attributeError 'SSLTimeoutError' after upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pywbem/+bug/1434991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1491894] Re: lucid to precise to trusty upgrade may leave system unbootable
** Changed in: grub2 (Ubuntu) Assignee: Louis Bouchard (louis) => (unassigned) ** Changed in: grub2 (Ubuntu Trusty) Assignee: Louis Bouchard (louis) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1491894 Title: lucid to precise to trusty upgrade may leave system unbootable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1491894/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815178] Re: 18.04: Raid performances on kernel 4.15 and newer are suboptimal when used on NVMe devices
** Summary changed: - 18.04: Raid5 performances on kernel 4.15 are suboptimal + 18.04: Raid performances on kernel 4.15 and newer are suboptimal when used on NVMe devices -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815178 Title: 18.04: Raid performances on kernel 4.15 and newer are suboptimal when used on NVMe devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1815178/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815178] Re: 18.04: Raid5 performances on kernel 4.15 are suboptimal
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815178 Title: 18.04: Raid5 performances on kernel 4.15 are suboptimal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1815178/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815178] [NEW] 18.04: Raid5 performances on kernel 4.15 are suboptimal
Public bug reported: Hello, We have been running multiple tests using the md driver to build various type of RAID devices. Performances on RAID5 are particularly disappointing so we would like to know if there are any known issue with the md driver on Bionic kernels. Here are some of our results : Test (Threads) QCT JBODQCT RAID5 (8 threads) QCT RAID10 read(1) 838751 (-10%) 572 (-32%) read(2) 1226 1172 (-4%) 1057 (-14%) read(4) 1129 2006 (+78%) 1760 (+56%) write(1)804382 (-52%) 398 (-50%) write(2)1047 175 (-83%) 667 (-36%) write(4)883415 (-53%) 871 (-1%) randread(1) 863749 (-13%) 619 (-28%) randread(2) 1346 1067 (-21%) 1020 (-24%) randread(4) 1648 1785 (+8%) 1650 (=) randwrite(1)766287 (-63%) 391 (-50%) randwrite(2)1044 313 (-70%) 664 (-36%) randwrite(4)916282 (-69%) 885 (-3%) We are preparing tests with one of the latest mainline kernel. TIA, ...Louis ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815178 Title: 18.04: Raid5 performances on kernel 4.15 are suboptimal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1815178/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1662345] Re: smbios parameter settings not visible in guest
Hello, I have revived this bug and assigned myself to it. It turns out that -smbios type=1,manufacturer=Scaleway is required by us to trigger cloud-init's DataSourceScaleway on our infrastructure. And, moreover, the functionality works as designed on Bionic : # dmidecode | head # dmidecode 3.1 Getting SMBIOS data from sysfs. SMBIOS 3.0.0 present. Table at 0xBC03. Handle 0x0100, DMI type 1, 27 bytes System Information Manufacturer: Scaleway Product Name: KVM Virtual Machine Version: 1.0 # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04 LTS Release:18.04 Codename: bionic # arch aarch64 So I am going to work on trying to identify what was added to version 1:2.11+dfsg-1ubuntu7.4 to make it work as expected. ** Changed in: qemu (Ubuntu) Importance: Wishlist => Medium ** Changed in: qemu (Ubuntu) Assignee: (unassigned) => Louis Bouchard (louis) ** Also affects: qemu (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: qemu (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: qemu (Ubuntu Xenial) Status: New => Confirmed ** Changed in: qemu (Ubuntu Bionic) Status: New => Fix Released ** Changed in: qemu (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: qemu (Ubuntu Bionic) Importance: Undecided => Low ** Changed in: qemu (Ubuntu Xenial) Assignee: (unassigned) => Louis Bouchard (louis) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1662345 Title: smbios parameter settings not visible in guest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1662345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1780062] Re: Cloud-init causes potentially huge boot delays with 4.15 kernels
Hello, I have noticed the same issue on our recently released scaleway images with cloud-init enabled on Bionic running 4.15.0-24. Testing with the 4.15.0-26-generic kernel in -proposed _DOES_ fix the delay issue on our image. I'm taking the liberty of marking the bug tested. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1780062 Title: Cloud-init causes potentially huge boot delays with 4.15 kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1780062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1780817] [NEW] kernel panic in nested VM with latest 4.15 kernel (4.15.0-24-generic)
Public bug reported: When starting a nested VM in a Bionic VM, the "host" VM kernel panics following a simple drop to QEMU monitor by hitting A-c. For some reason kdump is unable to capture the kernel panic so I only have a screen capture of the panic. It also happens on the latest mainline kernel(4.18-rc4). It is fairly trivial to reproduce. In a Bionic VM, install qemu & ovmf and run the following : qemu-system-x86_64 -enable-kvm \ -name balloontest \ -display none \ -monitor none \ -nographic \ -nodefaults \ -m 2048M \ -serial mon:stdio \ -smp 2 \ -cpu host \ -drive if=pflash,format=raw,readonly,file=/usr/share/OVMF/OVMF_CODE.fd \ -drive if=pflash,format=raw,file=/home/caribou/balloon/efi.vars Use A-c to drop to QEMU monitor and . ^[]0;/opt/ocs/gotty-serial/nolp-cli^G^[]2;Loading...^G^[]2;avogadro^G[ 267.784299] general protection fault: [#1] SMP PTI [ 267.785834] Modules linked in: nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype ip6t_MASQUERADE nf_nat_masquerade_ipv6 ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_filter i> [ 267.804312] xor raid6_pq libcrc32c raid1 raid0 multipath linear floppy aesni_intel pata_acpi aes_x86_64 crypto_simd cryptd glue_helper psmouse i2c_piix4 virtio_net virtio_blk [ 267.807946] CPU: 6 PID: 0 Comm: swapper/6 Not tainted 4.15.0-24-generic #26-Ubuntu [ 267.809710] Hardware name: Scaleway Standard PC (i440FX + PIIX, 1996), BIOS 0.0.0 02/06/2015 [ 267.811666] RIP: 0010:native_write_cr4+0x4/0x10 [ 267.812727] RSP: 0018:8c01ffd83f48 EFLAGS: 00010006 [ 267.813960] RAX: 003626e0 RBX: 0046 RCX: 8c01ffd8 [ 267.815582] RDX: 8c01ffd94020 RSI: 8c01ffda5040 RDI: 003606e0 [ 267.817095] RBP: 8c01ffd83f48 R08: 00478079a547 R09: [ 267.818625] R10: R11: R12: 00025040 [ 267.820130] R13: 0001 R14: R15: [ 267.821638] FS: () GS:8c01ffd8() knlGS: [ 267.823352] CS: 0010 DS: ES: CR0: 80050033 [ 267.824592] CR2: CR3: 00058c00a006 CR4: 003626e0 [ 267.826108] DR0: DR1: DR2: [ 267.827567] DR3: DR6: fffe0ff0 DR7: 0400 [ 267.828973] Call Trace: [ 267.829470] [ 267.829893] hardware_disable+0xaa/0xc0 [kvm_intel] [ 267.830897] kvm_arch_hardware_disable+0x19/0x40 [kvm] [ 267.831928] hardware_disable_nolock+0x2b/0x30 [kvm] [ 267.832912] flush_smp_call_function_queue+0x4c/0xf0 [ 267.833911] generic_smp_call_function_single_interrupt+0x13/0x30 [ 267.835121] smp_call_function_interrupt+0x36/0xd0 [ 267.836069] call_function_interrupt+0x84/0x90 [ 267.836950] [ 267.837396] RIP: 0010:native_safe_halt+0x6/0x10 [ 267.838272] RSP: 0018:a2e1431afe80 EFLAGS: 0246 ORIG_RAX: ff03 [ 267.839698] RAX: acd97150 RBX: 0006 RCX: [ 267.840978] RDX: RSI: RDI: [ 267.842258] RBP: a2e1431afe80 R08: 0002 R09: [ 267.843554] R10: 00b3 R11: 00a6 R12: 0006 [ 267.844826] R13: R14: R15: [ 267.846107] ? __cpuidle_text_start+0x8/0x8 [ 267.846875] default_idle+0x20/0x100 [ 267.847533] arch_cpu_idle+0x15/0x20 [ 267.848186] default_idle_call+0x23/0x30 [ 267.848917] do_idle+0x172/0x1f0 [ 267.849516] cpu_startup_entry+0x73/0x80 [ 267.850255] start_secondary+0x1ab/0x200 [ 267.850971] secondary_startup_64+0xa5/0xb0 [ 267.851700] Code: 0f 1f 80 00 00 00 00 55 48 89 e5 0f 20 d8 5d c3 0f 1f 80 00 00 00 00 55 48 89 e5 0f 22 df 5d c3 0f 1f 80 00 00 00 00 55 48 89 e5 <0f> 22 e7 5d c3 0f 1f 80 00 00 00 00 55 48 89 e5 44 0f 20 c0> [ 267.854894] RIP: native_write_cr4+0x4/0x10 RSP: 8c01ffd83f48 [ 268.848104] invalid opcode: [#2] SMP PTI [ 268.848524] Modules linked in: nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype ip6t_MASQUERADE nf_nat_masquerade_ipv6 ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_filter i> [ 268.854013] xor raid6_pq libcrc32c raid1 raid0 multipath linear floppy aesni_intel pata_acpi aes_x86_64 crypto_simd cryptd glue_helper psmouse i2c_piix4 virtio_net virtio_blk [ 268.855212] CPU: 6 PID: 0 Comm: swapper/6 Not tainted 4.15.0-24-generic #26-Ubuntu [ 268.855790] Hardware name: Scaleway Standard PC (i440FX + PIIX, 1996), BIOS 0.0.0 02/06/2015 [ 268.856438] RIP: 0010:native_machine_crash_shutdown+0x136/0x190 [ 268.856893] RSP: 0018:8c01ffd83cc0 EFLAGS: 00010002 [ 268.857295] RAX:
[Bug 1743529] Re: Merge kexec-tools 2.0.16-1 from Debian: System hung with Kernel panic -not syncing: Out of memory message when crash is triggered.
Hello, For information, the current presence of kexec-tools in -proposed causes a dependency problem when installing the linux-crashdump meta-package : # apt update Hit:1 http://archive.ubuntu.com/ubuntu xenial InRelease Hit:2 http://archive.ubuntu.com/ubuntu xenial-updates InRelease Hit:3 http://archive.ubuntu.com/ubuntu xenial-security InRelease Reading package lists... Done Building dependency tree Reading state information... Done 11 packages can be upgraded. Run 'apt list --upgradable' to see them. # apt install linux-crashdump Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: linux-crashdump : Depends: kdump-tools but it is not going to be installed E: Unable to correct problems, you have held broken packages. When adding the -proposed archive, linux-crashdump installs correctly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1743529 Title: Merge kexec-tools 2.0.16-1 from Debian: System hung with Kernel panic -not syncing: Out of memory message when crash is triggered. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1743529/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775086] Re: cloud-init fails to recognize scaleway
Hello, Indeed, scw-generate-network-config does create a circular dependancy hence systemd ends up shooting the cloud-init unit which breaks the cloud-init.process. We are in the process of implementing cloud-init on our platform. Please keep yourself up to date, there should be some announcement soon. Kind regards, ...Louis -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1775086 Title: cloud-init fails to recognize scaleway To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1775086/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743537] [NEW] linux-crashdump meta-package does not exist for arm64
Public bug reported: The linux-crashdump meta-package should be enabled for arm64 now that kdump-tools & makedumpfile are enabled for this architecture ** Affects: linux-meta (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/1743537 Title: linux-crashdump meta-package does not exist for arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1743537/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1714485] Re: Ubuntu 16.04.03: kdump fails with error "kdump-tools[1532]: /etc/init.d/kdump-tools: 26: [: -ne: unexpected operator" when / file system is xfs.
Hello, I would like to add that triggering a kernel dump in seconds following the installation of the package remains a corner case in a test context and not the usual behavior. I have seen that too in my test scripts and syncing right after the installation fixed the issue as well. Bringing in the upstream change is a good solution. ...Louis -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1714485 Title: Ubuntu 16.04.03: kdump fails with error "kdump-tools[1532]: /etc/init.d/kdump-tools: 26: [: -ne: unexpected operator" when / file system is xfs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1714485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1714485] Re: Ubuntu 16.04.03: kdump fails with error "kdump-tools[1532]: /etc/init.d/kdump-tools: 26: [: -ne: unexpected operator" when / file system is xfs.
** Also affects: makedumpfile (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: makedumpfile (Ubuntu Bionic) Importance: High Assignee: Canonical Kernel Team (canonical-kernel-team) Status: In Progress ** Also affects: makedumpfile (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: makedumpfile (Ubuntu Zesty) 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/1714485 Title: Ubuntu 16.04.03: kdump fails with error "kdump-tools[1532]: /etc/init.d/kdump-tools: 26: [: -ne: unexpected operator" when / file system is xfs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1714485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1658733] Re: Ubuntu 16.04.2KVM:kdump fails to mount root file system on multipath root device
*** This bug is a duplicate of bug 1635597 *** https://bugs.launchpad.net/bugs/1635597 This bug is a duplicate of bug #1635597. As outlined in the other bug, could you test the potential fix in the following PPA : ppa:louis/kdump-tools-multipath ** This bug has been marked a duplicate of bug 1635597 Ubuntu16.10:talclp1: Kdump failed with multipath disk -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1658733 Title: Ubuntu 16.04.2KVM:kdump fails to mount root file system on multipath root device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1658733/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1635597] Re: Ubuntu16.10:talclp1: Kdump failed with multipath disk
Hello, Would it be possible to test a potential fix in the following PPA : ppa:louis/kdump-tools-multipath I do not have the hardware to fully test a kernel dump but the partial test I have confirm that the modules are correctly loaded. Please let me know the outcome of you tests whenever possible. Kind regards, -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1635597 Title: Ubuntu16.10:talclp1: Kdump failed with multipath disk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1635597/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1635597] Re: Ubuntu16.10:talclp1: Kdump failed with multipath disk
** Changed in: makedumpfile (Ubuntu) Status: Triaged => In Progress ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: makedumpfile (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: makedumpfile (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: makedumpfile (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux (Ubuntu Zesty) Status: New => Invalid ** Changed in: makedumpfile (Ubuntu Trusty) Assignee: (unassigned) => Louis Bouchard (louis) ** Changed in: makedumpfile (Ubuntu Xenial) Assignee: (unassigned) => Louis Bouchard (louis) ** Changed in: makedumpfile (Ubuntu Zesty) Assignee: (unassigned) => Louis Bouchard (louis) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1635597 Title: Ubuntu16.10:talclp1: Kdump failed with multipath disk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1635597/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1658733] Re: Ubuntu 16.04.2KVM:kdump fails to mount root file system on multipath root device
** Also affects: kexec-tools (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: makedumpfile (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: kexec-tools (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: makedumpfile (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: kexec-tools (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: makedumpfile (Ubuntu Xenial) 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/1658733 Title: Ubuntu 16.04.2KVM:kdump fails to mount root file system on multipath root device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1658733/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1658733] Re: Ubuntu 16.04.2KVM:kdump fails to mount root file system on multipath root device
** Changed in: kexec-tools (Ubuntu) Assignee: Nish Aravamudan (nacc) => Louis Bouchard (louis) ** Changed in: makedumpfile (Ubuntu) Assignee: Nish Aravamudan (nacc) => Louis Bouchard (louis) ** Changed in: kexec-tools (Ubuntu) Status: Confirmed => Invalid ** Changed in: makedumpfile (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1658733 Title: Ubuntu 16.04.2KVM:kdump fails to mount root file system on multipath root device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1658733/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1676884] Re: kdump-tools uses the wrong crashkernel command line parameter in ppc64le
Hello, Well, this is to be expected as the postinst script will only change the target of the symlink if the architecture is ppc64EL and not ppc64LE ( EL != LE). Now if both are interchangeable (I must admit my ignorance of this architecture), I don't mind fixing the script to apply to both EL and LE. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1676884 Title: kdump-tools uses the wrong crashkernel command line parameter in ppc64le To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1676884/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1536904] Re: Kdump fails on Ubuntu 16.04 (PowerVM/PowerKVM/BareMetal)
** Changed in: makedumpfile (Ubuntu) Assignee: Louis Bouchard (louis) => (unassigned) ** Changed in: makedumpfile (Ubuntu Wily) Assignee: Louis Bouchard (louis) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1536904 Title: Kdump fails on Ubuntu 16.04 (PowerVM/PowerKVM/BareMetal) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1536904/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655625] Re: ISST-LTE:pVM:roselp4:ubuntu 16.04.2: vmcore cannot be analysed by crash
** Changed in: crash (Ubuntu Xenial) Assignee: Louis Bouchard (louis) => (unassigned) ** Changed in: makedumpfile (Ubuntu Xenial) Assignee: Louis Bouchard (louis) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1655625 Title: ISST-LTE:pVM:roselp4:ubuntu 16.04.2: vmcore cannot be analysed by crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1655625/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1366103] Re: sosreport doesn't collect all data from /etc/apparmor.d/
** Changed in: sosreport (Ubuntu Trusty) Assignee: Louis Bouchard (louis) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1366103 Title: sosreport doesn't collect all data from /etc/apparmor.d/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1366103/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1356211] Re: cannot collect rotated syslog.1
** Changed in: sosreport (Ubuntu Trusty) Assignee: Louis Bouchard (louis) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1356211 Title: cannot collect rotated syslog.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1356211/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1626269] Re: Ubuntu 16.10: kdump is not working in 4.8 kernel.
** Changed in: makedumpfile (Ubuntu Xenial) Assignee: Louis Bouchard (louis) => (unassigned) ** Changed in: makedumpfile (Ubuntu Trusty) Assignee: Louis Bouchard (louis) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1626269 Title: Ubuntu 16.10: kdump is not working in 4.8 kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1626269/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1614052] Re: SOSREPORT need to collect OPAL msglog
** Changed in: sosreport (Ubuntu Trusty) Assignee: Louis Bouchard (louis) => (unassigned) ** Changed in: sosreport (Ubuntu Xenial) Assignee: Louis Bouchard (louis) => (unassigned) ** Changed in: sosreport (Ubuntu Yakkety) Assignee: Louis Bouchard (louis) => (unassigned) ** Changed in: sosreport (Ubuntu Zesty) Assignee: Louis Bouchard (louis) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1614052 Title: SOSREPORT need to collect OPAL msglog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1614052/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1605243] Re: iscsi initiator related configs and logs are not recorded
** Changed in: sosreport (Ubuntu)
Assignee: Louis Bouchard (louis) => (unassigned)
** Changed in: sosreport (Ubuntu Trusty)
Assignee: Louis Bouchard (louis) => (unassigned)
** Changed in: sosreport (Ubuntu Xenial)
Assignee: Louis Bouchard (louis) => (unassigned)
** Changed in: sosreport (Ubuntu Yakkety)
Assignee: Louis Bouchard (louis) => (unassigned)
** Changed in: sosreport (Ubuntu Zesty)
Assignee: Louis Bouchard (louis) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1605243
Title:
iscsi initiator related configs and logs are not recorded
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1605243/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1638695] Re: Python 2.7.12 performance regression
** Changed in: python2.7 (Ubuntu) Assignee: Louis Bouchard (louis) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1638695 Title: Python 2.7.12 performance regression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1638695/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1643837] Re: Please merge clamav (0.99.2+dfsg-4) from Debian unstable
** Changed in: clamav (Ubuntu) Status: In Progress => Fix Released ** Changed in: clamav (Ubuntu) Assignee: Louis Bouchard (louis) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1643837 Title: Please merge clamav (0.99.2+dfsg-4) from Debian unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1643837/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1666239] Re: Add ZFS sosreport plugin
** Changed in: sosreport (Ubuntu Trusty) Assignee: Louis Bouchard (louis) => (unassigned) ** Changed in: sosreport (Ubuntu Xenial) Assignee: Louis Bouchard (louis) => (unassigned) ** Changed in: sosreport (Ubuntu Yakkety) Assignee: Louis Bouchard (louis) => (unassigned) ** Changed in: sosreport (Ubuntu Zesty) Assignee: Louis Bouchard (louis) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1666239 Title: Add ZFS sosreport plugin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1666239/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1614052] Re: SOSREPORT need to collect OPAL msglog
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1614052 Title: SOSREPORT need to collect OPAL msglog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1614052/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1654600] Re: unattended-upgrade-shutdown hangs when /var is a separate filesystem
** Changed in: unattended-upgrades (Ubuntu Xenial) Assignee: Louis Bouchard (louis) => (unassigned) ** Changed in: unattended-upgrades (Ubuntu Yakkety) Assignee: Louis Bouchard (louis) => (unassigned) ** Changed in: unattended-upgrades (Ubuntu Zesty) Assignee: Louis Bouchard (louis) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1654600 Title: unattended-upgrade-shutdown hangs when /var is a separate filesystem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1654600/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1687791] Re: Install of kdump-tools fails
Hello, I am surprised by a few things : first of all, linux-crashdump, hence kdump-tools, is not installed by default on a server install. So you must have added that step somehow. I have just installed Xenial using the mini.iso network install and kdump-tool is not installed after completion. I installed it without any issue, rebooted and the functionality works as expected. Now your output shows that it is the kernel's post-install trigger that fails, so this is where you should but the -x (add it to the sh -e shebang at the top of the script). Then you can run the following & paste the output here : /etc/kernel/postinst.d/kdump-tools $(uname -r) FYI, this script is responsible for building the smaller initrd used by kdump when rebooting after a crash. ...Louis -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1687791 Title: Install of kdump-tools fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1687791/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1614052] Re: SOSREPORT need to collect OPAL msglog
Hello, could someone from the reporter team or with access to the proper hardware test the package in -proposed for the following releases ? - Trusty - Xenial - Yakkety - Zesty This is the last bug which requires testing, hence it is holding the release of the sosreport with the requested fix. TIA, ...Louis -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1614052 Title: SOSREPORT need to collect OPAL msglog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1614052/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1605243] Re: iscsi initiator related configs and logs are not recorded
Test done for the following releases : Trusty, Xenial, Yakkety, Zesty
1) Launch a container
2) Enable proposed
3) apt update
4) apt install sosreport and open-iscsi(if absent)
5) sosreport --batch -oiscsi
6) Extract sosreport tarball locally
7) Verify collected files :
# ls sosreport-zesty-sosiscsi-20170505095538/etc/isc*
initiatorname.iscsi iscsid.conf
8) Verify the output of the collected commands :
find sosreport-zesty-sosiscsi-20170505095538/sos_commands/iscsi/* -exec cat {}
\; -ls
# find sosreport-zesty-sosiscsi-20170505095538/sos_commands/iscsi/* -exec cat
{} \; -ls
Iface: default
Iface: iser
34041 5 -rw-r--r-- 1 root root 27 May 5 09:55
sosreport-zesty-sosiscsi-20170505095538/sos_commands/iscsi/iscsiadm_-m_iface_-P_1
iscsiadm: No records found
34043 5 -rw-r--r-- 1 root root 27 May 5 09:55
sosreport-zesty-sosiscsi-20170505095538/sos_commands/iscsi/iscsiadm_-m_node_--op_show
iscsiadm: No records found
34044 5 -rw-r--r-- 1 root root 27 May 5 09:55
sosreport-zesty-sosiscsi-20170505095538/sos_commands/iscsi/iscsiadm_-m_node_-P_1
iscsiadm: No active sessions.
iSCSI Transport Class version 2.0-870
version 2.0-873
34042 5 -rw-r--r-- 1 root root 84 May 5 09:55
sosreport-zesty-sosiscsi-20170505095538/sos_commands/iscsi/iscsiadm_-m_session_-P_3
** Tags removed: sts-sru-needed verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1605243
Title:
iscsi initiator related configs and logs are not recorded
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1605243/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1687779] Re: Ubuntu 16.04.2: kdump is not working in 4.8.0-46 kernel
** Also affects: makedumpfile (Ubuntu Xenial) 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/1687779 Title: Ubuntu 16.04.2: kdump is not working in 4.8.0-46 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687779/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1687779] Re: Ubuntu 16.04.2: kdump is not working in 4.8.0-46 kernel
Re-targetting the bug to the linux kernel as this is not a makedumpfile issue ** Package changed: makedumpfile (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1687779 Title: Ubuntu 16.04.2: kdump is not working in 4.8.0-46 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687779/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1654600] Re: unattended-upgrade-shutdown hangs when /var is a separate filesystem
Test performed for verification-done for : - Xenial - Yakkety - Zesty 1) Installed unattended-upgrades from -proposed 2) Verified the status of the unattended-upgrades service. All displayed : # systemctl status unattended-upgrades ● unattended-upgrades.service - Unattended Upgrades Shutdown Loaded: loaded (/lib/systemd/system/unattended-upgrades.service; enabled; vendor preset: enabled) Active: active (exited) since Fri 2017-04-28 14:02:35 CEST; 47s ago Docs: man:unattended-upgrade(8) 3) Enabled Unattended-Upgrade::InstallOnShutdown "true"; in /etc/apt/apt.conf.d/50unattended-upgrades and rebooted. All releases applied the upgradeable packages upon reboot (some had too many and the timeout ran out before end of update) 4) Ran apt -y dist-upgrade on all releases. Rebooted. systems rebooted normally. 5) Enabled trusty-proposed on a Trusty system and ran do-release-upgrade to go to Xenial. After completion of the full upgrade, unattended- upgrades service was active (as seen in #2) 6) Enabled zesty-proposed on a system with /var as a separate file system. Upgraded unattended-upgrades. After upgrade, unattended-upgrades service was active (as seen in #2) 7) Verified that the workaround for Debian Bug #809669 left the upgraded system in an adequate configuration : cat /var/lib/systemd/deb-systemd-helper-enabled/unattended-upgrades.service.dsh-also /etc/systemd/system/multi-user.target.wants/unattended-upgrades.service # find /etc/systemd | grep unatt /etc/systemd/system/multi-user.target.wants/unattended-upgrades.service -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1654600 Title: unattended-upgrade-shutdown hangs when /var is a separate filesystem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1654600/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
