CN109002346B - Conversion method of Windows virtual machine bootstrap program - Google Patents
Conversion method of Windows virtual machine bootstrap program Download PDFInfo
- Publication number
- CN109002346B CN109002346B CN201810750184.1A CN201810750184A CN109002346B CN 109002346 B CN109002346 B CN 109002346B CN 201810750184 A CN201810750184 A CN 201810750184A CN 109002346 B CN109002346 B CN 109002346B
- Authority
- CN
- China
- Prior art keywords
- windows
- virtual machine
- boot
- file
- nbd
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/4401—Bootstrapping
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45575—Starting, stopping, suspending or resuming virtual machine instances
Abstract
The invention discloses a conversion method of a Windows virtual machine bootstrap program, which belongs to the technical field of cloud computing and comprises the following steps: s1, creating a Windows virtual machine in a UEFI mode; s2, mounting the Windows virtual machine as an NBD network block device of a Linux host machine; and S3, copying the Legacy boot file and the UEFI boot file to two different partitions of the NBD network block device respectively. The invention mainly solves the problems that a UEFI (unified extensible firmware interface) guidance mode and a Legacy guidance mode are incompatible with each other in a Windows system, the Windows system is restarted once in the conversion process and after the conversion, and the two guidance modes are incompatible with each other in the conversion process.
Description
Technical Field
The invention relates to the technical field of cloud computing, in particular to a conversion method of a Windows virtual machine bootstrap program.
Background
The cloud computing technology provides a high-efficiency and powerful computing platform for users, and with the increasing development of the virtualization cloud computing technology, the virtual machine in the virtual machine environment can be provided with different types of Windows operating systems, namely a Windows operating system.
The Windows operating System is usually started by two booting methods, one is Unified Extensible Firmware Interface (UEFI), and the other is Legacy BIOS, i.e., Basic Input Output System (BIOS), which is a conventional BIOS booting method.
In many cases, the booting of the Windows operating system requires a transition between the two boot modes described above. For example, in the virtualized cloud computing technology, a host of a virtual Windows operating system is a cloud server, and when GPU computing resources of the host need to be used, the Windows operating system needs to be started in a UEFI boot manner; when the GPU computing resources of the cloud terminal are required to be used, the Windows operating system is started in a Legacy boot mode.
However, in the Windows system, the UEFI boot method and Legacy boot method are not compatible with each other. When the same Windows virtual machine is switched from a UEFI boot mode to a Legacy boot mode, a switching program needs to be run in the system in the boot state of the Windows virtual machine. If the conversion is carried out by the method, the Windows system needs to be restarted respectively in the conversion process and after the conversion, the problem that the two guide modes are incompatible with each other also exists in the conversion process, the process of converting the Legacy guide mode to the UEFI guide mode is the same, the process of restarting the Windows system needs to be carried out twice, the waiting time of a user is long, inconvenience is caused, the user experience is influenced, the conversion process needs manual participation of the user, and extra learning cost is added for the user.
Disclosure of Invention
In order to solve the above problems, the present invention provides a method for converting a boot program of a Windows virtual machine, so that the Windows virtual machine can simultaneously support two boot modes, namely UEFI and Legacy.
The technical scheme adopted by the invention is as follows: a conversion method of a Windows virtual machine bootstrap program comprises the following steps:
s1, creating a Windows virtual machine in a UEFI mode;
s2, mounting the Windows virtual machine as an NBD network block device of a Linux host machine;
and S3, copying the Legacy boot file and the UEFI boot file to two different partitions of the NBD network block device respectively.
In the above method, in step S3, the Legacy boot file is copied to the Windows visible partition of the NBD network block device, and the UEFI boot file is copied to the system partition of the NBD network block device.
In the above method, step S1 includes:
s101, creating a Windows virtual machine by using virtual machine software;
s102, selecting to start in a UEFI (unified extensible firmware interface) guiding mode in the setting of the Windows virtual machine;
s103, installing the operating system of the Windows virtual machine by using the Windows installation file.
In the method, before the Legacy boot file is copied to the Windows visible partition of the NBD network block device, the disk partition table of the NBD network block device is converted into an mbr format so as to be compatible with the Legacy boot mode.
In the method, the Windows visible partition of the NBD network block device is activated as the active partition before the Legacy boot file is copied to the Windows visible partition of the NBD network block device.
In the method, the Legacy boot file and the UEFI boot file are copied to two different partitions of the NBD network block device, and the operating system type of the Windows virtual machine is determined, so that the Legacy boot file and the UEFI boot file corresponding to the operating system are copied to the two different partitions of the NBD network block device.
In the method, the step of judging the operating system type of the Windows virtual machine comprises the following steps:
judging the number of partitions in the NBD network block device file,
if the number of the partitions in the NBD network block device file is three, further judging whether an operating system of the Windows virtual machine is Windows 7 or Windows Vista;
and if the number of the partitions in the NBD network block device file is four, further judging whether the operating system of the Windows virtual machine is Windows 10 or Windows 8.
In the method, after the Legacy boot file and the UEFI boot file are respectively copied to two different partitions of the NBD network block device, the Linux host unloads the NBD network block device.
In the method, the first boot devices of the Legacy boot file and the UEFI boot file are both local disks, so that the local hard disk is preferentially booted, and the boot speed of the Windows virtual machine is increased.
In the method, the first starting program of the Legacy boot file and the UEFI boot file is pointed to and modified into a Windows loader loading program in a local hard disk, so that the local hard disk is started preferentially, and the starting speed of the Windows virtual machine is increased.
The invention has the beneficial effects that:
1. the Windows virtual machine is mounted as the NBD network block device of the Linux host, and the UEFI boot file and the Legacy boot file are respectively loaded in different partitions of the NBD network block device, so that the Windows virtual machine can simultaneously support two boot modes of UEFI and Legacy, a user or maintenance personnel is not required to perform secondary conversion operation and restart switching, the operation time and the waiting time are saved, the process is completed when a virtual machine operating system is established, the user does not sense the process, and the user experience is improved;
2. the invention relates to a conversion method of a Windows virtual machine bootstrap program, which is characterized in that a Legacy bootstrap file is copied to a Windows visible partition of an NBD network block device, a disk partition table of the NBD network block device is converted into an mbr format, and the Windows visible partition of the NBD network block device is activated into a movable partition, so that the successful starting of the Legacy bootstrap mode is ensured;
3. the conversion method of the Windows virtual machine bootstrap program of the invention, before copying the Legacy boot file to the Windows visible partition of the said NBD network block device, judge the operating system type of the Windows virtual machine, in order to copy the Legacy boot file of the corresponding operating system to the Windows visible partition of the said NBD network block device, guarantee that the Legacy boot mode starts successfully;
4. the first starting devices of the Legacy boot file and the UEFI boot file are local disks, so that the starting speed of the Windows virtual machine is increased, and the starting time is saved.
Drawings
FIG. 1 is a flowchart of a method for converting a Windows virtual machine boot program according to a first embodiment of the present invention;
fig. 2 is a flowchart of creating a Windows virtual machine in UEFI mode using Windows mount files according to a first embodiment of the present invention.
Detailed Description
The present invention will be described in further detail with reference to the accompanying drawings.
The first embodiment is as follows:
a conversion method of a Windows virtual machine bootstrap program is applied to a host machine running a Linux kernel, and the host machine can be mounted with NBD network block equipment.
The conversion method of the Windows virtual machine bootstrap program comprises the following steps:
and S1, respectively extracting a boot file of a Legacy boot method and a boot file of a UEFI boot method from the Windows installation file.
The Windows installation files can be obtained from Windows optical disks, which are optical disks of issued Windows operating systems such as Windows 10, Windows 8, Windows 7, Windows Vista, and the like.
When the boot files are extracted from the Windows installation files, the corresponding boot files of the Legacy boot mode and boot files of the UEFI boot mode are respectively extracted according to the Windows version, that is, the boot files of the Legacy boot mode and boot files of the UEFI boot mode in the Windows installation files such as Windows 10, Windows 8, Windows 7, Windows Vista, and the like are respectively extracted.
And S2, creating a Windows virtual machine in the UEFI mode by using the Windows installation file.
In this embodiment, step S2 specifically includes:
s201, creating a Windows virtual machine by using virtual machine software;
s202, selecting to start in a UEFI (unified extensible firmware interface) guiding mode in the set of the created Windows virtual machine;
s203, installing the operating system of the Windows virtual machine by using the Windows installation file.
After the Windows virtual machine is established in the UEFI mode, the deployment of the Windows virtual machine can be completed for subsequent operation; at this time, the Windows virtual machine supports UEFI boot mode startup.
And S3, closing the Windows virtual machine and mounting the Windows virtual machine as the NBD network block device of the host machine.
The Windows virtual machine is mounted as an NBD network block device of a host machine running a Linux kernel, namely the Windows virtual machine can be regarded as a disk of the host machine, and the partition format of the NBD network block device can be changed, so that a Legacy boot mode is supported.
And S4, acquiring the partition number in the NBD network block device file.
Considering that if Windows 7 and Windows Vista systems are started in UEFI boot mode, in the process of system deployment, an installer automatically creates a system partition and a reserved partition, wherein the two partitions are hidden partitions and the total of three partitions are the Windows visible partition.
If the Windows 10 and Windows 8 systems are started in a UEFI boot mode, in the process of system deployment, an installation program automatically creates a recovery partition, a system partition and a reserved partition, wherein the three partitions are all hidden partitions, and the total of the three partitions is four partitions by adding visible Windows partitions.
After the Windows virtual machine is mounted as the NBD network block device of the host, all the partitions are in a visible state as the NBD network block device of the host running the Linux kernel. The Windows visible partition refers to a visible partition divided by a Windows installing program in the process of deploying the Windows system.
And S5, converting the disk partition table of the NBD network block device into an mbr format.
When the disk partition table is in an mbr format, the method can be compatible with a Legacy boot mode, and provides convenience for subsequent operation.
And S6, activating the Windows visible partition in the NBD network block device as an active partition.
After the Windows visible partition is activated as the active partition, the partition can be used as a boot partition of a Windows virtual machine Legacy boot mode, and convenience is provided for subsequent operations.
S7, judging the number of partitions in the NBD network block device file, and executing the step S8 if the number of the obtained partitions in the NBD network block device file is three; if the number of the acquired partitions in the NBD network block device file is four, step S11 is executed.
If the number of the obtained partitions in the NBD network block device file is three, it indicates that the operating system of the Windows virtual machine may be Windows 7 or Windows Vista, so step S8 is executed to make a further determination.
If the number of the acquired partitions in the NBD network block device file is four, it indicates that the operating system of the Windows virtual machine may be Windows 10 or Windows 8, so step S11 is executed to make a further determination.
S8, judging whether the operating system of the Windows virtual machine is Windows 7 or Windows Vista, if so, executing the next step, if not, indicating that the operating system is not the supported operating system (the actual number of partitions is not matched with the number of partitions which the system should actually have) and finishing the operation.
S9, copying the boot file of the Legacy boot mode of Windows 7 or Windows Vista to the Windows visible partition.
And S10, copying the boot file of the UEFI boot mode of Windows 7 or Windows Vista to the system partition.
And copying the boot file of the Legacy boot mode to the visible Windows partition, so that the Windows virtual machine can support the boot of the Legacy boot mode.
And copying the boot file of the UEFI boot mode to the system partition, so that the Windows virtual machine can support the start of the UEFI boot mode.
And S11, the host machine unloads the NBD network block device and ends the operation.
The step ensures that the Windows virtual machine is not mounted as the NBD network block device of the Linux host machine, thereby ensuring that the Windows virtual machine can run independently.
And S12, judging whether the operating system of the Windows virtual machine is Windows 10 or Windows 8, if so, executing the next step, otherwise, indicating that the operating system is not the supported operating system (the actual number of the partitions is not matched with the number of the partitions which the system actually should have) and finishing the operation.
S13, copying the boot file of the Legacy boot mode of Windows 10 or Windows 8 to the Windows visible partition.
And S14, copying the boot file of the UEFI boot mode of Windows 10 or Windows 8 to the system partition.
And copying the boot file of the Legacy boot mode to the visible Windows partition, so that the Windows virtual machine can support the boot of the Legacy boot mode.
And copying the boot file of the UEFI boot mode to the system partition, so that the Windows virtual machine can support the start of the UEFI boot mode.
And S15, the host machine unloads the NBD network block device and ends the operation.
The step ensures that the Windows virtual machine is not mounted as the NBD network block device of the Linux host machine, thereby ensuring that the Windows virtual machine can run independently.
After the conversion method of the Windows virtual machine boot program is applied to complete operation, the obtained operating system of the Windows virtual machine can simultaneously support two boot modes of UEFI and Legacy. The operating system of the Windows virtual machine can be applied to a cloud server, and provides cloud computing service for users.
When the Windows virtual machine is started, the cloud server judges that GPU computing resources of a host machine or GPU computing resources of a cloud terminal need to be used.
When GPU computing resources of a host computer need to be used, the Windows virtual machine is started in a UEFI boot mode, and specifically, the Windows virtual machine is started in a boot file of the UEFI boot mode in a system partition created by a Windows installing program in a boot mode.
When GPU computing resources of the cloud terminal are needed to be used, the Windows virtual machine is started in a Legacy boot mode, and specifically, the Windows virtual machine is started in a Legacy boot mode by extracting boot files from Windows installation files and copying the boot files to a Windows visible partition.
Example two:
the method for converting a Windows virtual machine boot program provided in this embodiment is different from the method for converting a Windows virtual machine boot program provided in the first embodiment in that:
after step S1 is executed, the boot file is modified, so that when the boot file is booted, a local hard disk is used as a first boot device, specifically, the boot file of the Legacy boot method and the boot file of the UEFI boot method are modified respectively, and the first boot program of the boot file is modified to a Windows loader in the local hard disk, so as to preferentially boot the local hard disk.
The boot files refer to the boot files of the Legacy boot method and the boot files of the UEFI boot method extracted from the Windows installation file in step S1, that is, the boot files include the boot files of the Legacy boot method and the boot files of the UEFI boot method.
Generally speaking, the Windows virtual machine does not use an optical drive, so when booting the boot file, the optical drive is not necessarily used as the first boot device, but the optical drive directly points to the local hard disk and searches for a Windows loader loading program from the local hard disk, so as to improve the boot speed of the Windows virtual machine.
The remaining steps of the method for converting a Windows virtual machine bootstrap program provided in this embodiment are all the same as those of the method for converting a Windows virtual machine bootstrap program provided in the first embodiment, and refer to the first embodiment in detail.
The above examples are intended to illustrate rather than to limit the invention, and all equivalent changes and modifications made by the methods described in the claims of the present invention are intended to be included within the scope of the present invention.
Claims (6)
1. A conversion method of a Windows virtual machine bootstrap program is characterized by comprising the following steps:
s1, creating a Windows virtual machine in a UEFI mode;
s2, mounting the Windows virtual machine as an NBD network block device of a Linux host machine;
s3, copying a Legacy boot file and a UEFI boot file to two different partitions of the NBD network block device respectively;
step S1 includes:
s101, creating a Windows virtual machine by using virtual machine software;
s102, selecting to start in a UEFI (unified extensible firmware interface) guiding mode in the setting of the Windows virtual machine;
s103, installing the operating system of the Windows virtual machine by using the Windows installation file;
in step S3, copying the Legacy boot file to the Windows visible partition of the NBD network block device, and copying the UEFI boot file to the system partition of the NBD network block device;
before copying the Legacy boot file to the Windows visible partition of the NBD network block device, converting the disk partition table of the NBD network block device into an mbr format;
respectively copying the Legacy boot file and the UEFI boot file to two different partitions of the NBD network block device, and judging the type of an operating system of the Windows virtual machine so as to copy the Legacy boot file and the UEFI boot file of the corresponding operating system to the two different partitions of the NBD network block device;
judging whether the operating system of the Windows virtual machine is Windows 7 or Windows Vista, if so, copying a boot file of a Legacy boot mode of the Windows 7 or Windows Vista into a Windows visible partition; copying boot files of the UEFI boot mode of Windows 7 or Windows Vista to the system partition;
judging whether the operating system of the Windows virtual machine is Windows 10 or Windows 8, if so, copying the boot file of the Legacy boot mode of the Windows 10 or Windows 8 into a Windows visible partition; copying a boot file of the UEFI boot mode of Windows 10 or Windows 8 to the system partition;
when the Windows virtual machine is started, the cloud server judges that GPU computing resources of a host machine or GPU computing resources of a cloud terminal need to be used;
when GPU computing resources of a host machine need to be used, a Windows virtual machine is booted and started through a boot file of a UEFI boot mode in a system partition created by a Windows installation program;
when GPU computing resources of the cloud terminal need to be used, the Windows virtual machine is booted and started through a bootstrap file in a Legacy bootstrap mode, wherein the bootstrap file is extracted from a Windows installation file and copied into a Windows visible partition.
2. The method for converting the Windows virtual machine boot program according to claim 1, wherein: and before copying the Legacy boot file to the Windows visible partition of the NBD network block device, activating the Windows visible partition of the NBD network block device as an active partition.
3. The method for converting the Windows virtual machine boot program according to claim 1, wherein:
the step of judging the operating system type of the Windows virtual machine comprises the following steps:
judging the number of partitions in the NBD network block device file,
if the number of the partitions in the NBD network block device file is three, further judging whether an operating system of the Windows virtual machine is Windows 7 or Windows Vista;
and if the number of the partitions in the NBD network block device file is four, further judging whether the operating system of the Windows virtual machine is Windows 10 or Windows 8.
4. The method for converting the Windows virtual machine boot program according to claim 1, wherein: and after copying the Legacy boot file and the UEFI boot file to two different partitions of the NBD network block device respectively, the Linux host uninstalls the NBD network block device.
5. The method for converting the Windows virtual machine boot program according to claim 1, wherein: and the first starting equipment of the Legacy boot file and the UEFI boot file are both local disks.
6. The method for converting Windows virtual machine boot program according to claim 1 or 5, wherein: and the first starting program of the Legacy boot file and the UEFI boot file points to a Windows loader loading program modified into a local hard disk.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810750184.1A CN109002346B (en) | 2018-07-10 | 2018-07-10 | Conversion method of Windows virtual machine bootstrap program |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810750184.1A CN109002346B (en) | 2018-07-10 | 2018-07-10 | Conversion method of Windows virtual machine bootstrap program |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109002346A CN109002346A (en) | 2018-12-14 |
| CN109002346B true CN109002346B (en) | 2022-04-15 |
Family
ID=64598916
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810750184.1A Active CN109002346B (en) | 2018-07-10 | 2018-07-10 | Conversion method of Windows virtual machine bootstrap program |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109002346B (en) |
Families Citing this family (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111913753A (en) * | 2020-07-10 | 2020-11-10 | 江苏安超云软件有限公司 | Method and system for changing starting mode in cloud migration of windows system |
| CN111831346B (en) * | 2020-07-20 | 2023-06-09 | 平安科技（深圳）有限公司 | Method and device for starting memory operating system for data acquisition |
| CN112860377A (en) * | 2021-02-08 | 2021-05-28 | 广东微云科技股份有限公司 | Dual-system coexistence method and system |
| CN113419814B (en) * | 2021-05-27 | 2022-03-08 | 济南浪潮数据技术有限公司 | Virtual machine creating method, device, equipment and storage medium in cloud platform |
| CN113687837A (en) * | 2021-08-17 | 2021-11-23 | 锐捷网络股份有限公司 | Starting mode conversion method and system and virtual machine operation method |
Family Cites Families (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7162629B2 (en) * | 2003-11-20 | 2007-01-09 | Intel Corporation | Method to suspend-and-resume across various operational environment contexts |
| KR100746025B1 (en) * | 2006-01-12 | 2007-08-06 | 삼성전자주식회사 | Apparatus and method for switching between operating systems |
| CN102110007B (en) * | 2009-12-29 | 2014-01-29 | 中国长城计算机深圳股份有限公司 | Interaction method and system for BIOS/UEFI and virtual machine monitor |
| CN105117272B (en) * | 2015-08-21 | 2018-05-01 | 浪潮集团有限公司 | A kind of operating system management device, virtual machine and operating system method for switching between |
| CN105573819A (en) * | 2015-12-11 | 2016-05-11 | 国云科技股份有限公司 | Method for obtaining disk capacity information of virtual machine directly through host machine |
| CN107220071A (en) * | 2016-03-22 | 2017-09-29 | 北京蓝光引力网络股份有限公司 | A kind of method for guiding electronic equipment activation system |
| CN107436761B (en) * | 2017-07-01 | 2021-01-15 | 武汉噢易云计算股份有限公司 | UEFI (unified extensible firmware interface) system and traditional system coexistence management method based on UEFI mainboard |
-
2018
- 2018-07-10 CN CN201810750184.1A patent/CN109002346B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN109002346A (en) | 2018-12-14 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109002346B (en) | Conversion method of Windows virtual machine bootstrap program | |
| US8166477B1 (en) | System and method for restoration of an execution environment from hibernation into a virtual or physical machine | |
| US6804774B1 (en) | Software image transition aid comprising building a disk image based on identified hardware | |
| EP3518099B1 (en) | Installation of operating system | |
| US20110208929A1 (en) | In-place virtualization during operating system installation | |
| US20080126792A1 (en) | Systems and methods for achieving minimal rebooting during system update operations | |
| US20210240545A1 (en) | Information Handling System And Method To Automatically Synchronize Operating System And Boot Firmware Languages | |
| US20220214945A1 (en) | System Booting Method and Apparatus, Node Device, and Computer-Readable Storage Medium | |
| CN103514015A (en) | Method and device for booting operation system from storage medium | |
| WO2020063432A1 (en) | Method and apparatus for upgrading virtualized emulator | |
| CN112445495A (en) | Mirroring and recovery method for high-performance computing cluster nodes | |
| CN115390996A (en) | Virtual machine migration method and device, computing equipment and storage medium | |
| WO2011114476A1 (en) | Multicore processor system, notification program, and notification method | |
| JP7102524B2 (en) | Firmware release of multiple binary images | |
| CN115220797A (en) | Operating system starting and deploying method, device, equipment, medium and program product | |
| CN111433747A (en) | Virtual memory for loading an operating system | |
| WO2016177261A1 (en) | Method and device for online upgrading module based on kernel virtual machine | |
| CN113687837A (en) | Starting mode conversion method and system and virtual machine operation method | |
| CN111913753A (en) | Method and system for changing starting mode in cloud migration of windows system | |
| EP3543849A1 (en) | Driver management method and host machine | |
| CN107357400B (en) | Method for automatically starting up hard disk with specified operating system type | |
| US8554956B1 (en) | Method for creation of a device driver for a peripheral device | |
| CN101470657A (en) | Verification method for BIOS refreshing content | |
| CN114296810A (en) | Operating system migration method, device, server and storage medium | |
| US10789082B2 (en) | Execution of multiple operating systems without rebooting |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |