VM images versus cloud images

[elasmo]

The distinguishment between VM images (vm image) and cloud images (vm img) is unclear and not explained in VM-BHYVE(8) and somewhat confusing for an end-user.

Excerpt from VM-BHYVE(8)

...
     vm image list
     vm image create [-d description] [-u] name
     vm image provision [-d datastore] uuid new-name
     vm image destroy uuid
...
     image list
             List available images.  Any virtual machine can be packaged into
             an image, which can then be used to create additional machines.
...

Excerpt from README.md ... To launch FreeBSD using official cloud image:

# vm img https://download.freebsd.org/ftp/releases/VM-IMAGES/11.2-RELEASE/amd64/Latest/FreeBSD-11.2-RELEASE-amd64.raw.xz
# vm create -t freebsd-zvol -i FreeBSD-11.2-RELEASE-amd64.raw freebsd-cloud
# vm start freebsd-cloud

To list downloaded images:

# vm img
DATASTORE           FILENAME
default             CentOS-7-x86_64-GenericCloud-20180930_02.raw
default             debian-9-openstack-amd64.qcow2

...

[Ofloo]

Also there seems to be an option running vm create -C -k that assigns to add a public key from what I can tell all it does is make a cdrom image with the supplied public key in a file called user_data.

Is there anything that it supposed to be doing? Can't seem to find any documentation on that in the man page nor on vm img.

Also -C -k -n flag are missing from the man mages. For vm create maybe I'm missing something

vm img isn't in there at all. At least for me. Installed vm-bhyve from pkg version is 1.5.0

[elasmo]

@Ofloo The cdrom image is used by cloud-image typically bundled with cloud images. It makes it possible to ssh into the guest without manually adding the key to an authorized_keys file or by using ssh-copy-id. Please, use the master branch while considering open issues here. Issues existing in the package version are likely to be fixed, and new functionality added.

[PetruGarstea]

it looks like specifying the disk size when disk0_dev="file" is instead of disk0_dev="sparse-zvol" doesnt work. I expect when qemu-img converts the cloud image the vm framework has to resize the disk0.img file to at least default 20G.

if you opt out "spare-zvol" in favour "file", here is the quick tutorial on how to resize the disk:

vm stop $name
truncate -s 40G disk0.img
vm start $name
gpart recover nda0
gpart resize -i 5 -a 1m nda0
zpool set autoexpand=on zroot
zpool online -e zroot nda0p5

UPDATE I found that last month the fix was merged

The issue was reported.

I assume it will appear soon in the pkg repositories