What are the side effects of cloudbase-init automatic disk expansion?

Today, I will talk to you about the side effects of cloudbase-init automatic expansion. Many people may not know much about it. In order to let you know more, Xiaobian summarized the following contents for you. I hope you can gain something according to this article.

One of the features of cloudbase-init is to automatically expand Windows C drives. For example, if the Windows image is 20G, and the flavor disk definition selected when deploying instance is 40G, then cloudbase-init will automatically expand the C disk to 40G when deploying instance.

cloudbase-init auto-expand This is what we need, but it has a side effect.

In windows, we can divide the hard disk into multiple logical disks C: , D: , etc. For example, for 40G of space, the user can give C disk 20G, D disk 20G, but this will be a problem for the system with cloudbase-init installed.

Cloudbase-init merges drive C and drive D into a single drive C each time the system boots.

The solution to this problem is simple: uninstall cloudbase-init, and you're back to a normal windows virtual machine. However, if you resize instance later in OpenStack, you can only manually expand the disk.

The recommended way is: the system disk is only used as disk C. If you need disk D and disk E, you can add a cylinder volume.

After reading the above, do you have any further understanding of the side effects of cloudbase-init auto-expansion? If you still want to know more knowledge or related content, please pay attention to the industry information channel, thank you for your support.