CN111181953A - Method and device for supporting spice protocol through Roc virtualization - Google Patents
Method and device for supporting spice protocol through Roc virtualization Download PDFInfo
- Publication number
- CN111181953A CN111181953A CN201911368218.1A CN201911368218A CN111181953A CN 111181953 A CN111181953 A CN 111181953A CN 201911368218 A CN201911368218 A CN 201911368218A CN 111181953 A CN111181953 A CN 111181953A
- Authority
- CN
- China
- Prior art keywords
- spice
- server
- qemu
- kvm
- processor
- 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.)
- Granted
Links
- 235000013599 spices Nutrition 0.000 title claims abstract description 58
- 238000000034 method Methods 0.000 title claims abstract description 23
- 230000004048 modification Effects 0.000 claims abstract description 20
- 238000012986 modification Methods 0.000 claims abstract description 20
- 238000001228 spectrum Methods 0.000 claims abstract description 6
- 238000010276 construction Methods 0.000 claims description 7
- 230000007717 exclusion Effects 0.000 claims description 2
- 238000012217 deletion Methods 0.000 claims 1
- 230000037430 deletion Effects 0.000 claims 1
- 230000001419 dependent effect Effects 0.000 description 3
- 241000931526 Acer campestre Species 0.000 description 2
- 230000003044 adaptive effect Effects 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 238000009434 installation Methods 0.000 description 2
- 241000157302 Bison bison athabascae Species 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000002349 favourable effect Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/26—Special purpose or proprietary protocols or architectures
-
- 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/451—Execution arrangements for user interfaces
- G06F9/452—Remote windowing, e.g. X-Window System, desktop virtualisation
-
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/08—Protocols specially adapted for terminal emulation, e.g. Telnet
-
- 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/45562—Creating, deleting, cloning virtual machine instances
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Human Computer Interaction (AREA)
- Computing Systems (AREA)
- Computer Security & Cryptography (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The application discloses a method and a device for supporting a spice protocol in spread virtualization, which are used for solving the problems that the existing server based on a spread processor does not support the spice protocol and brings inconvenience to the operation of a user. According to the method, according to the modification of a canonical file in a spice-server source code packet in the server based on the spread processor, the canonical file is determined to be adapted to the architecture of the spread processor, and a spice-server binary packet is constructed; and determining that the qemu-kvm source code package supports the spice protocol according to the modification of the specification file and the patch file in the qemu-kvm source code package in the server based on the spread-spectrum processor, and constructing a qemu-kvm binary package. The source codes of the spice-server software and the qemu-kvm software are adjusted to adapt to the architecture of the spread-peng processor, so that a spice protocol can be supported, virtual display is realized, and user operation is facilitated.
Description
Technical Field
The application relates to the technical field of virtualization, in particular to a method and a device for supporting a spice protocol through spread virtualization.
Background
Virtualization means that a plurality of virtual machine systems are simultaneously operated on one server through a virtualization technology, and application programs in each virtual machine system can be operated in mutually independent spaces without mutual influence, so that the working efficiency of the server is remarkably improved.
When the virtual machine is running, a certain desktop virtualization data transmission protocol (such as a spice protocol) is usually adopted to realize virtualization display, so that a user interface for operating the virtual machine is provided for a user in a Linux system, and the operation of the user is facilitated.
However, since the architecture of the mashup processor is different from the architecture of x86 and the like, the virtualized environment of the server based on the mashup processor does not support the spice protocol, which is not favorable for the user to operate the virtual machine, and brings much inconvenience to the user.
Disclosure of Invention
The embodiment of the application provides a method and a device for supporting a spice protocol in spread-grid virtualization, which are used for solving the problems that the existing server based on a spread-grid processor does not support the spice protocol and is inconvenient for a user to operate.
The method for supporting the spice protocol by the spread virtualization, provided by the embodiment of the application, is characterized in that a server based on a spread processor is set up in advance, and the method comprises the following steps:
determining that the canonical file is adapted to the architecture of the spread-server processor according to the modification of the canonical file in the spice-server source code packet in the server based on the spread processor, and constructing a spice-server binary packet;
and determining that the qemu-kvm source code package supports the spice protocol according to the modification of the specification file and the patch file in the qemu-kvm source code package in the server based on the spread-spectrum processor, and constructing a qemu-kvm binary package.
The embodiment of the application provides a spread penny virtualization support spice protocol's device, has set up the server based on spread penny processor in advance, the device includes:
the first determining module is used for determining that the canonical file is adapted to the architecture of the spread-penning processor according to the modification of the canonical file in the spice-server source code packet in the server based on the spread-penning processor and constructing a spice-server binary packet;
and the second determination module is used for determining that the qemu-kvm source code package supports the spice protocol and constructing a qemu-kvm binary package according to the modification of the canonical file and the patch file in the qemu-kvm source code package in the server based on the spread-spectrum processor.
The embodiment of the application provides a method and a device for supporting a spice protocol by spread-penny virtualization, and the method carries out adaptive adjustment on spice-server software and qemu-kvm software source codes related to the spice protocol according to the architecture of a spread-penny processor so as to enable the spice-server software and the qemu-kvm software source codes to support the architecture of the spread-penny processor, so that a virtualization management system installed in a server based on the spread-penny processor can support the spice protocol, realize virtualized display and facilitate operation of a user.
Drawings
The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:
fig. 1 is a flowchart of a method for supporting a spice protocol by spread virtualization according to an embodiment of the present disclosure;
fig. 2 is a schematic structural diagram of a device for supporting a spice protocol in the spread virtualization according to an embodiment of the present disclosure.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the technical solutions of the present application will be described in detail and completely with reference to the following specific embodiments of the present application and the accompanying drawings. It should be apparent that the described embodiments are only some of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
At present, the virtualized system installed in the server based on the mason processor does not support the spice protocol, and for this reason, the supporting situation of the server based on the mason processor on the spice protocol can be checked by installing the virtualized system in the server based on the mason processor.
Specifically, during installation, a virtualization system in an official software warehouse can be installed through server connection, and the virtualization system comprises qemu-kvm software, virt-manager software and the like. The qemu-kvm is a combination of a Quick Emulator (qemu) and a system virtualization module (Kernel-based Virtual Machine, kvm), the qemu is used for realizing I/O virtualization, the kvm is an open-source system virtualization module, and virt-manager software is computer software suitable for a Linux platform and is a main tool for managing a kvm Virtual environment.
In operation, the specific instructions may include:
yum install qemu-kvm libvirt virt-manager
systemctl start libvirtd
further, when the virtualization system is installed, a Unified Extensible Firmware Interface (UEFI) based on the spread Architecture aarch64 needs to be installed, and specifically may be an ARM Architecture Virtual Machine Firmware (AAVMF) Firmware. The UEFI firmware is a new mode of interaction between the operating system and the firmware, and if the UEFI firmware is missing, the virtual machine cannot be installed on a virt-manager interface through an ISO (International organization for standardization). The ISO represents an image file, the spread architecture refers to an ARM architecture of the spread processor, and the aarch64 is an execution state of the ARM architecture.
In operation, the specific instructions may include:
yum install AAVMF
further, after the virtualization system is installed, an attempt may be made to execute a command to initiate the spice protocol to see if support for the spice protocol can be implemented within the corresponding virtualization system in the spread processor based server.
In operation, the specific instructions may include:
/usr/libexec/qemu-kvm-spice port＝5900
after the above instructions are executed, the output results obtained are:
qemu-kvm:-spice port＝5900:There is no option group'spice'
qemu-kvm:-spice port＝5900:spice support is disabled
therefore, the current virtualization system does not support the spice protocol.
In particular, commands may be further executed to view the currently supported display devices.
The specific instructions may include:
/usr/libexec/qemu-kvm-device help
after the above instructions are executed, the output result is:
Display devices:
name"virtio-gpu-device",bus virtio-bus
name"virtio-gpu-pci",bus PCI,alias"virtio-gpu"
as can be seen, the output result does not include the spice-dedicated graphics card QXL. Thus, the virtualization system installed in the mashup processor-based server does not support the spice protocol.
Fig. 1 is a flowchart of a method for supporting a spice protocol by spread virtualization according to an embodiment of the present application, which specifically includes the following steps:
s101: according to the modification of the specification file in the spice-server source code packet in the server based on the spread processor, determining the framework of the specification file adaptive to the spread processor, and constructing a spice-server binary packet.
In the embodiment of the application, a server based on a spread-spectrum processor is set up in advance. And then, installing a spice-server source code packet, and modifying a specification file, namely a spice. The spice-server software is one of spice components.
Aiming at different operating systems, the spice-server software can be correspondingly adjusted in a targeted manner. In the embodiment of the present application, a description is given by taking the ubiquitous processor supported CentOS 7 operating system as an example, and how to implement the support of the spice protocol by the virtualization environment in the ubiquitous processor supported CentOS 7 operating system is described in detail.
Specifically, when the spice-server is adjusted, a construction dependent package of spice-server software needs to be determined first. The construction dependency package is used for providing support for constructing the spice-server software and can comprise spice-protocol and the like.
In operation, the specific instructions may include:
yum install wget spice-protocol
yum install gcc glib2-devel pixman-devel openssl-devel libjpeg-turbo-devel opus-devel bison flex
yum install rpm-build rpmdevtools yum-utils
yum install celt051-devel alsa-lib-devel libcacard-devel cyrus-sasl-devel lz4-devel pyparsing git libtool
the source code package of the spice-server software can be downloaded and installed in the system.
In operation, the specific instructions may include:
wgethttp://vault.centos.org/centos/7.6.1810/updates/Source/SPackages/spice-0.14.0-6.el7_6.1.src.rpm
rpm-ivh spice-0.14.0-6.el7_6.1.src.rpm
after that, the spice. spec file in the spice-server source code packet can be modified accordingly, and the aarch64 architecture representing the architecture of the mashup processor is added to the target architecture supported by the spice-server source code packet, so that the target architecture supports the architecture of the mashup processor.
In operation, the specific instructions may include:
sed-i's/^ExclusiveArch.*/&aarch64/'～/rpmbuild/SPECS/spice.spec
after modification, the spice-server source code packet can be constructed to generate a final executable rpm binary packet file and stored in a root/rpmbild/RPMS/aach 64/directory.
When the building is carried out, the specific instruction is as follows:
rpmbuild-bb/root/rpmbuild/SPECS/spice.spec
s102: according to the modification of the specification file and the patch file in the qemu-kvm source code package in the server based on the Roc processor, determining that the qemu-kvm source code package supports the spice protocol, and constructing a qemu-kvm binary package.
In the embodiment of the application, the spice-server constructed in the S101 can be used as a support component of qemu-kvm. Then, in S102, the source code of the installed qemu-kvm may be modified and constructed according to the architecture of the spread processor.
First, before the qemu-kvm source code is modified, the construction dependent package of qemu-kvm needs to be determined. The construction dependent package is used for providing support for constructing qemu-kvm software and can comprise ipxe-roms-qemu seavgabios-bin and the like.
When installing the build dependency package, the specific instructions may include:
yum install ipxe-roms-qemu seavgabios-bin
yum install gnutls-devel libaio-devel pciutils-devel libiscsi-develncurses-devel libattr-devel libusbx-devel texinfo libseccomp-devel libcurl-devel libssh2-devel librados2-devel librbd1-devel systemtap systemtap-sdt-devel libpng-devel libuuid-devel bluez-libs-devel brlapi-devel check-devellibcap-devel rdma-core-devel gperftools-devel libfdt-devel lzo-devel snappy-devel numactl-devel libgcrypt-devel device-mapper-multipath-devel systemd-devel libcap-ng-devel libxkbcommon-devel
after the dependency package is built, the spice-server built in the S101 can be installed, so that the spice-server can support qemu-kvm.
The specific instructions may include:
rpm-ivh
/root/rpmbuild/RPMS/aarch64/spice-server-devel-0.14.0-6.el7.1.aarch64.rpm
rpm-ivh
/root/rpmbuild/RPMS/aarch64/spice-server-0.14.0-6.el7.1.aarch64.rpm
thereafter, the source rpm package for qemu-kvm may be downloaded and installed in the system.
The specific instructions may include:
wget
http://vault.centos.org/centos/7.6.1810/virt/Source/kvm-common/qemu-kvm-ev-2.12.0-18.el7_6.7.1.src.rpm
rpm-ivh qemu-kvm-ev-2.12.0-18.el7_6.7.1.src.rpm
then, according to the architecture of the mashup processor, the source code package of qemu-kvm can be adaptively modified, and the specification file (i.e., qemu-kvm.
Specifically, the information indicating whether the spice protocol is supported or not in the qemu-kvm. Spec file is the original information, specifically, the% global have _ spec 0.
The specific instructions comprise:
sed-i'38s/0/1/'/root/rpmbuild/SPECS/qemu-kvm.spec
spec file can be removed with aarch64 typeface at a specified position, so that qemu-kvm software can cancel exclusion of aarch 64.
The specific instructions may include:
sed-i'131s/aarch64//'/root/rpmbuild/SPECS/qemu-kvm.spec
sed-i'2236s/aarch64//'/root/rpmbuild/SPECS/qemu-kvm.spec
sed-i'2249s/aarch64//'/root/rpmbuild/SPECS/qemu-kvm.spec
sed-i'2395s/aarch64//'/root/rpmbuild/SPECS/qemu-kvm.spec
spec file in the package, the information of the version number of the target rpm file generated by the control at the specified position may be modified to a higher version for the subsequent upgrade operation.
The specific instructions may include:
sed-i'/^Release/s/18/50/'/root/rpmbuild/SPECS/qemu-kvm.spec
the patch file in the qemu-kvm source code package can be modified, so that the patch file can modify default-configurations/aarch 64-softmmu.
The specific instructions may include:
sed-i'270a+CONFIG_QXL＝$(CONFIG_SPICE)\n+CONFIG_VGA＝y'
/root/rpmbuild/SOURCES/0004-Enable-disable-devices-for-RHEL-7.patch
sed-i'233s/29/31/'
/root/rpmbuild/SOURCES/0004-Enable-disable-devices-for-RHEL-7.patch
the qemu-kvm source code packet is modified in this step, so as to increase the support for the spice protocol as a whole and to increase the support for the QXL display device dedicated to the spice protocol.
In the embodiment of the application, after the source code packet of qemu-kvm is adjusted, the adjusted qemu-kvm source code packet can be constructed to generate a final executable rpm binary packet file, and the final executable rpm binary packet file is stored in a root/rpmbiold/RPMS/aach 64/directory.
Specific instructions may include:
rpmbuild-bb/root/rpmbuild/SPECS/qemu-kvm.spec
further, the built qemu-kvm rpm package can be upgraded for installation.
Specific instructions may include:
rpm-Uvh
/root/rpmbuild/RPMS/aarch64/qemu-kvm-ev-2.12.0-53.el7_6.7.1.aarch64.rpm
rpm-Uvh
/root/rpmbuild/RPMS/aarch64/qemu-img-ev-2.12.0-53.el7_6.7.1.aarch64.rpm
rpm-Uvh
/root/rpmbuild/RPMS/aarch64/qemu-kvm-common-ev-2.12.0-53.el7_6.7.1.aarch64.rpm
rpm-Uvh
/root/rpmbuild/RPMS/aarch64/qemu-kvm-tools-ev-2.12.0-53.el7_6.7.1.aarch64.rpm
in the embodiment of the application, by using the method for supporting spice through the spread virtualization, for the aarch64 architecture of the spread processor, the specification files, the patch files and the like in the related software of the virtualization system in the server based on the spread processor are adaptively adjusted, so that the aarch64 architecture of the spread processor is supported, and therefore the virtualization system in the server based on the spread processor can support the application of spice protocol, the virtualized display is realized, convenience is provided for the operation of a user, and the user experience is improved.
In addition, after the relevant software is adjusted, constructed and installed to support the spice protocol, the server can be tested to determine that the software can support the spice protocol.
Specifically, firstly, an X Server program may be installed on another machine except the local machine, and then the ssh telnet tool is installed, and the X11 port forwarding is opened. And then, the machine can be remotely logged in, and the ISO file used for installing the virtual machine can be downloaded. When the virt-manager runs on the machine, the management interface of the virt-manager is displayed locally on the Windows machine. And (4) newly building a virtual machine according to the guidance of the graphical interface, selecting Spice when adding display equipment, and appointing to monitor all ports, and then adding a QXL display card. Through the steps, the virtual machine can be successfully operated, and the fact that the system of the virtual machine supports the Spice protocol is shown.
Based on the same inventive concept, the method for supporting a spice protocol by spread virtualization provided by the embodiment of the present application further provides a corresponding device for supporting a spice protocol by spread virtualization, as shown in fig. 2.
Fig. 2 is a schematic structural diagram of an apparatus for supporting a spice protocol in the spread virtualization according to the embodiment of the present application, which specifically includes:
a first determining module 201, configured to determine, according to a modification of a canonical file in a spice-server source code packet in the server based on the maser, that the canonical file is adapted to a framework of the maser, and construct a spice-server binary packet;
the second determining module 202 determines that the qemu-kvm source code package supports the spice protocol according to the modification of the canonical file and the patch file in the qemu-kvm source code package in the server based on the spread processor, and constructs a qemu-kvm binary package.
The above description is only an example of the present application and is not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.
Claims (9)
1. A method for supporting spice protocol by Roc virtualization, wherein a server based on a Roc processor is built in advance, the method comprises the following steps:
determining that the canonical file is adapted to the architecture of the spread-server processor according to the modification of the canonical file in the spice-server source code packet in the server based on the spread processor, and constructing a spice-server binary packet;
and determining that the qemu-kvm source code package supports the spice protocol according to the modification of the specification file and the patch file in the qemu-kvm source code package in the server based on the spread-spectrum processor, and constructing a qemu-kvm binary package.
2. The method of claim 1, wherein the operating system of the server is a CentOS 7 operating system.
3. The method of claim 1, wherein the modifying of the canonical file in the spice-server source package in the spread processor based server comprises:
enabling the spice-server source code packet in the server based on the Kunpeng processor to comprise a construction dependency packet, wherein the construction dependency packet at least comprises a spice-protocol.
4. The method of claim 2, wherein the modifying of the canonical file in the spice-server source package in the spread processor based server comprises:
modifying the spice. The modification includes adding aarch64 representing the architecture of the spread processor in a framework supported by the spice.
5. The method of claim 1, wherein the modifying of the canonical files and patch files in the qemu-kvm source code package in the spread-based processor server comprises:
enabling the qemu-kvm software in the server based on the Kunpeng processor to include the construction dependency package.
6. The method of claim 2, wherein the modifying of the canonical files and patch files in the qemu-kvm source code package in the spread-based processor server comprises:
determining that the qemu-kvm source code packet supports the spice protocol based on the modification of the information indicating whether the spice protocol is supported or not in the qemu-kvm.
Determine that the qemu-kvm source code package negates exclusion of aarch64 based on deletion of aarch64 typeface at a specified location in a qemu-kvm.
And adding configuration parameters for the qemu-kvm source code by the patch file based on the modification of the patch file in the qemu-kvm source code package.
7. The method of claim 1, wherein ARM architecture virtual machine firmware is installed in the virtualization system.
8. The method according to claim 1, wherein the spread-processor-based server comprises a virtual machine, the virtual machine is built based on virt-manager software, and the virtual machine is used for testing whether the server supports the spice protocol.
9. A device for enabling a spice protocol to be virtualized in a roc, wherein the device is pre-populated with a server based on a roc processor, the device comprising:
the first determining module is used for determining that the canonical file is adapted to the architecture of the spread-penning processor according to the modification of the canonical file in the spice-server source code packet in the server based on the spread-penning processor and constructing a spice-server binary packet;
and the second determination module is used for determining that the qemu-kvm source code package supports the spice protocol and constructing a qemu-kvm binary package according to the modification of the canonical file and the patch file in the qemu-kvm source code package in the server based on the spread-spectrum processor.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911368218.1A CN111181953B (en) | 2019-12-26 | 2019-12-26 | Method and device for supporting spice protocol through Roc virtualization |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911368218.1A CN111181953B (en) | 2019-12-26 | 2019-12-26 | Method and device for supporting spice protocol through Roc virtualization |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111181953A true CN111181953A (en) | 2020-05-19 |
| CN111181953B CN111181953B (en) | 2022-03-11 |
Family
ID=70650314
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911368218.1A Active CN111181953B (en) | 2019-12-26 | 2019-12-26 | Method and device for supporting spice protocol through Roc virtualization |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111181953B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113891080A (en) * | 2021-12-06 | 2022-01-04 | 麒麟软件有限公司 | Optimization method for image processing in SPICE cloud desktop |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103685441A (en) * | 2013-07-02 | 2014-03-26 | 重庆绿色智能技术研究院 | Remote desktop control system based on Loongson terminal |
| CN106598698A (en) * | 2016-11-25 | 2017-04-26 | 山东乾云启创信息科技股份有限公司 | Method and system for starting virtual acceleration machines in batch based on migration mode |
| CN106936636A (en) * | 2017-03-15 | 2017-07-07 | 无锡华云数据技术服务有限公司 | A kind of implementation method of the cloud computing test platform of rapid deployment containerization |
| US9720674B1 (en) * | 2008-05-05 | 2017-08-01 | Open Invention Network, Llc | Automating application of software patches to a server having a virtualization layer |
| CN107608760A (en) * | 2017-09-14 | 2018-01-19 | 郑州云海信息技术有限公司 | A kind of kvm virtual machine deployment methods, system and computer-readable recording medium |
| CN107704312A (en) * | 2017-10-18 | 2018-02-16 | 顺丰科技有限公司 | A kind of qemu kvm virtual machines is performed any order method and storage medium |
-
2019
- 2019-12-26 CN CN201911368218.1A patent/CN111181953B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9720674B1 (en) * | 2008-05-05 | 2017-08-01 | Open Invention Network, Llc | Automating application of software patches to a server having a virtualization layer |
| CN103685441A (en) * | 2013-07-02 | 2014-03-26 | 重庆绿色智能技术研究院 | Remote desktop control system based on Loongson terminal |
| CN106598698A (en) * | 2016-11-25 | 2017-04-26 | 山东乾云启创信息科技股份有限公司 | Method and system for starting virtual acceleration machines in batch based on migration mode |
| CN106936636A (en) * | 2017-03-15 | 2017-07-07 | 无锡华云数据技术服务有限公司 | A kind of implementation method of the cloud computing test platform of rapid deployment containerization |
| CN107608760A (en) * | 2017-09-14 | 2018-01-19 | 郑州云海信息技术有限公司 | A kind of kvm virtual machine deployment methods, system and computer-readable recording medium |
| CN107704312A (en) * | 2017-10-18 | 2018-02-16 | 顺丰科技有限公司 | A kind of qemu kvm virtual machines is performed any order method and storage medium |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113891080A (en) * | 2021-12-06 | 2022-01-04 | 麒麟软件有限公司 | Optimization method for image processing in SPICE cloud desktop |
| CN113891080B (en) * | 2021-12-06 | 2022-02-18 | 麒麟软件有限公司 | Optimization method for image processing in SPICE cloud desktop |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111181953B (en) | 2022-03-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101989212B (en) | Method and device for providing virtual machine management program for starting blade server | |
| US9798881B2 (en) | Dynamic feature enhancement in client server applications and high volume server deployment with dynamic app store integration | |
| EP2973147B1 (en) | Policy-based secure web boot | |
| US7886292B2 (en) | Methodology of individualized software deployment for hardware-independent personal computer mass development | |
| EP4100829A1 (en) | Firmware update patch | |
| US9184991B2 (en) | Method and apparatus for developing service processor solutions | |
| US20150067399A1 (en) | Analysis, recovery and repair of devices attached to remote computing systems | |
| US20150039875A1 (en) | Deployment of Software Images with Distinct Configuration Logic | |
| US20200356358A1 (en) | Systems and methods for incrementally and dynamically updating firmware | |
| US9448807B2 (en) | Automatic creation, deployment, and upgrade of disk images | |
| US10353727B2 (en) | Extending trusted hypervisor functions with existing device drivers | |
| CN110457073A (en) | A kind of credible starting method of the Pre-boot Execution Environment PXE of Shen prestige server | |
| WO2016062146A1 (en) | Serial number information update method, device and terminal | |
| US20200042303A1 (en) | Systems and methods to stage external device firmware for an external device in an information handling system | |
| EP2805233B1 (en) | Installation engine and package format for parallelizable, reliable installations | |
| US20190205109A1 (en) | Computer system, baseboard management controller, and os installation method | |
| CN111181953B (en) | Method and device for supporting spice protocol through Roc virtualization | |
| US11137995B2 (en) | Updating firmware of a microcontroller | |
| CN112631915B (en) | Method, system, device and medium for PCIE device software simulation | |
| US20140173589A1 (en) | Software installer with built-in hypervisor | |
| CN116112412A (en) | Virtual network card binding redundancy function test method, system, device and medium | |
| KR102320313B1 (en) | Utilization Method of Integrated BSP for Server Mainboard Control | |
| KR102414260B1 (en) | Method and apparatus for automatically installing operating system in an environment of network | |
| US20160246637A1 (en) | Determining Trustworthiness of a Virtual Machine Operating System Prior To Boot UP | |
| EP3161652B1 (en) | Full virtual machine functionality |
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 | ||
| PE01 | Entry into force of the registration of the contract for pledge of patent right |
Denomination of invention: A Method and Device for Supporting Spice Protocol in Kunpeng Virtualization Effective date of registration: 20230629 Granted publication date: 20220311 Pledgee: Jinan Rural Commercial Bank Co.,Ltd. Runfeng sub branch Pledgor: SHANDONG QIANYUN QICHUANG INFORMATION TECHNOLOGY Co.,Ltd. Registration number: Y2023980046395 |
|
| PE01 | Entry into force of the registration of the contract for pledge of patent right | ||
| PC01 | Cancellation of the registration of the contract for pledge of patent right |
Granted publication date: 20220311 Pledgee: Jinan Rural Commercial Bank Co.,Ltd. Runfeng sub branch Pledgor: SHANDONG QIANYUN QICHUANG INFORMATION TECHNOLOGY Co.,Ltd. Registration number: Y2023980046395 |
|
| PC01 | Cancellation of the registration of the contract for pledge of patent right | ||
| PE01 | Entry into force of the registration of the contract for pledge of patent right |
Denomination of invention: A method and device for Kunpeng virtualization supporting spice protocol Granted publication date: 20220311 Pledgee: Jinan Rural Commercial Bank Co.,Ltd. Runfeng sub branch Pledgor: SHANDONG QIANYUN QICHUANG INFORMATION TECHNOLOGY Co.,Ltd. Registration number: Y2024980025471 |
|
| PE01 | Entry into force of the registration of the contract for pledge of patent right |