Azure images are Microsoft VHD files which use the .vhd extension. We use the mkimg format arg "vhdf" to specify the fixed vhd format, but the extension should remain .vhd.
Details
Details
- Reviewers
whu lwhsu - Group Reviewers
releng - Commits
- rG641a58239520: nullfs: avoid the interlock in null_lock with smr
rG249ec85352b5: nullfs: smr-protected hash lookup
rG72347d73464c: nullfs: assert the vnode is not doomed in null_hashget_locked
rG94aae0513896: nullfs: remove the vhold/vdrop cycle around unlock
rG2d997bf6b5a5: release: Use standard Azure disk image extension
rGfb77d8e546e1: release: Use standard Azure disk image extension
Diff Detail
Diff Detail
- Repository
- rG FreeBSD src repository
- Lint
Lint Not Applicable - Unit
Tests Not Applicable
Event Timeline
Comment Actions
I'm fine with this. For the record, when I worked on this, I kept azure.vhdf as it is an intermediate product and for aligning with other images. Note that the azure-do-upload target in Makefile.azure will upload as .vhd suffix, with more clear naming.
Comment Actions
I garbage collected the AZURE_DISK variable since it was unused. (Note that CLOUDWARE does not include AZURE so in fact *none* of the cloudware-related AZURE variables are used, but _DISK in particular isn't used for any of the cloudwares.)
The AZURE_IMG bit needs to change since we now have support for building separate UFS and ZFS images (with different file names).