Skip to content

hwinther/proxmox

BranchesTags

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

50 Commits
.github
.github
 
 
.idea
.idea
 
 
.vscode
.vscode
 
 
admin-skel
admin-skel
 
 
compose
compose
 
 
images
images
 
 
scripts
scripts
 
 
src
src
 
 
templates
templates
 
 
tools
tools
 
 
vm-images
vm-images
 
 
.flake8
.flake8
 
 
.gitignore
.gitignore
 
 
.gitmodules
.gitmodules
 
 
Dockerfile
Dockerfile
 
 
LICENSE
LICENSE
 
 
README.md
README.md
 
 
TODO.md
TODO.md
 
 
git-commands.md
git-commands.md
 
 
llm.md
llm.md
 
 
package-lock.json
package-lock.json
 
 
package.json
package.json
 
 
pyproject.toml
pyproject.toml
 
 
serial.md
serial.md
 
 
snippets.md
snippets.md
 
 
tsconfig.json
tsconfig.json
 
 
vscode-extensions.md
vscode-extensions.md
 
 

Repository files navigation

Proxmox Virtual Environment - IAC and notes

Building image files for mounting to VM

Floppy drives

Combine multiple floppy images to one:

mkdir /tmp/win31 # and copy all images there
mkdir /mnt/tmpflp

mount -o loop /tmp/win31/Disk01.img /mnt/tmpflp/ && cp -i /mnt/tmpflp/* . && umount /mnt/tmpflp
mount -o loop /tmp/win31/Disk02.img /mnt/tmpflp/ && cp -i /mnt/tmpflp/* . && umount /mnt/tmpflp
# repeat for all floppies

Create new floppy image:

# Normal floppy image size, 1.4mb
mkfs.msdos -C /tmp/combined.img 1440

# Extended floppy size, adjust to fit the data in combination folder, with floppy name HCW
mkfs.msdos -C /tmp/combined.img 5760 -n TEST
mount -o loop /tmp/combined.img /mnt/tmpflp
copy file1 file2 file3 /mnt/tmpflp/
umount /mnt/tmpflp

QEMU monitor commands:

# mount new image as floppy0 (A:)
change floppy0 /tmp/Disk1.img

ISO / CDROM images

# Create default ISO layout and character set, typically smallest common denominator (8 char length, caps insensitive?)
# similar to FAT16 but supports a little more I think (TODO: fact checks)
mkisofs -o win31-inst.iso /root/win31-iso/

mkisofs -iso-level 4 -o win95_games.iso win95_games

mkisofs -l -o dos_drivers.iso dosdrivers/
mkisofs -l -o dos_games.iso dos_games/

LXC creation

export ROOTPASS=testpassword
echo "ssh-ed25519 AAAA... ed25519-replace-me" > container_authorized_keys

pct create 300 /var/lib/vz/template/cache/alpine-3.17-default_20221129_amd64.tar.xz --hostname testct --memory 128 --swap 128 --net0 name=eth0,bridge=vmbr0,firewall=1,ip=dhcp,type=veth --storage local --rootfs local:0.1 --unprivileged 1 --pool Testing --ssh-public-keys container_authorized_keys --ostype alpine --password="$ROOTPASS" --cmode shell --cores 2 --start 1 --mp0 volume=local:0.01,mp=/etc/testconfig,backup=1,ro=0,shared=0

# pct status 300
status: running

# echo "uname -a" | pct console 300
Linux testct 6.1.15-1-pve #1 SMP PREEMPT_DYNAMIC PVE 6.1.15-1 (2023-03-08T08:53Z) x86_64 Linux

# pct mount 300
mounted CT 300 in '/var/lib/lxc/300/rootfs'

# push file to ct
echo test > /tmp/file.cfg
pct push 300 /tmp/file.cfg /etc/testconfig/file.cfg

# pull file from ct
pct pull 300 /etc/testconfig/file.cfg /tmp/file.cfg

QEMU old OS guide

To emulate an old operating system you usually have to choose an older cpu such as pentium2 with single socket and core, the i440fx machine + SeaBIOS, default controller with IDE drive(s) and relatively small disks and RAM - typically max 32GB/512MB. The network card can be Realtek RTL8139 in most cases, but some systems may require ne2k_pci - see an example below.

Links

Old linux XF86Config

Working steps for local or vnc based desktop on RedHat 5.2 as of 28.11.2023

If you select the CIRRUS chipset during install it should autodetect most of the options [1], if not choose "Cirrus Logic GD544x". You can also add one or more serial ports as either a backup console or network interface.

PVE VM configuration

vga: cirrus,memory=8
net0: ne2k_pci=00:11:22:33:44:55,bridge=vmbr0
# To (re)configure X in a similar fashion to the original installer (easier) then run
Xconfigurator

# The more old fashioned graphical configuration provided by XF86 can be launched with
XF86Setup

If the X server starts but the display freezes then try adding these options to the Device section [1]

Section "Device"
   ...
   Option "no_bitblt"
   Option "noaccel"
   Option "sw_cursor"

Linux 2.2 and framebuffer graphical mode

Linux kernel 2.2 supports SMP (multiprocessor), the "linux up" choice in LILO is the single processor kernel, by default the SMP version will be used by lilo. The SMP kernel might have issues related to APIC, to resolve this you should try one of the following

  1. Choose linux-up in the lilo prompt, and change the default (default=linux) in /etc/lilo.conf after booting.
  2. Disable APIC by typing linux noapic in the lilo prompt, and adding append="noapic" to the linux entry in /etc/lilo.conf after booting.

Newer 2.2.x kernels or linux distros using them might automatically disable APIC and APM, so it is not always required to configure this bp If you updated the /etc/lilo.conf file in the previous step, remember to run lilo afterward.

Color 640x480 800x600 1024x768 1280x1024 1600x1200
8 / 256 0x301 0x303 0x305 0x307 0x31C
15 / 32k 0x310 0x313 0x316 0x319 0x31D
16 / 64k 0x311 0x314 0x317 0x31A 0x31E
24 / 16M 0x312 0x315 0x318 0x31B 0x31F

Older lilo versions can't convert the hexadecimal representation and must be configured with decimal values, so here is the same table with decimal values:

Color 640x480 800x600 1024x768 1280x1024 1600x1200
8 / 256 769 771 773 775 796
15 / 32k 784 787 790 793 797
16 / 64k 785 788 791 794 798
24 / 16M 786 789 792 795 799

256 = 8 bits, 32k = 15 bits, 65k = 16 bits, 16M = 24 bits, 32bits is not typically used, but it would mask out the extra 8 bits and fit the bus width better. 15 bit is not supported by XF86_FBDev

Add vga=775 to the root section to enable framebuffer and set the console resolution to 1280x1024. Run lilo afterward to update the config.

On most systems the /usr/bin/X11R6/bin/X will be symlinked to the appropriate XF86_Server binary, but on RedHat this is in /etc/X11/X. You will want to update this if SVGA or some other driver has already been selected as the default driver, otherwise you'll need to configure additional parameters and not just use startx to launch X11. cd /etc/X11 && rm -f X && ln -s ../../usr/X11R6/bin/XF86_FBDev X

You can use the template in templates/x11/XF86Config-3-FBDev to get started with XF86-FBDev, it will use the resolution set at boot, but you have to specify the bit depth if it doesn't match the default (8), e.g. startx -- -bpp 16

If you for whatever reason spend a lot of time to compile kernel 2.2.x into a 2.0.x system, you will need to reuse the kernel include folder in the XF86 include path, it should suffice to symlink e.g. /usr/src/kernel-2.2.26-custom/include/{linux,video} to /usr/src/redhat/BUILD/XFree86-3.3.3.1/xc/exports/include/. You will also need to create the devices manually as that is normally done by the RPM or similar installer:

mknod /dev/fb0 c 29 0
mknod /dev/fb1 c 29 32
mknod /dev/fb2 c 29 64
...
mknod /dev/fb7 c 29 224

The amount of devices that are currently active can be found via cat /proc/fb

And create the xserver pam.d file if it does not exist:

cat > /etc/pam.d/xserver
#%PAM-1.0
auth       sufficient   /lib/security/pam_rootok.so
auth       required     /lib/security/pam_console.so
account    required     /lib/security/pam_permit.so

If you want to add a serial console in lilo.conf then it should look something like this: append="console=ttyS1,19200n8 console=tty1", you should also add the following line to /etc/inittab: S0:23:respawn:/sbin/mingetty -h -L ttyS0 19200 vt100

TODO: test VMware SVGA device in RedHat 7.0 TODO: try out an alternative, remote X to windows: http://www.straightrunning.com/XmingNotes/ and configuration details from https://unix.stackexchange.com/questions/407022/trying-to-run-an-old-version-of-redhat

Linux 2.0 and 2.2 network driver

To autoload the NIC driver at boot, add an alias to /etc/modules.conf such as alias eth0 pcnet32 On linux kernel 2.0 ne2k-pci seems to work, but it does not seem to be very stable as after prolonged use the interface stops responding. On linux kernel 2.2 pcnet32 seems to be the most stable, however it is limited to 10/100mbps.

RedHat source RPM

RedHat source RPMs can be useful to backport or reconfigure known working and patched versions of older software. This can be utilized even if the operating system does not natively support RPM, just prepare the build on a RedHat system first and then transfer the source folder over to the target system. There have been changes to how this process works over the years, so I had to do some digging to find the old (pre centos and RHEL) examples. Before rpmbuild [1], you install the src.rpm and then prepare the build to extract and patch the source files:

Install the source code in the SOURCES directory used by RPM (/usr/src/redhat/SOURCES) with this command:
  rpm -ivv realport-version-revision.src.rpm
This command also copies the specification file (/usr/src/redhat/SPECS/realport-version.spec) to the SPECS directory.
Use the RPM tools to open the source archive:
  cd /usr/src/redhat/SPECS
  rpm -bp realport-version.spec
The -bp option specifies that only the preparation section (%prep) of the specification file should be executed. This might result in the source files being uncompressed, removed from the archive, and placed in the following directory:
  /usr/src/redhat/BUILD/realport-version

excerpt from Custom Installation Procedure[2]

Links

Old BSD

TODO

Links

MS DOS 6, Windows 3.x

TODO: list relevant contents of DOS iso

Memory tips

Use checkit or scandma? to check memory allocation/usage Use mem /a/c to see the overview

Links

Windows 95/98

Install chipset drivers first to have other devices detected (TODO) Enable DMA for all IDE devices (hd and cdrom) in their properties in device manager

TODO: List relevant contents of DOS iso

Before installing, either use patch9x (-drive file=/var/lib/vz/template/iso/patcher9x-0.8.50-boot.img,if=floppy,index=0 -boot a) on the installation media or reduce host cpu frequency via cpupower frequency-set -u 1G.

To install Windows 98 SE add the boot floppy image and the cdrom iso file:

args: -drive file=/var/lib/vz/template/iso/Windows_98_Second_Edition_Boot.img,if=floppy,index=0 -boot a
ide1: local:iso/EN_WIN98SE_115_OEM_WPLUS.ISO,media=cdrom,size=632374K

scsi0: local-lvm:vm-900-disk-0,size=4G
scsihw: lsi

And then run fdisk and format to create your new system volume:

TODO: script the whole thing in two bat files, stage0 and stage1 to automate the process

fdisk

(or one liner)

fdisk /fprmt
fdisk 1 /pri:4095

Then copy over the win98 files to the newly formatted volume and add the win9x display++ drivers from dosdrivers.iso to the same folder so that they can be detected and installed without selecting a path later. There is also a script that will make the installation mostly unattended in this folder. Launch setup with the /nm (ignore hardware demand) and /pj (force use of ACPI/PnP)

d:\win98\format C:
set PATH=%PATH%;d:\tools\oldmsdos
xcopy32 /E d:\win98\ c:\win98\

c:
cd win98
xcopy32 e:\win9x\vmdisp9x\*.*
setup /nm /pj

Links

OS/2 Warp 4

Warp 4.0 installation stopped at the final installation floppy due to an unknown issue. Warp 4.52 installs from bootable iso with IDE disk and cdrom, and spice with attached audio drivers (sb16, adlib and pc speaker). With cirrus-vga over VNC (and audio over VNC once that is available in free clients), higher resolutions should be possible.

Links

Solaris 2.x on SPARC

qemu-system-sparc is 32 bit and supports the SS-5 machine with typically sub 200mhz cpus and max 512 mb ram qemu-system-sparc64 supports - TODO

OpenBios exists for both platforms and will simplify configuring boot on the command line, here are some configuration examples:

xxx TODO

Alternatively there are BIOS'es that have been dumped from EPROM which can be found in the SPARC BIOS collection [1]:

Image name System name
cpu10.bin x
cpu24.bin x
ipc.bin SPARCstation IPC
lx.bin SPARCstation LX
lx564.bin SPARCstation LX
ross225r.bin x
ss10_v2.25_rom SPARCstation 10
ss20_v2.25_rom SPARCstation 20
ss4.bin SPARCstation 4
ss5-170.bin SPARCstation 5
ss5.bin SPARCstation 5
ss600mp.bin SPARCserver 600MP
voyager.bin SPARCstation Voyager

An example of using SPARCstation 5 BIOS:

# SPARCstation 5 expects the disk to be scsi target 3 and cdrom to be scsi target 6, and have max 256MB ram and a single CPU.
# To properly emulate a SUN cdrom we use a physical block size of 512.
qemu-system-sparc \
 -drive file=disk0.raw,if=none,id=drive-scsi0,format=raw,cache=none,aio=io_uring,detect-zeroes=on \
 -device scsi-hd,scsi-id=3,drive=drive-scsi0,id=scsi0 \
 -drive file=sun-solaris-8-0101-installation-sparc.iso,if=none,id=drive-scsi1,media=cdrom,aio=io_uring \
 -device scsi-cd,scsi-id=6,drive=drive-scsi1,id=scsi1,physical_block_size=512 \
 -machine accel=tcg,type=SS-5 -cpu "TI SuperSparc 60" \
 -m 256 \
 -vga cg3 -g 1024x768x8 -monitor stdio \
 -bios ss5.bin

# If graphical install fails, you can switch the -vga line with the following to install the OS over serial terminal:
# -nographic -vga none -serial mon:stdio \

# Use 'sendkey stop-a' in monitor if it goes into a boot retry loop
# Use probe-scsi to verify the scsi ids or devalias to see device aliases in the nvrom
# Use module-info to see cpu and bus speeds

# Type 'boot cdrom:d' to boot the d partition of the cdrom iso

# If cdrom installation fails, you can try again via boot disk3:b

# Type 'boot sd()' to boot the first partition of the primary disk

Tips

  • Use monitor and sendkey to break if you're stuck trying to boot from network for instance: sendkey stop-a
  • Serial terminal seems to conflict with sendkey stop-a, but if you disconnect the network interface the BIOS might skip network boot and go to the prompt.
  • An 8GB virtual disk can be formatted with the following parameters; type 18, data cylinders 16200, alternative cylinders 2, physical cylinders 16202, heads 16, data sectors 60, rpm 3600, disk type name Qemu8G, everything else default
  • Otherwise use a 2GB, 2.1GB or 3GB vm disk and use the SUN1.3, SUN2.1G or SUN2.9G disk layout, respectively.
  • Solaris 2.4/2.5 (and probably older) need the cdrom to be identified as a scsi-hd in order to boot the installation environment from it. You can change -device scsi-cd to scsi-nd and add readonly=true to the drive parameter.
  • The Solaris 2.5 installer will spend a long time without any output but it should finish eventually.
  • Solaris 2.x should be fine with 3GB, but solaris 8 needs over 3GB so use the 8G template. Solaris 9, 10 and 11 probably need even more if every package is to be installed.
  • TODO: add template raw disk 3G + 8G to repo
  • Solaris 9 can install from a dvd iso, but ss5.bin does not seem to work, use OpenBIOS32 instead

Sun/Oracle installation guides

SPARC 64

# sparc64 support seems to be pretty limited, in order to boot from cdrom you either have to use the "-boot d" argument or type "boot cdrom:f" in the OpenBIOS prompt.

# Create a raw disk image first, then the machine can be started with the following:
ISO=/var/lib/vz/templates/iso/NetBSD-9.3-sparc64.iso
sudo /usr/bin/qemu-system-sparc64 -drive file=hd.raw,if=none,id=drive-ide0-0-1,format=raw,cache=none -device ide-hd,bus=ide.0,unit=0,drive=drive-ide0-0-1,id=ide0-0-1 -serial pty -monitor stdio -boot c -machine sun4u -netdev type=tap,id=net0,ifname=tap0,script=no,downscript=no -device sunhme,mac=BC:24:11:47:EA:AA,netdev=net0,bus=pciB -cdrom $ISO -nographic

# ne2k_pci can be used instead of sunhme, but it will be limited to 10mbps and it might be less stable

# Then open the serial terminal in another window, e.g.:
miniterm -D /dev/pts/8

# Attaching the network interface manually (it should be configured via a script), can be done like this:
ovs-vsctl add-port vmbr0 tap0
ip link tap0 up

Links

Wayback browsing

Links

Dialup ISP emulation

Links

About

No description, website, or topics provided.

Resources

Readme

License

Apache-2.0 license
Activity

Stars

0 stars

Watchers

1 watching

Forks

0 forks
Report repository

Releases

3 tags

Packages

 
 
 

Contributors 2

  •  
  •  

Languages