CN106502763A - A kind of Oftware updating method and device - Google Patents
A kind of Oftware updating method and device Download PDFInfo
- Publication number
- CN106502763A CN106502763A CN201610940659.4A CN201610940659A CN106502763A CN 106502763 A CN106502763 A CN 106502763A CN 201610940659 A CN201610940659 A CN 201610940659A CN 106502763 A CN106502763 A CN 106502763A
- Authority
- CN
- China
- Prior art keywords
- virtual machine
- data
- software
- updating method
- oftware updating
- 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.)
- Pending
Links
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
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- 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/4557—Distribution of virtual machine instances; Migration and load balancing
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Stored Programmes (AREA)
Abstract
The invention provides a kind of Oftware updating method and device, to host local input target version software, the second virtual machine is set up using target version software, the migration receiving terminal of the first virtual machine that sets up as local current version software, by the Data Migration of corresponding first virtual machine in the second virtual machine, interrupt the first virtual machine, start the second virtual machine, corresponding for the first virtual machine network flow is switched to the second virtual machine.The Oftware updating method and device that the present invention is provided need not generate specific software code patch or binary patches, it is only necessary to prepare a target version software, it is not necessary to rely on compiler, reduce technical difficulty.The calculating of complexity is not only restricted to, can be updated for software code on a large scale.
Description
Technical field
The present invention relates to computer software fields, more particularly to a kind of Oftware updating method and device.
Background technology
With the operation of software, it usually needs be optimized upgrading to software, but for some important systems and journey
Sequence needs to run incessantly, and the interruption of any process can all cause serious consequence, therefore the mode quilt of software dynamic update
Increasing use such that it is able to realize the members in the case where not affecting existing software normally to run, to software
Function be updated.
The mode of existing software dynamic update has to be realized by way of hot patch, specifically includes and is compiled by compilation unit
Patch function is translated, is loaded in the internal memory of patch function to operating system using loading unit, searching unit searches patch function pair
The antiderivative address that answers, modification unit is according to the antiderivative instruction of address modification so that between original function and patch function
Can realize mutually calling, call unit calls original function, execution patch function is redirected by original function directly, patch function is held
Returned by original function after having gone.
However, the mode of hot patch has compared with big limitation, need by compiling the specific patch function of generation, to compiling
There is dependence in device, patch generates also complex.The method also cannot be upgraded to the function being carrying out, and be easily caused liter
Level process check is in some functions.
The method of existing software dynamic update also has to be realized based on the mode of dynamic pitching pile, i.e., in binary level non-source
To the source program insertion key code being currently running in code layer time so that upgrading needs not rely on specific compiler, based on asynchronous
Checkpointing algorithm is able to ensure that all threads are in blocked state before dynamic update such that it is able to disposably update all threads
And avoid new and old edition from safeguarding the expense that brings, realize that function is redirected indirectly by the way of binary rewrite, can upgrade not
In the function to be updated for executing, the function to be updated being carrying out of being upgraded using the mode of storehouse reconstruct so that dynamic rises
Level eliminates the waiting time that cannot be expected for updating that loop body and principal function etc. bring.
The function to be updated the being carrying out although mode of above dynamic pitching pile can be upgraded, the method require that software exists
During renewal, all threads are carried out the position of pitching pile, for virtual machine, it is likely that processor long-play occurs and exists
In virtual machine, and the software in the host for needing upgrading is not run, so as to the position of unreachable pitching pile, cause the software cannot
Quick upgrading.Next, with the complexity increase of software, difficulty is also increasing, so as to realize on a large scale for the position of pitching pile
Software code updates.
Content of the invention
Above-mentioned the problems of the prior art are based on, it is an object of the invention to provide a kind of Oftware updating method and device,
Compiler is needed not rely on, technical difficulty is little, the method that software code updates on a large scale can be realized.
According to the first aspect of the invention, there is provided a kind of Oftware updating method, comprise the following steps：To local input mesh
Mark version software；One second virtual machine is set up using target version software, first set up as local current version software
The migration receiving terminal of virtual machine；By the Data Migration of corresponding first virtual machine in the second virtual machine；And it is virtual to interrupt first
Machine, starts the second virtual machine, corresponding for the first virtual machine network flow is switched to the second virtual machine.
Preferably, before the first virtual machine is interrupted, the first virtual machine runs current version software.
Preferably, also included step before the step of second virtual machine being set up using target version software：Judge this
Whether ground has the memory space for setting up the second virtual machine enough, if so, then sets up the second virtual machine；If it is not, then terminating.
Preferably, the step by the Data Migration of corresponding first virtual machine in the second virtual machine includes：Confirm that first is empty
The data that needs in plan machine are replicated；While the first Virtual Machine Worker, by the data duplication in the first virtual machine to second
Virtual machine；The data duplication that will be marked as modification in the first virtual machine is circulated to the second virtual machine.
Preferably, the step of interrupting the first virtual machine, the second virtual machine of startup includes：Interrupt the first virtual machine；By first
In virtual machine, the last data duplication for being marked as generation modification is to the second virtual machine；Start the second virtual machine.
Preferably, by socket port replicate data.
Preferably, the first virtual machine and the second virtual machine are operated in local internal memory.
Preferably, the step by the Data Migration of corresponding first virtual machine in the second virtual machine also includes：To be locally hard
Data in disk are mounted to the second virtual machine.
Preferably, first Microsoft Loopback Adapter information and the second void of the first virtual machine, before the first virtual machine is interrupted, are obtained
Corresponding for first virtual machine network flow is switched after starting the second virtual machine by the first Microsoft Loopback Adapter information of plan machine by network flow
To the second virtual machine.
Preferably, the time of network flow switching is less than 1ms.
Preferably, data include the internal storage data and processor data of the first virtual machine, input-output equipment status data.
According to the second aspect of the invention, there is provided a kind of software renewing apparatus, including：Input module, input module to
Local input target version software；Creation module, creation module set up one second virtual machine using target version software, used as this
The migration receiving terminal of the first virtual machine that the current version software on ground is set up；Transferring module, transferring module will corresponding first virtuality
The Data Migration of machine is in the second virtual machine；Handover module, handover module interrupt the first virtual machine, start the second virtual machine, will
The corresponding network flow of first virtual machine is switched to the second virtual machine.
The present invention realizes target version software upgrading by the method for virtual machine (vm) migration, as the second virtual machine is by mesh
Mark version software create, therefore when the second virtual machine replace the first virtual machine process external request when, software just naturally from
Current version software upgrading for target version software, so as to specific software code patch or binary patches need not be generated,
Only need to prepare a target version software.Therefore Oftware updating method of the invention needs not rely on compiler, it is to avoid life
The step of into patch, reduce technical difficulty.Due to being not only restricted to the calculating of complexity, therefore, it is possible to be directed to software code on a large scale
Update.Need not be that different software generates different update scheme, therefore there is versatility.
By way of the migration between the first virtual machine and the second virtual machine is using dynamic migration, it is ensured that ask for outside
The normal response that asks.
First virtual machine and the second virtual machine are operated in the internal memory of same host, during dynamic migration of virtual machine, it is only necessary to
Internal storage data is wanted to migrate, so as to software upgrading speed is fast.
Overall update method is caused for the break period of external request is very short, so as to realize being close to lossless software more
New process.
Description of the drawings
Technical scheme is described in detail below in conjunction with the drawings and specific embodiments, so that the present invention
Characteristic and advantage become apparent from.
Fig. 1 is the structural representation of an example of the host of the present invention；
Fig. 2 is the flow chart of an example of the Oftware updating method of the present invention；
Fig. 3 is the detail flowchart of step S105 and step S106 in Fig. 2；
Fig. 4 is the module diagram of an example of the software renewing apparatus of the present invention.
Specific embodiment
Hereinafter will embodiments of the invention be given with detailed description.Although the present invention will be in conjunction with some specific embodiments
It is illustrated and illustrates, but it should be noted that the present invention is not merely confined to these embodiments.Conversely, to the present invention
The modification for carrying out or equivalent, all should cover in the middle of scope of the presently claimed invention.
Some exemplary embodiments are described as process or the method that describes as flow chart.Although flow chart is grasped every
The process of order is described into, but many of which operation can be implemented concurrently, concomitantly or simultaneously.Additionally, each
The order of item operation can be rearranged.The process can be terminated when its operations are completed, it is also possible to have not
Including additional step in the accompanying drawings.The process can correspond to method, function, code, subroutine, subprogram etc..
The present invention realizes the software upgrading in host, software upgrading provided by the present invention by the method for virtual machine (vm) migration
Method and device are applied to the virtual environment under host-virtual machine, are not suitable for the dynamic update of common software.
Fig. 1 is the structural representation of an example of the host of the present invention.As shown in figure 1, host 101 includes processing
Device 102, internal memory 103 and hard disk 104.
Current version software 301 is stored in the hard disk 104 of host 101, and current version software 301 is to need to update
Software.In other embodiments, current version software 301 can be also stored in other storage devices of host 101.
First virtual machine 201 is operated in the internal memory 103 of host 101 by current version software 301.
Target version software 302 stores same in the hard disk 104 of host 101.Software upgrading of the present invention
Method is locally completing in same host 101, without carrying out virtual machine remote thermophoresis, accelerates software upgrading
Speed.
Second virtual machine 202 is created in the internal memory 103 of host 101 by target version software 302.Namely
Say, the first virtual machine 201 and the second virtual machine 202 are operated in the internal memory of same host 101, such setting causes virtuality
Machine is in dynamic migration, it is only necessary to which internal storage data is migrated, and so as to effectively shorten the dynamic migration time, helps to realize being close to lossless
Software upgrading process.It should be noted that although the first virtual machine 201 and the second virtual machine 202 operate in same host 101
Internal memory in, but in order to avoid both configuration conflicts be not and meanwhile start.
Lower mask body introduces Oftware updating method provided by the present invention.
Fig. 2 is the flow chart of an example of the Oftware updating method of the present invention.In conjunction with shown in Fig. 1 and Fig. 2, software upgrading
Method S100 is mainly implemented the steps of：
Step S101：To local input target version software 302.
Step S102：Judge locally whether there is the memory headroom for setting up the second virtual machine 202 enough.
Step S103：The second virtual machine 202 is created using target version software 302.
Step S104：Obtain send to the first virtual machine 201 network flow, obtain the first Microsoft Loopback Adapter (vnet) information with
And the 2nd vnet information.
Step S105：By the data dynamic migration of corresponding first virtual machine 201 in the second virtual machine 202.
Step S106：Interrupt the first virtual machine 201, start the second virtual machine 202.
Step S107：First virtual machine, 201 corresponding network flow is switched to the second virtual machine 202.
In conjunction with Fig. 1 and Fig. 2, first such as step S101, to the input target version of hard disk 104 software 302 of host 101,
In this step, target version software 302 is only stored in the local of host 101, the processor also without host 101
102 by actual motion.Meanwhile, during whole software upgrading, the first virtual machine 201 is still through current version software 301
Operate in host 101, the operation so as to ensure the first virtual machine 201 is not affected by software upgrading.
Such as step S102, judge locally whether there is the memory space for setting up the second virtual machine 202 enough.In the present embodiment
In, the first virtual software 201 and the second virtual software 202 are operated in the internal memory 103 of host 101, that is to say, that in step
In rapid S102, the internal memory 103 of host 101 is judged whether while the first virtual machine 101 is present, with enough storage skies
Between set up the second virtual machine 202, then carry out below step in this way, such as otherwise terminate software upgrading.
Then, such as step S103, second virtual machine 202 is created using target version software 302.It should be noted that this
When the first virtual machine 201 in application service is still provided, therefore will not on outside requesting party produce impact.In this step
Second virtual machine 202 only includes virtual machine functional framework and do not include specific content-data, such as internal storage data, input and output
Status data, processor data etc..
Such as step S104, the network flow sent to the first virtual machine 201 is obtained, obtain a vnet information and second
Vnet information.Here a vnet information refers to that the Microsoft Loopback Adapter information of the first virtual machine 201, the 2nd vnet information refer to
The Microsoft Loopback Adapter information of two virtual machines 202.Step S104 be in order to the second virtual machine 202 afterwards start when, can be by network flow
The second virtual machine 202 is switched to from the first virtual machine 201 to prepare.
Then such as step S105, by the data dynamic migration of corresponding first virtual machine 201 in the second virtual machine 202.Such as
Step S106, interrupts the first virtual machine 201, starts the second virtual machine 202.
As the second virtual machine 202 is created by target version software 302, therefore when 202 replacement of the second virtual machine
When first virtual machine 201 processes external request, software is just upgraded for target version software from current version software 301 naturally
302.
Fig. 3 is the detail flowchart of step S105 and step S106 in Fig. 2.Illustrate below with reference to Fig. 3 and Fig. 1
Step S105 and step S106.
As shown in figure 3, step S105 includes：
Step S1051：Confirm the data that the needs of corresponding first virtual machine 201 are replicated.
Step S1052：Second virtual machine 202 is received and is prepared.
Step S1053：First virtual machine, 201 replicate data.
Step S1054：First virtual machine 201 sends data.
Step S1055：Second virtual machine, 202 receiving data.
Step S1056：First virtual machine, 201 never mark is the data that modification occurs.
Step S1057：First virtual machine 201 judges whether duplication completes.
Specifically, first such as step S1051, confirm that corresponding first virtual machine 201 needs the data for replicating, due to first
Virtual machine 201 and the second virtual machine 202 are operated in the internal memory of same host 101, it is therefore desirable to which the data of duplication are not wrapped
Include the data in hard disk.The data for replicating are needed to include the internal storage data of the first virtual machine, input-output equipment status data, place
Reason device data.On the other hand, such as step S1052, the second virtual machine 202 carries out reception preparation.In the present embodiment, empty first
Set up socket port in plan machine 201 and the second virtual machine 202 respectively, and by two socket ports set up one two-way
Communication connection, so that pass through socket port replicate data.Socket is originally that but socket also may be used for Design of Network Communication
To realize the communication between the different processes (i.e. different virtual machine) of same host.Socket process communications are used with network service
Be to unify socket, simply address structure is different from some parameters, and the socket addresses of such as network service are that IP address adds
Port numbers, and the socket addresses of process communication are path of the file of a socket type in file system.
Then while the application in the first virtual machine 201 provides service, by the data duplication in the first virtual machine 201
To the second virtual machine, i.e., such as 201 replicate data of the first virtual machine of step S1053, the first virtual machine of step S1054 201 sends number
According to such as 202 receiving data of the second virtual machine of step S1055.
Implementation steps S1054 and step S1055 are transmitted using socket files, due to socket file transfer rates very
Hurry up, shorten the software upgrading time therefore, it is possible within a very short time by the data duplication in the first virtual machine to the second virtual machine.
As in the internal memory 103 of same host 101, therefore the first virtual machine 201 and the second virtual machine 202 operate in
Replicate and internal memory of the transmission generation in Same Physical machine be between internal memory, the duplication of data in hard disk can be omitted completely,
So as to shorten the software upgrading time.
Then the data duplication that will be marked as modification in the first virtual machine 201 is circulated to the second virtual machine 202.Right
The data for occurring to change in reproduction process need to be marked, and carry out repeatedly circulation more to the data for being labeled as occurring modification
Newly, so that it is guaranteed that in the second virtual machine 202 and the first virtual machine 201 data concordance.Concrete such as step S1056 first is virtual
201 never mark of machine is the data that modification occurs, and the first virtual machine of step S1054 201 sends replicate data, step S1055 the
Two virtual machine 202 receives replicate data, and judges whether duplication is completed being walked by the first virtual machine of step S1057 201
The circulation of rapid S1056, step S1054 and step S1055.The condition that duplication is completed can be carried out by the condition for pre-setting
Judge, for example remaining data volume for being labeled as occurring modification is less than a threshold value.
For the data in 101 hard disk 104 of host, data are moved to from the first virtual machine 201 by carry operation
Second virtual machine 202.Carry operation is not copied to data, but the file by corresponding for data the first virtual machine 201
Carry is carried out in the second virtual machine 202.So as in the transition process to virtual machine, it is to avoid the duplication of data in hard disk is grasped
Make, reduce migration and consume, lift migration velocity.
When the first virtual machine 201 judges that duplication is completed, step S106 is entered.Step S106 includes：
Step S1061：First virtual machine 201 interrupts application.
Step S1062：First virtual machine 201 replicates the data that last labelling is modification.
Step S1054：First virtual machine 201 sends replicate data.
Step S1055：Second virtual machine 202 receives replicate data.
Step S1063：Second virtual machine 202 starts application.
Specifically, first such as step S1061, interrupt the first virtual machine 201 and run, before this step of when executing,
Still service is provided in first virtual machine 201, and when this step is executed, external request will be unable to be processed again.Such as step
S1062, by the last data duplication for being marked as occurring modification in the first virtual machine 201 to the second virtual machine 202, wherein most
The data for being marked as generation modification afterwards are referred to and are not also migrated to the number of the second virtual machine 202 after step S105 is executed
According to.The labelling that will be also not replicated after step S105 is executed is that the data of modification are replicated, so as to ensure number
According to integrity, it is not lost.Such as step S1054, such as the transmission replicate data of the first virtual machine 201, the second virtual machine of step S1055
202 receive replicate data.Last execution step S1063, starts the second virtual machine 202.
After the second virtual machine 202 starts, 201 corresponding network flow of the first virtual machine is switched to by execution step S107
Second virtual machine 202.Specifically, a vnet information and the 2nd vnet information are obtained according in step S104, is being executed
During step S107, it is only necessary to which host 101 is by monitor in real time and the network flow that receives is converted to second from a vnet information
Vnet information, can complete network flow switching.When flow switch is completed, external request will retrieve response.Due to taking
The said method of the present invention, the time of network flow switching are less than 1ms, so as to the time of external flow interrupt response is very short, because
This will not cause external request people's change perceived, so as to realize being close to lossless software upgrading process.
It should be noted that virtual motor-driven in the Oftware updating method that introduces in above-described embodiment and variant embodiment
State moving method is not unique method, all is that by 201 dynamic migration of the first virtual machine to the second virtual machine 202
Additive method can be suitable in the present invention.
Present invention also offers a kind of software renewing apparatus, Fig. 4 is an example of the software renewing apparatus of the present invention
Module diagram.As shown in Fig. 4 and Fig. 1, software renewing apparatus 401 are arranged in host 101, including input module 402,
Creation module 403, transferring module 404 and handover module 405.Input module 402 is used for local input target version software
302.Creation module 403 sets up the second virtual machine 202 using target version software 302, used as local current version software 301
The migration receiving terminal of the first virtual machine 201 that sets up.Transferring module 404 is by the Data Migration of corresponding first virtual machine 201 to the
In two virtual machines 202.Handover module 405 interrupts the first virtual machine 201, starts the second virtual machine 202, by the first virtual machine 201
Corresponding network flow is switched to the second virtual machine 202.The operation method of concrete modules Oftware updating method described above, this
Place repeats no more.
The present invention realizes software upgrading by the method for virtual machine (vm) migration and device, need not any type of patch, from
And needing of avoiding that patch brought relies on compiler, technical difficulty is big, the problems such as not there is versatility.Due to being not only restricted to
Complicated calculating, updates therefore, it is possible to be directed to software code on a large scale.
The Oftware updating method renewal time provided by the present invention is short, can realize being close to lossless software upgrading process.
The above is only the concrete application example of the present invention, protection scope of the present invention is not limited in any way.Except above-mentioned
Implement exception, the present invention there can also be other embodiment.The technical scheme that all employing equivalents or equivalent transformation are formed,
Fall within scope of the present invention.
Claims (12)
1. a kind of Oftware updating method, it is characterised in that comprise the following steps：
To local input target version software；
One second virtual machine is set up using the target version software, as the first virtuality that local current version software is set up
The migration receiving terminal of machine；
By the Data Migration of correspondingly first virtual machine in second virtual machine；And
Interrupt first virtual machine, start second virtual machine, corresponding for first virtual machine network flow is switched to
Second virtual machine.
2. Oftware updating method as claimed in claim 1, it is characterised in that before first virtual machine is interrupted, described
First virtual machine runs current version software.
3. Oftware updating method as claimed in claim 1, it is characterised in that
Also included step before the step of second virtual machine being set up using the target version software：
Judge locally whether there is the memory space for setting up second virtual machine enough, if so, then set up second virtual machine；
If it is not, then terminating.
4. Oftware updating method as claimed in claim 1, it is characterised in that
Step of the Data Migration of correspondingly first virtual machine in second virtual machine is included：
Confirm the data for needing to replicate in first virtual machine；
While first Virtual Machine Worker, by the data duplication in first virtual machine to second virtual machine；
The data duplication that will be marked as modification in first virtual machine is circulated to second virtual machine.
5. Oftware updating method as claimed in claim 4, it is characterised in that
Described interrupt first virtual machine, include the step of start second virtual machine：
Interrupt first virtual machine；
By the last data duplication for being marked as modification in the first virtual machine to second virtual machine；
Start second virtual machine.
6. the Oftware updating method as described in claim 4 or 5, it is characterised in that the data are replicated by socket port.
7. Oftware updating method as claimed in claim 1, it is characterised in that first virtual machine and second virtual machine
Operate in local internal memory.
8. Oftware updating method as claimed in claim 7, it is characterised in that the data by correspondingly first virtual machine
The step moved in second virtual machine also includes：Data in local hard drive are mounted to second virtual machine.
9. Oftware updating method as claimed in claim 1, it is characterised in that before first virtual machine is interrupted, obtains
First Microsoft Loopback Adapter information of first virtual machine and the second Microsoft Loopback Adapter information of second virtual machine, start described the
Corresponding for first virtual machine network flow is switched to second virtual machine by network flow after two virtual machines.
10. Oftware updating method as claimed in claim 6, it is characterised in that the time of the network flow switching is less than 1ms.
11. Oftware updating methods as claimed in claim 1, it is characterised in that the data include first virtual machine
Internal storage data and processor data, input-output equipment status data.
12. a kind of software renewing apparatus, it is characterised in that include：
Input module, the input module is to local input target version software；
Creation module, the creation module set up one second virtual machine using target version software, used as local current version
The migration receiving terminal of the first virtual machine that software is set up；
Transferring module, the transferring module is by the Data Migration of correspondingly first virtual machine in second virtual machine；
Handover module, the handover module interrupt first virtual machine, start second virtual machine, virtual by described first
The corresponding network flow of machine is switched to second virtual machine.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610940659.4A CN106502763A (en) | 2016-11-01 | 2016-11-01 | A kind of Oftware updating method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610940659.4A CN106502763A (en) | 2016-11-01 | 2016-11-01 | A kind of Oftware updating method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN106502763A true CN106502763A (en) | 2017-03-15 |
Family
ID=58321788
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610940659.4A Pending CN106502763A (en) | 2016-11-01 | 2016-11-01 | A kind of Oftware updating method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106502763A (en) |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109491698A (en) * | 2018-12-29 | 2019-03-19 | 武汉思普崚技术有限公司 | Method for updating system and device based on hot patch |
| CN109558219A (en) * | 2017-09-25 | 2019-04-02 | 阿里巴巴集团控股有限公司 | Frequency reducing method, device and storage medium in a kind of thermophoresis |
| CN110489150A (en) * | 2019-08-26 | 2019-11-22 | 深信服科技股份有限公司 | A kind of hot upgrade method of virtual machine, device and its relevant device |
| WO2020063432A1 (en) * | 2018-09-30 | 2020-04-02 | 华为技术有限公司 | Method and apparatus for upgrading virtualized emulator |
| CN113885904A (en) * | 2021-09-02 | 2022-01-04 | 奇安信科技集团股份有限公司 | System upgrading method and device, electronic equipment and storage medium |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101727331A (en) * | 2008-10-24 | 2010-06-09 | 国际商业机器公司 | Method and equipment for upgrading client operating system of active virtual machine |
| CN104102527A (en) * | 2014-07-10 | 2014-10-15 | 国云科技股份有限公司 | Method for updating software of virtual machine |
| CN104391717A (en) * | 2014-11-18 | 2015-03-04 | 南京大学 | Method for dynamically updating code during debugging |
| US20150071111A1 (en) * | 2013-09-10 | 2015-03-12 | Cisco Technology, Inc. | Auto Tunneling in Software Defined Network for Seamless Roaming |
| CN105426213A (en) * | 2015-12-04 | 2016-03-23 | 深圳市深信服电子科技有限公司 | Software update method and system |
| CN105591935A (en) * | 2015-08-26 | 2016-05-18 | 杭州华三通信技术有限公司 | Method and device for updating EID-RLOC mapping relation after virtual machine migration |
-
2016
- 2016-11-01 CN CN201610940659.4A patent/CN106502763A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101727331A (en) * | 2008-10-24 | 2010-06-09 | 国际商业机器公司 | Method and equipment for upgrading client operating system of active virtual machine |
| US20150071111A1 (en) * | 2013-09-10 | 2015-03-12 | Cisco Technology, Inc. | Auto Tunneling in Software Defined Network for Seamless Roaming |
| CN104102527A (en) * | 2014-07-10 | 2014-10-15 | 国云科技股份有限公司 | Method for updating software of virtual machine |
| CN104391717A (en) * | 2014-11-18 | 2015-03-04 | 南京大学 | Method for dynamically updating code during debugging |
| CN105591935A (en) * | 2015-08-26 | 2016-05-18 | 杭州华三通信技术有限公司 | Method and device for updating EID-RLOC mapping relation after virtual machine migration |
| CN105426213A (en) * | 2015-12-04 | 2016-03-23 | 深圳市深信服电子科技有限公司 | Software update method and system |
Cited By (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109558219A (en) * | 2017-09-25 | 2019-04-02 | 阿里巴巴集团控股有限公司 | Frequency reducing method, device and storage medium in a kind of thermophoresis |
| CN109558219B (en) * | 2017-09-25 | 2023-05-26 | 阿里巴巴集团控股有限公司 | Down-conversion method, device and storage medium in thermal migration |
| WO2020063432A1 (en) * | 2018-09-30 | 2020-04-02 | 华为技术有限公司 | Method and apparatus for upgrading virtualized emulator |
| CN110968392A (en) * | 2018-09-30 | 2020-04-07 | 华为技术有限公司 | Method and device for upgrading virtualization simulator |
| US11875174B2 (en) | 2018-09-30 | 2024-01-16 | Huawei Technologies Co., Ltd. | Method and apparatus for virtual machine emulator upgrading virtualization emulator |
| CN110968392B (en) * | 2018-09-30 | 2024-04-12 | 华为技术有限公司 | Method and device for upgrading virtualized simulator |
| CN109491698A (en) * | 2018-12-29 | 2019-03-19 | 武汉思普崚技术有限公司 | Method for updating system and device based on hot patch |
| CN109491698B (en) * | 2018-12-29 | 2022-07-08 | 武汉思普崚技术有限公司 | System updating method and device based on hot patch |
| CN110489150A (en) * | 2019-08-26 | 2019-11-22 | 深信服科技股份有限公司 | A kind of hot upgrade method of virtual machine, device and its relevant device |
| CN113885904A (en) * | 2021-09-02 | 2022-01-04 | 奇安信科技集团股份有限公司 | System upgrading method and device, electronic equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106502763A (en) | A kind of Oftware updating method and device | |
| CN100492292C (en) | Automatic backup storage for firmware upgrading | |
| KR100825348B1 (en) | Server system and online software update method | |
| CN110073333B (en) | Method and system for recovering logic in FPGA chip and FPGA device | |
| CN100568938C (en) | The upgrading of digital media server | |
| US20090067334A1 (en) | Mechanism for process migration on a massively parallel computer | |
| CN102147747B (en) | The system and method for the upgrading path strengthened | |
| CN103493003B (en) | The copy of disk image is sent from source memory to target memory | |
| CN101815988A (en) | Firmware image update and management | |
| WO2011076089A1 (en) | Method and device for managing operating systems in embedded system | |
| US8893272B2 (en) | Method and device for recombining runtime instruction | |
| CN102597963B (en) | Dynamic copies volume in cluster exchanges | |
| CN107943504B (en) | Dynamic upgrading method for software module in embedded system | |
| CN104424037A (en) | Method and device for dynamically patching function | |
| CN108121558B (en) | Oftware updating method, device, storage medium and equipment | |
| KR101130875B1 (en) | Automatic backup store in firmware upgrades | |
| JP5387767B2 (en) | Update technology for running programs | |
| US20220326869A1 (en) | Storage system and control method for storage system | |
| KR100744502B1 (en) | Basic Architecture for Software Environment framework in radio terminal and method of the same | |
| US20080077925A1 (en) | Fault Tolerant System for Execution of Parallel Jobs | |
| CN113051122B (en) | Performance data acquisition method, device, electronic equipment and medium | |
| CN109308232A (en) | The method, apparatus and system of rollback after live migration of virtual machine failure | |
| CN117349025B (en) | Configuration migration method and device, electronic equipment and storage medium | |
| US11271999B2 (en) | Flexible associativity in multitenant clustered environments | |
| KR20030041605A (en) | Apparatus and method for remote upgrading of program in communication system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| CB02 | Change of applicant information |
Address after: 200433 Room 201, 10 B, 619 Longchang Road, Yangpu District, Shanghai. Applicant after: Excellent Polytron Technologies Inc Address before: 200433 room 1207-10, 6 Wade Road, Yangpu District, Shanghai. Applicant before: SHANGHAI UCLOUD INFORMATION TECHNOLOGY CO., LTD. |
|
| CB02 | Change of applicant information | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20170315 |
|
| RJ01 | Rejection of invention patent application after publication |