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
+15-15Lines changed: 15 additions & 15 deletions
Original file line number
Diff line number
Diff line change
@@ -345,35 +345,35 @@ sections:
345
345
VM images must have 1-MB free space
346
346
answer: |
347
347
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.
349
349
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.
351
351
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.
353
353
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)
355
355
356
-
These steps apply only to Linux.
356
+
These steps apply only to Linux.
357
357
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 >**.
359
359
360
-

360
+

361
361
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**.
363
363
364
-

364
+

365
365
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.
367
367
368
-

368
+

369
369
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.
371
371
372
-
1. Select **Attach existing disk**:
372
+
1. Select **Attach existing disk**:
373
373
374
-

374
+

375
375
376
-

376
+

0 commit comments