Skip to content

Commit ee13ab8

Browse files
committed
text edits
1 parent 7a08ee1 commit ee13ab8

File tree

1 file changed

+10
-10
lines changed

1 file changed

+10
-10
lines changed

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

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -342,40 +342,40 @@ sections:
342342
|
343343
344344
- question: |
345-
VM images must have 1-MB free space
345+
VM images must have 1 MB of free space
346346
answer: |
347347
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.
348348
349349
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.
350350
351351
To keep the first 1 MB free in your OS disk, complete the steps in the next section.
352352
353-
### How to keep 1 MB of free space at the start on an empty VHD (2,048 sectors, each sector of 512 bytes)
353+
### How to keep 1 MB of free space at the start on an empty VHD (2,048 sectors, each sector 512 bytes)
354354

355355
These steps apply only to Linux.
356356

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

359359
![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)
360360

361361
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**.
362362

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

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

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

369369
1. Attach your VHD as data disk to your VM for creating a partition table.
370370

371-
1. Select **Attach existing disk**:
371+
1. Select **Attach existing disks**:
372372

373-
![Screenshot showing how to add a data disk to your VHD.](./media/create-vm/existing-data-disk.png)
373+
![Screenshot showing how to add a data disk to your V H D.](./media/create-vm/existing-data-disk.png)
374374

375-
![Screenshot showing how to select the data disk for your VHD](./media/create-vm/source-data-disk.png)
375+
![Screenshot showing how to select the data disk for your V H D.](./media/create-vm/source-data-disk.png)
376376

377377
1. Find your VHD storage account.
378-
1. Select **Container** and then select your VHD.
378+
1. Select **Container**, and then select your VHD.
379379
1. Select **OK**.
380380

381381
![Screenshot of the attach unmanaged disk page.](./media/create-vm/vm-certification-issues-solutions-19.png)
@@ -401,7 +401,7 @@ sections:
401401
1. Enter 2048 as _first sector_ value. You can leave _last sector_ as the default value.
402402

403403
>[!IMPORTANT]
404-
>Any existing data will be erased until 2048 sectors (each sector of 512 bytes). Backup of the VHD before you create a new partition.
404+
>Any existing data will be erased until 2048 sectors (each sector of 512 bytes). Back up the VHD before you create a new partition.
405405

406406
![Putty client command-line screenshot showing the commands and output for erased data.](./media/create-vm/vm-certification-issues-solutions-22.png)
407407

0 commit comments

Comments
 (0)