[KingEllis]

I have feedback on the Ubuntu 18.04 LTS Cloud Image that I am hoping reaches the right ears.

There is something about the way the disk is partitioned that makes the use of virt-resize no longer work (as it does for 16.04).

Specifically, I am referring to: https://cloud-images.ubuntu.com/bionic/20180124/bionic-serve...

The boot partion looks to be sda14 or sda15. But judging from the output of virt-resize, it appears that although these are sda14/15, they appear in front of sda1. (When virt-resize is run on sda1, sda14 becomes sda1, sda15 becomes sda2, and sda1 is now the resized sda3, and grub is confused.

  $ virt-filesystems --long --parts --blkdevs -h -a bionic-server-cloudimg-amd64.img 
  Name        Type       MBR  Size  Parent
  /dev/sda1   partition  -    2.1G  /dev/sda
  /dev/sda14  partition  -    4.0M  /dev/sda
  /dev/sda15  partition  -    106M  /dev/sda
  /dev/sda    device     -    2.2G  -

  $ virt-resize --expand /dev/sda1 bionic-server-cloudimg-amd64.img bionic0.qcow2

  $ virt-filesystems --long --parts --blkdevs -h -a bionic0.qcow2
  Name       Type       MBR  Size  Parent
  /dev/sda1  partition  -    4.0M  /dev/sda
  /dev/sda2  partition  -    106M  /dev/sda
  /dev/sda3  partition  -    25G   /dev/sda
  /dev/sda   device     -    25G   -

I am hoping this can be addressed before April, as I would prefer not to maintain my own LTS image (that doesn't have this issue).

[dustinkirkland]

Thanks! I'll make sure that gets to the right team!