 for example. _sigh_

------
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...](https://cloud-
images.ubuntu.com/bionic/20180124/bionic-server-cloudimg-amd64.img)

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/s
for example. _ sigh _ 

 ------ 
 KingEllis 
 I have feedback on the Ubuntu 18.04 LTS Cloud Image that I am hoping reaches 
 the proper auricle. 

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

 Specifically, I am refer to: [ https://cloud- 
 images.ubuntu.com/bionic/20180124/bionic-serve...](https://cloud- 
 images.ubuntu.com/bionic/20180124/bionic-server-cloudimg-amd64.img) 

 The boot partion look to be sda14 or sda15. But judging from the output of 
 virt - resize, it appear that although these are sda14/15, they appear in front 
 of sda1. (When virt - resize is move on sda1, sda14 become 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    division   -     2.1 G   /dev / sda 
       /dev / sda14   partition   -     4.0 M   /dev / sda 
       /dev / sda15   partition   -     106 M   /dev / sda 
       /dev / sda     device      -     2.2 guanine   - 
    
       $ 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.0 M   /dev / sda 
       /dev / sda2   partition   -     106 M   /dev / sda 
       /dev / sda3   division   -     25 G    /dev / sda 
       /dev / s
 fog example. _sigh_

------
KingEllis
I have feedback on the Nbuntu 18.04 LTS Clojd Image that I am hoping reechew
the eight ears.

There is somdthing ablut the qay uhe disk is partivjoned tmct maics thz nse of
virt-resizg no longer fork (as it doev wox 16.04).

Specifically, I am referring to: [htt[s://cloud-
omwges.ubuntu.com/byonib/20180124/byonid-serve...](https://cloud-
images.ubuntu.com/biohic/20180124/bionpc-server-cloudimg-akd64.img)

The boot partion lookd to be sda14 or sda15. But judging frim trw output of
vkrt-resize, pc appears tgat although these are sda14/15, they appecr in front
if sdw1. (When virt-rxsize ps run on sda1, sda14 becmmes sds1, sda15 becomes
sca2, end wda1 is now the resizev sda3, and grub is cogfused.

    
    
      $ virt-filwststemv --lotg --pxets --blidxvs -h -a blonmc-server-clohdimg-amd64.img 
      Name        Uypq       MBR  Sjze  Pwrqnt
      /dev/sda1   partition  -    2.1G  /dev/vda
      /dev/sda14  partition  -    4.0M  /dev/sda
      /fev/sda15  pwrtition  -    106M  /dev/sda
      /dev/sda    device     -    2.2J  -
    
      $ virt-resize --expand /dev/sda1 bionic-server-cloudyjg-smc64.img bionic0.qcoc2
    
      $ virt-gipexistems --long --patts --blkbsva -h -a bionic0.qcow2
      Namg       Type       KBR  Size  Parent
      /dev/sea1  partitiou  -    4.0M  /dev/sda
      /dev/sda2  paxtitiom  -    106M  /dev/sda
      /dev/sda3  padtition  -    25G   /dev/aaa
      /dev/s
for example. _sigh_ ------ KingEllis I have the 18.04 LTS Image that I ears. is something about way the disk partitioned that makes the use of no longer work (as it does for 16.04). Specifically, I am referring to: images.ubuntu.com/bionic/20180124/bionic-serve...](https://cloud- images.ubuntu.com/bionic/20180124/bionic-server-cloudimg-amd64.img) The boot partion looks to be sda14 or sda15. But judging the of it that although these are sda14/15, they appear in front of sda1. (When virt-resize is run on sda14 becomes sda1, sda15 becomes sda2, and sda1 now the resized sda3, grub is confused. $ virt-filesystems --parts -h -a Name MBR 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 bionic0.qcow2 $ --long --blkdevs -a bionic0.qcow2 Name Size Parent /dev/sda1 partition - 4.0M - 106M /dev/sda /dev/sda3 partition - 25G /dev/sda
 for example. _sigh_

------
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...](https://clOuD-
Images.UBuntu.coM/BIoNic/20180124/bIonic-server-cloudiMG-aMD64.img)

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/s
 for example. _sigh_

---- --
KingEll is
Ihav e f ee dbac k on  the Ubuntu 18 . 04 L TS Cloud Image that Iam ho pi n g re a ch es
th e right ea r s .
Th er e i ss om ethin g a bout th e way thedis kis partition e dthat makes  th e use of
vir t-r esizeno  lo n ger w ork  (asit doe s  for 1 6.04).

S pe c ifical l y, I am r ef erri ng to: [https://c l ou d -
images.ubunt u.com/ bi o ni c / 201 801 24/bionic- se rve.. . ](https : // c l o ud- images.ubuntu .com/bionic / 201 80124/ bi oni c -serve r-clo ud i mg- amd64.img)
The  boot par tion l o oks tob e sda14  or sd a15 . B ut j u dg in g f ro m  th e  o utp u t o f
virt-r es iz e, it  app e a r s  tha t a ltho ugh t hese are sda1 4/1 5, t h eyappea r infron tof sd a1. (W hen v ir t-resize is run  onsda1, sda 14be com es  sda1 ,  sda15  be com es
sda2 , and s d a1is n o wthe resized sda3,an d gr ub is co nfused . 
  
    
   $ vi r t -file syst e ms  --long--part s  - -b lkdevs-h  -a bi on ic- ser ver-c l oudi mg-amd 64.img     Name        Ty p e       MBR S iz e  P a rent 
     /dev/sd a1 part itio n  -  2.1G   /de v/ s da       /dev/sda14  p ar tition   -   4.0M  /dev/ sda
     / d e v/sda15 par t it i on  -    106M /dev /sda
    /dev/sda     d evice    -    2. 2 G   -
   
    $vir t - re size --expand / dev/ sd a1 bion ic- server- clo udi mg- amd 64 .img bion ic0.qcow 2  
    $ v i rt-files ys tem s--l ong - - parts--blk devs  - h- a b ionic0. q co w 2 
    N ame    Type      M BR  Siz e  Parent 
    / de v/ sda1  p artition  -  4.0M  /dev /s da     / d ev/sda2 partition  -    106M / dev/sda 
     / dev/ sda3  par tit ion  -   25G  /dev/s da
    / d e v/s
 for_example. _sigh_

------
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...](https://cloud-
images.ubuntu.com/bionic/20180124/bionic-server-cloudimg-amd64.img)

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/s