Proxmox Ve server, configured the spice client as ubuntu, the console point the SPICE download the configuration file, but how to open it

1 thought on “Proxmox Ve server, configured the spice client as ubuntu, the console point the SPICE download the configuration file, but how to open it”

1. 

   Rudy

   December 3, 2022 at 5:06 am

   The protocol is the basis for communication with the client.
   The client is a terminal machine to enjoy the service.

   0. Preparatory work before installation:
   It because the source code is installed from the Git server, you need to rotate the GIT tool

   [plain] View Plain Copy Print?
   u003Cspan style = "font-siZe: 18px;"> Sudo Apt-get instant-esocyf git-core n u003C/span>
   of course Also installed:

   [plain] View Plain Copy Print?
   u003Cspan style = "font-siZe: 18px;"> Sudo Apt-get install -Dev Libssl-Dev xlibmesa-glu-dev libasound-dev libpng12-dev -dev rn-dev libogg-dev libxrandr-dev kvm libgcrypt-dev libsdl-dev libnss3-dev libpixman-1-dev libxfixes-dev libjpeg8-dev rnlibsasl2 -Dev Python-Pyparsing u003C/span>

   In the final preparation to create a folder to store the installation package downloaded (if you know the download and installation position, of course, you can create a new folder without creating this folder. )

   CD
   mkdir spice-savercess
   cd spice-sauces

   1. SPICE dependency package:
   n1.1 Libcacard
   this library is what space users to emas and smart card readers.
   sudo make install
   CD ..

   1.2. Installation protocol (SPICE Protocol Headers)
   the first to install is the spice propol he ADERS.
   WGET SPICE-SPACE/DOWNLOAD/Releases/Spice-PROTOCOL-0.8.0.TAR.BZ2
   TAR XJVF Spice-ProTocol-0.8.0.0.bz2 NCD SpROTOCOL-0.88 .0
   mkdir m4
   ./configure
   make
   sudo make install
   cd ..
   1.3. Install CELT
   spice requires a special Version of the Celt Low-Latence Audio Codec (0.5.1.3). SINCE It is in the ubuntu, it must also be compired. nWget doubleds.us.xiph/reg/celt/celt-0.5.1.3.t. GZ
   TAR XVZF CELT-0.5.1.3.TAR.GZ
   CD CELT-0.5.1.1.3/
   ./configure
   make
   sudo make install
   cd ..

   2. SPICE Client
   this gives us spicec, The Spice Client. Its user to connect to spicests.

   Wget Spice-Space/Download/Releases/Spice-0.8.1.TAR.BZ2
   TAR XJVF Spice-0.8.1.bz2
   CD spice-0.8.1 r
   ./configure-ENable-Smartcard
   make
   sudo make install
   cd .. n
   this step is public to perform on a 32-bit host; Client.
   is worth noting that: 32 -bit systems can only install the SPICE client, and the following server cannot be installed!

   3. Install spice server

   now, its time to build the spice server iTSELF. spice has ben rolled into qemu now, so this step amounts to a rencent. fact, we will be pulling the latest QEMU source code for version 0.14. Oddly enough, QEMU 0.14 is available in the Ubuntu , but SPICE support is not included in the build.rn以上的意思是说QEMU已经包含SPICE服务，rnrnFirst, we need to change an variable so that ./configure can find the spice protocol libraries we installed. You will need to set this variable anytime you want to use qemu with SPICE, so its easiest to put it in your .bashrc.
   mix to modify the environment variables so that Configure finds the function library of our installation of the spice protocol.

   eCho "export ld_library_path =/usr/local/lib: $ {ld_library_path}" >>/.bashrc nsourc
   n nnowue with the . Note that if you require a specific softmmu target, you can add a list of them with the --target argument. By default, QEMU only builds with support for 32-bit x86 guests.rn继续安装，（ PS: If QEMU has been installed before, this step can be omitted)

   Wget download.savannah.gnu/releases/qemu/qemu-0.14.0.tar.gz ntar xzvf qemu- 0.14.0.tar.gz
   CD QEMU-0.14.0
   ./configure-ENable-SPICE-ENable-KVM-ENable-IO-Thread-Audio-Drv-List = ALSA, OSS-ENable-SYSTEM
   make
   Sudo Make Install

   now, we need to copy ove bios files that qemu will need sps. Location that qemu extens them to be.
   copy related files to the QEMU directory to allow QEMU to start the virtual machine. (PS: If QEMU has been installed before, this step only needs to be confirmed that there are the following two files under the/usr/share/qemu/directory. If not, then manually copy the past)

   sudo CP PC-BIOS/VGABIOS-QXL.BIN/USR/Share/QEMU/
   SUDO CP PC-BIOS/PXE-E1000.bin/USR/Share/QEMU/
   CD .. N R nNow, qemu with SPICE support is installed in /usr/local/bin, and the ordinary system qemu is installed in/usr/bin. Well make a shortcut command called qemu-spice that you can invoke from the system qemu (which doesnt Have spice support).
   The QEMU containing SPICE services above is installed to USR/LOCAL/BIN (PS: may also be under USR/BIN), and the ordinary QEMU system is installed under/usr/bin. The following is a tool called QEMU-SPICE, which is actually a copy of QEMU.

   cd/usr/local/bin
   sudo MV qemu-spmu-spmu-spmu

   . At this point, the server is installed.

   4. Use spice
   4.1 Use client
   to invoke the spice client, use the command: call the client, use the following commands
   Note: u003Cserver may> is The address of the server, if your computer installed the customer server at the same time, then you can use 127.0.0.1 to test it. u003CPort Number> is the port number formulated by the server

   Spicec -H u003CServer HostName> -P u003CPort Number>

   4.2 Use Server
   INVOKING The Spice Server is Rather Complex than the client, since you have to set the guest. For exmple,
   Calling server is much more troublesome than the client.

   QEMU -SPICE -SPICE PORT = 5930, DISable -TICKETING -Drive File =/Path/to/Image -vga QXL -DEVICE AC97 -USBDEVICE TABLET -M 1024 -Nable -KVM -Net Nic -Net Nic -Net Nic -Net Nic -Net User

   Note: File =/PATH/TO/Image must be replaced with a system mirror file, such as my file =/kvm/vdisk.img
   n. The SPICE server, then use the client command on the client
   Spicec -H u003CServer Hostname> -P u003CPort Number>
   to start the virtual machine system on the SPICE client.

   Reply