To verify this is fixed, I have done the following. For good measure, I've also successfully booted the above with additional parameter '-smp cpus=2'. That verifies that there is no obvious regression on SMP system.
$ img_url="http://cloud-images.ubuntu.com/daily/server/xenial/current/xenial-server-cloudimg-amd64-disk1.img"; $ wget "${img_url}" -O disk.img # patch the image to have a root passwd and disable cloud-init for simplicity. $ sudo mount-image-callback disk.img -- chroot _MOUNTPOINT_ sh -exc ' touch /etc/cloud/cloud-init.disabled echo "root:root" | chpasswd' # attached 'get-kernels' enables proposed, installs linux-virtual into disk.img # and copies kernels out to out.d $ ./get-kernels disk.img linux-virtual out.d $ for i in out.d/*info; do echo == $i ==; cat $i; done == out.d/build.info == build_name: server serial: 20170106.1 == out.d/vmlinuz-4.4.0-57-generic.pkg-info == linux-image-4.4.0-57-generic: /boot/vmlinuz-4.4.0-57-generic == out.d/vmlinuz-4.4.0-59-generic.pkg-info == linux-image-4.4.0-59-generic: /boot/vmlinuz-4.4.0-59-generic $ kver=4.4.0-57 ; qemu-system-x86_64 -enable-kvm -m 512 \ -drive file=disk.img,if=none,format=qcow2,id=nvme0 \ -device nvme,drive=nvme0,serial=nvme-0 \ -snapshot -nographic -echr 0x05 \ -kernel out.d/vmlinuz-$kver-generic \ -initrd out.d/initrd.img-$kver-generic \ -append "root=LABEL=cloudimg-rootfs console=ttyS0" # if you set 'ver' to 4.4.0-57 (from released kernel version) # then you see failure to find root device from the initramfs # if you set 'ver' to 4.4.0-59 (from -proposed) then it finds root, # and you can log in as root on console with 'root'. ** Attachment added: "get-kernels: enable proposed, install a kernel, copy kernels out." https://bugs.launchpad.net/maas/+bug/1651602/+attachment/4801992/+files/get-kernels ** Tags removed: verification-needed-xenial ** Tags added: verification-done-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: NVMe driver regression for non-smp/1-cpu systems Status in curtin: Invalid Status in MAAS: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Committed 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" Related bugs: * bug 1647485: NVMe symlinks broken by devices with spaces in model or serial strings * bug 1642903: introduce disk/by-id (model_serial) symlinks for NVMe drives To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+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
