[Bug 222089] Official Google Cloud image configuration errors

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222089

            Bug ID: 222089
           Summary: Official Google Cloud image configuration errors
           Product: Base System
           Version: 11.1-RELEASE
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Many People
          Priority: ---
         Component: conf
          Assignee: freebsd-bugs at FreeBSD.org
          Reporter: vivek at khera.org

I installed a GCE image from the image as per the 11.1 release notes:

gcloud compute instances create fbsd-test1 --image freebsd-11-1-release-amd64
--image-project=freebsd-org-cloud-dev --zone "us-central1-c" --subnet default
--maintenance-policy MIGRATE --boot-disk-size 22

The resulting VM had some significant issues:

1. /etc/hosts does not have localhost. default resolv.conf setting does not let
the system resolve "localhost" either. It appears that the file is overwritten
rather than appended to.

2. /boot/loader.conf requests kern.timecounter.hardware=ACPI-safe, but choices
are ACPI-fast(900) TSC-low(1000). The system then chooses TSC-low timer, which
is running the clock fast about 2 minutes every 30 minutes. Using ACPI-fast the
clock remains very accurate with ntpd.

2.5. loader.conf is the wrong place to set timecounter. The setting there is
ignored. It appears that the right place is sysctl.conf.

3. /etc/ttys enables all the virtual consoles; these are inaccessible so should
just be off other than the serial console so that there are not a bunch of
getty processes running doing nothing.

4. google_accounts_manager takes a *long* time to exit, which holds up reboots
by over a minute. It also issues a warning about mismatched interpreter name.

Minor issues:

1. The last line of /etc/syslog.conf is a duplicate of a line further up. This
line seems appended specifically in the GCE image and is totally redundant.

2. The console setting in rc.conf does nothing. It is only valid to put this in
loader.conf.

Also, it would be great if the image did not require a 22GB disk. I think it
would fit very easily into 10GB as a minimum size. All of the above issues can
be fixed by editing the config files, but this minimum size requirement cannot
be.

-- 
You are receiving this mail because:
You are the assignee for the bug.