Name | Modified | Size | Downloads / Week |
---|---|---|---|
Parent folder | |||
Appliances | 2017-03-02 | ||
Ubuntu 18.04.4 LTS Server x64.ova | 2020-06-24 | 740.0 MB | |
README.md | 2020-06-24 | 1.7 kB | |
Ubuntu 20.04 LTS Server x64.ova | 2020-06-24 | 814.6 MB | |
Ubuntu 19.10 Server x64.ova | 2020-06-23 | 791.1 MB | |
Ubuntu 16.04.6 LTS Server x64.ova | 2020-05-27 | 639.1 MB | |
Ubuntu 12.04.5 Server x64.ova | 2016-11-09 | 508.0 MB | |
Ubuntu 09.10 Server x64.ova | 2016-11-08 | 276.5 MB | |
Ubuntu 14.04 LTS Server x64.ova | 2016-11-02 | 666.6 MB | |
Ubuntu 14.04.4 LTS Server x64.ova | 2016-06-24 | 670.8 MB | |
Ubuntu 10.10 Server i386.ova | 2016-06-24 | 263.1 MB | |
Totals: 11 Items | 5.4 GB | 19 |
Ubuntu Releases
This section contains Ubuntu based Operating Systems and Appliances.
CPU Sockets
I have allocated 1 core to each of the VMs
RAM
The RAM allocation for the VMs is 512MB, you may increase as needed
Hard Disks
The hard disks will generally be SCSI disks, and use LVM. If this is not the case, please file a bug and I will correct it if the installer allows it.
Machine ID
In Ubuntu 18+ releases I have symlinked /var/lib/dbus/machine-id
to /etc/machine-id
and truncated the /etc/machine-id
file. On the first boot, /etc/machine-id
will be regenerated and should cause the /etc/machine-id
to be unique for each VM. This change should fix issues where all the VMs have the same IP because in Ubuntu 17+ releases will transmit the RFC4361-compliant Client ID to the DHCP server for IP leases.
Note: In Ubuntu 16.04 and 17.10 /etc/machine-id
is not automatically recreated if removed. Once you remove /etc/machine-id
, you should manually recreate it using systemd-machine-id-setup
and reboot
.
Networking
netplan
Modern Ubuntu releases (Ubuntu 17+) will use netplan instead of ifupdown.
As noted in the Machine ID section, in the netplan enabled images (Ubuntu 18+) I have symlinked /var/lib/dbus/machine-id
to /etc/machine-id
this should cause the /etc/machine-id
to be different for each VM, and allow VMs to have their NICs swapped out without affecting DHCP leases.
Alternatively, you can also add the line dhcp-identifier: mac
to the file /etc/netplan/01-netcfg.yaml
to use the device's MAC address as the unique identifier rather than the default RFC4361-compliant Client ID, however, this will not have any additional benefit in practice.