CN118760448A - Method, device and application of automatic burning virtual machine system - Google Patents

Abstract

The present invention proposes a method, device and application of automatically burning a virtual machine system, including creating or downloading and executing a first script, creating a virtual machine with default parameters and setting two virtual optical drives and two virtual hard disks, filling in corresponding image files and setting hard disk capacity as needed, activating the virtual machine after setting the startup sequence, entering the command line interface of Linux maintenance mode after the virtual machine is started, creating or downloading and executing a second script for burning, burning the virtual machine system to be burned from the second virtual optical drive to the first virtual hard disk, and shutting down the virtual machine after the burning is successful. It also includes file detection, virtual device detection before burning, executing a third script for subsequent cleanup, and a fourth script to delete the virtual machine. It has the advantages of wide compatibility, automatic and efficient, low cost, and safe and stable.

Description

Method, device and application of automatic burning virtual machine system

Technical Field

The present invention relates to the field of virtual machine technology, and in particular to a method, a device and an application thereof for an automated virtual machine burning system.

Background Art

In virtual machine technology, a virtual machine must be installed with a corresponding operating system. However, many operating systems do not provide image files that can be directly installed. Such image files need to be burned into a medium with a boot function before the installation of the virtual machine system can be booted.

Currently, the common virtual machine system burning methods are mainly the following:

1. Use the commands provided by the virtual machine management system to burn it to the local virtual hard disk. When in use, read the local virtual hard disk to boot the installation of the virtual machine system.

2. Use a third-party hard disk burning tool to burn it to the local virtual hard disk. When in use, read the local virtual hard disk to boot the installation of the virtual machine system.

3. Use third-party optical drive burning software to burn the disc to an external optical disc device. When using it, connect the optical disc device to the target virtual machine management system/virtual machine management software through the CD/DVD optical drive to boot the virtual machine system for installation.

4. Use third-party storage burning software to burn to an external storage device. When in use, connect the storage device to the target virtual machine management system/virtual machine management software via a data cable or interface to boot the virtual machine system for installation.

However, these existing methods have the following obvious defects:

1. Poor compatibility: The built-in burning command only supports a few virtual machine management systems, while the rest of the virtual machine management systems and most virtual machine management software require an additional computer to install specific third-party burning tools for burning, which is not very universal.

2. High cost: Some burning methods require the preparation of an external storage device such as a USB flash drive or USB drive or CD or SD card or mobile hard disk that meets the requirements of sufficient capacity, stability, high speed, and security. Some burning tools even require payment, which increases expenditure costs; changing to different platforms often requires changing corresponding tools and methods, increasing learning costs; many methods can only be manually operated in the interface and cannot be automated, which increases time costs.

3. High risk: The environment affects the working state of external devices. High temperature, low temperature, power failure, poor contact, etc. will cause burning failure. Wrong operation methods may cause data loss, burning abnormalities, etc. Poor storage chips and materials may lead to uncontrollable consequences and low stability.

4. Low efficiency: Many burning methods require specific operating steps; some methods also require manual verification to check whether the burning is successful; a storage device can only be used to install a virtual machine, and it cannot be automated or synchronized with multiple virtual machine systems at the same time; during the burning process, it is necessary to continuously connect, identify, read, remove and other complicated and trivial operations of storage devices on different platforms, which is inefficient.

Summary of the invention

The embodiments of the present invention provide a method, device and application of an automatic burning virtual machine system, aiming at the problems of poor compatibility, high cost, high risk and low efficiency existing in the current technology.

The core technology of the present invention mainly utilizes the Linux maintenance mode to realize the automatic burning and installation of the virtual machine system through a series of scripts, including the steps of creating a virtual machine, setting up virtual devices, entering maintenance mode, performing burning operations, cleaning and optional virtual machine deletion, etc., which solves many problems of existing virtual machine burning methods.

In a first aspect, the present invention provides a method for automatically burning a virtual machine system, the method comprising the following steps:

S00, creating or downloading and executing a first script;

S10, creating a virtual machine with default parameters, and setting the number of virtual CD-ROM drives and virtual hard disks to two;

S20, filling the image file of the Linux system to be maintained into the first virtual CD-ROM drive, filling the image file of the virtual machine system to be burned into the second virtual CD-ROM drive, and setting the capacity of the two virtual hard disks as needed;

S30, setting the boot sequence, setting and activating the virtual machine according to the first virtual CD-ROM drive, the second virtual CD-ROM drive, the first virtual hard disk and the second virtual hard disk;

S40. After the virtual machine is started, enter the command line interface of Linux maintenance mode;

S50, creating or downloading and executing a second script;

S60, using a burning command to burn the virtual machine system to be burned from the second virtual optical drive to the first virtual hard disk;

S70. After the burning is successful, shut down the virtual machine.

Furthermore, in step S20, the capacity of the first virtual hard disk is set to be more than twice the size of the image file of the virtual machine system to be burned, and the capacity of the second virtual hard disk is set to be more than 32 GB.

Furthermore, between step S10 and step S20, a file check is performed, including the virtual machine system file to be burned and the Linux file with maintenance mode; if the file does not exist, it is downloaded from the network and decompressed.

Furthermore, in step S60, before burning, it is first detected whether all virtual hard disks and virtual optical drives are successfully loaded, and the number is greater than or equal to 2;

If yes, the virtual hard disk and virtual optical drive will be automatically matched according to capacity and type; if not, an error message will be given and the burning process will be exited.

Furthermore, the method further includes step S80, after shutting down the virtual machine, creating or downloading and executing a third script;

In step S90, all virtual optical drives are deleted and the virtual machine is restarted to enter the virtual machine system installation interface, and the second virtual hard disk is used as the system installation disk.

Furthermore, a fourth script is included, which deletes the corresponding virtual machine in response to the virtual machine ID input by the user, or deletes all virtual machines in response to the all-delete instruction input by the user.

Furthermore, in step S00, a temporary file storage server is located in a local area network, and all scripts and image files are stored on the temporary file storage server.

In a second aspect, the present invention provides a device for automatically burning a virtual machine system, comprising:

Temporary file storage server module, used to store all scripts and image files;

The LAN module provides local network services for data interaction between the temporary file storage server module and the virtual machine module;

The virtual machine module is used to create a virtual machine with default parameters and set the number of virtual optical drives and virtual hard disks to two; fill the image file of the Linux system to be maintained in the first virtual optical drive, fill the image file of the virtual machine system to be burned in the second virtual optical drive, and set the capacity of the two virtual hard disks as needed; set the startup sequence, set and activate the virtual machine according to the first virtual optical drive, the second virtual optical drive, the first virtual hard disk and the second virtual hard disk; after the virtual machine is started, enter the command line interface of the Linux maintenance mode; create or download and execute the second script; use the burning command to burn, and burn the virtual machine system to be burned from the second virtual optical drive to the first virtual hard disk; and shut down the virtual machine after the burning is successful.

In a third aspect, the present invention provides an electronic device, including a memory and a processor, wherein a computer program is stored in the memory, and the processor is configured to run the computer program to execute the above-mentioned method of automatically burning a virtual machine system.

In a fourth aspect, the present invention provides a readable storage medium, in which a computer program is stored. The computer program includes a program code for controlling a process to execute the process. The process includes the method of automatically burning a virtual machine system according to the above-mentioned method.

The main contributions and innovations of the present invention are as follows:

1. Improved compatibility

In the prior art, the use of built-in burning commands only supports a few virtual machine management systems, while the remaining virtual machine management systems and most virtual machine management software need to rely on an additional computer to install a specific third-party burning tool for burning, and the versatility is not high. The present invention implements the burning of virtual machine systems in Proxmox VE through specific scripts and processes, does not rely on specific virtual machine management systems or additional computers, and greatly improves compatibility. Therefore, the current mainstream virtual machine management systems directly installed on the motherboard, such as Proxmox VE, VMware Esxi, Unraid, etc., and virtual machine management software installed on the host host, such as Parallels Desktop, VMware Fusion, VMware Workstation Player, Oracle VM Virtual Box, etc., can all adopt the method of the present invention. The specific platform only needs targeted trimming, the basic steps are consistent, and it is not limited to specific platforms and specific devices, and it has strong versatility.

2. Cost reduction

In the prior art, some burning methods require the preparation of external storage devices, which increases the expenditure cost; changing different platforms often requires the replacement of corresponding tools and methods, which increases the learning cost; many methods can only be operated manually in the interface and cannot be automated, which increases the time cost. The present invention does not require additional external storage devices, and the required scripts and image files can be obtained through the temporary file storage server in the local area network, reducing the expenditure cost. At the same time, the entire burning and installation process has a high degree of automation, which reduces the learning cost and time cost. Various files and startup virtual disks can be deleted directly after use, saving the capacity of the local hard disk. The effect of slimming and leaving no trace is achieved.

3. Risk reduction

In the prior art, the environment affects the working state of external devices. High temperature, low temperature, power failure, poor contact, etc. can cause burning failure. Wrong operation methods may cause data loss, burning abnormalities, etc. Poor storage chips and materials may lead to uncontrollable consequences and low stability. The present invention performs burning operations inside the virtual machine, which is not affected by external environmental factors and reduces the risk of burning failure. At the same time, through strict detection and matching steps, the accuracy and stability of the burning process are ensured.

4. Improved efficiency

In the prior art, many burning methods require specific operation steps; some methods also require manual verification to check whether the burning is successful; a storage device can only be used for the installation of a virtual machine, and it is impossible to automate and simultaneously burn multiple virtual machine systems; during the burning process, it is necessary to continuously perform complicated and trivial operations such as connecting, identifying, reading, and removing storage devices on different platforms, etc., which is inefficient. The present invention uses automated script execution, except for manual selection and manual input required to enter the maintenance mode of Linux, other operations are completely automated, without the need for manual intervention and manual proofreading; there is no need to frequently connect/remove storage devices; there is no restriction that a storage device can only be connected to one virtual machine; it also avoids the need to clear the storage device and format it in a specific format, and any system can be burned at will, which is flexible and free; in addition, it can simultaneously carry out synchronous burning deployment of multiple virtual machine systems, and the efficiency is increased by 90% compared with the previous method.

The details of one or more embodiments of the invention are set forth in the following drawings and description so that other features, objects, and advantages of the invention are more readily apparent.

BRIEF DESCRIPTION OF THE DRAWINGS

The drawings described herein are used to provide a further understanding of the present invention and constitute a part of the present invention. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute an improper limitation of the present invention. In the drawings:

FIG1 is a flow chart of a method for automatically burning a virtual machine system according to an embodiment of the present invention;

FIG. 2 is a schematic diagram of the hardware structure of an electronic device according to an embodiment of the present invention.

DETAILED DESCRIPTION

Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with one or more embodiments of this specification. Instead, they are merely examples of devices and methods consistent with some aspects of one or more embodiments of this specification as detailed in the appended claims.

It should be noted that: in other embodiments, the steps of the corresponding method are not necessarily performed in the order shown and described in this specification. In some other embodiments, the method may include more or fewer steps than those described in this specification. In addition, a single step described in this specification may be decomposed into multiple steps for description in other embodiments; and multiple steps described in this specification may be combined into a single step for description in other embodiments.

Embodiment 1

The present invention aims to propose a method for automatically burning a virtual machine system, which is implemented through the maintenance mode of Linux. Specifically, referring to FIG1 , the open source virtual machine management system ProxmoxVE uses RockyLinux to automatically burn an OpenWrt virtual machine system, and temporarily deploys a local area network script storage service, and directly downloads the script when using it.

The first step is to create or download and execute the following script [s1_create.sh] in ProxmoxVE to automatically create and set up virtual machines. The script content of s1_create.sh is as follows:

#!/bin/bash

#ScriptName:s1_create.sh

#Description:Technical point Step 1 - Used for automatic creation and setting of virtual machines under PVE virtual management system.

#Author:Candy

#Date:2024-08-06

#################################

#Parameter Configuration#

#################################

readonlyVM_NAME="OpenWrt"

readonlyVM_CPU=1

readonlyVM_MEMORY=2048

#The capacity of the boot disk used for booting and installation after burning.

readonlyVM_BOOT_DISK=5

#The disk capacity used for virtual machine system installation and use.

readonlyVM_HARD_DISK=16

aliasLOG='f(){echo[$(TZ=UTC-8date"+%H:%M:%S")]:$1;};f'

#################################

#Steps#

#################################

#1. Detection File

LOG"=========File check whether it exists========"

readonlyISO_PATH="/var/lib/vz/template/iso"

LOG "Local file save path: ${ISO_PATH}."

#(1) Check the files of the virtual machine system to be burned.

readonlyBURN_SYSTEM_NAME="OpenWrt"

readonlyBURN_SYSTEM_FILE="openwrt-23.05.3-x86-64-generic-ext4-combined-efi.img"

readonlyBURN_SYSTEM_LINK="https://downloads.openwrt.org/releases/23.05.3/targets/x86/64/${BURN_SYSTEM_FILE}.gz"

LOG"The name of the virtual machine system to be burned is: ${BURN_SYSTEM_NAME}."

LOG"The virtual machine system file to be burned is: ${BURN_SYSTEM_FILE}."

LOG"Check whether the virtual machine system files to be burned exist in this machine:"

if[-e"${ISO_PATH}/${BURN_SYSTEM_FILE}"];then

LOG "The virtual machine system files to be burned exist, continue to the next step."

else

LOG "The virtual machine system file to be burned does not exist and will be downloaded from the network."

wget-P${ISO_PATH}${BURN_SYSTEM_LINK}

LOG "The virtual machine system files to be burned have been downloaded."

LOG "The virtual machine system files to be burned are starting to be decompressed."

gzip-d${ISO_PATH}/${BURN_SYSTEM_FILE}.gz

LOG "The virtual machine system files to be burned have been decompressed. Continue to the next step."

fi

#(2)Detect Linux files with maintenance mode.

readonlyRESCUE_LINUX_NAME="RockyLinux"

readonlyRESCUE_LINUX_FILE="Rocky-9.4-x86_64-minimal.iso"

readonlyRESCUE_LINUX_LINK="https://download.rockylinux.org/pub/rocky/9/isos/x86_64/${RESCUE_LINUX_FILE}"

LOG"The name of the Linux with maintenance mode is: ${RESCUE_LINUX_NAME}."

LOG"The Linux file with maintenance mode is: ${RESCUE_LINUX_FILE}."

LOG"Check whether the Linux file with maintenance mode exists on this machine:"

if[-e"${ISO_PATH}/${RESCUE_LINUX_FILE}"];then

LOG "Linux file with maintenance mode exists, continue to the next step."

else

LOG "Linux with maintenance mode file does not exist, will be downloaded from the network."

wget-P${ISO_PATH}${RESCUE_LINUX_LINK}

LOG "Download of Linux file with maintenance mode completed, continue to the next step"

fi

LOG"========File detection completed========"

#2. Create a default virtual machine

LOG"=========The virtual machine starts to be created========"

#(1) Get the next available virtual machine ID.

VM_ID=$(pveshget/cluster/nextid)

echo "newVM${VM_ID}:-id${VM_ID}"

#(2). Create a blank virtual machine.

qmcreate${VM_ID}--name${VM_NAME}

echo "createVM${VM_ID}:-name${VM_NAME}"

#(3)Set the default CPU.

qmset${VM_ID}--cpux86-64-v2-AES--cores${VM_CPU}--sockets${VM_CPU}

#(4)Set the default memory.

qmset${VM_ID}--memory${VM_MEMORY}

#(5) Set up the EFI hard disk.

qmset${VM_ID}--efidisk0local-lvm:0,efitype=4m,size=4M,pre-enrolled-keys=no

#(6)Set the default BIOS.

qmset ${VM_ID} --biosovmf

#(7)Set the default machine type.

qmset ${VM_ID} --machineq35

#(8)Set up the SCSI controller.

qmset${VM_ID}--scsihwvirtio-scsi-single

#(9) Set up the network.

qmset${VM_ID}--net0virtio,bridge=vmbr0,firewall=1

#(10) Dynamically adjust ThinPool. Some versions need to be set.

#lvmconfig--withcomments--typediffactivation/thin_pool_autoextend_threshold=80

#lvmconfig--withcomments--typediffactivation/thin_pool_autoextend_percent=20

LOG"=========Virtual machine creation completed========"

#3. Key setting point settings

LOG"=========Core setting point starts setting========"

#(1) Create and fill in virtual CD-ROM drive 1 as the Linux system image in maintenance mode.

qmset${VM_ID}--ide0local:iso/Rocky-9.4-x86_64-minimal.iso,media=cdrom

#(2) Create and fill in virtual CD-ROM drive 2 as the virtual machine system image to be burned.

qmset${VM_ID}--ide1local:iso/openwrt-23.05.3-x86-64-generic-ext4-combined-efi.img,media=cdrom

#(3) Create a blank virtual hard disk 1 to store the burning data of the virtual machine system image file.

qmset${VM_ID}--scsi0local-lvm:${VM_BOOT_DISK},iothread=1,size=${VM_BOOT_DISK}G

#(4) Create a blank virtual hard disk 1 for installing the virtual machine system.

qmset${VM_ID}--scsi1local-lvm:${VM_HARD_DISK},iothread=1,size=${VM_HARD_DISK}G

#(5) Set the boot order (virtual CD-ROM drive 1, virtual CD-ROM drive 2, virtual hard disk 1, virtual hard disk 2) and activate the virtual device.

qmset${VM_ID}--bootorder=ide0--bootdiskscsi0

LOG"=========Core setting point setting completed========"

#4. Virtual Machine Operation

#(1) Prompt countdown.

LOG"=========The virtual machine starts========"

TIME_COUNTDOWN=5

while[${TIME_COUNTDOWN}-gt0];do

LOG"Virtual machine ${VM_NAME}:${VM_ID} will start after ${TIME_COUNTDOWN}s, please switch to Linux maintenance mode!"

sleep1

TIME_COUNTDOWN=$((TIME_COUNTDOWN-1))

done

LOG"=========Virtual machine startup completed========"

#(2)Start the virtual machine.

qmstart${VM_ID}.

After the virtual machine starts, you will be prompted to proceed to the next step.

In this embodiment, the general idea of the first script (s1_create.sh) is:

First, configure the parameters, including the virtual machine name, CPU, memory, boot disk, and system installation disk capacity. Then perform file detection, including the virtual machine system files to be burned and the Linux files with maintenance mode. If the file does not exist, download it from the network and decompress it. Then create a default virtual machine, including obtaining the virtual machine ID, creating a blank virtual machine, setting the CPU, memory, BIOS, machine type, etc. Finally, set the key setting points, including creating a virtual CD-ROM drive and filling in the corresponding image file, creating a blank virtual hard disk for burning and installing the virtual machine system, setting the startup order and activating the virtual device.

In this embodiment, the means of building a temporary script storage service in a local area network is an existing technology, and the steps and principles are not repeated here. It can be built on a device running a virtual machine (built using virtual machine software or a system of a host device running a virtual machine), or a computer with moderate performance can be selected as a server to ensure that it has a stable network connection and sufficient storage space to store scripts and image files.

Step 2: After starting the virtual machine, you need to manually select the command line interface in the Linux maintenance mode because it spans different systems (since it is an operation interface of the prior art, it will not be shown in the figure or detailed description of the function). The operation steps are as follows:

a) On the RockyLinx installation interface, select Troubleshooting--> and press the "Enter" key.

b) Select the RescueaRockyLinuxsystem option and press the "Enter" key.

c) After the loading is complete, press the "1" key, then press the "Enter" key to enter the command line interface of the maintenance mode.

Step 3. Create or download and execute the following script [s2_burn.sh] to implement the automated burning system. The script content of s2_burn.sh is as follows:

#!/bin/bash

#ScriptName:s2_brun.sh

#Description: Technical point step 2 - used for automatic burning of virtual machines under the PVE virtual management system.

#Stored in Linux maintenance mode:

#->Either deploy a temporary file server and use the wget command to download to maintenance mode (recommended).

#-> Either create a new shellscript file in maintenance mode and type all the commands manually.

#Because Chinese characters are garbled in maintenance mode, logs are output in English.

#Author:Candy

#Date:2024-08-07

#################################

#Parameter Configuration#

#################################

readonlyVM_NAME="OpenWrt"

#Same as the variable defined in create.sh, used to automatically match the mounted virtual boot hard disk.

readonlyVM_BOOTDISK=5

#Same as the variable defined in create.sh, used to automatically match the mounted virtual hard disk.

readonlyVM_HARDDISK=16

#################################

#Burn Steps#

#################################

#(1) Check whether all virtual hard disks are loaded successfully. The number must be greater than or equal to 2.

echo

echo "========STARTCheckingDisks========"

DISKS_COUNT=$(lsblk-oTYPEawk'$1=="disk"{count++}END{printcount}')

if["${DISKS_COUNT}"-lt2];then

echo "Failedtoloaddisks,exitburning."

exit1

fi

echo "Therequired${DISKS_COUNT}numberofdiskshavebeenloaded."

echo "========ENDCheckingDisks========"

echo

#(2) Check whether all virtual CD-ROM drives are loaded successfully. The number must be greater than or equal to 2.

echo "========STARTCheckingCDROMs========"

CDROMS_COUNT=$(lsblk-oTYPEawk'$1=="rom"{count++}END{printcount}')

if["${CDROMS_COUNT}"-lt2];then

echo "Failedtoloadcdroms,exitburning."

exit1

fi

echo "Therequired${CDROMS_COUNT}numberofcdromshavebeenloaded."

echo "========ENDCheckingCDROMs========"

echo

#(3)Automatically match the virtual hard disk.

echo "========STARTMatchingDisks========"

echo "Automaticallymatchdisknamesbasedontheircapacity:"

NAME_BOOTDISK=$(lsblk-oNAME,SIZE,TYPEawk-vsize="${VM_BOOTDISK}G"'$2==size&&$3=="disk"{print$1}')

NAME_HARDDISK=$(lsblk-oNAME,SIZE,TYPEawk-vsize="${VM_HARDDISK}G"'$2==size&&$3=="disk"{print$1}')

echo"Thematchedbootdisk1is\"${NAME_BOOTDISK}\",harddisk2is\"${NAME_HARDDISK}\"."

if[-z"${NAME_BOOTDISK}"][-z"${NAME_HARDDISK}"];then

echo "Failedtomatchdisks,exitburning."

exit1

fi

echo "========ENDMatchingDisks========"

echo

#(4) Automatically match the virtual CD-ROM drive.

echo "========STARTMatchingCDROMs========"

echo "Automaticallymatchcdromnamesbasedontheirtype:"

NAME_RESCUECDROM=$(lsblk-oNAME,TYPE,MOUNTPOINTawk-vmp="/run/install/repo"'$2=="rom"&&$3==mp{print$1}')

NAME_SYSTEMCDROM=$(lsblk-oNAME,TYPE,MOUNTPOINTawk'$2=="rom"&&$3==""{print$1}')

echo"Thematchedrescuecdrom1is\"${NAME_RESCUECDROM}\",systemcdrom2is\"${NAME_SYSTEMCDROM}\"."

if[-z"${NAME_RESCUECDROM}"][-z"${NAME_SYSTEMCDROM}"];then

echo "Failedtomatchcdroms,exitburning."

exit1

fi

echo "========ENDMatchingCDROMs========"

echo

#(5) Use native burning commands to achieve automated burning.

echo "========STARTBurning========"

echo "Burnvirtualmachine'ssystemfromSystemCD-ROM(/dev/${NAME_SYSTEMCDROM})toBootableDisk(/dev/${NAME_BOOTDISK}):"

ddif=/dev/${NAME_SYSTEMCDROM}of=/dev/${NAME_BOOTDISK}bs=4Mstatus=progress

if[$?-eq0];then

echo"Congratulations,virtualmachine'ssystem\"${VM_NAME}\"isburnedsuccessful!"

echo "Pleaseshutdownthisvirtualmachine."

echo"Andexecute\"clean.sh\"onthehostmachinetoproceedwiththesubsequentoperations."

echo "========ENDBurning========"

echo

read-p"ShutdownNow?(y/n):"answer

case${answer}in

[Yy]*)

echo "Shutdownthisvirtualmachinein3s..."

sleep3

shutdown-hnow

;;

[Nn]*)

echo "Cancel.Pleasemanuallyshutdown."

;;

*)

echo "Invalidinput,pleaseenteryorn."

;;

esac

else

echo "Burningfailed,pleasetryagain."

echo "========ENDBurning========"

fi

After the execution is successful, start burning.

In this embodiment, the general idea of the second script (s2_burn.sh) is:

First, check whether all virtual hard disks and virtual optical drives are successfully loaded. The number must be greater than or equal to 2. Then automatically match virtual hard disks and virtual optical drives according to capacity and type. Finally, use the native burning command to achieve automatic burning, burning the virtual machine system from the system CD-ROM to the startup disk. If the burning is successful, prompt the user to shut down the virtual machine and perform subsequent cleanup operations. If the burning fails, prompt the user to try again.

Step 4. After shutting down the virtual machine, create or download and execute the following script [s3_clean.sh] to achieve automatic cleanup before subsequent installation. The specific code of s3_clean.sh is as follows:

#!/bin/bash

#ScriptName:s3_clean.sh

#Description: Technical point step 3 - used for automatic cleanup of virtual machines under the PVE virtual management system.

#Author:Candy

#Date:2024-08-08

#################################

#Parameter Configuration#

#################################

readonlyVM_NAME="OpenWrt"

#Same as the variables defined in create.sh.

readonlyVM_BOOT_DISK=5

#Same as the variables defined in create.sh.

readonlyVM_HARD_DISK=16

#################################

#Steps#

#################################

echo

echo "=========Virtual machine cleanup started========"

#(1) Search for the previously created virtual machine by name.

VM_ID=$(qmlistgrep-i${VM_NAME}awk'{print$1}')

if[-z"${VM_ID}"];then

echo">>>>>Error: Unable to find the specified '${VM_NAME}' virtual machine."

echo"=========Virtual machine cleanup failed========"

exit1

fi

echo">>>>>Found virtual machine "${VM_NAME}:${VM_ID}".

#(2)Stop the virtual machine.

echo">>>>>Stop virtual machine ${VM_ID}."

qmstop${VM_ID}

#(3) Delete all virtual drives.

CDROMS=$(qmconfig${VM_ID}grep-oP'^(idesatascsi)\d+:.*cdrom'cut-d:-f1)

forCDROMin${CDROMS};do

qmset ${VM_ID} -delete ${CDROM}

echo">>>>>The virtual CD-ROM drive "${CDROM}" has been deleted from the virtual machine "${VM_NAME}:${VM_ID}"."

done

#(4) Search for the virtual hard disk.

ID_BOOTDISK=$(echo$(qmconfig${VM_ID}grep-E"size=${VM_BOOT_DISK}G")awk-F:'{print$1}')

if[-z"${ID_BOOTDISK}"];then

echo">>>>>Error: Unable to find the specified startup disk."

echo"=========Virtual machine cleanup failed========"

exit1

fi

echo">>>>>Found the boot disk: ${ID_BOOTDISK}."

ID_HARDDISK=$(echo$(qmconfig${VM_ID}grep-E"size=${VM_HARD_DISK}G")awk-F:'{print$1}')

if[-z"${ID_HARDDISK}"];then

echo">>>>>Error: Unable to find the specified system disk."

echo"=========Virtual machine cleanup failed========"

exit1

fi

echo">>>>>Found system disk: ${ID_HARDDISK}."

#(4) Set the boot sequence (virtual boot hard disk 1, virtual blank hard disk 2) and activate the virtual device.

qmset${VM_ID}--bootorder="${ID_BOOTDISK};${ID_HARDDISK}"--bootdisk${ID_BOOTDISK}

echo"=========Virtual machine cleanup completed========"

echo">>>>>Start virtual machine ${VM_ID}."

qmstart${VM_ID}

echo">>>>>The virtual machine ${VM_ID} has been started. Please continue to install the virtual machine system."

echo

After successful execution, you can install the virtual machine system.

In this embodiment, the general idea of the third script (s3_clean.sh) is:

First, search for the previously created virtual machine by name. If it is not found, exit. Then stop the virtual machine and delete all virtual CD-ROMs. Next, search for the virtual hard disk. If it is not found, exit. Finally, set the boot order and activate the virtual device, start the virtual machine, and prompt the user to continue the installation of the virtual machine system.

Step 5. Attach the script [s4_destroy.sh] to implement automated testing (not a required script or step). The specific code of s4_destroy.sh is as follows:

#!/bin/bash

#ScriptName:s4_destroy.sh

#Description: Technical point step 4 - used for virtual machine deletion under PVE virtual management system.

#Author:Candy

#Date:2024-08-09

#################################

#Parameter Configuration#

#################################

aliasLOG='f(){echo[$(TZ=UTC-8date"+%H:%M:%S")]:$1;};f'

#################################

#Steps#

#################################

LOG"========Start deleting virtual machine========"

read-p">>>Please enter the virtual machine ID to be deleted (enter 0 to delete all):"VM_ID

if["${VM_ID}"-eq0];then

qmlistawk'NR>1'whileIFS=read-rline;do

NAME=$(echo"$line"awk'{print$2}')

ID=$(echo"$line"awk'{print$1}')

LOG "Deleting virtual machine ${NAME}:${ID}."

qmstop${ID}

sleep3

qmdestroy ${ID} --purge

LOG "Virtual machine ${NAME}:${ID} has been deleted."

done

else

VM_NAME=$(qmconfig"${VM_ID}"grepnameawk-F':''{print$2}')

if[-z"${VM_NAME}"];then

LOG "Virtual machine ${VM_ID} does not exist!"

exit1

fi

LOG "Deleting virtual machine ${VM_NAME}:${VM_ID}."

qmstop${VM_ID}

sleep3

qmdestroy ${VM_ID} --purge

LOG "Virtual machine ${VM_NAME}:${VM_ID} has been deleted."

fi

LOG"========Deleting virtual machine completed========"

In this embodiment, the general idea of the fourth script (s4_destroy.sh) is:

The user can enter the VM ID to be deleted. If 0 is entered, all VMs will be deleted. First, the VM will be stopped, then deleted and related data will be cleared.

Through the above steps, the present invention realizes the automated burning and installation of the virtual machine system in Proxmox VE, which improves compatibility, reduces costs, reduces risks, and improves efficiency.

The codes of the command line interface in the figure shown in this implementation are all required by the code standards and therefore cannot be translated into Chinese. Only the comments can be written in Chinese.

Embodiment 2

Based on the same concept, the present invention also proposes a device for automatically burning a virtual machine system, comprising:

Temporary file storage server module, used to store all scripts and image files;

The LAN module provides local network services for data interaction between the temporary file storage server module and the virtual machine module;

The virtual machine module is used to create a virtual machine with default parameters and set the number of virtual optical drives and virtual hard disks to two; fill the image file of the Linux system to be maintained in the first virtual optical drive, fill the image file of the virtual machine system to be burned in the second virtual optical drive, and set the capacity of the two virtual hard disks as needed; set the startup sequence, set and activate the virtual machine according to the first virtual optical drive, the second virtual optical drive, the first virtual hard disk and the second virtual hard disk; after the virtual machine is started, enter the command line interface of the Linux maintenance mode; create or download and execute the second script; use the burning command to burn, and burn the virtual machine system to be burned from the second virtual optical drive to the first virtual hard disk; and shut down the virtual machine after the burning is successful.

Embodiment 3

This embodiment further provides an electronic device, referring to FIG. 2 , comprising a memory 404 and a processor 402 , wherein the memory 404 stores a computer program, and the processor 402 is configured to run the computer program to execute the steps in any one of the above method embodiments.

Specifically, the processor 402 may include a central processing unit (CPU), or an application specific integrated circuit (ASIC), or may be configured to implement one or more integrated circuits of the embodiment of the present invention.

Among them, the memory 404 may include a large capacity memory 404 for data or instructions. For example, but not limitation, the memory 404 may include a hard disk drive (HDD), a floppy disk drive, a solid state drive (SSD), a flash memory, an optical disk, a magneto-optical disk, a tape, or a universal serial bus (USB) drive, or a combination of two or more of these. In appropriate cases, the memory 404 may include a removable or non-removable (or fixed) medium. In appropriate cases, the memory 404 may be inside or outside the data processing device. In a specific embodiment, the memory 404 is a non-volatile memory. In a specific embodiment, the memory 404 includes a read-only memory (ROM) and a random access memory (RAM). Where appropriate, the ROM may be a mask-programmed ROM, a programmable ROM (Programmable Read-Only Memory, PROM for short), an erasable PROM (Erasable Programmable Read-Only Memory, EPROM for short), an electrically erasable PROM (Electrically Erasable Programmable Read-Only Memory, EEPROM for short), an electrically alterable ROM (Electrically Alterable Read-Only Memory, EAROM for short) or a flash memory (FLASH) or a combination of two or more of these. In appropriate circumstances, the RAM may be a static random access memory (SRAM) or a dynamic random access memory (DRAM), wherein the DRAM may be a fast page mode dynamic random access memory 404 (FPMDRAM), an extended data output dynamic random access memory (EDODRAM), a synchronous dynamic random access memory (SDRAM), etc.

The memory 404 may be used to store or cache various data files required for processing and/or communication, as well as possible computer program instructions executed by the processor 402 .

The processor 402 reads and executes the computer program instructions stored in the memory 404 to implement any one of the methods for automatically burning a virtual machine system in the above embodiments.

Optionally, the electronic device may further include a transmission device 406 and an input/output device 408 , wherein the transmission device 406 is connected to the processor 402 , and the input/output device 408 is connected to the processor 402 .

The transmission device 406 can be used to receive or send data via a network. Specific examples of the above-mentioned network may include a wired or wireless network provided by a communication provider of the electronic device. In one example, the transmission device includes a network adapter (Network Interface Controller, referred to as NIC), which can be connected to other network devices through a base station so as to communicate with the Internet. In one example, the transmission device 406 can be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

Input/output devices 408 are used to input or output information.

Embodiment 4

This embodiment further provides a readable storage medium, in which a computer program is stored. The computer program includes a program code for controlling a process to execute the process. The process includes the method for automatically burning a virtual machine system according to the first embodiment.

It should be noted that the specific examples in this embodiment can refer to the examples described in the above embodiments and optional implementation modes, and this embodiment will not be described in detail here.

In general, various embodiments may be implemented in hardware or dedicated circuits, software, logic, or any combination thereof. Some aspects of the invention may be implemented in hardware, while other aspects may be implemented in firmware or software executed by a controller, microprocessor, or other computing device, but the invention is not limited thereto. Although various aspects of the invention may be shown and described as block diagrams, flow charts, or using some other graphical representation, it should be understood that, as non-limiting examples, the boxes, devices, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, dedicated circuits or logic, general-purpose hardware or controllers or other computing devices, or some combination thereof.

Embodiments of the present invention can be implemented by computer software, which is executable by a data processor of a mobile device, such as in a processor entity, or implemented by hardware, or implemented by a combination of software and hardware. Computer software or programs (also referred to as program products) including software routines, applets and/or macros can be stored in any device-readable data storage medium, and they include program instructions for performing specific tasks. Computer program products can include one or more computer executable components configured to perform embodiments when the program is running. One or more computer executable components can be at least one software code or a part thereof. In addition, at this point, it should be noted that any box of the logic flow in Figure 1 can represent program steps, or interconnected logic circuits, boxes and functions, or a combination of program steps and logic circuits, boxes and functions. Software can be stored in physical media such as memory chips or storage blocks implemented in processors, magnetic media such as hard disks or floppy disks, and optical media such as, for example, DVDs and data variants thereof, CDs. Physical media are non-transient media.

Those skilled in the art should understand that the technical features of the above embodiments may be arbitrarily combined. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

The above embodiments only express several implementation modes of the present invention, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present invention. It should be pointed out that, for those of ordinary skill in the art, several modifications and improvements can be made without departing from the concept of the present invention, and these all belong to the protection scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the attached claims.

Claims (10)

1. A method for automating a virtual machine system, comprising the steps of:

S00, creating or downloading and executing a first script;

s10, creating a virtual machine with default parameters, and setting the number of virtual CD-ROM and the number of virtual hard disks to be two;

s20, filling an image file of a Linux system in a mode to be maintained into a first virtual CD-ROM, filling an image file of a virtual machine system to be recorded into a second virtual CD-ROM, and setting the capacities of two virtual hard disks according to requirements;

s30, setting a starting sequence, and setting and activating the virtual machine according to the first virtual drive, the second virtual drive, the first virtual hard disk and the second virtual hard disk;

s40, after the virtual machine is started, entering a command line interface of a maintenance mode of Linux;

s50, creating or downloading and executing a second script;

s60, recording the virtual machine system to be recorded from the second virtual drive into the first virtual hard disk by using a recording command;

And S70, closing the virtual machine after the successful burning.

2. The method of claim 1, wherein in step S20, the capacity of the first virtual hard disk is set to be more than twice the capacity of the mirror image file of the virtual machine system to be recorded, and the capacity of the second virtual hard disk is set to be more than 32 GB.

3. The method of claim 1, wherein the file detection is performed between the step S10 and the step S20, and the file detection includes a virtual machine system file to be recorded and a Linux file with a maintenance mode; if the file does not exist, downloading and decompressing from the network.

4. The method of an automatic virtual machine system for recording as claimed in claim 1, wherein in step S60, it is detected whether all virtual hard disks and virtual optical drives are successfully loaded before recording, and the number is greater than or equal to 2;

if yes, automatically matching the virtual hard disk with the virtual CD-ROM, and matching according to the capacity and the type; if not, reporting error and exiting the recording flow.

5. The method of an automated virtual machine system according to claim 1, further comprising the step of S80, after closing the virtual machine, creating or downloading and executing a third script;

And S90, deleting all the virtual CD-ROM and restarting the virtual machine to enter a virtual machine system installation interface, and taking the second virtual hard disk as an installation disk of the system.

6. The method of claim 1, further comprising a fourth script that deletes all virtual machines by deleting corresponding virtual machines in response to a virtual machine ID input by a user, or deleting all virtual machines in response to an all deletion instruction input by a user.

7. A method of an automated virtual machine system according to any one of claims 1-6, wherein in step S00, a temporary file storage server is in the local area network, on which all scripts and image files are stored.

8. An apparatus for automating a virtual machine system, comprising:

the temporary file storage server module is used for storing all scripts and mirror image files;

the local area network module is used for providing local network service and is used for data interaction between the temporary file storage server module and the virtual machine module;

The virtual machine module is used for creating a virtual machine with default parameters and setting the number of virtual CD-ROM and virtual hard disk to two; filling an image file of a Linux system in a mode to be maintained into a first virtual drive, filling an image file of a virtual machine system to be recorded into a second virtual drive, and setting capacities of two virtual hard disks according to requirements; setting a starting sequence, setting and activating a virtual machine according to the first virtual drive, the second virtual drive, the first virtual hard disk and the second virtual hard disk; after the virtual machine is started, a command line interface of a maintenance mode of Linux is entered; creating or downloading and executing a second script; the virtual machine system to be recorded is recorded from the second virtual CD driver into the first virtual hard disk by using the recording command; and closing the virtual machine after the successful burning.

9. An electronic device comprising a memory and a processor, wherein the memory has stored therein a computer program, the processor being arranged to run the computer program to perform the method of the automated virtual machine system of any one of claims 1 to 7.

10. A readable storage medium, characterized in that the readable storage medium has stored therein a computer program comprising program code for controlling a process to execute a process comprising a method of automating a virtual machine system according to any one of claims 1 to 7.