Problem on sizing the VM

Question

Hi,

Im having a problem sizing my VM from Standard_D2s_v3 to D2s V5 but upon checking on the sizing tab their is no D2s V5 and i also want to retain my public IP

Answer 1

Hi Jared,

Reason you are not seeing D2sv5 is because it does not include temporary disk whereas the current size does include temporary disk. When using resize capability, you are limited to sizes with temporary disk since your current VM size has a temporary disk. Please see FAQ, excerpt below:

Can I resize a VM size that has a local temp disk to a VM size with no local temp disk? No. The only combinations allowed for resizing are:

1. VM (with local temp disk) -> VM (with local temp disk); and
2. VM (with no local temp disk) -> VM (with no local temp disk). If interested in a work around, please see next question.

You may retain your existing Public IP by dissociating it from the current VM's network interface and associating it with the new VM's network interface (created using workaround below).

Workaround/Solution:

Excerpt from FAQ article below:

How do I migrate my Windows VM from a size with local temp disk to a VM size with no local temp disk?

You can migrate by following these steps:

1. Connect to your Virtual Machine that has a local temporary disk (for example, a D: Drive) as a local admin.

2. Follow the guidelines on the "Temporarily move pagefile.sys to C drive" section of Use the D: drive as a data drive on a Windows VM to move the page file from the local temporary disk (D: drive) to the C: drive.

Note Follow the guidelines on the "Temporarily move pagefile.sys to C drive" section of Use the D: drive as a data drive on a Windows VM to move page file from the local temporary disk (D: drive) to C: drive. Deviation from the steps outlined will lead to the error message - "Unable to resize the VM since changing from resource disk to non-resource disk VM size and vice-versa is not allowed.

3. Take a snapshot of the VM by following the steps outlined in Create a snapshot using the portal or Azure CLI.

4. Use snapshot to create a new diskless VM (such as, Dv5, Dsv5, Dasv5, Ev5, Esv5, Easv5 series) by following the steps outlined in Create a virtual machine from a snapshot with CLI.

If you have concerns please add comment below.

Please click Accept Answer and upvote if the above was helpful.

Thanks.

-TP

Answer 2

To resolve it, we walked through the official migration workaround step-by-step on their Windows VM:

Connected as local admin and moved the pagefile.sys from the temp disk (D: drive) to C: drive, following the exact guidelines in Use the D: drive as a data drive to avoid resize errors.

Created a snapshot of the VM OS disk via the portal, as detailed in Create a snapshot.

Used the snapshot to deploy a new diskless VM (Dsv4 series) with Azure CLI, per Create VM from snapshot.

We also dissociated their existing Public IP from the old NIC and reassociated it to the new VM's NIC to retain it seamlessly. The new VM is now running successfully without issues.