Comment 19 for bug 1727358

I've taken your kernel (vmlinuz-4.4.0-1009-kvm) and booted a "normal" cloud image with that kernel.
It hangs similarly (but for noticibly shorter time).

http://cloud-images.ubuntu.com/daily/server/artful/20171026.1/artful-server-cloudimg-amd64.img

I did have to disable the UEFI partition (vfat) since there were modules for your kernel in /lib.

$ qemu-img create -f qcow2 -b artful-cloud-image.img my.img
$ sudo mount-image-callback -vv my.img -- mchroot sed -i "/LABEL=UEFI/s/^/#/" /etc/fstab

$ xkvm --netdev=user --disk=my.img --disk=my-seed.img
-- -snapshot -m 768 -nographic -echr 0x05 -smp 2 -kernel vmlinuz-4.4.0-1009-kv
m -append "root=PARTUUID=9697fbdd-a35d-46d6-a51c-08bfab833468 console=ttyS0 syst
emd.log_target=console systemd.log_level=info systemd.log_target=console"

 qemu-system-x86_64 -enable-kvm -device virtio-scsi-pci,id=virtio-scsi-xkvm -device virtio-net-pci,netdev=net00 -netdev type=user,id=net00 -drive file=my.img,id=disk00,if=none,format=qcow2,index=0 -device virtio-blk,drive=disk00,serial=my.img -drive file=my-seed.img,id=disk01,if=none,format=raw,index=1 -device virtio-blk,drive=disk01,serial=my-seed.img -snapshot -m 768 -nographic -echr 0x05 -smp 2 -kernel vmlinuz-4.4.0-1009-kvm -append "root=PARTUUID=9697fbdd-a35d-46d6-a51c-08bfab833468 console=ttyS0 systemd.log_target=console systemd.log_level=info systemd.log_target=console"

...

log looks like this, and hangs there.
 http://paste.ubuntu.com/25832616/

Heres a diff of configs for the not working kernel and the working kernel.
$ diff -u config-4.4.0-59-generic config-4.4.0-1009-kvm |
   pastebinit -f diff
http://paste.ubuntu.com/25825403/