I tested on my nvme system with the boot param 'maxcpus=0' (i.e. UP mode), the boot fails with kernel 4.4.0-57, because the nvme drive fails enumeration, with the error from comment 2. With the 4.4.0-57 kernel including my nvme patch, and using boot param 'maxcpus=0', the boot succeeds. The patched kernel is at this ppa: https://launchpad.net/~ddstreet/+archive/ubuntu/lp1651602
and the patch is here: https://lists.ubuntu.com/archives/kernel-team/2016-December/081637.html the patch fixes a bug introduced by my previous commit 96fce9e4025b ("NVMe: only setup MSIX once") which is only currently included in Xenial, so this patch only needs to be applied to Xenial. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1651602 Title: [2.1.1] MAAS has nvme0n1 set as boot disk, curtin fails Status in MAAS: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: MAAS Version 2.1.1+bzr5544-0ubuntu1 (16.10.1) Deploying Xenial Nodes 1) Deploy MAAS 2.1.1 on Yakkety 2) Associate Juju 2.1 beta3 3) Juju deploy Kubernetes Core Nodes begin to deploy but fail Installation failed with exception: Unexpected error while running command. Command: ['curtin', 'block-meta', 'custom'] Exit code: 3 Reason: - Stdout: b"no disk with serial 'CVMD434500BN400AGN' found\n" To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1651602/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
