Skip to content

Commit 559635f

Browse files
committed
alignment
1 parent a923d7f commit 559635f

File tree

1 file changed

+15
-15
lines changed

1 file changed

+15
-15
lines changed

articles/marketplace/azure-vm-certification-faq.yml

Lines changed: 15 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -345,35 +345,35 @@ sections:
345345
VM images must have 1-MB free space
346346
answer: |
347347
348-
If you are publishing your image to Azure (with **GPT partition**), we *highly recommend* that you keep the first 2,048 sectors (1 MB) of the OS disk empty. This requirement is to allow Azure to add important metadata to the image (examples include metadata to improve boot time for customers, billing, and other details). Note that this is a recommendation for best practice if you are already using [an approved base image](azure-vm-create-using-approved-base.md) and your image has a valid billing tag. However, if your image does not have a valid billing tag, your publishing might fail if the first 1 MB of the OS disk isn't empty.
348+
If you are publishing your image to Azure (with **GPT partition**), we *highly recommend* that you keep the first 2,048 sectors (1 MB) of the OS disk empty. This requirement is to allow Azure to add important metadata to the image (examples include metadata to improve boot time for customers, billing, and other details). Note that this is a recommendation for best practice if you are already using [an approved base image](azure-vm-create-using-approved-base.md) and your image has a valid billing tag. However, if your image does not have a valid billing tag, your publishing might fail if the first 1 MB of the OS disk isn't empty.
349349
350-
If you are building your own image that does not have any valid billing tag, ensure the first 2,048 sectors (1 MB) of the OS disk are empty. Otherwise, your publishing will fail. This requirement is applicable to the OS disk only (not data disks). If you are building your image from an approved base, it will already have first 1 MB empty. Hence, you won't need to work on it separately.
350+
If you are building your own image that does not have any valid billing tag, ensure the first 2,048 sectors (1 MB) of the OS disk are empty. Otherwise, your publishing will fail. This requirement is applicable to the OS disk only (not data disks). If you are building your image from an approved base, it will already have first 1 MB empty. Hence, you won't need to work on it separately.
351351
352-
To keep the first 1 MB free in your OS disk, complete the steps in the next section.
352+
To keep the first 1 MB free in your OS disk, complete the steps in the next section.
353353
354-
### How to keep 1 MB of free space at the start on an empty VHD (2,048 sectors, each sector of 512 bytes)
354+
### How to keep 1 MB of free space at the start on an empty VHD (2,048 sectors, each sector of 512 bytes)
355355

356-
These steps apply only to Linux.
356+
These steps apply only to Linux.
357357

358-
1. Create any kind of Linux VM, such as Ubuntu, CentOS, or other. Fill the required fields and select **Next: Disks >**.
358+
1. Create any kind of Linux VM, such as Ubuntu, CentOS, or other. Fill the required fields and select **Next: Disks >**.
359359

360-
![Screenshot that shows the Create a virtual machine page with the Next: Disks command button highlighted.](./media/create-vm/vm-certification-issues-solutions-15.png)
360+
![Screenshot that shows the Create a virtual machine page with the Next: Disks command button highlighted.](./media/create-vm/vm-certification-issues-solutions-15.png)
361361

362-
1. Create an unmanaged disk for your VM. Either use the default values or specify any value for fields like **OS disk size**, **OS disk type**, and **Encryption type**.
362+
1. Create an unmanaged disk for your VM. Either use the default values or specify any value for fields like **OS disk size**, **OS disk type**, and **Encryption type**.
363363

364-
![Screenshot image of the Data disks page in the Create a virtual machine flow.](./media/create-vm/disks-pane.png)
364+
![Screenshot image of the Data disks page in the Create a virtual machine flow.](./media/create-vm/disks-pane.png)
365365

366-
1. After you create the VM, select **Disks** in the left pane.
366+
1. After you create the VM, select **Disks** in the left pane.
367367

368-
![Screenshot showing how to select disks for a VM.](./media/create-vm/vm-certification-issues-solutions-17.png)
368+
![Screenshot showing how to select disks for a VM.](./media/create-vm/vm-certification-issues-solutions-17.png)
369369

370-
1. Attach your VHD as data disk to your VM for creating a partition table.
370+
1. Attach your VHD as data disk to your VM for creating a partition table.
371371

372-
1. Select **Attach existing disk**:
372+
1. Select **Attach existing disk**:
373373

374-
![Screenshot showing how to add a data disk to your VHD.](./media/create-vm/existing-data-disk.png)
374+
![Screenshot showing how to add a data disk to your VHD.](./media/create-vm/existing-data-disk.png)
375375

376-
![Screenshot showing how to select the data disk for your VHD](./media/create-vm/source-data-disk.png)
376+
![Screenshot showing how to select the data disk for your VHD](./media/create-vm/source-data-disk.png)
377377

378378
1. Find your VHD storage account.
379379
1. Select **Container** and then select your VHD.

0 commit comments

Comments
 (0)