fixed!

issue was virtualization was not enabled in BIOS settings
logs on XOA was not good enough

xcp-ng center gave me a better error log message of HVM is Required for this Operation

thanks!

@fohdeesha

created the cloud image and here is what am getting when booting a new VM from the cloud image

the VM is unable to complete boot process

@olivierlambert

I do not see HUB in 5.46

@olivierlambert what is link to hub?

the documentation in blog post is also what am after

@fohdeesha ok great..will try it out

any plan to release ubuntu 20.04 cloud image on blog? community will really appreciate it

thanks!!!

any help?

is this going to work with creating a cloud image?

@olivierlambert thanks!

To my original question, will the ubuntu be able to be used as cloud image?

here is current storage

root@ubuntu:~# fdisk -l
Disk /dev/loop0: 55.45 MiB, 58130432 bytes, 113536 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop1: 70.32 MiB, 73728000 bytes, 144000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop2: 32.3 MiB, 33865728 bytes, 66144 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/xvda: 8 GiB, 8589934592 bytes, 16777216 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 8821F92D-EF64-44B5-9F75-A25778F4AD7E

Device     Start      End  Sectors Size Type
/dev/xvda1  2048     4095     2048   1M BIOS boot
/dev/xvda2  4096 16775167 16771072   8G Linux filesystem

Is anyone able to create Ubuntu 20.04 cloud image?
As we all know it is necessary to create a manual single partition but i was unable to create a single partition with Ubuntu 20.04 installation step. It never has the done clickable and just could not create a single partition

After several back and forth and trying all options to create a single partition, so i ended up using the option use entire disk and here is what i have after installation is completed

root@ubuntu:~# fdisk -l
Disk /dev/loop0: 55.45 MiB, 58130432 bytes, 113536 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop1: 70.32 MiB, 73728000 bytes, 144000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop2: 32.3 MiB, 33865728 bytes, 66144 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/xvda: 8 GiB, 8589934592 bytes, 16777216 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 8821F92D-EF64-44B5-9F75-A25778F4AD7E

Device     Start      End  Sectors Size Type
/dev/xvda1  2048     4095     2048   1M BIOS boot
/dev/xvda2  4096 16775167 16771072   8G Linux filesystem

Will this work to create a cloud image? I am following this (very old) guide https://xen-orchestra.com/blog/debian-cloud-template-for-xenserver/

Anyone able to succeed with this?

P.S. @olivierlambert any plan to create a new blog post on newer Ubuntu 20.04 cloud image? old debian link here https://xen-orchestra.com/blog/debian-cloud-template-for-xenserver/

@fohdeesha

yeah for the centos 8 i think am fine with that
the ubuntu one does not work at all
i have my full cloud init config posted here https://xcp-ng.org/forum/topic/2387/how-to-create-single-partition-on-ubuntu-18-04-for-cloud-image/9

@fohdeesha

here is what is in my XOA cloud config file

#cloud-config
hostname: host
ssh_authorized_keys:
  - ssh-rsa user1@host1
  - ssh-rsa user2@host2
  - ssh-rsa user3@host3

redacted the ssh keys ofcourse but thats all am doing..just change hostname and add SSH keys..thats it

the SSH keys get added fine for centos 8, but hostname not working

@olivierlambert

yeah so far i got everything to work on centos 8 cloud image
only thing not working is the hostname changing..the hostname is not working
creating new VMs with a different hostname does not work and keeps hostname of the template