What Will the System Do to an Image File When I Use the File to Register a Private Image?¶
You are advised to enable automatic configuration when registering a private image using an image file. Then, the system will perform the following operations:
Linux¶
Check whether any PV drivers exist. If yes, the system deletes them.
Modify the grub and syslinux configuration files to add the OS kernel boot parameters and change the disk partition name (UUID=UUID of the disk partition).
Change the names of the disk partitions in the /etc/fstab file (UUID=UUID of the disk partition).
Check whether the initrd file has the IDE driver. If no, the system will load the IDE driver.
Modify the X Window configuration file /etc/X11/xorg.conf to prevent display failures.
Delete services of VMware tools.
Record the latest automatic modification made to the image into /var/log/rainbow_modification_record.log.
Copy the built-in VirtIO driver to initrd or initramfs. For details, see External Image File Formats and Supported OSs.
Note
For the following image files, the system does not copy this driver after Enable automatic configuration is selected:
Image files whose /usr directory is an independent partition
Fedora 29 64bit, Fedora 30 64bit, and CentOS 8.0 64bit image files that use the XFS file system
SUSE 12 SP4 64bit image files that use the ext4 file system
Windows¶
Restore the IDE driver to enable the OS to use this driver for its initial start.
Delete the registry keys of the mouse and keyboard and generate the registry keys on the new platform to ensure that the mouse and keyboard are available.
Inject the VirtIO driver offline so that the system can start without UVP VMTools installed.
Restore DHCP. The system will dynamically obtain information such as the IP address based on the DHCP protocol.