Welcome to the Slackware Documentation Project

¡Esta es una revisión vieja del documento!


En Proceso de traducción. Victor

Instale Slackware en un VPS basado en Proxmox VE o SolusVM

Me he enfrentado al desafío de instalar Slackware como un VPS en un proveedor de hosting que tenía Proxmox VE como plataforma de virtualización. Proxmox VE es una solución completa de gestión de virtualización de código abierto para servidores. Se basa en KVM virtualization y en la virtualización basada en contenedores y administra máquinas virtuales, almacenamiento, redes virtualizadas y agrupación de alta disponibilidad. Más información está contenida en el Proxmox Wiki.

Recientemente he tenido que migrar a una infraestructura basada en SolusVM, utilizando la virtualización KVM. Esto no se aplica a la virtualización de Xen por SolusVM, que es oficialmente compatible con Slackware. Suponiendo que su equipo esté configurado con un disco de tipo virtio, todas las instrucciones a continuación aplican lo mismo.

SolusVM es una infraestructura de virtualización comercial capaz de proporcionar virtualización KVM, contenedores OpenVZ y Xen. Más información está contenida en SolusVM Documentation.


Requisitos previos

Debe solicitar a su proveedor de alojamiento que agregue la imagen ISO del DVD de instalación de Slackware al dispositivo de CD / DVD virtual de la máquina virtual.

Además, debe tener una máquina local (física o virtual por otros medios) con una copia en ejecución de la misma versión de Slackware que instalará en el Proxmox VE.

Preparing a custom initrd

On your own running Slackware installation (I've done this using Slackware64-14.1) you must prepare an initrd for your virtual server.
Make sure you have the proper kernel version, if your installation was updated you may need to temporarily downgrade the kernel to match the version in the installation disk.
Alternately, you may through in a quick installation in VMware Player, build your initrd there, then deploy it to a FTP server.

It is very simple, with mkinitrd tool.

# mkinitrd -m virtio_pci:virtio_mmio:virtio_balloon:virtio_blk -k 3.10.17 -f ext4 -r /dev/vda1

This creates an initial ramdisk (initrd.gz) with the virtio* modules, for booting a root partition /dev/vda1 formatted using etx4 filesystem.
Adjust according to your needs and use the same partition name and fs when you install your VM.

The resulting ramdisk will be here: /boot/initrd.gz Upload this file to a FTP or HTTP server so that it may be downloadable using wget. That server's IP address must be accessible to the hosted VM.
It must be a direct download link, so don't use a filesharing system like Rapidshare, etc.
Remember, the Slackware installation disk has a minimum set of utilities.
Also note that you may not have the resolver library working, so I recommend using plain FTP server and call it by IP instead of hostname.

Installation

Booting from the ISO image presents no problems.

After booting, as usual, start by partitioning the (virtual) disk. You will discover that instead of the usual sda or hda, you are presented with devices such as:

/dev/vda

Not to worry, it's the same as /dev/sda, but it is the source of several issues that need to be solved later.

Partition your disk, run setup and perform the installation.

Configuration

Upon configuring lilo, choose Advanced.
Simple lilo autoconfiguration defaults to /dev/sda and won't generate the proper lilo.conf.
Using *Advanced* you will manually tell lilo to install itself on dev/vda.
Configure the rest of the parameters as needed.

Installing lilo will fail due to unrecognized block device 0xfc00. Accept the error and proceed with the rest of the configuration process.

DO NOT REBOOT after the configuration process ends.

Exit the setup program and configure your networking.

# ip a add IP_ADDRESS/NETMASK dev eth0
# ip link set eth0 up
# ip ro add default via GATEWAY dev eth0

Go to the /boot directory of the installation and download the initrd.gz file

# cd /mnt/boot
# wget URL_TO_YOUR_SERVER/initrd.gz

Go to the /etc directory of your installation and edit lilo.conf

# cd /mnt/etc
# vi lilo.conf

Right under boot= add the following (without the comments):

disk=/dev/vda              # your disk device
bios=0x80                  # first disk according to BIOS
max-partitions=15          # as usual for SCSI disks, this refers to no. of disks
                           # on a controller, see man lilo.conf

Scroll down to where the bootable partition is configured and add below root = :

initrd = /boot/initrd.gz

Save and run lilo:

lilo -C lilo.conf

You will get some warnings, but it will work.

Now you can reboot your system.

Important: you must rebuild the initrd.gz file every time you upgrade or change the kernel.

Sources

  • Originally written by Andrei B.


En otros idiomas
Traducciones de esta página?:
QR Code
QR Code es:howtos:slackware_admin:slackware-proxmox-ve (generated for current page)