You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/marketplace/azure-vm-certification-faq.yml
+10-10Lines changed: 10 additions & 10 deletions
Original file line number
Diff line number
Diff line change
@@ -342,40 +342,40 @@ sections:
342
342
|
343
343
344
344
- question: |
345
-
VM images must have 1-MB free space
345
+
VM images must have 1 MB of free space
346
346
answer: |
347
347
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
348
349
349
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
350
351
351
To keep the first 1 MB free in your OS disk, complete the steps in the next section.
352
352
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)
354
354
355
355
These steps apply only to Linux.
356
356
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**.
358
358
359
359

360
360
361
361
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
362
363
363

364
364
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**.
366
366
367
-

367
+

368
368
369
369
1. Attach your VHD as data disk to your VM for creating a partition table.
370
370
371
-
1. Select **Attach existing disk**:
371
+
1. Select **Attach existing disks**:
372
372
373
-

373
+

374
374
375
-

375
+

376
376
377
377
1. Find your VHD storage account.
378
-
1. Select **Container** and then select your VHD.
378
+
1. Select **Container**, and then select your VHD.
379
379
1. Select **OK**.
380
380
381
381

@@ -401,7 +401,7 @@ sections:
401
401
1. Enter 2048 as _first sector_ value. You can leave _last sector_ as the default value.
402
402
403
403
>[!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.
405
405
406
406

0 commit comments