[2024-feb-29] Sad news: Eric Layton aka Nocturnal Slacker aka vtel57 passed away on Feb 26th, shortly after hospitalization. He was one of our Wiki's most prominent admins. He will be missed.

Welcome to the Slackware Documentation Project

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
howtos:slackware_admin:slackware-proxmox-ve [2014/03/15 11:00 (UTC)] – created. alienbobhowtos:slackware_admin:slackware-proxmox-ve [2020/01/13 19:42 (UTC)] (current) – small correction andrixnet
Line 1: Line 1:
-====== Install Slackware on a VPS based on Proxmox VE ======+====== Install Slackware on a VPS based on Proxmox VE or SolusVM ======
  
-Recently I've been faced with the challenge to install Slackware as a VPS at a hosting provider that had [[http://www.proxmox.com/proxmox-ve|Proxmox VE]] as virtualization platform. +I've been faced with the challenge to install Slackware as a VPS at a hosting provider that had [[http://www.proxmox.com/proxmox-ve|Proxmox VE]] as virtualization platform. 
  
 Proxmox VE is a complete open source virtualization management solution for servers. It is based on [[http://www.linux-kvm.org/page/Main_Page|KVM virtualization]] and container-based virtualization and manages virtual machines, storage, virtualized networks, and HA Clustering. Further information is contained in the [[https://pve.proxmox.com/wiki/Main_Page|Proxmox Wiki]]. Proxmox VE is a complete open source virtualization management solution for servers. It is based on [[http://www.linux-kvm.org/page/Main_Page|KVM virtualization]] and container-based virtualization and manages virtual machines, storage, virtualized networks, and HA Clustering. Further information is contained in the [[https://pve.proxmox.com/wiki/Main_Page|Proxmox Wiki]].
 +
 +Recently I've had to migrate to a [[http://solusvm.com/|SolusVM]] based infrastructure, using KVM virtualization. This does not apply to Xen virtualization by SolusVM which officially supports Slackware. Assuming your is configured with virtio type disk, all the instructions below apply the same.
 +
 +SolusVM is a commercial virtualization infrastructure able to provide KVM virtualization, OpenVZ containers and Xen. Further information is contained in the [[https://documentation.solusvm.com/|SolusVM Documentation]].
 +
  
  
Line 9: Line 14:
  
 === Prerequisites === === Prerequisites ===
 +
 +This guide is valid for **Slackware-14.1 only**. 
 +Slackware-14.2 already has the virtio support in the default kernel that is deployed at installation. //(verified at least with >4.4.190 kernel build)//
 +
 +__**If you build your own kernel make sure to include virtio* drivers built-in, not modules.**__
  
 You must ask your hosting provider to add the Slackware install DVD ISO image to the virtual CD/DVD device of the virtual machine. You must ask your hosting provider to add the Slackware install DVD ISO image to the virtual CD/DVD device of the virtual machine.
Line 16: Line 26:
 === Preparing a custom initrd === === 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.+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. It is very simple, with ''mkinitrd'' tool.
 <code> <code>
-# mkinitrd -m virtio_pci:virtio_mmio:virtio_balloon:virtio_blk -k 3.10.17 -f ext3 -r /dev/vda1+# mkinitrd -m virtio_pci:virtio_mmio:virtio_balloon:virtio_blk -k 3.10.17 -f ext4 -r /dev/vda1
 </code> </code>
-This creates an initial ramdisk (initrd.gz) with the virtio* modules, for booting a root partition /dev/vda1 formatted using etx3 filesystem.\\ //Adjust according to your needs and use the same partition name and fs when you install your VM.//+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'' 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.\\ Remember, the Slackware installation disk has a minimum set of utilities.+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 === === Installation ===
Line 88: Line 102:
 **Now you can reboot your system**. **Now you can reboot your system**.
  
 +**Important**: you must rebuild the initrd.gz file every time you upgrade or change the kernel.
  
 ====== Sources ====== ====== Sources ======
Line 96: Line 111:
 <!-- Please do not modify anything below, except adding new tags.--> <!-- Please do not modify anything below, except adding new tags.-->
 <!-- You must remove the tag-word "template" below before saving your new page --> <!-- You must remove the tag-word "template" below before saving your new page -->
-{{tag>howtos virtualization kvm}}+{{tag>howtos virtualization kvm proxmox solus solusvm}}
 howtos:slackware_admin:slackware-proxmox-ve ()