summaryrefslogtreecommitdiffstats
path: root/release/tools
Commit message (Collapse)AuthorAgeFilesLines
* MF11 r320731,320749,320759: Add Amazon Elastic Network Adapter drivercperciva2017-07-071-0/+3
| | | | | | | | | and turn it on in EC2 AMI builds Approved by: re (gjb) Relnotes: FreeBSD now supports "next generation" Enhanced Networking in the Amazon EC2 cloud Sponsored by: Amazon.com Inc. (original work)
* MFC r318872:gjb2017-05-281-0/+5
| | | | | | | Enable DHCP and IPv6 autoconfig on non-cloud VM images. PR: 203653 Sponsored by: The FreeBSD Foundation
* MFC r314935 (thompsa):gjb2017-05-261-1/+2
| | | | | | | Change ec2.conf to use the pkg tool from a chroot rather than trying to bootstrap it and fail from the livecd readonly filesystem. Sponsored by: The FreeBSD Foundation
* MFC r307008:np2017-05-241-1/+1
| | | | | | | Add the ability to override the size of the swap partition when building VM images. The default continues to be 1G. Sponsored by: Chelsio Communications
* MFC r317169:gjb2017-04-261-0/+1
| | | | | | | | | | Trim trailing '/release/..' when setting _OBJDIR so arm64/aarch64 boot1.efifat is properly located when creating virtual machine images. Note, the underlying issue has no direct impact against stable/10, as arm64/aarch64 virtual machine images are not created for 10-STABLE. Sponsored by: The FreeBSD Foundation
* MFC r314561:gjb2017-04-071-2/+2
| | | | | | | | Increase the EC2 image size. The recent snapshot builds of EC2 images for 12-CURRENT (and now 11-STABLE) failed due to a full filesystem on the md(4) device during creation. Sponsored by: The FreeBSD Foundation
* MFC 308106:lwhsu2017-03-121-2/+2
| | | | - Use virtualbox-ose-additions-nox11 for vagrant image to reduce size
* MFC r312214: Enable IPv6 on EC2 AMIs.cperciva2017-01-261-3/+8
|
* MFC r302929: Now that potentially buggy versions of Xen are automaticallycperciva2016-07-301-6/+0
| | | | | | | | detected (see r302635, MFCed as r302895), there is no need to force msix interrupt migration off via loader.conf. Reverts: r302184 Approved by: re (gjb)
* Enable indirect segment I/Os by default in the Xen blkfront driver whencperciva2016-06-291-5/+0
| | | | | | | | | | | | running on EC2. Due to improvements in EC2, the performance penalty which was present on some EC2 instances no longer exists, and enabling this feature now consistently yields ~20% higher throughput with equal or lower latency. Reverts: r286063 Approved by: re (gjb) MFC after: 2 weeks Relnotes: Improved disk throughput on EC2
* Turn off MSI-X interrupt migration by default in EC2 instances; this workscperciva2016-06-241-0/+6
| | | | | | | | around a bug in older versions of Xen and unbreaks SR-IOV (aka. "EC2 Enhanced Networking"). Approved by: re (gjb) Thanks to: jhb, Jeremiah Lott
* Bump /tmp from 30m to 50m for ARM release images.manu2016-06-161-1/+1
| | | | | | | | 30m isn't enough for pkg anymore to extract packagesite.txz. 40m is fine for now but let's take a safer way as we don't know when pkg will need more. Reported by: many Approved by: re (gjb), andrew (mentor)
* Switch from console="comconsole" to boot_multicons="YES" in EC2.cperciva2016-06-091-2/+4
| | | | | | | Amazon recently introduced an API for capturing screenshots of an emulated VGA device; this commit makes that (somewhat) useful. MFC after: 3 weeks
* Turn off nfsv4acls for arm/armv6 builds, which has an impactgjb2016-06-011-1/+0
| | | | | | | | | | on performance, especially with SD cards on certain SoCs. Requested by: trasz Discussed with: ian, kientzle MFC after: 3 days Sponsored by: The FreeBSD Foundation
* Fix tmpfs(5) '/tmp' mount point.gjb2015-11-251-1/+1
| | | | | | | | A stray trailing space snuck in with one of the recent changes, making r290550 and r290573 effectively no-op. MFC after: 3 days Sponsored by: The FreeBSD Foundation
* Remove noatime from tmpfs(5) fstab(5) entry.gjb2015-11-091-1/+1
| | | | | | | Submitted by: Howard Su MFC after: 3 days X-MFC-With: r290550 Sponsored by: The FreeBSD Foundation
* Use tmpfs(5) instead of md(4) for '/tmp' mount.gjb2015-11-081-1/+1
| | | | | | | Submitted by: Nikolai Lifanov Differential Revision: D3506 MFC after: 3 days Sponsored by: The FreeBSD Foundation
* In vm_copy_base(), turn off SU+J on the resultant filesystem,gjb2015-09-291-1/+1
| | | | | | | | leaving only SU enabled. Discussed with: kib (a few weeks ago) MFC after: 3 days Sponsored by: The FreeBSD Foundation
* Disable blkif indirect segment I/Os in EC2 by default due to performancecperciva2015-07-301-0/+5
| | | | | | issues on some EC2 instance types. Users may want to experiment with removing this from loader.conf and measuring the performance impact on the EC2 instances they are using.
* Fix an out-of-order execution issue regarding pkg(8):gjb2015-07-211-1/+1
| | | | | | | | | | | | | - pkg(8) cannot be removed before subsequent reinvocations - The PKG_CACHEDIR cannot be cleaned after the repo*.sqlite has been removed - pkg(8) cannot be removed as a precursor to any of the other steps involved here MFC after: 3 days X-MFC-With: r285722 X-MFC-Before: 10.2-{BETA3,RC1} (whichever happens next) Sponsored by: The FreeBSD Foundation
* Add support for building VirtualBox Vagrant images.brd2015-07-203-8/+42
| | | | | | Abstract the build, package and upload to handle building either type. Approved by: re (gjb)
* Do not mount /var/log and /var/tmp as md(4)-backed devices.gjb2015-07-121-4/+0
| | | | | | Discussed with: ian MFC after: 3 days Sponsored by: The FreeBSD Foundation
* Revert r285018, r285019, r285076, r285078, r285082.gjb2015-07-041-8/+0
| | | | | | | | | | | | | The true cause of the missing UFS/MSDOSFS labels has been identified, and only affects stable/10 at the moment. An request for commit to stable/10 will be pending RE approval after this commit. MFC after: 1 day X-MFC-Note: never X-MFC-Never: r285018, r285019, r285076, r285078, r285082 Sponsored by: The FreeBSD Foundation
* Test for loader.rc existence before attempting to creategjb2015-07-031-2/+5
| | | | | | | | | | | the symlink from loader.rc.sample. Fix paths relative to the CHROOTDIR. MFC after: 3 days X-MFC-With: r285076, r285078 X-MFC-Before: 10.2-BETA1 Sponsored by: The FreeBSD Foundation
* Revert r285018 and r285019, which attempted to resolvegjb2015-07-031-12/+0
| | | | | | | | | | | | UFS/MSDOSFS label issues on FreeBSD/arm builds, however the real problem was addressed in r285076, which is due to two separate issues, unrelated to md(4) stale device existence. MFC after: 3 days X-MFC-With: r285076 X-MFC-Before: 10.2-BETA1 Sponsored by: The FreeBSD Foundation
* Fix the real problem with missing UFS/MSDOSFS labels on thegjb2015-07-031-0/+5
| | | | | | | | | | | | | | FreeBSD/arm builds. The problem stems from the loader.rc file not existing, as well as geom_label not being loaded at boot. For now, add the geom_label_load entry to loader.conf, and symlink loader.rc.sample to loader.rc, both of which allowed my BeagleBone Black to boot fine with a UFS label reference in fstab(5). MFC after: 3 days X-MFC-Before: 10.2-BETA1 Sponsored by: The FreeBSD Foundation
* Fix the path to the UFS/MSDOSFS filesystem labels, since theygjb2015-07-021-2/+2
| | | | | | | | | cannot possibly exist within the chroot(8) before the target filesystem actually exists. MFC after: 3 days X-MFC-With: r285018 Sponsored by: The FreeBSD Foundation
* Implement an evil workaround that prevents UFS/MSDOS labels from beinggjb2015-07-021-0/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | written to disk with newfs(8) and newfs_msdosfs(8). When iterating through snapshot builds in serial, it is possible for a build failure to leave stale md(4) devices behind, in some cases, they could have a UFS or MSDOS filesystem label assigned. If the md(4) is not destroyed (or not able to be destroyed, as has happened recently due to my own fault), the filesystem label that already exists can interfere with a new md(4) device that is targeted to have the same label. This behavior, although admittedly a logic error in the wrapper build scripts, has caused intermittent reports (in particular with the armv6 builds) of missing UFS/MSDOSFS labels, causing the image to fallback to the mountroot prompt. This appears to only happen when the backing md(4) device is destroyed before the calling umount(8) on the target mount, after which the UFS/MSDOSFS label persists. The workaround is this: If EVERYTHINGISFINE is set to non-empty value, check for an existing ufs/rootfs and msdosfs/MSDOSBOOT filesystem label in arm_create_disk(), and rm(1) them if they exist. The EVERYTHINGISFINE variable is chosen because it is used in exactly one other place - release/Makefile.mirrors - and there are big scary warnings at the top of that file as well that it should *not* be used under normal circumstances. This should not destroy a build machine that also uses '/dev/ufs/rootfs' as the UFS label, and I have verified in extensive local testing that the destroyed label is recreated when the md(4) is unmounted/mounted, but this really should not be enabled by anyone. Having said all that, I absolutely *do* plan MFC this to stable/10 for the 10.2-RELEASE cycle, as so far, I have only observed this behavior on stable/10, but this is a temporary solution until I can unravel all of the failure paths to properly trap them. MFC after: 3 days Sponsored by: The FreeBSD Foundation
* Add initial support for building Vagrant images for VMWare. Next steps will ↵brd2015-06-271-0/+81
| | | | | | be adding Virtualbox support and uploading to Hashicorp Atlas for others to consume. Approved by: re (gjb)
* Add initial support for automatically uploading GCE virtualgjb2015-06-271-47/+0
| | | | | | | | | | | | | | | | | | | | machine images to the Google Compute Engine platform. By default, gcutil/gsutil requires an Oauth2 login generated from a URL that must be opened in a browser, a verification code copied back to the terminal from which it was invoked, etc., etc., making it near impossible for automation. I've hacked together an evil solution to work around this, so unless GCE_LOGIN_SKIP is set to a non-empty value, this Makefile will not do anything useful. As a result of this commit, remove the gce-package.sh script that was never, nor will ever be, used. MFC after: 3 days X-MFC-Note: (hopefully) Sponsored by: The FreeBSD Foundation
* Ensure ASSUME_ALWAYS_YES is set when deleting pkg(8) from thegjb2015-06-241-1/+1
| | | | | | | | | DESTDIR, otherwise it can get stuck in ttyin. This means no 10-STABLE EC2 images this week. MFC after: 3 days Sponsored by: The FreeBSD Foundation
* Chase r284656 and r284658:gjb2015-06-211-14/+1
| | | | | | | | | | | | | | | | | | Remove the Azure-local vm_extra_create_disk(), since we no longer need qemu-img to convert the final VHD image to an Azure-compatible format. Although the waagent utility is installed from ports, create the symlink to /usr/sbin, pending investigation on where this is hard-coded, so it can be reported upstream. In the meantime, this is good enough. MFC after: 3 days X-MFC-Needs: r284269, r284270, r284271, r284655, r284656, r284657, r284658, r284659 X-MFC-Note: Required for 10.2-RELEASE, marcel@ has implicit approval for the required changes Sponsored by: The FreeBSD Foundation
* Fix path to waagent.gjb2015-06-191-2/+2
| | | | | MFC after: 3 days Sponsored by: The FreeBSD Foundation
* Work around a potential bug in pw(8) when '-m' is specified.gjb2015-06-051-1/+1
| | | | | | | | According to the manual page, '-m' should create the user home directory, however rigorous testing suggests it does not, and it is unclear if this is an implementation or expectation issue. Sponsored by: The FreeBSD Foundation
* Make sure /home exists within the DESTDIR before creating thegjb2015-06-041-0/+1
| | | | | | 'freebsd' user account. Sponsored by: The FreeBSD Foundation
* Use the new pw(8) '-R' option to create the users/groups.gjb2015-06-031-5/+4
| | | | | | MFC after: 1 week X-MFC-after: r283961 Sponsored by: The FreeBSD Foundation
* Pass the '-b' argument to pw(8) so the '/home' directory is createdgjb2015-06-021-1/+2
| | | | | | | in the correct place. MFC after: 3 days Sponsored by: The FreeBSD Foundation
* In arm_create_disk(), disable soft updates journaling.gjb2015-06-011-1/+1
| | | | | | | | | | Disabling soft updates journaling appears to resolve issues with kernel panics, and may also be generally bad to have enabled for SD cards. Requested by: ian MFC after: 3 days Sponsored by: The FreeBSD Foundation
* Re-enable arm_create_user(), and pass the '-V DESTDIR/etc' togjb2015-06-011-4/+7
| | | | | | | | | | pw(8) to set the correct /etc directory for the user/group files. Provided by: ian (thanks!) MFC after: 3 days X-MFC-with: r283894 Sponsored by: The FreeBSD Foundation
* Disable arm_create_user(). As-is, this does not create thegjb2015-06-011-1/+1
| | | | | | | | | | | | user in the userland for the target image, but creates the user in the build chroot. Before this is re-enabled, I want to figure out a clean way to do this without requiring the overhead of third-party utilities (such as qemu). MFC after: 3 days Sponsored by: The FreeBSD Foundation
* Fix virtual machine disk format creating by passing VMFORMATgjb2015-05-111-3/+4
| | | | | | | | | to mkimg(1) PR: 200068 Submitted by: Jeremy Norris MFC after: 3 days Sponsored by: The FreeBSD Foundation
*-. Merge ^/projects/release-arm-redux into ^/head.gjb2015-05-097-185/+137
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Of note: - This commit adds native FreeBSD/arm release build support without requiring out-of-tree utilities. - Part of this merge removes the WANDBOARD-{SOLO,DUAL,QUAD} kernel configuration files, for which the IMX6 kernel configuration file should be used instead. - The resulting images have a 'freebsd' user (password 'freebsd'), to allow ssh(1) access when console access is not available (VGA or serial). The default 'root' user password is set to 'root'. - The /etc/ttys file for arm images now enable both ttyv0 and ttyu0 by default. Help from: many (boot testing, feedback, etc.) Sponsored by: The FreeBSD Foundation
| * | Fix path to /boot/msdos for the target image.gjb2015-05-081-1/+1
| | | | | | | | | | | | Sponsored by: The FreeBSD Foundation
| * | Reorder / and /boot/msdos mount to avoid the following error:gjb2015-05-071-2/+2
| | | | | | | | | | | | | | | | | | | | | Mounting local file systems: mount: /boot/msdos: No such file or directory Sponsored by: The FreeBSD Foundation
| * | Create the /boot/msdos directory so the FAT partition is mountedgjb2015-05-071-0/+1
| | | | | | | | | | | | | | | | | | | | | properly. Noticed by: sbruno Sponsored by: The FreeBSD Foundation
| * | Enable the growfs rc(8) script.gjb2015-05-071-0/+1
| | | | | | | | | | | | Sponsored by: The FreeBSD Foundation
| * | In arm_create_disk(), chroot(8) to the build environmentgjb2015-05-071-29/+29
| | | | | | | | | | | | | | | | | | | | | | | | | | | is necessary. In arm_install_base(), chroot(8) when installing world and kernel. Fix paths for fstab(5) and rc.conf(5). Sponsored by: The FreeBSD Foundation
| * | In release.sh, create the /dev directory within the chrootgjb2015-05-071-2/+2
| |/ | | | | | | | | | | | | | | | | | | | | before attempting to mount(8) devfs. Also, create the .OBJDIR for the 'release' target, so files end up in the correct location. In tools/arm.subr, fix the target device when creating the gpart partition scheme. Sponsored by: The FreeBSD Foundation
| * Add tools/arm.subr to contain common subroutines used forgjb2015-05-061-0/+121
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | building arm images. This is similar to tools/vmimage.subr used for building virtual machine disk images. By default, only arm_create_disk() and arm_install_base() contain real functionality here, and arm_install_uboot() must be overridden in the arm/KERNEL.conf file. In release.sh, make create_arm_armv6_build_release() do something now. In arm/BEAGLEBONE.conf, set IMAGE_SIZE, PART_SCHEME, FAT_SIZE, FAT_TYPE, and MD_ARGS, as well as make arm_install_uboot() functional. Parts of this were taken from disecting a previous BEAGLEBONE image, and other parts obtained from Crochet sources. Sponsored by: The FreeBSD Foundation
| * Remove crochet configuration files and tools/arm/ directory.gjb2015-05-066-185/+0
|/ | | | Sponsored by: The FreeBSD Foundation
OpenPOWER on IntegriCloud