Hacker News new | ask | show | jobs
by Mallory_Ringess 24 days ago
FYI, those running a Proxmox system can import the two drive images from the lite distribution and run the thing as a vm without any of the other included 'baggage'. Here's how:

0: create an empty VM called osmuseum with 4 cores, 8192 MB of memory, no drives, OS type Linux 6.x - 2.6 kernel using whatever vmid fits your schedule

1: unzip the relevant part of the distribution:

   unzip virtual_os_museum-2026.05.19-lite.zip virtual_os_museum-2026.05.19-lite/VirtualOSMuseum.utm/*
2: convert the drive images in the Data directory to something understood by qemu-img:

   qemu-img convert Data/host_x86.vdi Data/host_x86.raw
   qemu-img convert Data/guest_images.vdi Data/guest_images.raw
3: import these images to whatever Proxmox storage you want to use for this VM. The host_x86 image is 250 MB, guest_images is 5 TB. Both are sparse images so they won't take up more space than actually required. I'm using 700 as vmid and ext-lvm for storage, change these to what fits your installation:

   qm importdisk 700 Data/host_x86.raw ext-lvm
   qm importdisk 700 Data/guest_images.raw ext-lvm
4: attach these images to scsi0 (host_x86) and scsi1 (guest_images) in the vm Hardware settings page

5: set the scsi0 drive as bootable in the vm Options settings page and move it up in the boot order (e.g. ide2, scsi0, net0)

6: boot the vm and change the network configuration in /etc/network/interfaces to fit your needs. In my case I changes the address for br0 to a free address on a local network segment, corrected the broadcast, network mask, gateway and dns-nameservers parameters to fit my network and restarted the networking service (service networking restart)

7: Things should now work, you may want to reboot the vm but it should not be necessary.