On installation I while installing ports the device will run out of swap
space. With the default 2G it happens 1 in every 4-6 times. I change it
to 3G and I've had it happen once in the last 25 installations (however
I had added src to the installation it failed on with 3G). I have had the
same error occur with RC2 and RC3
About my environment:
FreeBSD virtual device on Ubuntu/KVM
2 disks, 30 gig each.
Each iscsi disk is on a different virtual instance of FreeBSD running
as temporary fix change default swap space to 3G or higher. Note if you
are installing with src (which I often do) you may want to set it to 4G
How-To-Repeat: freebsd cd rebuilt as following (I'm building on the ubuntu device but
it shouldn't matter where it's built):
mount -o loop FreeBSD-10.0-RC3-amd64-disc1.iso /mnt
cp -Rfp /mnt/* /tmp/new-freebsd/
sed -i '/^ttyu0/s/off/on/;/^ttyu0/s/dialup/vt100/' /tmp/new-freebsd/etc/ttys
echo "console=\"comconsole\"" >> /tmp/new-freebsd/boot/loader.conf
echo "virtio_load=\"YES\"" >> /tmp/new-freebsd/boot/loader.conf
echo "virtio_pci_load=\"YES\"" >> /tmp/new-freebsd/boot/loader.conf
echo "beastie_disable=\"YES\"" >> /tmp/new-freebsd/boot/loader.conf
echo "/dev/cd0 / cd9660 ro 0 0" > /tmp/new-freebsd/etc/fstab
mkisofs -v -b boot/cdboot -no-emul-boot -r -J -V "FreeBSD 9.2" -o /var/lib/libvirt/iso/FreeBSD-10.0-RC3-new.iso /tmp/new-freebsd/
now start an install with the command:
virt-install -n mail0 -r 2048 --vcpus=2 --os-variant=freebsd8 --accelerate -v --disk path=/dev/mapper/mail0-f0,bus=virtio,size=30 --disk path=/dev/mapper/mail0-f1,bus=virtio,size=30 -w bridge:br1,model=virtio -c /var/lib/libvirt/iso/FreeBSD-10-rc3-new.iso --connect=qemu:///system
*Note the two disk names in /dev/mapper. These are iscsi disks renamed with multipath
During the installation use the following options:
Continue with default keymap
pool type=mirror (choose both disks)
pool name (choose a name)
Part of the way through archive extract of ports (the final extract)
you 'might' receive an "out of swap space" error
>>> Install Proceed with Installation x x
x x T Pool Type/Disks: mirror: 2 disks x x
x x - Rescan Devices * x x
x x - Disk Info * x x
x x N Pool Name mail1 x x
x x 4 Force 4K Sectors? YES x x
x x E Encrypt Disks? NO x x
x x P Partition Scheme GPT x x
x x S Swap Size 2g
When installing from a snapshot - I have a similar problem.
Same here, trying to install 10.1-RELEASE on an old PC (1GB RAM) with ZFS root.
Does anyone know a workaround ?
I am able to replicate this on 10.2-RELEASE-amd64: Default installation options, using single-desk striped ZFS-on-Root. Tested with Parallels, VM configurations of <= 1GB.
Workaround seems to be using a bare (base and kernel only) install, and adding Ports and other packages after.
For bugs matching the following conditions:
- Status == In Progress
- Assignee == "bugs@FreeBSD.org"
- Last Modified Year <= 2017
- Set Status to "Open"